How to Build a Practical Run of Show
A practical run of show connects programme timing to owners, technical cues, speaker movement, dependencies and live decision-making.
Reviewed by Upshot Concept · Last updated 26 July 2026
What a run of show needs to do
A run of show is the operational sequence used to deliver the live event. It should tell the team what is happening, when it happens, who owns it and which cues or dependencies must be ready.
It is not the same as a guest agenda. The audience may see one line called “Opening session”; the production team may need separate actions for standby, room reset, walk-on music, microphone, screen content, lighting, speaker entrance and the first slide.
Build the timeline from fixed points
Start with immovable times such as venue access, doors open, broadcast windows, meal service, transport departures and venue close. Place programme sessions between them, then work backwards to define setup, checks and rehearsals.
Include realistic transition time. Moving a panel, resetting microphones or changing a room state takes time even when the audience does not see the work.
Use clear columns and owners
A useful structure includes scheduled time, running duration, programme action, stage action, audio, lighting, video or playback, speaker status and notes. The exact columns should match the event rather than a generic template.
Assign a responsible owner to each important action. “Presentation ready” is not a plan unless someone has received, checked and loaded the file and knows which version is approved.
Write cues that can be called
Use consistent names for videos, music, lighting looks and speakers. Separate a standby from the action itself. If several actions must happen together, decide whether they share one cue or require a deliberate sequence.
Avoid paragraphs inside cue cells. The show caller must be able to scan ahead while listening to communications and watching the room. Put background detail in a separate notes document.
Control revisions and live changes
Give the document a clear version and owner. Distribute an approved copy before rehearsal, then record revisions in one controlled source rather than multiple private versions.
On show day, state changes over communications and update the current sequence where practical. A run of show is not valuable because it never changes; it is valuable because it gives the team one shared reference when change happens.