Running a Dress Rehearsal With a Written Pre-Stream Checklist

Why the rehearsal is a run, not a glance

A dress rehearsal is the whole show played through at the real pace, with the real people, on the real equipment, using the same connection you will use on the day. It is not a quick look at the camera feeds while someone says that everything seems fine. The difference matters because most live problems appear only when several things happen together: a presenter walks in front of a lens while a scene changes and a microphone is unmuted.

When I teach this module I ask learners to treat the rehearsal as a short production of its own. It has a start time, a running order, a person responsible for each position and a written record at the end. That structure is what turns a vague feeling of readiness into something you can actually check.

The rest of this guide shows how to build the checklist, how to run the session in a sensible order and how to close it out, so the next rehearsal starts from what you learned.

Building the checklist before anyone arrives

Write the checklist at your desk, a day or two ahead, not in the venue while people wait. Divide it into four blocks that match how a stream actually fails: cameras, sound, scenes and platform settings. Under each block, list the specific items for your own setup, such as the number of cameras, the cable types, the microphones in use and the destination you are streaming to.

Phrase every line as something that can be confirmed with a yes or a no. Camera two shows a clean picture at the agreed resolution is checkable. Cameras look good is not. Add a space beside each line for initials and a time, so the page doubles as proof of what was verified and by whom.

Keep the list to one sheet if you can. A long document gets skimmed, and a skimmed checklist is only slightly better than none. If an item has never caught a problem in several rehearsals, consider whether it still earns its place.

• Cameras: power, signal, framing, labels
• Sound: levels, mutes, monitoring, echo
• Scenes: overlays, transitions, fallback scene
• Platform: ingest address, key, title, privacy setting

Running the session in a fixed order

Work through the sheet from the source toward the audience. Start with power and cables, then confirm each camera signal reaches the switcher, then bring in the audio, then test the scenes, and only then connect to the platform. Following the path of the signal means a fault found early is easy to place, because everything upstream of it has already been confirmed.

Once the sheet is complete, run the show itself without stopping. Have presenters speak in their real positions, bring graphics up and down on cue, and cut between cameras as you would live. Resist the urge to pause and fix small things mid-run. Note them, keep going and fix them afterward, because the point is to see how the whole sequence behaves under normal pressure.

If your platform allows a private or unlisted test broadcast, send the rehearsal through it and watch the result on a separate device, ideally one connected to a different network from the venue.

What to watch for during the run-through

Pay attention to the moments between the planned events. A camera that looks fine while idle can overheat or drop its signal after twenty minutes. A wireless microphone that works at the desk may break up when the presenter walks to the far side of the room. A scene that loads instantly with one overlay may stutter when a second is added.

Assign one person to watch only the outgoing stream, not the control screens. Their job is to say what the audience would see and hear: a late caption, a level that jumps, a dark corner of the frame. The operator is too close to the controls to notice these things reliably.

Give the run-through the same length as the real event, or at least a representative slice of it. A stream that holds steady for ten minutes tells you little about one that must hold for ninety. Results still depend on the venue connection, the platform and the agreed equipment, so test against those, not against ideal conditions.

• Signal that drops after warming up
• Microphones moving out of range
• Scene changes that lag under load
• Audio drifting behind the picture

Closing out: notes, fixes and a second pass

When the run ends, sit down for five minutes while memory is fresh. Go through the problems you jotted down, decide on the fix for each and write it on the sheet next to the original item. Put a name beside every fix so nothing is left as a general intention. If a change affects the signal path, such as a new cable or a different encoder setting, repeat the relevant check once to confirm it worked.

Keep the marked-up sheet. On the day of the event it becomes the shorter pre-stream list you walk through in the final half hour: the same items, now confirmed once, needing only a quick second look. Over several events your sheet will also show which items fail repeatedly, and those deserve a permanent fix rather than another reminder.

Store the file with the show settings, so whoever runs the next stream starts from what this one taught you, even if that person was not in the room.