The run of show: how to write one your crew can actually call

Somewhere in your event folder is a document called the agenda. It says things like “9:00 — Welcome & Opening Remarks.” It is a fine document for attendees. It is nearly useless to the people running your show, because it answers when and what but never how: whose mic is live, what’s on the screen, what audio plays under the walk-up, who is standing where when the lights change. The document that answers those questions is the run of show, and whether your event has a real one is the single best predictor of whether the transitions (the moments audiences actually judge) feel deliberate or improvised.

You don’t have to be an AV professional to write a good first draft. You have to think in a different unit.

Think in cues, not time blocks

An agenda is a list of time blocks. A run of show is a list of state changes. Every time anything the audience sees or hears changes (a person, a slide, a light, a sound), that’s a cue, and it belongs on paper. “Opening remarks, 9:00–9:15” is one line on an agenda. As cues, it’s five:

1. Walk-in music fades out.
2. Lights shift from room-bright to stage look.
3. Title slide changes to speaker slide.
4. Speaker’s mic goes live as she enters from house left.
5. Confidence timer starts: 15 minutes.

Nobody on your team has to know how to execute any of these. But if they’re written down, the crew can execute all of them on your first read-through together. More importantly, everyone discovers now that nobody decided where the speaker enters from, instead of discovering it while she wanders the stage edge looking for stairs.

The columns that matter

Build it as a table: spreadsheet, not prose. Prose hides missing decisions; columns expose them. The set that covers almost every corporate event:

• Item number. Sequential, unambiguous. On headset, “we’re jumping to item 24” beats thirty seconds of describing where you are.
• Clock time and duration. Planned start and how long it runs. Durations are what let everyone recalculate when, not if, the schedule slips.
• Segment name. What a person would call it: “CEO welcome,” “Panel: next year’s market.”
• Who. Every person on stage or at a podium during the segment, by name, with entrance side if they’re entering.
• Audio. Which mics are live, what playback happens, walk-up music and when it dies.
• Video/screens. What’s on every screen, including the moments when the answer is “logo loop.” A screen with nothing planned is a screen showing a desktop.
• Lighting. Room state in plain words: “full bright for networking,” “stage warm, house half.”
• Notes. The human intelligence: “winner uses wheelchair — ramp side,” “this presenter runs long; hard cut at :45,” “board member in row 1 gets first Q&A question.”

If filling in a cell forces a decision nobody’s made, the document is doing its job. Every blank is a question you got to answer in a conference room instead of live.

Write the transitions, not just the segments

Segments almost never fail; seams fail. The awkward silence while a panel finds its chairs, the presenter talking to a dead mic while walking up, the video that starts before the speaker finishes her setup line. All seams. For each boundary between segments, decide three things:

What covers the movement? People take real time to cross a stage. Thirty to sixty seconds of walk music, a slide with the next segment’s title, or a moderator’s bridge line: something intentional owns that time.

What’s the trigger? The single most valuable convention you can steal from professional show calling: a standby and a go. The person calling the show says “standby music cue 4” ten seconds early, then “music cue 4 — go.” Two-word vocabulary, learnable in one rehearsal, and it eliminates the entire category of “I thought you meant now.”

Whose voice ends the old segment and starts the new one? If the answer is “nobody’s,” you’ve planned dead air.

Build in the buffers, and decide the cuts in advance

Every live program runs long. Not sometimes; every time, because speakers given fifteen minutes discover a sixteenth. A run of show that adds up to exactly your end time is a plan to end late. Two disciplines fix it:

Pad the seams, not the segments. Give transitions real durations (two minutes, not zero) and add a five-minute buffer per program hour, held by the person calling the show and spent invisibly, thirty seconds at a time.

Pre-decide the sacrifices. Mark, in the document, which segments flex if you’re ten minutes over at the halfway point: which video drops, which Q&A shortens, which award pair combines. Deciding this in advance takes one calm conversation. Deciding it live takes a whispered argument at side stage during your keynote.

Versions, names, and the one-owner rule

Three habits separate documents that help from documents that mislead.

• Version visibly — “v4 — FINAL — Oct 12, 3pm” on every page, because the most dangerous object backstage is last week’s printout.
• Name humans, not roles — “IT will run slides” is how slides don’t get run; “Marcus runs slides from FOH” is how they do.
• Give it one owner — one person holds the master, accepts changes, and reissues. Five people with edit access produce five run of shows.

Then rehearse from it, even once, even partially. A twenty-minute cue-to-cue the afternoon before, walking only the transitions, converts the document from theory into muscle memory and surfaces the last missing decisions while they’re still cheap. It’s the highest-value twenty minutes on your 30-day timeline.

Where your AV team comes in

Bring your provider the draft, not the final. A good production team will mark it up (where a video needs a longer pre-roll, where a mic swap needs fifteen more seconds, where two cues want to merge), and for full programs they’ll assign a dedicated show caller so your team watches the event instead of running it. That review is part of what you’re paying for in show production, and it works best on a document that already thinks in cues.

An agenda tells four hundred people when lunch is. A run of show is the reason the room never once wonders what’s supposed to happen next.