How to Build a Run of Show That Survives the Live Event
A practical method for sequencing event segments, calculating changeovers, assigning recovery buffer, and publishing a schedule the crew can actually call.
A useful run of show is an operational timeline, not a decorated agenda. It should let a producer answer three questions immediately: what is happening now, what must happen next, and what changes if the event is late.
Start with the fixed points
Mark the times that cannot move: doors, broadcast windows, meals, venue curfews, sponsor commitments, and the published finish. These anchors define where flexibility exists. Build audience-facing segments between them instead of adding durations first and discovering the finish later.
Calculate every segment and changeover
- Name each segment in language the crew will recognize.
- Assign the actual content duration.
- Add speaker walk-on, microphone changes, media resets, applause, and room turnover as explicit changeover time.
- Carry the end time forward to calculate the next start.
Keeping changeovers separate prevents speakers from treating operational time as available content. It also shows producers where a small overrun can be absorbed safely.
Add recovery capacity deliberately
Not every gap should be labelled “buffer.” Small changeovers support a specific handoff. Recovery buffer is held for uncertainty across the event. Put meaningful reserves before immovable anchors, and decide in advance who may release them.
Write cues that describe observable actions
“Start keynote” is ambiguous. “House lights to half; walk-on music; presenter enters stage left; start timer on first spoken word” gives the caller and timer operator the same trigger. The more expensive the mistake, the more concrete the cue should be.
Publish two views
The audience schedule should stay simple. The production version can include contacts, cues, sources, dependencies, fallback actions, and actual timings. Both must share the same approved segment names and start times.
Move from planning to live control
Use the free run-of-show calculator to verify start and end times. Then open the result in TimedFlow so the controller, presenter display, and remote viewers work from the same segment plan. During the show, record actual durations separately and use schedule drift—not instinct—to decide when recovery is necessary.
Frequently asked questions
What should a run of show include?
At minimum, include the segment name, owner or speaker, planned start, duration, planned end, transition time, and the cue that starts the segment. Technical notes and contingency actions belong beside the relevant segment.
Is a run of show the same as an event agenda?
No. An agenda tells attendees what happens. A run of show tells the production team how and when it happens, including cues, transitions, technical actions, and recovery time.
How often should the run of show be updated?
Update it whenever an approved duration, sequence, cue, or owner changes. During the event, preserve the baseline and record actual timing separately so the crew can see schedule drift.