Most run-of-show documents are works of fiction. They assume the AV will work first time, the caterers arrive on the dot, and no delegate ever stands at a locked door at 08:40 asking where registration is. A useful run-of-show plans for the version of the day that actually happens: the slightly late get-in, the speaker stuck on a delayed train, the registration desk that needs to absorb a sudden rush at 09:05. This is how we build one that holds up.
Start from doors, not from the agenda
The published agenda starts when the first session does. Your run-of-show should start well before that, at the get-in, and the most important hour on the whole document is the one before doors open. That hour is where everything either comes together or quietly falls apart.
Work backwards from the moment the first delegate arrives. If doors open at 09:00, the registration desk needs to be live and tested by 08:30, which means staff briefed by 08:15, which means crew on site by 08:00, which means the venue open by 07:45. Each of those is a hard dependency. Miss the venue opening and the whole chain moves. Planning backwards from the front door is the single habit that keeps the morning calm.
A worked timeline for a 600-capacity conference
Here is a realistic morning for a mid-sized conference. Adjust the clock to your event, but keep the shape and the dependencies.
| Time | What happens | Who owns it |
|---|---|---|
| 07:45 | Venue opens, power and wifi confirmed | Venue liaison |
| 08:00 | Crew arrive, kit unboxed and charged | Front-of-house lead |
| 08:15 | Door crew briefed, scanners tested on a dummy ticket | Registration lead |
| 08:30 | Registration desk live, kiosks switched on | Registration lead |
| 08:45 | AV check complete, holding slide up | Production |
| 09:00 | Doors open, first delegates checked in | Whole door crew |
| 09:25 | Doors quieten, walk-up lane stays open | Registration lead |
| 09:30 | Welcome from the stage | Host |
The detail that matters is the 08:15 line. Briefing the door crew and testing the scanners on a real pass, not just powering them on, is what stops the 09:00 surge turning into a queue. We have written separately about briefing your door crew before doors open, and it is the part teams skip most often when they are running behind.
Build in the slack you will need
A timeline with no gaps is a timeline that breaks at the first delay. Deliberate slack is not laziness; it is the buffer that absorbs the inevitable.
- Ten minutes either side of doors. If the venue opens late or a scanner refuses to pair, you want margin before the first delegate sees a problem.
- A floating crew member. One person with no fixed station who can plug whatever gap opens — a jammed printer, a confused delegate, a desk that suddenly has a queue.
- A walk-up lane that stays open. The pre-registered rush eases by 09:25, but walk-ups and latecomers keep arriving. Keep one lane running rather than tearing the desk down the moment the agenda starts.
A schedule with no slack is a schedule that has already decided to fail at the first surprise.
Name the owner for every line
The most common failure in a run-of-show is not a missing task. It is a task that everyone assumed someone else had. Every line should have exactly one name against it. Not a team, a person. "Registration" does not open a locked door; a named individual with a key does.
This matters most for the handover points. When the morning registration lead goes for a break, who holds the desk. When production finishes the AV check, who confirms it is done. Ambiguity at a handover is where things get dropped, which is why crew shift handovers that lose nobody deserve their own line on the document rather than an assumption.
Plan the failure modes, not just the happy path
A realistic run-of-show includes a short list of what to do when the obvious things go wrong. You will not predict every problem, but you can pre-decide the response to the common ones.
- Wifi drops at the door. Scanners fall back to validating offline against the downloaded list, and sync when the connection returns. Nobody waits.
- A delegate is not on the list. A named person owns the exceptions desk so the main lanes keep moving while the edge case is sorted.
- A speaker is late. The host has a five-minute fallback ready, and the running order can flex by one slot without anyone in the room noticing.
- The printer jams. Pre-printed badges for confirmed VIPs sit in a box as a backup, so the most sensitive arrivals never depend on a working printer.
Deciding these in advance, in writing, means the response on the day is a glance at a document rather than a panic.
Keep it on one page
A run-of-show nobody reads is decoration. The version that gets used is short enough to hold in one hand and clear enough to scan in five seconds. Times down the left, tasks in the middle, one name on the right. Everything else — contact numbers, supplier details, the full agenda — belongs in an appendix, not on the page your door lead is glancing at while the room fills.
The point of all this planning is not to control the day. It is to free you up for the part you cannot plan: the problem nobody saw coming. Get the routine onto paper, give every line an owner, and build in the slack, and the run-of-show stops being fiction and starts being the thing that keeps everyone calm when the schedule slips. Because it will slip. The good ones just slip without anyone in the room noticing.
