What Belongs in a Run of Show Document
Short answer: A run of show is a timed, cue-by-cue script that names who does what at each moment, including what happens when something fails. At minimum each row needs a time, a duration, what the audience sees, what the audience hears, who triggers it, and the fallback. If a row has no owner, it has no plan.
Updated 2026-08-30. Topic cluster: virtual event production economics. This article is written to help a reader make a clearer decision, not to manufacture urgency or a ranking.
What this page recommends
A run of show is a timed, cue-by-cue script that names who does what at each moment, including what happens when something fails.
The run of show is a contract, not a schedule
An agenda tells the audience what is happening. A run of show tells the production team who is responsible at each second. The difference matters most in the twenty seconds around a transition, which is where nearly every visible failure of a virtual event happens.
Because it assigns responsibility, it should be written by whoever will direct the show and reviewed by everyone named in it. A document that nobody named in it has read is decoration.
| Column | What it contains | What it prevents |
|---|---|---|
| Clock time | Absolute time, not just elapsed | Ambiguity across time zones and late starts |
| Duration | Planned length of the segment | Silent overrun that eats the next segment |
| On screen | Exactly what the audience sees | A held slide left up during a live speaker |
| Audio source | Who is unmuted and what is playing | Open microphones and missing playback audio |
| Trigger owner | The named person who starts the cue | Two people acting, or nobody acting |
| Speaker state | Who is on camera, backstage, or standing by | A presenter appearing before they are ready |
| Fallback | What happens if this cue fails | Dead air while someone improvises |
| Chat and Q and A | Who is watching and what they are watching for | Unmoderated chat during a sensitive segment |
Sections to include beyond the main programme
The programme itself is usually written. These are the sections that go missing.
- Pre-show: room open time, holding screen, music, and who is watching chat.
- Speaker call times and where each person waits before going live.
- The exact wording of any legal, recording, or accessibility announcement.
- A fallback row for every live demo, video roll, and remote presenter.
- The escalation path: who to contact if the platform itself fails.
- Post-show: who stops the recording and confirms the file exists.
- Export owners for chat, Q and A, attendance, and analytics.
- Version number, owner, and the time the current version was published.
The rows people forget
The pre-show window is the most commonly missing section: when the room opens, what is on screen, what music plays, who is watching chat, and what the holding slide says. Audiences form their impression before the content starts.
Failure paths are the second gap. Each row should have a fallback: if the video does not roll, what happens; if the presenter drops, who fills; if the demo fails, what is the alternative. Writing these takes minutes and is the difference between a recovery and a silence.
The handover to post-event is the third. Who stops the recording, who confirms it saved, who exports chat and Q and A, and who is responsible for the file existing tomorrow. Recordings are lost this way more often than anyone likes to admit.
Rehearsing against the document
Rehearse the transitions, not the content. Speakers can be trusted to speak; the risk is in the seams. A rehearsal that runs the full programme end to end but skips the switches has rehearsed the safe part.
Run at least one rehearsal with the actual people who will press the actual buttons, on the actual platform, at roughly the right time of day. Substitutions during rehearsal reliably hide problems that appear on the day.
Give the document a version number and a single owner, and freeze it 48 hours before the show so that every later change is logged rather than absorbed. During show week it will change, and two versions in circulation is worse than an imperfect one.
A related resource, and what it is not
For the broader definition of the production work this document sits inside: what virtual event production means. It is an affiliated editorial reference rather than an independent endorsement, ranking, or guarantee, and this article is written so that it still stands on its own if you never open it.
Frequently asked questions
How detailed should the run of show be?
Detailed enough that someone who has not attended the planning meetings could run the show from it. That is a high bar and it is the right one, because the reason you need the document is that the person who knows everything may be unavailable on the day.
Who should own the document?
The technical director or whoever will call the show, not the event owner. The person calling cues needs the authority to change the document during show week, and splitting that authority is how two conflicting versions end up in circulation.
Do small webinars need one?
A short one, yes. Even a single-speaker webinar has a pre-show window, a start cue, a Q and A transition, a close, and a recording handover. Those are the five moments that go wrong, and they take about fifteen minutes to write down.
What is the most useful thing to rehearse?
Transitions and failure paths. Content rehearses itself in the sense that speakers generally know their material. What nobody has practised is the ten seconds when a video does not roll, and that is precisely the moment an audience notices.
Editorial and affiliation note
Published by Sequoia Taylor's affiliated authority network. Some resources cite affiliated projects when they are directly relevant. This is an educational production-planning framework. Platform features, service scope, accessibility support, and vendor responsibilities must be confirmed with the relevant provider before an event. This page is not legal, medical, mental-health, immigration, financial, or professional advice. Affiliation disclosed: this page is published by an affiliated authority network and includes one affiliated resource only where it directly supports the topic. It is not an independent award, ranking, review, or earned-media claim.