Quick answer: An event livestream run of show is the live production map that connects the program in the room to what remote viewers see and hear. It should give every event beat an exact time, duration, owner, stage action, camera or screen output, audio source, graphic or playback asset, accessibility cue, permission boundary and fallback. The best version is built jointly by the organizer and production lead, tested in rehearsal and controlled by one person on show day.
This guide is for conference teams, corporations, public agencies, associations, festivals, tourism organizations, schools, universities and cultural organizations planning livestreamed or hybrid events in Canada.
What is an event livestream run of show?
A run of show is a timed operating document for the people delivering a live event. It tells the team what happens, when it happens, what the audience should experience and who calls the next action.
It is not the same as an attendee agenda. An agenda might say “9:00 a.m. keynote.” A production run of show also states when the holding screen changes, which microphone is live, where the presenter enters, which camera opens, when captions begin, what lower-third appears, who watches stream health, whether the segment may remain in the replay and what happens if the slides or remote connection fail.
A speaker script is also different. The script contains words. The run of show contains decisions and cues. They should point to each other without becoming one enormous document that nobody can scan under pressure.
The 10 fields every livestream cue sheet needs
| Field | What to record | Why it matters |
|---|---|---|
| Time and duration | Planned start, end and running time | Keeps the room, stream and access services aligned |
| Event beat | The session, transition, break or announcement | Names the moment everyone is supporting |
| Stage action | Entrance, exit, seating, microphone handoff or reset | Connects backstage movement to the broadcast |
| Stream output | Camera, slide, video, holding screen or remote feed | Defines what online viewers should see |
| Audio | Microphone, playback, room sound or interpretation feed | Prevents a good room experience from becoming a silent stream |
| Graphics and assets | Lower-third, title, file name, slide deck or link | Gives operators the approved asset and version |
| Accessibility | Caption, interpreter, description, pace or participation cue | Makes access part of execution rather than an afterthought |
| Permissions | Live, replay, clip, archive or camera restriction | Translates approvals into actions the crew can follow |
| Cue and owner | Who calls the action and who performs it | Removes ambiguity at the moment of change |
| Fallback | Approved alternate state and decision authority | Gives the team a useful response when the plan changes |
Not every crew member needs every column. Keep one master file, then create filtered operator views for audio, graphics, stage, captions, interpretation and stream control. The times, segment names and version number must stay identical across all views.
Build the run of show in seven passes
1. Lock the audience promise and broadcast boundaries
Before filling rows, write a short header that answers:
- Who is attending in person and online?
- Is the stream public, private, registration-only or limited to members?
- Which rooms, stages or sessions are included?
- Can remote viewers ask questions, vote, use chat or access interpreted channels?
- What will remain after the event: full replay, edited replay, clips, transcript, archive master or nothing?
- Who can approve a change to the broadcast?
These choices determine what belongs in the file. They also help a production partner quote the work accurately. Use the conference livestream checklist when several rooms, presenters or audience paths need to be scoped before the cue sheet is built.
2. Build the time architecture before the fine cues
Start with immovable anchors: doors, broadcast start, contractual speaker times, breaks, venue curfew and the promised end time. Add the invisible broadcast blocks around them:
- crew call and system checks;
- presenter microphone and slide checks;
- captioner or interpreter connection;
- private test transmission;
- viewer holding screen and pre-show audio;
- live opening and closing;
- post-show slate;
- recording checks and file handoff.
Then add realistic transitions. A panel does not begin the instant a keynote ends. People leave and enter, microphones move, chairs reset, names change, interpreters switch and online viewers need a coherent picture while it happens.
For the broader schedule from first scope to replay, follow the event livestream planning timeline.
3. Map what the room and remote audience experience
For every row, ask two questions: what happens in the venue, and what reaches the remote viewer? Those answers are often different.
An audience question may sound clear in the room but disappear online if it never reaches the broadcast mix. A presenter may point to a chart that remote viewers cannot read. A break may feel natural on site but look like a frozen or abandoned stream without a holding screen and return time.
Trace every important sight and sound through the full path. The Government of Canada’s accessible virtual-event guidance recommends assigning roles, preparing scripts, testing equipment and access services, conducting a dry run when needed and correcting accessibility problems during the event. Put those actions into timed rows with named owners.
4. Turn accessibility requirements into live cues
“Captions provided” is a scope statement, not a show-day plan. The cue sheet should say when the caption feed connects, who confirms it, how speaker names and specialized terms were supplied, who monitors accuracy, what backup applies and who corrects the replay.
Use separate cues where needed for:
- live captions and captioner audio;
- sign-language interpreter framing and lighting;
- spoken-language interpretation channels;
- verbal description of meaningful visual information;
- accessible presentation files and links;
- remote questions and a private help route;
- breaks and time for people to process or respond.
The W3C media accessibility planning guide distinguishes captions, transcripts and description of visual information. They are different deliverables. The accessible event livestream checklist helps teams define the right combination before rehearsal.
A signed agreement is not useful to a camera operator if the approved boundary never reaches the show file. Mark each restricted segment with an unambiguous instruction such as “room only,” “audio only,” “no audience camera,” “live only,” “remove from replay” or “approved for clips.” Name the person authorized to change that instruction.
For an Indigenous cultural gathering or a program that includes community-specific knowledge, language or protocols, the host community and authorized rights holders determine what may be shown, heard, retained and reused. The production company should not invent those boundaries. The run of show should carry the approved instruction and a cue that the crew can execute.
Use the event livestream permissions checklist to separate attendance, live broadcast, replay, clip, partner-distribution and archive decisions.
6. Design an approved fallback for important transitions
“Troubleshoot” is not a fallback. A useful fallback is a viewer-ready state with an owner and a trigger.
| Risk | Possible approved fallback | Decision owner |
|---|---|---|
| Presenter is late | Extend the holding screen, advance a break or move to a confirmed segment | Event lead or show caller |
| Slides fail | Stay on presenter camera while the speaker continues without slides | Show caller |
| Remote guest drops | Move to moderator, prepared question or backup recording | Program lead |
| Restricted segment begins early | Cut to approved slate and mute the restricted audio path | Permissions lead and show caller |
| Primary stream path fails | Switch to the tested backup or publish the approved viewer message | Stream lead |
| Caption feed fails | Activate the agreed backup and have support notify affected viewers | Accessibility lead |
YouTube’s current live streaming guidance recommends checking the preview, testing encoder failover where used, verifying local archive files, testing viewer access and continuously monitoring audio and video quality. Those checks belong in the pre-show and live portions of the run of show. Venue connectivity should also be verified with the event livestream internet requirements checklist.
7. Assign one controller and make changes visible
One person should control the master file. Put the event name, date, timezone, file owner, version number and last-updated time at the top. During the final change window:
- lock the column structure;
- mark every revision visibly;
- announce changes through the agreed production channel;
- replace old printed copies;
- confirm that operator views match the master;
- keep a simple decision and incident log.
Version discipline sounds administrative until a presenter order changes and graphics, microphones, captions and cameras each follow a different document.
A practical sample: opening a livestreamed keynote
| Time | Event beat | Stream and audio | Access and permission | Cue and fallback |
|---|---|---|---|---|
| 8:55 | Five-minute pre-show | Approved holding screen; pre-show audio at confirmed level | Captions connected and checked; viewer help contact visible | Stream lead confirms green status; remain on slate if room is not ready |
| 8:59 | Stand by opening | Camera 1 framed; host microphone muted until cue; opening graphic ready | Interpreter framed if required; presenter name verified | Show caller calls one-minute warning |
| 9:00 | Go live | Fade from slate to host; open host microphone; lower-third on cue | Recording notice and access instructions delivered | If camera is not ready, hold on approved title and use host voice |
| 9:03 | Keynote introduction | Camera changes follow the host; keynote microphone checked in preview | Approved name, Nation or community wording used as supplied | Stage manager confirms presenter ready |
| 9:05 | Keynote begins | Keynote microphone live; slides or camera according to content | Permission state confirmed for live and replay | If slides fail, stay on presenter and continue |
This is a structure, not a universal script. Adapt the detail to the program, venue, audience, platform, access plan and approvals.
Rehearse decisions, not just equipment
A useful rehearsal runs the difficult moments at real pace. Test the actual opening, a presenter handoff, a video, a remote guest, captions or interpretation, an audience question, a restricted segment, a break, a failure response and the closing.
During rehearsal, have someone watch on an ordinary remote device and report what they can see, hear and use. YouTube advises testing with audio and movement similar to the program and monitoring stream health during the event. A control-room preview alone does not confirm the viewer journey.
Record the result of each test in the cue sheet or issue log: pass, change required, owner and deadline. Resolve major gaps before the final file is issued.
What to send a livestream vendor for a quote
A draft run of show does not need every camera cut. It does need enough information to reveal the production problem. Send:
- event date, city, venue and timezone;
- load-in, rehearsal, broadcast and teardown windows;
- rooms, stages and sessions to cover;
- audience access and participation model;
- speaker, panel, performance, playback and remote-guest counts;
- caption, interpretation and accessibility requirements;
- permission, recording, replay and archive boundaries;
- platform ownership and viewer security needs;
- available venue audio, internet and power information;
- approved fallback expectations;
- budget range or procurement method and decision deadline.
This brief allows vendors to compare the same scope. It also helps organizers see which decisions are still open before they become costly show-week changes. For budget planning, use the event livestream cost guide.
Frequently asked questions
Who creates the event livestream run of show?
The organizer owns program decisions, approvals and audience commitments. The production lead translates them into technical and show cues. Accessibility, permissions, venue, stage, audio and platform leads should review the parts they own. One named controller maintains the master file.
When should a livestream run of show be finished?
Create the first production version once the program structure and broadcast scope are known. Refine it through technical planning and rehearsal, then set a final change deadline. Complex multi-room, multilingual or culturally sensitive events need earlier decisions than a simple single-room program.
What is the difference between a run of show and a cue sheet?
Teams often use the terms interchangeably. A run of show usually describes the complete timed event flow. A cue sheet may be a filtered operational view for a specific department such as audio, graphics, stage or streaming. Both should use the same times, segment names and version.
Should the public agenda be copied into the run of show?
Use the public agenda as a starting point, but add setup, transitions, checks, stream states, access services, permission cues, owner assignments and fallbacks. Do not expose private contacts, stream keys or internal security details in the attendee version.
How detailed should a livestream run of show be?
It should be detailed enough that each role knows the next action, trigger, owner and approved alternative. It should remain scannable under live conditions. Keep the master complete and give operators filtered views rather than deleting important context.
What should happen when the schedule slips?
The show caller and authorized event lead should use pre-approved cut points, break adjustments or alternate segments. Update the online audience when the delay affects their experience. Do not improvise across permission, accessibility or governance boundaries without the authorized decision-maker.
Turn the agenda into a broadcast plan
A strong run of show protects more than timing. It connects the organizer’s promise to the viewer experience, gives the crew approved boundaries, makes accessibility executable and keeps live decisions with the right people.
To plan a professional event livestream with Powwow Times, request availability and discuss your event. Include the date, city, venue, program outline, audience, rooms or stages, platform, accessibility and language needs, replay goals, budget or procurement method and proposal deadline.
