A webinar run of show is a shared production plan: it tells each person what happens, when it happens, who owns it and what cue moves the event forward. It is more operational than the attendee agenda, and it should include enough detail for the team to act without becoming a word-for-word script.
Build it around your actual format, platform and crew. A useful plan makes likely delays and technical snags easier to handle, but it cannot prevent them or guarantee that every segment will finish on time.
Run of show versus attendee agenda
An attendee agenda describes the experience you intend to offer: perhaps a welcome, a product demonstration, questions and a closing. It is written for people deciding whether to attend or following along during the event. A run of show is for the people producing that experience. It adds the sequence of actions behind each agenda item, including who introduces a speaker, which slide appears and what happens if a handoff is late.
Vimeo’s webinar production guide describes a run of show as a schedule, often kept in a spreadsheet, that serves as a shared planning and execution reference. The useful distinction is not the file type but the information it carries. A polished agenda can be a single line reading “Questions”; the production plan might show that the moderator collects questions, the speaker answers selected ones, the host gives a time cue, and the producer prepares the closing slide.
Keep both documents if your event needs both. The attendee version can stay brief and stable while the production plan carries internal notes, backup presenters and technical checks. Do not circulate confidential crew instructions or private contact details in an attendee agenda.
For a company broadcast, the same distinction matters whether the event is a one-off town hall or a series. This guide to live-streaming company events on YouTube can help with the wider broadcast setup; the run of show handles the event’s sequence and people.
Gather the event details and owners
Start with the event as promised to the audience. Write down its purpose, audience, format, scheduled start and intended finish, and the outcome you want people to leave with. Collect the announced agenda, presenter names and roles, the webinar platform, the audience interaction tools, and any approved links or follow-up action. These details constrain what belongs in the plan; they are not decoration.
Then ask each person involved what they need to do their part. A host may need speaker introductions and a clear closing cue. A moderator may need to know which question channel to watch and when to stop taking questions. A producer may need the exact slide deck, video file, screen-share order, microphone plan and permission to cut or extend a segment. A speaker needs to know their slot, time available, handoff and connection expectations. IFLA’s speaker and moderator checklist is an older institutional reference for agreeing roles and briefing speakers; use it for planning context, then confirm current platform-specific details with your own webinar provider.
Name an owner for each meaningful task, not merely a department. “Production” is harder to act on than “Mina opens the room and confirms the holding slide.” A row may also need a separate active-speaker field: the person accountable for the task is not always the person speaking. If one person has multiple roles, make that visible and consider whether those duties can actually be handled at the same moment.
Build the sequence before refining the minutes. Depending on the event, it could include opening the room, a holding activity, welcome and expectations, introductions, the main presentation, a demonstration, audience interaction, a close and a follow-up handoff. Add pre-show or post-show operations when they affect the crew or audience. A public agenda does not prescribe a universal length or order, so choose a sequence that fits this particular event rather than copying a template wholesale.
Choose a table structure
A spreadsheet is often practical because a crew can scan rows, edit fields and sort or filter the plan. A shared document can work for a simpler event or a team that already coordinates well in one. Dedicated event-production software may suit a larger operation with established workflows, but it adds another place to maintain information. Choose by how your team will use the plan under pressure, not by how elaborate the tool looks.
| Format | Useful when | Check before choosing |
|---|---|---|
| Shared spreadsheet | Rows need timings, owners and cues that several people can scan or revise | Can everyone find the current version, and are columns readable on the devices they will use? |
| Shared document | The plan is short and the team benefits from explanatory notes alongside the sequence | Can the operator locate the next action quickly without searching through prose? |
| Event-production software | Your team already uses it to coordinate schedules, people or technical tasks | Does it support the cue detail you need, and will every responsible person check it? |
Whichever form you choose, keep one clear working copy. Label it with the event name and revision status, make the owner of updates clear, and ensure the people executing the show can access it. If there is a printed or downloaded copy for use during a connection problem, decide who updates it when the plan changes. A stale backup can be more confusing than no backup.
Use one row for each meaningful segment or operational change. Rows should be short enough to scan, but do not combine actions that require different owners or cues. “Presentation” could be one row if the speaker runs it continuously; split it if there is a demo handoff, a video playback or a scheduled interaction that changes who is active.
Add timing, segment and presenter columns
Start with a stable order number and a short segment label. Add planned start and duration, then consider a planned end as a cross-check. The plan should make clear whether the time is a clock time or elapsed time from the event start; mixing the two creates avoidable ambiguity. Use the time zone relevant to the crew, especially when presenters join from different regions.
Here is a compact illustration. The labels show the kinds of detail to record, not a recommended webinar length or a fixed sequence. Replace every timing, role, asset and fallback with details confirmed by the event team.
| Order | Planned time | Duration | Segment/activity | Owner and active speaker | Cue/handoff | Production action and assets | Notes/fallback |
|---|---|---|---|---|---|---|---|
| 1 | Before doors | Set locally | Open room / holding activity | Producer; moderator | Producer confirms ready | Open room; check holding content and interaction settings | Use the team’s confirmed alternate access plan if the room is unavailable |
| 2 | Start | Set locally | Welcome and expectations | Host | Host begins after producer’s ready cue | Confirm opening slide and audio | Keep the opening concise if the event starts late |
| 3 | After welcome | Set locally | Speaker introduction and handoff | Host, then speaker | Host names speaker and yields | Bring up the correct speaker and presentation asset | Use the agreed backup if the presenter cannot connect |
| 4 | Main segment | Set locally | Presentation or demonstration | Speaker; producer supports | Give a time cue before the segment ends | Advance slides or launch the specified asset | Trim or switch to an available fallback if delayed |
| 5 | Interaction | Set locally | Q&A, poll or discussion | Moderator and speaker | Moderator opens and closes the segment | Monitor the selected interaction channel | Prioritise questions or shorten the segment to protect the close |
| 6 | Close | Set locally | Summary and next step | Host | Host gives final cue | Show final slide; moderator shares an approved link | Preserve time for the intended close |
You do not need every column in every event. A single-presenter session may not need a separate active-speaker field if the owner and speaker are the same person. A panel may need one. For a demonstration, include the screen-sharing operator and asset; for a discussion, identify who monitors audience contributions. Keep the columns that help the team act and remove those that merely make the sheet feel comprehensive.
Include cues, transitions and technical needs
A transition should answer three questions: what triggers it, who gives the cue and what changes next. “Move to Q&A” is not enough if the host, moderator and producer each assume someone else will start. Write something actionable, such as “Host closes final slide and names moderator; moderator opens selected questions; producer switches to discussion layout.” Use the team’s own language and spell out any abbreviations that might be unclear to a guest or stand-in operator.
Record production actions next to the relevant segment, not in a separate equipment list that no one can connect to the schedule. Note which slide or video is required, who shares it, whether a microphone is muted or handed over, and what the audience should see while that happens. If a video is played, name the file or a reliable identifier and specify whether it has audio. If a poll or question tool is used, say who opens it and who watches for responses.
Check the assets before show time and assign the check to a person. A producer can confirm the deck opens in the expected order; a moderator can confirm the intended interaction channel is ready; a speaker can check their microphone and connection. The goal is not to document every click. It is to make the next consequential action and its owner obvious. If part of the event is a pre-recorded segment, this guide to adding a pre-roll video to a YouTube live stream offers relevant context for thinking about when video enters the broadcast.
For a stream-based production, keep the webinar plan distinct from the continuous channel setup. If you use OBS and recorded material, the practical notes in how to use a playlist file to automate prerecorded YouTube streams concern playback automation; your run of show should still name who checks the asset and what the crew does if it does not play. Do not assume that a successful file test confirms the entire live handoff.
Document contingencies and recovery choices
A plan is more useful when it states what the team will do about a few plausible problems than when it tries to predict every possible failure. Focus on moments with audience impact: a presenter cannot join, a slide or video is unavailable, audience questions are sparse or abundant, or an earlier segment runs long. For each, name the decision-maker and one workable response. Keep the response consistent with the event’s purpose and the authority the team has agreed in advance.
For an overrun, decide what can be shortened without damaging the essential outcome. The team might reduce the number of audience questions, trim a secondary example or have the host move directly to the close. Do not silently take time from a segment whose content is essential or from the promised closing action. Mark which material is optional so that the producer is not asked to improvise a cut while the presenter is still speaking.
For a presenter who cannot connect, note whether a co-presenter can take over, the host should continue with a prepared introduction, or the team should pause and communicate through the agreed channel. For a missing asset, identify whether there is a verified alternate or whether the speaker can describe the point without it. A fallback should be something the team has checked, not an optimistic note such as “fix quickly”.
Use the same care with the access and technical recovery plan. Confirm the platform’s current guidance for host controls, access and any stream settings with its official help materials; the YouTube Help Centre is the appropriate starting point for YouTube-specific questions. A run of show can tell the crew who communicates and when to switch to an agreed alternative, but it cannot make a platform or connection problem disappear. Avoid promising that the event will proceed unchanged.
Keep contingency notes concise. If every row carries multiple hypothetical branches, the live document becomes difficult to scan. Put the few decisions that matter beside the affected segment, and keep more detailed contact or escalation information in a suitable crew-only location. Revisit those choices if the presenters, platform or format changes.
Share, rehearse and update the plan
Send the working copy to the people who need to execute it, and ask them to review the fields they own. A speaker should confirm their name, slot, asset and handoff. The moderator should verify interaction responsibilities. The producer should check cues, technical actions and fallback options. The host should confirm introductions and the closing. This review often surfaces a missing owner or a transition that looked obvious only to the person who wrote it.
Rehearse the actual plan with the actual assets. First walk the production crew through the sequence, cues and transitions; then practise with the participants when that is practical. Open the slide deck, use the video, perform the handoffs and test the interaction flow. A rehearsal that merely discusses the plan will not show whether a file is hard to find or a cue is too vague to recognise.
After the walkthrough, revise the document rather than expecting everyone to remember verbal corrections. Standardise segment labels and times, resolve conflicting versions, and tell the crew which copy is current. If you change a cue or move a speaker slot near show time, notify the people affected directly. The document is a working reference, not a polished artefact that becomes untouchable after approval.
For anyone carrying out both a scheduled broadcast and the event’s live production duties, reduce the number of jobs that depend on one person watching a computer continuously. StreamNeo may remove that specific source of distraction for a pre-recorded 24/7 YouTube channel: you upload the file once, provide your YouTube stream key, and the broadcast can continue with your computer switched off. It is YouTube-only, and it does not replace the webinar’s own host, presenter or production plan.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is a run of show the same as a webinar agenda?
No. An agenda communicates the intended experience to attendees; a run of show gives the production team timing, owners, cues and technical actions. You can derive both from the same event plan, but the crew document usually needs operational detail that does not belong in public copy.
What should each row include?
At minimum, make the order, planned time or duration, segment, owner or active speaker, cue, production action and relevant note legible. Add fields only when they help the people doing the work, such as an asset identifier or a separate moderator. The right structure depends on the format and team.
How much timing detail should I add?
Use enough to make the sequence and handoffs clear, and allow realistic room around transitions or audience-dependent segments. The exact duration depends on your content, speakers and format; no single template sets a suitable length for every webinar. Rehearsal is a useful way to find unrealistic assumptions.
Does a run of show prevent delays or technical problems?
No. It gives the team a shared reference and agreed choices for responding, which can reduce uncertainty when something changes. Rehearse with the actual assets, confirm platform guidance and keep expectations realistic: a plan cannot guarantee that the event will run without interruption.