Nine minutes before go-live on a 700-registrant product webinar, our keynote speaker’s laptop decided it was the perfect moment to install updates. Nobody panicked — because line 14 of the run of show said exactly who would cover, which backup deck they’d share from, and which producer would text the speaker a rejoin link. We started on time. Maybe five people in the audience ever suspected anything.
That document is the difference between a webinar that feels produced and one that feels improvised. Below is the webinar run of show template I’ve refined across a thousand-plus enterprise B2B webinars — the minute-by-minute rundown, the pre-show call agenda, the cue language, and the failure plans. Copy it, adapt it, and stop running live events from memory.
What a run of show is — and what it isn’t
A run of show is not an agenda. An agenda is what the audience sees: three bullet points on a title slide. A run of show is the backstage document — a minute-by-minute rundown that assigns every action to a named person with an exact timestamp. Who launches poll two, and at what minute. Who is watching the Q&A pane. What the moderator says, word for word, if the demo environment dies.
Mine is a single shared spreadsheet. One tab, frozen header row, sorted by time. Everyone on the crew has it open in a second monitor for the entire event. If a decision has to be made live, the answer should already be written down. The document thinks so the humans don’t have to.
The production schedule that feeds it
The run of show is the last artifact in a chain, not the first. Working backward from event day, here’s the webinar production schedule that makes the document trustworthy instead of aspirational:
- T-minus 3–4 weeks. Topic locked, registration page live, promotion running. Your reminder emails should already be drafted — the four-email reminder sequence is its own playbook.
- T-minus 1 week. Speaker briefing call. Slides at 90%, polls written, run of show drafted and shared. My guest speaker briefing doc covers what to send them.
- T-minus 2–3 days. Full tech check and dry run — real platform, real slides, real handoffs. I run it off the tech check and dry run checklist, and every issue found gets written into the run of show as a cue or a contingency.
- T-minus 1 day. Final version locked. No edits after this point except timestamps. A run of show that changes on event morning is worse than none, because half the crew is working from the old one.
The minute-by-minute template
Here is the actual rundown structure for a standard 45-minute B2B webinar with one host, one speaker, and one producer. Times are relative to go-live. Adapt the segment lengths, keep the columns.
| Time | Segment | Owner | Cues and notes |
|---|---|---|---|
| T-30 | Pre-show call | Producer | All crew on the platform. Audio, video, slides, screen share each tested live. Backup phone numbers confirmed. |
| T-10 | Waiting room opens | Producer | Holding slide up, music on if the platform supports it. Speaker goes quiet — no last-minute slide edits. |
| T-5 | Final go/no-go | Producer | Verbal confirmation from host and speaker. Recording armed. Q&A and chat panes staffed. |
| 0:00 | Cold open | Host | Scripted first 90 seconds — see below. Recording starts on the first word, not after housekeeping. |
| 0:02 | Housekeeping + poll 1 | Host | One sentence on Q&A logistics. Producer launches poll 1 on the phrase “let’s see who’s in the room.” |
| 0:05 | Speaker handoff | Host → Speaker | Host asks the setup question, speaker answers into the content. No “over to you” dead air. |
| 0:18 | Poll 2 + results riff | Producer / Speaker | Launch cue: “curious what this looks like for you.” Speaker reacts to results for 60–90 seconds. |
| 0:20 | Q&A checkpoint | Host | Host voices one strong question from the pane mid-stream. Signals the audience the pane is alive. |
| 0:35 | Wrap of content | Speaker | Hard stop. Anything uncovered moves to follow-up. Producer posts resource link in chat. |
| 0:36 | Live Q&A | Host | Host reads triaged questions — lanes below. Producer queues the next two in a side channel. |
| 0:44 | CTA + close | Host | One call to action, stated twice. End on time. The replay email is part of the follow-up playbook. |
Two rules make this table work. First, every row has exactly one owner — shared ownership is how polls launch twice or never. Second, cues are spoken phrases, not clock times. A producer listening for “let’s see who’s in the room” fires the poll at the right moment even when the show is running two minutes long, which it always is.
The T-30 pre-show call
Thirty minutes before go-live, everyone joins the actual event platform — not a separate call. This matters. Testing audio on Zoom and then presenting on a different platform tells you nothing. The pre-show agenda takes twelve minutes when nothing is wrong, which leaves eighteen for when something is.
- Audio and video, per person. Each presenter speaks for twenty seconds while the producer listens for levels, echo, and fan noise.
- Screen share, live. The speaker shares the real deck and advances three slides. Animations and embedded video are where shares die.
- Polls staged. Producer confirms every poll is loaded and in order. Misordered polls are the most common production error I see.
- Backchannel test. Crew confirms the side channel — a group text or Slack thread — with a test message. This is where “your mic is muted” lives during the show.
The first five minutes: cold open
Most webinars burn their highest-attention minutes on logo slides and “we’ll wait a few minutes for people to join.” Don’t wait. Across our programs, live attendance typically lands between 35–50% of registrations, and the people who showed up on time are your most engaged segment — rewarding them with dead air is backwards.
The cold open is 90 scripted seconds: a sharp claim or a number that earns the next 45 minutes, the speaker’s one-line credential, and the single promise of the session. Then two sentences of housekeeping, poll one, and handoff by minute five. Write those 90 seconds out word for word in the run of show. It’s the only part of the event I fully script, and it’s the part that most changes how the whole show feels.
Cue language: polls, Q&A lanes, handoffs
Q&A triage is the piece most run of show templates skip. During the event, the producer sorts every incoming question into one of three lanes, marked directly in the Q&A pane or the backchannel:
- Lane 1 — ask live. Broadly relevant, answerable in under two minutes. These get queued for the host, best question first — never “in the order received.”
- Lane 2 — answer in text. Narrow, technical, or account-specific. The producer or a subject-matter teammate answers in the pane during the show.
- Lane 3 — follow up after. Pricing, competitive, or anything deserving a real conversation. Logged with the asker’s name and routed to sales or the speaker post-event.
The host never reads the raw pane. They read the producer’s queue. That single change is most of what separates a smooth Q&A block from a rambling one — I go deeper on this in how to moderate a webinar panel, where triage gets harder with every added speaker.
When things break: backup plans
The last section of my template is a short table of failure modes with a named response. Not “we’ll figure it out” — a name and an action. Speaker drops: host bridges with the two backup discussion questions written in the doc while the producer texts the rejoin link. Slides freeze: producer shares the mirror copy of the deck from their own machine within 30 seconds. Platform-wide outage: producer emails registrants the backup link within five minutes, from a template drafted before the event.
You will use these rarely. In our programs, maybe one event in fifteen touches a contingency row. But the crew that knows the plan exists runs calmer for all fifteen — and calm is audible on a live stream.
Frequently asked questions
What is a run of show for a webinar?
A run of show is the internal minute-by-minute production document for a live event. It lists every segment with a timestamp, a single named owner, spoken cues for actions like poll launches, and contingency plans. The audience never sees it — it exists so the crew never has to improvise a decision live.
What is the difference between a run of show and an agenda?
An agenda is audience-facing and lists topics. A run of show is crew-facing and lists actions: who does what, at which minute, triggered by which cue. A 45-minute webinar might have a three-line agenda and a 25-row run of show.
How detailed should a webinar run of show be?
Detailed enough that a competent stand-in could run the event from the document alone. In practice that’s 20–30 rows for a single-speaker webinar: every segment, every poll, every handoff, and every failure plan. If a row has two owners or no cue, it isn’t finished.
Who should own the run of show?
The producer — the person not on camera. Hosts and speakers contribute, but the producer builds it, locks it the day before, and calls the show from it. On small teams where one person hosts and produces, the document matters even more, because it’s the only “second brain” in the room.
Does this template work for virtual events other than webinars?
Yes — the structure holds for panels, virtual summits, and hybrid sessions. Multiply the pre-show call length by the number of presenters, add a row per handoff, and keep the three-lane Q&A triage exactly as is. The columns don’t change; the row count does.
Want the fill-in-the-blank version of this template? It’s lesson-one material from our courses — see what’s coming, or get the free lessons by email as they ship.