A live stream run of show turns a loose idea into a timed production plan. Use this reusable template to map segments, scene changes, host and moderator cues, guest handoffs, technical checks, and backup actions before you go live on Twitch, YouTube Live, or another platform.
Overview
A run of show is the operational document for a live broadcast. It is more detailed than a content outline and more practical than a general streaming checklist. The document should tell everyone what happens, when it happens, who owns each action, and what to do if the planned sequence changes.
For a solo creator, the run of show may be a simple table beside the streaming computer. For a guest interview, panel, launch event, or recurring show, it becomes a shared handoff document for the host, producer, moderator, guest coordinator, and technical operator.
Build each rundown with the same core fields:
- Time: planned start time and expected duration.
- Segment: the purpose or on-air activity.
- Owner: the person responsible for moving the segment forward.
- Scene or asset cue: the OBS scene, graphic, video, lower third, link, or screen share required.
- Host cue: the phrase, question, or transition that begins the next action.
- Contingency: the fallback if a guest, asset, connection, or segment is unavailable.
Keep the document readable during a live broadcast. Use short instructions, consistent labels, and a separate notes area for links or technical details. For scene design, safe zones, alerts, and readable overlays, see the stream overlay design guide. If you are still configuring your software, pair this rundown with the OBS Studio setup guide.
Checklist by scenario
Reusable live stream run-of-show template
| Time | Segment | Scene or asset cue | Owner and action | Fallback |
|---|---|---|---|---|
| 00:00 | Pre-show holding | Starting screen, music, or countdown | Producer confirms stream health and chat readiness | Extend holding screen while resolving an issue |
| 00:05 | Opening | Camera scene; title or lower third | Host welcomes viewers and sets expectations | Use a shorter welcome if the start is delayed |
| 00:10 | Context or agenda | Agenda graphic, slide, or screen share | Host explains the format and key timing | Read the agenda verbally if the graphic fails |
| 00:15 | Main segment | Camera, guest, gameplay, demo, or presentation scene | Host leads; producer watches audio, video, and cues | Move to a prepared discussion or Q&A prompt |
| 00:45 | Audience interaction | Chat or Q&A scene | Moderator selects questions and flags urgent issues | Use a prewritten question set if chat is quiet |
| 00:55 | Closing | End card, call-to-action graphic, or camera scene | Host summarizes and states the next step | Deliver a brief close without the end card |
| 01:00 | End and review | End screen or holding scene | Producer confirms the broadcast has ended and saves notes | Keep the holding scene active until status is verified |
Adjust the times to fit your show. The value is not the exact schedule; it is the visible relationship between timing, cues, ownership, and recovery actions.
Solo creator checklist
- Write the opening line, segment transitions, and closing call to action.
- Place scene names in broadcast order so you can follow them without searching.
- Prepare one holding scene and one no-guest or no-screen-share version of the show.
- Keep a short list of safe filler topics, audience questions, or demonstrations.
- Mark any action that must happen off-camera, such as changing a source or checking a link.
Guest stream checklist
- Confirm the guest’s arrival time, contact method, display name, and pronunciation.
- Share the segment order, approximate answers or topics, and the signal for time warnings.
- Test the guest’s camera, microphone, headphones, and connection before the broadcast.
- Assign one person to communicate privately with the guest if the public chat becomes distracting.
- Prepare an opening segment that does not depend on the guest joining on time.
Panel, launch, or special-event checklist
- Give every participant a role: host, moderator, producer, speaker, or technical contact.
- List exact handoff phrases, presentation cues, video playback cues, and sponsor or resource mentions.
- Number the media assets and store them in one clearly labeled folder.
- Define who approves a schedule change and who communicates it to the team.
- Include extra time for transitions, questions, and late arrivals rather than filling every minute.
What to double-check
Before the broadcast
- Confirm the selected destination, visibility setting, title, description, category, thumbnail, and scheduled start time.
- Verify that the stream key or account connection is the intended one and is not exposed in the shared rundown.
- Check the correct canvas, output, and audio sources for the destination. A video aspect ratio and resolution guide can help when adapting a show for different platforms.
- Test microphone levels while speaking at normal volume, not only while silent.
- Preview every scene: camera, guest, screen share, browser, video playback, slides, chat, and end card.
- Open important links in advance and confirm that downloads, logins, notifications, and private information will not appear on screen.
- Review moderation settings, blocked terms, trusted moderators, chat rules, and the process for handling disruptive behavior. Platform controls may change, so confirm them in the current dashboard before important events.
During the broadcast
The producer or solo operator should track three things continuously: what the audience sees, what the audience hears, and what segment comes next. A scene that looks correct in the editor may still contain a muted source, hidden browser tab, stale graphic, or incorrect guest layout. Use concise cues such as “stand by guest,” “mic live,” “roll clip,” and “return camera.”
The moderator should filter questions, remove private information, flag technical problems, and tell the host when a question is suitable. The host should not need to monitor every chat message while presenting. Use a private communication channel for time warnings and urgent changes.
Common mistakes
- Planning only the content: A list of talking points does not specify scene changes, assets, owners, or recovery steps.
- Leaving no buffer: A schedule with every minute assigned becomes fragile when a guest talks longer or a file takes time to load.
- Using vague cues: “Show graphic” is less useful than “Switch to Agenda scene; return to Camera after host reads point three.”
- Relying on one person for every role: If possible, separate hosting, moderation, and technical monitoring. If you are solo, reduce on-screen complexity.
- Testing only before the show: Test the exact sequence you will use, including transitions, screen sharing, media playback, and returning to the camera.
- Forgetting the ending: Decide how you will close, where viewers should go next, and when the broadcast is actually finished. A relevant link or QR code can support that handoff; review the link-in-bio and QR code strategy before designing the call to action.
- Hiding the rundown from collaborators: Give the people responsible for cues and handoffs access before rehearsal, not when the stream is already live.
When to revisit
Review the run of show before every broadcast, even when the format is familiar. A recurring program can use a master template, but each episode should receive a dated copy with updated guests, links, assets, timings, and calls to action.
Revisit the template especially when you change streaming software, add a guest-production feature, switch destinations, introduce a new scene, replace a microphone or camera, or alter the moderation team. Platform dashboards and production tools can change after updates, so confirm current stream controls, guest access, scheduling options, chat tools, and recording behavior before a high-visibility event.
After each stream, record three notes: what ran late, what failed or confused the team, and what viewers asked for repeatedly. Convert those notes into a specific change in the next version. For example, add a two-minute guest buffer, rename an unclear scene, move an asset into the shared folder, or write a fallback question for a quiet chat.
Next action: copy the table above, replace the sample segments with your actual show, assign an owner to every cue, and rehearse the first five minutes plus one failure scenario. A short rehearsal will usually expose more production risk than another round of content polishing.