A run of show is the minute-by-minute master timeline of an event: a table listing every moment, from doors opening to the final cue, with its exact time and duration, its location or stage, the person responsible, and the technical requirements attached, such as audio, video, lighting and microphone changes. It is the operational script the production team follows live, and it is what lets dozens of people act in sync without improvised decisions.
If the agenda is what you print for attendees, the run of show is what keeps the event from falling apart behind the curtain. Here is how to build one that works, with a template and a worked example you can adapt.
Run of show, agenda, and cue sheet: three documents, three jobs
These terms get mixed constantly, and the confusion causes real problems in production meetings. A quick disambiguation:
- Agenda (or program): the attendee-facing schedule. Session names, speakers, approximate times. Deliberately low detail.
- Run of show (ROS): the production-facing master timeline. Every state change in the event, timed to the minute, with owners and technical notes. This is the document this article covers.
- Cue sheet: a technical extract of the ROS for a specific department, such as the lighting or video operator, listing only their cues in order.
A useful test: if a document tells the audience what to expect, it is an agenda. If it tells the team what to do and when, it is a run of show.
The columns every run of show needs
Formats vary between production companies, but a working ROS answers six questions for every row. Build your template with these columns:
| Column | What it answers | Example entry |
|---|---|---|
| Time | When does it start? | 09:42 |
| Duration | How long does it run? | 3 min |
| Item | What is happening? | CEO walk-on and welcome |
| Location | Where? | Main stage |
| Owner | Who executes or calls it? | Show caller / stage manager |
| Technical notes | What does it need? | Handheld mic 2 live, walk-on music, lights to state 3, IMAG on screens |
Two optional columns earn their place at larger events: a cue number (so the show caller can say “standby cue 47” on the radio instead of describing things) and a script or content reference linking each row to the exact video file or speech version it uses.
A worked example: product launch, 400 guests
Here is a condensed extract from a realistic ROS for a corporate product launch. A full version for this event would run about 90 rows; this excerpt shows the level of granularity that makes the document useful:
| Time | Dur | Item | Location | Owner | Technical notes |
|---|---|---|---|---|---|
| 08:00 | 60 | Technical rehearsal complete, stage frozen | Main stage | Production lead | Full cue-to-cue done, no changes after this point |
| 09:00 | 30 | Doors open, accreditation active | Lobby | Access lead | QR validation on 4 lanes, welcome loop on screens, playlist 1 |
| 09:30 | 10 | Guests seated, 5-minute call to team | Main room | Stage manager | House music fades at 09:38 |
| 09:40 | 2 | Opening video | Main stage | Show caller | Video A rolls full screen, lights out, audio from server |
| 09:42 | 3 | CEO walk-on and welcome | Main stage | Show caller | Handheld 2 live, walk-on music, lights state 3 |
| 09:45 | 15 | Keynote: product reveal | Main stage | Show caller | Slides on confidence monitor, reveal cue at minute 12, pyro safety check confirmed |
| 10:00 | 20 | Live demo with product team | Main stage | Stage manager | Lav mics 3 and 4, demo table lit, backup device standing by |
| 10:20 | 25 | Networking break, catering service 1 | Foyer | Catering lead | Coffee stations open at 10:18, screens to sponsor loop |
Notice what makes this different from an agenda: the frozen-stage deadline, the mic assignments, the backup device, the two-minute early start for coffee. None of it is visible to guests, and all of it is why the event feels effortless.
How to build one, step by step
- Start from the agenda and work inward. Place the attendee-facing blocks first, then decompose each into its production moments: walk-ons, videos, mic changes, transitions.
- Add the invisible layers. Doors, catering starts, room turnovers, VIP movements, photo moments, streaming start and stop. If your event has live streaming or professional coverage, its cues belong in the same document, not in a parallel one.
- Assign one named owner per row. “Production team” is not an owner. A name with a radio channel is.
- Time it honestly. Speakers overrun. Build explicit buffers where you can absorb delay (breaks, transitions) and mark the rows that cannot move, such as a satellite window or a contracted talent slot.
- Circulate, then freeze. Every department reviews its rows. After the final production meeting, the document freezes and only the show caller issues changes.
- Print it anyway. Screens die and venues have dead zones. The show caller and stage managers carry paper.
The mistakes that break a run of show live
After enough events, the failure patterns repeat. The most common:
- The document nobody updates. Three versions circulating on event morning is worse than no document at all. One live master, one owner, version numbers on everything.
- Times copied from the agenda. An agenda says 09:40; a production needs to know the video is 1 minute 52 seconds and the walk-on is 20 seconds. Real durations or nothing.
- No plan for delay. A ROS that only works if everything runs on time is a wish, not a plan. Pre-decide what compresses first when you are 12 minutes behind.
- Technical needs described vaguely. “Mic for speaker” is a problem waiting on stage. Which mic, which number, live from when.
- Skipping the cue-to-cue rehearsal. The rehearsal is where the document meets reality and the errors surface at a fixable hour. This failure usually descends from a compressed timeline: if you want to know what realistic preparation windows look like by event type, see how long it takes to produce an event.
A broader catalogue of the planning errors that end up detonating on show day is in our guide to the most common event planning mistakes; almost every one of them leaves a fingerprint on the run of show.
Who runs it on the day
The document is only half the system. The other half is the show caller: the single person who follows the ROS live, calls every cue on the radio (“standby video B… roll video B”) and makes the real-time decisions when reality diverges from the plan. Speakers talk to the stage manager; departments listen to the show caller; nobody freelances. At large or multi-stage events, each stage gets its own caller working from the same master.
This discipline is what separates productions that absorb a 15-minute delay invisibly from those where the audience watches the seams tear.
Get the document, keep the calm
A good run of show is boring to read and priceless to have: it turns a hundred coordinated decisions into a sequence anyone on the team can follow, and it is the difference between managing an event and merely attending your own.
If you are producing an event and want a team that builds and calls the show professionally, from the master ROS to the accreditation lanes and the technical cues, tell us what you are planning and we will show you how we would run it.