What a Run of Show Is
A run of show is the minute-by-minute document that everyone working the event runs from. Not the guests. The crew.
It contains everything the guests should never see: who is holding which microphone, when the doors open, which lighting state each segment needs, who walks a speaker to the stage, what happens if the video does not play, and the exact wording of the transition between session three and the break.
The single most useful test of whether yours is finished: if you were unreachable on the day, could your second run the event from this document? If a row only makes sense because of something that lives in your head, it is not done.
Run of Show vs Agenda vs Timeline
These three words get used interchangeably and they are not the same document.
| Document | Who reads it | What it contains |
|---|---|---|
| Agenda | Guests | Session titles and times. Marketing, essentially. |
| Timeline | Planner and client | The sequence and durations of the day at a working level. |
| Run of show | Everyone working it | Every cue, owner, dependency, and transition. The production document. |
What Every Row Needs
Five things, without exception:
- Start time and duration. Both. A duration without a clock time means nobody can tell how far behind you are.
- What happens. In plain words, written so a stranger could follow it.
- Who owns it. A name, not a role. A row with no owner is a row that does not happen.
- Dependencies. Microphone, screen, lighting state, catering, a prop that must be in position.
- What to do if it fails. For anything with a single point of failure, such as a video, a remote speaker, or a live demo.
Rows that are engagement moments carry two more: the one message the moment exists to deliver, and a hard time limit. Moments without a limit are how a three minute activity becomes eleven minutes and eats the next session.
How to Build One, Step by Step
- 1
Get the end time and work backwards
Start from the hard out-time and the fixed points that cannot move, such as meal service, a venue curfew, or a speaker's flight. Everything else flexes around those.
- 2
Block the segments before the minutes
Lay out the large blocks first: arrival, opening, sessions, breaks, meals, close. Do not assign minute-level timings until the shape of the day is right.
- 3
Decide the energy shape
Sketch where the energy needs to be high, where it should rest, and where the peak belongs. The peak goes before the close, not at it, so there is room to land.
- 4
Place the moments at the turns
Add engagement moments wherever the energy line changes direction, not at evenly spaced intervals. Each one gets a message, an owner, and a hard time limit.
- 5
Write the transitions
Script the handoffs between every segment. These are the most commonly skipped rows and the most commonly lost minutes.
- 6
Assign an owner to every row
Every single row needs a name against it. A row with no owner is a row that does not happen.
- 7
Share it with everyone who touches the day
AV, catering, speakers, the client, and your own team. A run of show that only the planner can see is a personal document, not a production one.
Note the order. Most people start by filling in minutes and end up with a document that is precise and shapeless. Decide the shape of the day first, then let the minutes serve it.
The Transitions Everyone Forgets
Between every segment there is a gap. Eight gaps at three wasted minutes each is twenty four minutes of dead air, and dead air is where the energy of a room goes to die.
Transitions are also the cheapest thing on the whole document to fix, because they cost nothing but the writing.
- Into a speaker: one specific human detail, then the name. Never read the bio the audience is holding.
- Out of a speaker: name the one thing you took from it, then thank them. This does the retention work for the whole room.
- Into a break: give a clock time, not a duration. This one change will save you more minutes across a day than anything else here.
- Back from a break: ask what people talked about out there and take two answers. The hallway is usually the real conference.
Put the actual words in the document. "MC transition" is not a transition, it is a hope.
A Worked Example
The opening ninety minutes of a 140 person sales kickoff:
| Time | What happens | Owner | Needs |
|---|---|---|---|
| 8:15 | Doors, coffee, music at low volume. Emcee works the room and talks to five guests. | Emcee | House music, lights 100% |
| 8:55 | Two minute warning chime. Music up, then down. | AV | Chime cue |
| 9:00 | Welcome. Housekeeping: break at 10:30, out by 5, participation is coming. | Emcee | Handheld mic 1 |
| 9:05 | CEO opening remarks. Stays on stage at the end. | CEO | Lectern mic, deck live |
| 9:20 | MOMENT: Regional Trade. Everyone stands, finds someone from another region, trades their hardest closed deal. 3 min hard stop. Message: you are sitting with the people who get you to the number. | Emcee | Timer on screen, lights 100%, music under |
| 9:23 | Transition into keynote. Emcee asks CEO one question about the speaker. | Emcee | Mic 1 + 2 |
| 9:25 | Keynote. If video fails, go to backup slides on stick. | Speaker | Confidence monitor, backup on USB |
| 10:10 | Q&A. Two runners with handhelds. Emcee has three questions ready if the room is quiet. | Emcee | Handhelds 2 and 3 |
| 10:30 | Break. Announce as: we start again at 10:52. | Emcee | House lights, music up |
Note the 9:20 row. It is not "icebreaker". It has a message, an owner, a hard stop, and its production dependencies. That is what separates a moment that lands from one that eats eleven minutes and confuses everybody.
Common Mistakes
- No owner on a row. The single most reliable predictor that something will not happen.
- Durations without clock times. You cannot tell how far behind you are, so you find out too late.
- No slack. Every day runs long somewhere. Build in the buffer deliberately or it gets taken from your close, which is the part people remember.
- A PDF emailed round. It is stale the moment anything moves, and then two people are working from two different versions of the day.
- Transitions left blank. The cheapest minutes on the document to save, and the ones most often lost.
- Written only for you. If your AV lead cannot follow it without asking questions, it is a personal note, not a production document.
Frequently Asked Questions
What is a run of show?
A run of show is the minute-by-minute document that everyone working an event runs from on the day. It lists every segment in order with its start time, duration, what happens, who is responsible, and what AV or staging is needed. It is the operational document, as opposed to the agenda, which is the guest-facing summary.
What is the difference between a run of show and an agenda?
The agenda is what guests see: session titles and times. The run of show is what the crew sees, and it includes everything the guests never should: microphone handoffs, lighting cues, who walks where, when the doors open, who is standing by if a speaker does not appear, and the exact wording of transitions. One is marketing, the other is production.
What should be included in a run of show?
Every row needs a start time, a duration, a description of what happens, an owner by name, and any AV, staging, or catering dependency. Rows for engagement moments should also carry the message they exist to deliver and a hard time limit. Anything with no owner will not happen.
How detailed should a run of show be?
Detailed enough that someone who is not you could run the segment. The test is simple: if you were unreachable on the day, could your second run it from this document? If a row only makes sense because of something in your head, it is not finished.
Who should have access to the run of show?
Everyone who has a row in it, plus the client. AV, catering, speakers, and your own team should all be looking at the same live version. The most common cause of an event going wrong is two people working from two different versions of the schedule.
How far in advance should the run of show be finished?
The structure should be locked a week out so speakers and vendors can be briefed against it, but expect to make timing adjustments up to the day itself. That is exactly why it needs to be a live shared document rather than a PDF emailed around, which goes stale the moment anything moves.
Build it somewhere your team can actually see it
Pulling off a great event means tracking a hundred moving details, and without a system built for it they scatter across notes, spreadsheets, and a dozen apps. A run of show only does its job if everyone is looking at the same live version, which is exactly what a document emailed round cannot do.
Ripluo gives you one place for every event detail: timelines, checklists, and tasks, easy to find and ready to use. Build the outline, attach a moment to any point on the timeline, assign who owns each row, and share it with your team, your vendors, and your client.
That is what the run of show builder in Ripluo does. If you want the thinking behind the moments themselves, it comes from Shatter the Fourth Wall.