A run of show is the one document your whole team runs the event from. The caterer checks it for load-in time, the AV tech checks it for the next cue, the emcee checks it to know who is walking on stage in four minutes. When it is built well, a run of show turns a room full of specialists into one coordinated machine. When it is built badly, or does not exist at all, every one of those people is guessing, and guessing is where events slip. A good template does not make you a better producer. It just hands you the column structure that has earned its place over hundreds of events, so you are not inventing the format at 11pm the night before doors open, and you start from a working shape instead of a blank page.
The columns that actually matter
Most templates fail in one of two directions: twenty columns nobody ever fills in, or four columns that leave out the exact thing that breaks the day. Here is the set that pulls its weight on almost every in-person event, from a ten-person board meeting to a three-day conference.
- Start time, in real clock time, not "after lunch, roughly"
- Duration in minutes, so the sheet can recalculate when a block moves
- Cue or segment title, written so a stranger could read it aloud
- Owner, the single name responsible for that block actually happening
- Cue type (stage, AV, catering, transition) so each department can scan just its own rows
- Notes, for the script line, the lighting state, or the thing that always slips
Time math, and one owner per row
Say your keynote is scheduled for 10:00 and runs 25 minutes. If badge pickup and coffee before it runs six minutes long, a hand-typed sheet leaves you two bad options: retype the next eleven rows under pressure, or let the sheet quietly go stale while you wing the rest of the day from memory. A sheet built on durations does neither. Change the one number that moved and every start time after it recalculates on its own. The run of show builder does this automatically, but even a spreadsheet with a running-total formula, next start equals previous start plus previous duration, beats hand-typed times that go stale the moment anything shifts.
"The team" is not an owner. Every row needs exactly one person accountable for it firing on time. If two names share a cue, decide now who calls it, because in the room there is no time to negotiate who was supposed to cue the video. Owners also turn the run of show into a rehearsal tool: you can walk each person through only the rows that belong to them, instead of making everyone sit through a read of the whole day.
Run of show needs differ by event type
The six core columns hold for almost any event, but what actually fills them changes a lot depending on what you are running.
A corporate event or conference lives and dies by the transitions between speakers. Build a hold cue before every stage entrance, a clear line for the Q&A cut-off, and a name against every microphone handoff, because the highest-risk minute of the day is the ninety seconds between one speaker leaving the stage and the next one starting to talk. Conference run of shows also carry more concurrent tracks, so color-code the sheet by room or split it entirely rather than forcing three simultaneous sessions into one linear list.
A wedding or milestone celebration run of show is built around a small number of unmovable moments, the processional, the toasts, the first dance, the cake cutting, and everything else flexes around them. Vendors matter more here than in almost any other event type: the photographer needs the golden-hour window, the DJ needs the exact order of announced moments, and the caterer needs the toast timing so plates land while people are seated, not mid-speech.
A fundraiser or gala run of show protects one thing above all else: the ask. Whatever moment does the emotional work, a testimony, a paddle raise, an impact reveal, gets built up to and out of deliberately, with everything before it setting the tone and everything after riding the momentum. That cue should never move for a program running behind; cut a reception mixer short before you touch the ask.
A community event or workshop run of show tends to be flatter and more forgiving, fewer hard stage cues, more parallel activities happening in different corners of a room or a park. Here the owner column does more work than the timing column, because the real risk is a station nobody is staffing, not a keynote running long. A summit or retreat spread across multiple days needs a run of show per day plus a one-page master schedule showing only the anchor times, meals, transport, and the sessions people cannot miss, so nobody has to flip through forty pages to find out when the bus leaves.
Rehearse off the sheet before you run it live
Treat the run of show as a rehearsal script, not just a day-of reference. Once owners are assigned, walk each person through only their rows, in order, out loud, before the room ever goes live. This is a tabletop read-through: no stage, no gear, just the sheet and the people responsible for it, saying out loud what happens and when. It surfaces the gaps a silent read never does: the cue with no owner, the transition nobody actually agreed on, the sound cue that assumes a microphone that was never booked. For anything with a live handoff, speaker to speaker, ceremony to reception, session to session, walk the physical path too, where the outgoing person goes, where the incoming person enters from, how many seconds that takes. A guide to writing a run of show is useful for building the sheet in the first place; the read-through is what turns the document into muscle memory.
Common formatting mistakes, and paper versus digital
A few formatting habits do more damage than any single scheduling error, because they quietly break the whole team's trust in the sheet.
- Merged cells and manual row heights that break the moment someone sorts or filters
- Color-coding with no legend anyone but the author can read
- One live file five people are editing at once, with no single version anyone can point to as current
- Vague windows like "afternoon" or "after lunch" instead of a real clock time
- A notes column doing triple duty as the script, the logistics log, and the place people argue about a change
The fix for most of these is the same: one owner of the document, one current version, and a format simple enough that a stranger could open it and understand what is happening in the next ten minutes. On the day itself, run digitally where you can, a live view that highlights the current cue and shows what's queued next keeps everyone reading the same page instead of asking. But print two paper copies anyway, one for whoever is calling the show at front of house, one for backstage cueing talent.
Buffers, and handling changes once the show is running
Buffers are not spare time, they are insurance you paid for on purpose. Place a small buffer, five to ten minutes is typical, after any block with real variance: a Q&A that could run short or long, a transition that involves moving a crowd, a meal service. When you are running early, hold to the clock rather than starting the next thing ahead of schedule, because guests time their return to breaks off the printed schedule, not off your instinct. When you are running late, take the time out of transitions and buffers first, never out of the headline content people showed up for.
When something does change mid-event, and something always does, name one person with the authority to edit the live sheet and announce changes over your comms channel the moment they happen, not after. Two people quietly editing two versions of the same cue sheet is how a transition gets fired twice, or not at all. If you're running day-of coordination with a live tool, the update should push to everyone's screen at once; if you're on paper, the show caller reads the change out loud and every owner marks their own copy before the next cue fires.
Start from a real example, then cut
Begin with a populated example for your event type rather than a blank grid. It is far faster to delete rows you do not need than to remember every transition from scratch under deadline pressure. Event70 seeds a sensible run of show per event type so you start with a working draft and shape it into yours, then switches into a live view with a real show clock once doors open. Start free, and your first event is on us.