# Rhinohead Labs — Proposed Broadcast Delivery Record

TEMPLATE — NOT A COMPLETED CLIENT PROJECT. No technical test or outcome is claimed.

## 1. Agreement and ownership
Client / project:
Named delivery lead:
Workstation and destination platform:
Agreed scope and exclusions:
Schedule / review dates / revision allowance:
Acceptance reviewer and review method:
Equipment / subscription costs approved separately:

## 2. Decision and evidence record
Intended format / audience:
Starting equipment and constraints:
Source URL / title / date checked / narrow supported claim:
Workflow choice / reason / alternatives / unknowns:
Account permissions and rights checks:
Never record passwords, stream keys or private customer data here.

## 3. Configuration inventory
Component | Configuration reference | Owner | Status
Software/version | | |
Scenes / inputs | | |
Audio / routing | | |
Destination / permissions (no secrets) | | |
Recovery / local backup | | |

## 4. Rehearsal and acceptance
Check | Agreed method and threshold | Actual observation | Evidence reference | Pass/open | Owner
Picture / expected sources | | | | |
Audio / routing | | | | |
Scene transitions / screen privacy | | | | |
Connection and destination | | | | |
Operator startup / shutdown | | | | |
Recovery procedure | | | | |
Use thresholds agreed for this project's format. Record failed checks and missing evidence.

## 5. Handoff
Client can locate and open the agreed configuration:
Client can run the agreed startup / shutdown sequence:
Operating checklist and storage location:
Open issue / consequence / next action / owner / review date:
Artifact ownership / access / rights:
Post-handoff support boundary:
Reviewer decision / date / remaining conditions:
Completion means the agreed artifacts and checks are accepted. It does not establish audience growth or revenue.
