RHINOHEAD LABSKNOW MORE. BUILD BETTER.Discuss a project ↗

SERVICE DOCUMENT / ILLUSTRATIVE EXAMPLE

A handoff you
can actually inspect.

A proposed format for a broadcast launch record. It shows the shape of the work and the acceptance questions—not a delivered client project or a successful technical test.

Download the editable record ↓Back to the broadcast service ↗

ILLUSTRATIVE PROJECT / SINGLE-CAMERA TEACHING STREAM

01 / THE DECISION

Start with a bounded setup.

Proposed boundary
One existing workstation, one camera, one microphone and one destination platform, confirmed in the agreement.
Starting question
Can the operator prepare and run the agreed teaching format using a documented workflow?
Decision still needed
Platform, equipment suitability, required software, network constraints and who performs each check.
Separate purchases
Equipment and recurring services are itemized and approved separately. No purchases are implied by this sample.

02 / THE CONFIGURATION RECORD

Know what was set up.

The actual handoff records software/version, scenes and inputs, audio routing, configuration locations and an agreed recovery procedure. Account access stays with the client; passwords and stream keys do not belong in this document.

Evidence to attach: configuration inventory and permitted screenshots or files, with a named owner and version. No configuration is claimed completed in this example.

03 / THE REHEARSAL

Record observations, including failures.

CheckEvidence requiredSample status
Picture and soundReviewable recording against the format’s agreed checks.Not tested
Transitions and privacyRehearsal of scenes and screens with private information excluded.Not tested
Destination and connectionAgreed destination test, relevant observations and unresolved constraints.Not tested
Operator handoffClient walkthrough of startup, shutdown and recovery instructions.Not tested

The agreement must set methods and thresholds appropriate to the format. A completed checklist is not evidence of audience growth or income.

04 / THE OPERATING HANDOFF

Make the next action obvious.

  1. List the accepted files, versions, storage locations and ownership.
  2. Provide the startup/shutdown checklist and explain the recovery procedure.
  3. Record each open issue, its consequence, owner and next review.
  4. Have the agreed reviewer accept, request a scoped revision or leave a condition open.
  5. State the post-handoff support boundary.

The downloadable record has blank fields for the real project. It can be edited locally and attached to an agreed scope. It is not a substitute for that agreement.

Prepare a broadcast brief ↗Compare all services ↗