A run of show (ROS) is a minute-by-minute document that maps every element of your virtual event in the sequence it will occur, with exact timing, responsible parties, and technical actions assigned to each moment.
It is not a marketing agenda. It is not a speaker schedule. It is not a slide deck outline. It is the operational backbone that a professional virtual event production team uses to coordinate every person, platform action, and piece of content so your event runs flawlessly.
A good run of show transforms a group of individuals — producers, moderators, speakers, technicians, coordinators — into a synchronized team that can execute a complex live event with precision. Without one, even experienced teams end up improvising, and improvisation in live events rarely looks intentional.
A complete run of show is typically built in a shared spreadsheet or document with the following columns:
Two time columns: one showing the clock time (e.g., 10:00 AM ET) and one showing elapsed time from event start (e.g., +00:00). Both are necessary. The clock time keeps everyone synchronized across time zones and systems. The elapsed time helps producers quickly assess whether the event is running on schedule.
A clear, descriptive label for each element: "Welcome Remarks," "Keynote Q&A," "Poll #1," "Break — 5 minutes," "Panel Introduction," "Transition to Breakout Rooms."
The planned length of each segment. Be realistic — factor in time for transitions, technical transitions between speakers, and Q&A that runs longer than planned.
Who is running this moment? Possibilities include: Host/Moderator, Producer 1, Producer 2, Speaker Name, Technical Lead, Q&A Coordinator.
What does the production team need to do for this element? Examples:
What does the speaker need to know, hear, or receive to begin their segment? This column is what your producer types into the green room chat: "You're live in 30 seconds, Dr. Chen."
What happens if this segment runs long, the speaker is unavailable, or a technical issue prevents this element from executing as planned? Brief contingency notes here save critical seconds during live problem-solving.
During the live event, a producer tracks each row with a simple status: Not Started / In Progress / Complete. This gives everyone a real-time view of where the event stands without requiring verbal communication.
The run of show starts with the publicly communicated agenda — session titles, speaker names, and session lengths as advertised. This is your constraint framework. Everything else is built within it.
Every technical action is a segment that needs time in the run of show:
These elements are invisible to the audience but essential to the producer. They need explicit time allocations.
Every speaker transition is a potential friction point. For each handoff, note:
The biggest run-of-show mistake is building no buffer. Speakers run long. Technical transitions take longer than expected. Q&A produces more questions than planned.
For a 60-minute event, plan to fill 55 minutes of content. For a 90-minute event, plan 80–82 minutes. Knowing where to compress and what to cut if you run over requires planning in advance — not live improvisation.
For every high-risk segment, document the contingency:
Contingencies feel like over-preparation until the moment you need them, at which point they are invaluable.
Share a draft run of show at least five business days before the event. Schedule a producer-team review call where every owner walks through their responsibilities. Questions and conflicts surface much more easily in a review call than in a shared document.
Label every version clearly (v1.0, v1.1, v1.2) and include a "last updated" timestamp. In the final 48 hours before an event, a misread draft version can cause real problems. Ensure every team member is working from the same version — consider locking earlier versions from editing.
During the event, the run of show is an active working document. Producers update timing in real time, mark segments complete, and flag issues. After the event, the annotated run of show becomes the primary debriefing document — what ran on time, what ran over, what had to be skipped, and what needs to change next time.
A run of show is a production tool, not a client deliverable. Color coding, conditional formatting, and clear typography make it easier to read under pressure. Long paragraphs of explanatory text make it harder. Optimize for scannability during a live event, not comprehensiveness in a document review.
The rehearsal exists to validate the run of show. If something in rehearsal consistently doesn't work as written, fix the run of show — don't just try harder on event day.
A dedicated virtual event producer is the person who "calls" the show — meaning they are the authoritative voice saying "Next segment in 10 seconds," "Launching the poll now," and "Speaker is live."
Producers use the run of show in three ways:
The quality of the run of show directly determines the quality of the live production. Organizations that invest in professional virtual event production get a producer who builds, maintains, and calls a run of show that makes the event look effortless — even when dozens of decisions are happening behind the scenes.
Virtual Velocity builds detailed, production-ready run-of-show documents for every event we produce. It is one of the first documents we create and the last one we close out. Book a consultation to see how we approach run-of-show development for events like yours.