The most professional events you have attended felt effortless because someone spent 10 hours building a document you never saw. The run-of-show is the master timing document that tells every person on the production team exactly what is happening, in what order, who owns each moment, and what the cue is to move to the next one. Without it, your day depends on memory and luck.
What a run-of-show contains
The run-of-show is a row-by-row breakdown of every event segment, from doors open to venue cleared. Each row answers five questions.
| Column | What it captures | Example |
|---|---|---|
| Time | Start time for this segment (clock time, not duration) | 9:15 AM |
| Duration | How long this segment runs in minutes | 20 min |
| Segment / cue | What is happening or what signal triggers the next action | Opening keynote begins. AV: play intro video |
| Owner | The named person responsible for executing or calling this segment | Sarah (stage manager) |
| Notes | Anything the owner needs to know: script cue, handoff, backup plan | If video fails, MC opens live. Backup slides on laptop 2. |
Build this document in a shared spreadsheet or in a tool your team actually uses. It must be accessible to every team member during the event, not just the event lead. A run-of-show that only the director can see is a single point of failure.
A sample run-of-show structure
Here is a simplified example for a half-day conference starting at 9:00 AM. Your event will have more rows and more specificity, but the structure is the same.
| Time | Duration | Segment | Owner | Notes |
|---|---|---|---|---|
| 7:30 AM | 90 min | Venue load-in: AV, signage, registration table | Operations lead | AV team has separate load-in checklist. Call when complete. |
| 8:30 AM | 30 min | Volunteer briefing and station assignments | Day-of lead | All volunteers in lobby. Review check-in flow and escalation process. |
| 9:00 AM | 45 min | Doors open, registration and networking | Registration lead | Music playing. Coffee service open. Name badges alpha-sorted. |
| 9:45 AM | 5 min | Attendees move to main room. Housekeeping slides loop. | Stage manager | AV cue: start slide deck loop. |
| 9:50 AM | 10 min | MC welcome and sponsor acknowledgment | MC (Jordan) | Script on lectern. Presenting sponsor named first. No ad libs on sponsor names. |
| 10:00 AM | 45 min | Opening keynote: Dr. Amara Osei | Stage manager | Clicker on podium. Slides loaded as Keynote file. Water on podium. |
| 10:45 AM | 15 min | Breakout transition and Q&A setup | Operations lead | Directional signs active. Mics moved to breakout rooms. |
| 11:00 AM | 60 min | Breakout sessions (3 concurrent tracks) | Track leads A, B, C | Each track lead has their own run-of-show subset. |
| 12:00 PM | 60 min | Lunch and exhibitor time | Operations lead | Catering opens. Sponsor tables staffed. |
| 1:00 PM | 30 min | Panel discussion | MC (Jordan) | Panelists briefed backstage at 12:45. 5 questions prepared, 2 backup. |
| 1:30 PM | 10 min | Closing remarks and next steps | Executive director | Announce next event date. Thank sponsors by name. |
| 1:40 PM | 20 min | Networking and venue clear | Day-of lead | Vendor teardown starts at 2:00 PM. All signage collected. |
Assigning owners to each block
The run-of-show is only as useful as the clarity of its ownership column. Vague entries like “team” or “staff” guarantee someone will wait for someone else while a cue is missed. Assign a specific name or role to every row.
- Stage manager calls all AV and lighting cues, keeps speakers on time, and is the last word on timing during the program.
- Day-of lead owns everything outside the main room: volunteers, logistics, vendor questions, and anything that would otherwise interrupt the stage manager.
- Registration lead owns the entry experience from doors open until the last attendee is checked in, then transitions to floating support.
- Track leads own their individual breakout rooms and have a condensed run-of-show for their sessions.
- MC or emcee owns transitions between segments on stage and is the audience-facing continuity voice.
The rehearsal and walkthrough
A run-of-show that has never been rehearsed is a hypothesis. The walkthrough converts it into a plan. Even a 90-minute technical rehearsal the day before will surface more problems than a week of planning meetings.
- Full technical rehearsal (day before) Walk every AV cue, every slide transition, every speaker entry and exit. Time the opening keynote from intro video to first word. Test the wireless mics in the actual room at the actual gain levels you will use.
- Speaker run-through (day before or day-of) Each speaker walks on stage, advances their slides, and confirms the clicker works and their notes are visible. This takes 10 minutes per speaker and prevents 80 percent of stage-day technical incidents.
- Volunteer briefing (day-of, at least 30 minutes before doors) Walk every volunteer through their station, their script for the most common attendee questions, and the escalation path. “If you do not know, here is who to radio” is not optional.
- Contingency walkthrough Call out the two or three most likely failure scenarios (main AV fails, a speaker is late, the Wi-Fi is down) and confirm who calls it and what the backup is. The run-of-show notes column should already have these. The walkthrough makes them real.
The condensed day-of version and comms plan
The full run-of-show is 50 rows and five columns. Nobody on the floor is reading a spreadsheet while managing a line of attendees. Create a condensed version for day-of use.
- One-page timeline. Time, segment name, and owner only. Print it. Laminate it if you have events often enough to justify it.
- Radio or text channel by role. Stage manager, day-of lead, and registration lead each have a dedicated channel or group thread. Cross-talk in a single group chat causes missed cues.
- Decision authority matrix. Write down in plain language who can make which calls on the day. Can the stage manager delay a session start by 5 minutes without approval? Who authorizes letting someone in without a ticket? Clear authority prevents paralysis.
Handling the inevitable slip
Every event slips. A speaker runs long. A registration line backs up. The AV setup takes 15 minutes longer than planned. The run-of-show does not prevent slippage. It makes recovery faster.
- Build recovery time into the schedule. A 5-minute transition between every major segment is not laziness. It is a buffer that absorbs minor slippage without cascading. Events that run back-to-back-to-back with no buffer fall apart when the first session runs 3 minutes long.
- Know your hard stops. Some times are immovable: venue must be cleared by 3:00 PM, catering is served at noon regardless of program timing, keynote speaker has a flight. Mark these in the run-of-show and the stage manager defends them above all else.
- Cut from the middle, not the end. If the program is running 20 minutes late, shorten a breakout or cut a Q&A segment in the middle of the program. Never cut the closing. Attendees remember how an event ends.
Key takeaways
- A run-of-show has five columns: time, duration, segment/cue, owner, and notes. Every row needs all five.
- Every segment needs a named owner, not “the team.”
- A technical rehearsal the day before surfaces more problems than a week of planning calls.
- Create a condensed one-page version for day-of use. The full spreadsheet is not floor-ready.
- Build 5-minute recovery buffers between major segments and know your hard stops.
Common questions
How detailed should the run-of-show be?
Detailed enough that someone who did not attend the planning meetings could execute their role from the document alone. If a row requires a verbal explanation to make sense, the notes column is not complete. For most events, that means 30 to 80 rows for a full-day program.
Who should have access to the run-of-show?
Every named owner in the document, plus any AV or production vendor with cues to execute. Sponsors and speakers do not need the full document. Speakers get a personal briefing sheet with their call time, session time, AV setup, and who to find backstage.
What is the difference between a run-of-show and a script?
A run-of-show is a timing and ownership document for the production team. A script is word-for-word content for a speaker or MC. They are companions, not substitutes. The run-of-show references the script at the relevant row but does not contain the full text.
How do we handle multi-track or multi-room events?
Build one master run-of-show for the full event and a subsidiary run-of-show for each track. The master tracks high-level transitions, shared logistics, and hard stops. Track leads own their subsidiary document and sync with the stage manager at defined moments.
