01Write the acceptance test
State what success looks like for coverage angles, height, delay zones and audience boundaries. Name the audience position, programme moment and output that must work. This gives the technical team something observable to test.
02Map the operating conditions
Working on coverage angles, height, delay zones and audience boundaries, record room shape, seating, stage, control position, access window, power, ambient light and background noise. Attach a floor plan or marked photograph to the brief.
03Draw the signal path
For coverage angles, height, delay zones and audience boundaries, trace each source through conversion, mixing or switching to every destination. Mark recording, stream and overflow feeds separately so shared dependencies are visible.
04Assign each cue
To keep coverage angles, height, delay zones and audience boundaries on track, place technical actions beside programme timings. Give every cue an owner, a trigger, a ready state and a recovery action.
05Test in programme order
A line check proves the connections. A cue rehearsal proves the event. Run the highest-risk transitions with the event files, selected devices and people involved.