How to Build a Run-of-Show Document: the Format Every Vendor Will Actually Read

I’ve been handed run-of-show documents at corporate events that were 14 pages of prose. One document, for a 250-person user conference in Santa Clara, had a paragraph for each program element, a section on “stakeholder expectations,” and a two-page appendix on the planner’s communication style. The AV lead, who had 20 minutes before doors opened, read the first paragraph and put it in his back pocket.

The run-of-show is not a planning document. It’s an operational tool. The people using it are managing cables, directing catering staff, cueing video, and handling speaker logistics simultaneously. They need to find their next action in under 10 seconds. That means one page per half-day of events, a table format, and four columns only.

The four-column format

Time	Owner	Action	Contingency
7:00am	AV Lead	Doors to service elevator open; AV load-in begins	If elevator delayed, notify [venue contact] at 617-555-0142
8:00am	Catering	Buffet breakfast staging complete; chafing dishes lit
8:30am	Planner (Tomas)	Walk room with AV and catering; confirm signage
9:00am	Venue	Doors open to attendees
9:05am	Registration Lead (Maria)	Registration table staffed; badge system active
9:45am	AV Lead	Cue walk-in music fade at volume 3
10:00am	Emcee	Welcome remarks begin; AV cues title slide	If speaker late, AV holds title slide; notify planner by 9:55am

That’s the format. Time is absolute (not “30 minutes before doors”), which removes interpretation. Owner is a name or role, not a company. Action is a single verb phrase. Contingency is a phone number or a specific alternative action.

Why most run-of-show documents fail

They use relative time. “T-minus 45 minutes” or “30 minutes before start” means different things depending on when the vendor reads the document. Use absolute clock times throughout, including load-in.

They combine multiple owners in one row. “AV and catering coordinate on room reset” tells neither party what they’re actually doing. Split it: row 1 = AV Lead, clear equipment from dining area; row 2 = Catering, reset tables for post-dinner program.

They don’t have a contingency column. The contingency column is the most important column in the document, and it’s the one that usually doesn’t exist. When the keynote speaker is late, the AV lead does not have time to call the planner, wait for an answer, and invent a solution. They need a pre-approved alternative on the document in front of them.

They include narrative explanation. “The CEO prefers to be introduced by the Regional VP rather than the emcee because of the history of their working relationship” is important context for the planner. It is not actionable for the AV operator. If context is necessary, put it in a separate speaker notes document and keep the ROS to action items only.

They run 8-12 pages. An AV lead running a full-day event cannot navigate a 12-page document while managing a four-person crew. Two pages max per day of programming, and only if the day is heavily sequenced.

What to include and what to leave out

Include:

• Every vendor action with a time stamp
• Every speaker transition (who introduces whom, who cues the slide)
• Every meal service window (when buffet opens, when it’s cleared)
• Every AV cue (music starts, lights change, video rolls)
• Break times with both start and end
• End-of-event load-out sequence
• Emergency contacts for each vendor category

Leave out:

• Program content or speaker talking points
• Background on why decisions were made
• Attendee communication instructions
• Budget information
• Anything that requires more than one sentence to describe

If you need to communicate something complex to a single vendor, put it in a separate vendor-specific brief and attach it. The ROS stays clean.

Building the contingency column

The contingency column requires you to make decisions in advance that most planners prefer to defer. That’s the point. If you haven’t decided what happens when the opening speaker runs 15 minutes long, you’ll make that decision under pressure on the day, and it will be a worse decision than the one you’d make now.

For each major program element, ask one question: what’s the 80% likely failure mode, and what’s the pre-approved response?

For a keynote speaker: late arrival, technical failure, or early finish. Pre-approved responses: hold title slide for up to 8 minutes before announcing a brief delay, have AV cue a 5-minute video fill if needed, or call the next speaker early.

For a catering service: slow setup, wrong headcount, dietary error. Pre-approved responses: name of the catering manager’s direct number, protocol for a delayed service (push program back 10 minutes with emcee announcement), process for routing a dietary error to the catering manager rather than through the planner.

For an AV failure: projector or screen goes down, mic fails, streaming cuts out. Pre-approved responses: backup presentation on USB at the AV console, second wireless mic at the back of the room, fallback recording if streaming fails.

Write these contingencies into the document. You won’t use most of them. But on the day when the projector bulb burns out 20 minutes before the general session, the AV lead who has a pre-approved contingency on paper will solve the problem without involving you.

Distribution

Send the final ROS to every vendor contact 5 days before the event. Send the day-of version (with any last-minute updates) 24 hours before the event. The day-of version should be in PDF format so it prints cleanly on any printer.

On event day, every vendor team lead should have a printed copy. Not a phone. Phones run out of battery, don’t zoom on key columns, and create a visual barrier between the vendor and the room they’re managing. Paper doesn’t need charging.

Your own copy gets annotated in real time: actual times next to planned times, notes on what ran over, contact names you used. That annotated copy becomes the source material for your post-event debrief.

For conference centers and convention centers, the venue will often have their own internal event order that runs in parallel with your ROS. Ask for a copy before the event and cross-reference it. Discrepancies between your ROS and the venue’s internal timeline are a common source of on-day confusion.

For standalone event venues without an internal operations team, your ROS is the only operational document on site. It has to be complete enough that a venue contact who just joined the team that week could follow it without calling you.

What’s your event start time and program length? I can tell you how many rows you’re looking at and which vendor columns need the most contingency planning.