How to Write an Event Run-of-Show That a New Volunteer Can Follow

A run-of-show is not a nicer agenda. An agenda tells attendees what they came for. A run-of-show tells the team who unlocks the room, who holds the spare badge stock, and who makes the call when the keynote’s car is stuck on the ring road. If you want to know how to write an event run-of-show that survives contact with a Tuesday morning, write it for the person who joined the team yesterday.

The test is simple. Could that person answer 90% of day-of questions from the document alone? If not, you still have a slide, not a plan.

What belongs on the page — and what does not

Every line needs four fields:

1. Clock time — local, 24-hour, including load-in and the hour after last session.
2. Place — hall, desk, loading dock. “Foyer” is not a place if you have two.
3. Action — a verb a stranger can do. “Check-in ready” is a mood. “Power on printers, load Hall A stock, scan a test pass” is an action.
4. Owner — one name. Two names means nobody.

Do not put strategy on this document. Goals live in the brief from how to plan a successful event. Risks live in a five-line register. The run-of-show is the delivery plan for one day.

Build it from the arrival peak backward

Most teams start at “doors 09:00” and invent the morning as they type. Start from the moment the queue is longest — usually the first 45 minutes — and walk backward.

• How many people arrive in that window? (Sixty percent of a conference is a safe guess if you have no history.)
• How many desks, scanners, and problem-lane staff does that number need?
• When must printers be tested against real passes, not a demo QR?
• When does the venue actually let you in — not the time on the sales tour?

Those four answers set the first page. The rest of the day is easier because sessions already have clocks. If you run parallel tracks, put room capacities and overflow rules on the same line as the start time. A capacity surprise is a run-of-show failure, not a programming surprise. We wrote about that class of failure in what actually breaks the check-in queue.

Rehearse it or it is fiction

A document that has never been walked is a hypothesis. In event week:

• Walk the venue with the run-of-show in hand. Move the printers if the cable does not reach. Change the line if the single entrance will fold in on itself.
• Scan real entry passes. Print real badges. A check-in system tested on event morning is not tested.
• Brief every station against the same pages. Volunteers get their extract and the name they escalate to. “Help at check-in” is not a role.

On the day, the core team works exceptions only. Everything routine was decided while you were still calm.

Keep a live command channel

The paper plan does not update itself when a session overruns. One channel — radio or a locked group chat — with every station represented, and one person who is allowed to change the clock. If three people “adjust” independently, you have three events.

Track attendance live. Hallway crowds are a lagging indicator; session check-in data is a leading one. Put the person watching the numbers next to the person who can hold a door.

Close the document after teardown

The last lines are teardown, the thank-you send window, and who owns the survey. An event that ends when the room is empty will repeat its mistakes with great confidence. Pair this page with the calendar version in our event planning checklist — the run-of-show is the last block of that list, written early enough to be rehearsed.

Frequently asked questions

What is an event run-of-show?

A minute-by-minute schedule of event day with a named owner for every item. If a volunteer who joined yesterday cannot answer 90% of questions from it, it is not finished.

How detailed should a run-of-show be?

Detailed enough that cues have a clock time, a place, and a name. “Morning check-in” is a wish. “07:45 — Mara opens Hall A desks; two scanners, one problem lane” is a line.

When should you write the run-of-show?

Draft at four weeks out. Lock it after the venue walkthrough in event week. Publish a freeze date for agenda and logos so print and the plan stop chasing each other.

Who needs a copy of the run-of-show?

Every station lead, AV, catering, and the volunteer brief. Speakers and partners get a short extract — call time, room, cue — not the whole document.