
What Is a Run of Show? A Practical Guide for Event Planners
A run of show is the working sequence the event team uses to execute a live program. It connects timing and content with the people and production cues needed to make each moment happen. For example, it can identify when a speaker enters, which video plays and who calls the transition.
A useful run of show helps different departments follow the same plan. It should be detailed enough to guide the team without burying important actions in paragraphs of background information.
Run of show versus agenda and production schedule
An audience agenda tells attendees what to expect: a welcome, a keynote, a panel and a break. A run of show describes how the team delivers those moments, including the handoffs that attendees may never notice.
A production schedule typically covers a broader operational timeline, such as load-in, setup, rehearsals, meals, the show and load-out. Terminology varies among teams, and some documents combine these functions. Agree on the purpose and level of detail rather than assuming everyone uses the same labels.
What should a run of show include?
Start with the sequence of program items, planned start times and durations. Then identify the speaker or participant, the person responsible for the action and the relevant audio, video, lighting or stage instructions. Use clear file names or asset references so “play video” cannot mean several different things.
Give important cues recognizable labels. Include the trigger as well as the action: a specific spoken phrase, the end of a video or the show caller’s instruction may be more useful than a clock time alone. A speaker finishing late should not cause the next video to start over their closing remarks.
Keep contact details and lengthy scripts in supporting materials when that makes the live document easier to scan. The team should be able to find the next action quickly.
A simple run of show example
The example below is illustrative, not an ASP project record. Clock times are planned targets; live actions follow the agreed cue.
| Target / length | Program item | Trigger | Action / owner |
| 9:00 / 2 min | Welcome | Caller gives GO | Audio: fade walk-in music;
stage: host enters |
| 9:02 / 1 min | Opening video | Host finishes introduction;
caller gives GO |
Video: play Opening v3;
audio: take playback |
| 9:03 / 15 min | Keynote | Video ends;
caller gives GO |
Stage: release speaker;
video: keynote title slide |
In a larger show, audio, video and lighting may each have their own columns or cue references. The right format is the one the operators and show caller can use consistently during the event.
Build the document with the production team
Begin with the program order, then review each transition with the people executing it. How does the next presenter reach the stage? Who confirms the microphone is ready? What appears on screen while panelists take their seats? Those questions often reveal missing time between agenda items.
Assign one person to maintain the master version. Add a clear revision date or version number, and make sure the team knows which copy is current. A last-minute change needs to reach everyone affected, including the person briefing speakers backstage.
Rehearse transitions and plan for changes
Walk through entrances, playback starts, microphone handoffs and session endings. Use rehearsal to clarify vague cues and test whether transitions have enough time. Update the master document afterward instead of leaving corrections in separate personal notes.
Agree on who can approve a cut or change when the program runs long. Identify any fixed commitments, such as a remote guest’s availability, so the team understands where flexibility exists. The run of show supports those decisions; it does not replace the person coordinating the live program.
The goal is a shared, usable plan that helps people act together when timing changes.
Preparing a program with several speakers or production cues? Contact the Advanced Staging Productions team to discuss the coordination your live event needs.











