How to Build a Run of Show Your Whole Crew Can Follow

Event production crew member operating a professional mixing console during technical preparation

A run of show is more than a schedule. It is the operating document that connects your event plan, technical departments, presenters, venue team, and production crew.

When it is written well, each person can see what is happening, when it happens, who owns the next action, and which cue moves the program forward. When it is incomplete, the crew has to fill in the gaps through phone calls, hallway conversations, and last-minute guesses.

We use the run of show as a central tool in technical event management. It gives everyone a shared timeline and creates a practical structure for making decisions under pressure. Whether you are producing a corporate conference, church program, awards ceremony, concert, or hybrid event, the document should help your crew act with confidence.

What Is a Run of Show?

A run of show is the detailed, production-facing version of an event schedule. It tracks each segment of the program from load-in and rehearsal through the final cue and load-out.

An attendee agenda may show:

  • 9:00 a.m. Keynote
  • 10:00 a.m. Break
  • 10:30 a.m. Panel discussion

A production run of show goes further. It may show:

  • When the presenter enters the stage
  • Which microphone is active
  • Which presentation file is loaded
  • When the walk-on music begins and ends
  • Which lighting look is active
  • When the camera switches to the presenter
  • Who calls the cue
  • What happens if the presenter is late
  • Which department must be ready before the segment begins

The run of show should be detailed enough that a qualified crew member can follow it without needing a separate explanation. It should also be readable enough that producers, presenters, and client stakeholders can understand the program at a glance.

Start With the Program, Not the Equipment

The strongest run of show begins with the event’s purpose and audience experience. Do not start by listing microphones, screens, or lighting fixtures. Start by defining what the audience should see, hear, and experience in each segment.

First, gather the core program information:

  • Event start and end times
  • Arrival, registration, and seating periods
  • Speakers, performers, and presenters
  • Breaks and meal periods
  • Videos, presentations, and demonstrations
  • Panel discussions and audience Q&A
  • Sponsor moments and announcements
  • Awards, transitions, and closing remarks
  • Rehearsal and technical check times

Then convert the program into a working timeline. Give every segment a start time, end time, duration, room, and owner.

For major events, we recommend separating the attendee-facing agenda from the production-facing run of show. The attendee agenda should remain simple. The production document should contain the operational detail your crew needs.

Our guide to choosing an AV production company explains why planning, staffing, rehearsals, and show operations should be considered before equipment is selected. The same principle applies to your run of show: define the production requirements before deciding how to format the document.

The Essential Run of Show Columns

Your columns should answer five basic questions:

  1. What is happening?
  2. When is it happening?
  3. Where is it happening?
  4. Who owns it?
  5. What must the crew do?

A practical run of show may include the following fields.

Column Purpose
Cue ID Gives each cue a stable reference, such as C-010 or VID-025.
Start Time Shows when the segment or cue begins.
End Time Shows the planned stopping point.
Duration Helps the producer track timing and schedule changes.
Segment Names the program item, such as “CEO keynote” or “Panel Q&A.”
Room or Channel Identifies the main stage, breakout room, stream, or virtual channel.
Presenter or Talent Lists the person appearing or speaking.
Owner Identifies the responsible department or crew member.
Audio Lists microphones, music, playback, or sound effects.
Video and Graphics Identifies slides, videos, lower thirds, camera shots, and screen content.
Lighting Notes stage looks, house lights, spots, blackouts, or transitions.
Platform or Stream Tracks virtual rooms, stream scenes, remote guests, polls, and recording.
Stage or Floor Covers entrances, exits, set changes, furniture, props, and handoffs.
Assets and Links Points to the correct presentation, video, script, or media file.
Dependencies Shows what must be ready before the cue can proceed.
Contingency Provides the backup action if a speaker, file, or system is unavailable.
Status and Notes Tracks live changes, holds, completed cues, and timing adjustments.

You may not need every column for a small meeting. You may need additional fields for a large conference or multi-room production. The goal is not to create a document that is difficult to read. The goal is to include the information that prevents confusion.

Write Cues So the Crew Can Act

A run of show should use direct, operational language. Avoid vague notes such as “get ready for the speaker” or “prepare video.”

Instead, write the action in a way that identifies the department, trigger, and result:

  • STANDBY A1: Podium microphone and handheld microphone.
  • STANDBY V1: Keynote deck, slide 1.
  • STANDBY L1: Keynote stage look.
  • ON MC: “Please welcome our next speaker.”
  • GO A1: Open podium microphone.
  • GO V1: Take keynote deck to screen.
  • GO L1: Bring up keynote look.
  • GO STAGE: Presenter enters from stage left.

This language reduces interpretation. It also allows the show caller, technical director, and department leads to communicate quickly during a live program.

Every important cue should include a trigger. The trigger may be a line of dialogue, a timecode, a visual action, or a direction from the show caller.

For example:

Trigger: MC says, “Let’s take a look at the year in review.”
Cue: Roll “Year in Review” video. Fade house lights to 20 percent. Take video audio. Return to stage look when the video ends.

This is more useful than a note that simply says, “Play video.”

Put Technical Cues in the Main Document

Technical cues should not live only in a separate department’s notebook. The master run of show should show how each department contributes to the program.

At minimum, include fields for:

Audio

List microphone assignments, walk-on music, playback, sound effects, panel handoffs, audience microphones, and recording feeds.

Avoid writing only “mic ready.” Identify the specific microphone and person:

  • Podium mic open
  • Handheld 2 to moderator
  • Lav 1 to keynote speaker
  • Playback track: opening_sting_v3.wav

This level of detail helps the audio team prepare while giving the stage manager and producer a shared reference.

Video and Graphics

Name the exact presentation, video, graphic, or camera shot required. Include file versions when content may change.

Useful notes include:

  • Take presentation deck: Q4_Keynote_Final_09-28.pptx
  • Roll sponsor video after introduction
  • Camera 2 on presenter
  • Lower third: speaker name and title
  • Return to wide shot for panel transition

A clear file naming system is especially important when several versions are being delivered close to show time.

Lighting

Connect lighting cues to program moments rather than describing them only by technical settings.

Examples include:

  • House lights to half during audience seating
  • Keynote stage look
  • Walk-on look for award recipient
  • Audience lights up for Q&A
  • Stage look for closing remarks

The lighting team can translate those notes into the console programming and venue plan.

Stage and Floor

Stage cues should identify movement, position, timing, and ownership.

Include:

  • Presenter entrance and exit
  • Furniture changes
  • Lectern placement
  • Award handoff
  • Panel seating
  • Stage reset
  • Confidence monitor check
  • Presenter waiting location

This information is essential for the stage manager, but it also helps audio, lighting, video, and camera operators anticipate changes.

Streaming and Platform

For hybrid events, include the online audience in the same production logic as the room audience.

Track:

  • Stream start and stop
  • Camera and graphics layouts
  • Remote presenter connection
  • Virtual green room
  • Platform scene changes
  • Polls and Q&A
  • Breakout room openings
  • Recording status
  • Replay or on-demand publishing

A hybrid show has multiple audiences and multiple channels. The run of show should make those relationships visible.

Build One Master Document for Multi-Room Events

For a multi-room event, use one master run of show as the source of truth. Add room and channel fields to every relevant row.

A main program may include:

  • Main stage
  • Breakout Room A
  • Breakout Room B
  • Sponsor area
  • Recording studio
  • Global livestream
  • Virtual breakout rooms

The master document should show the full timeline. From it, create filtered views for each department or room.

An audio operator may need:

  • Time
  • Room
  • Segment
  • Presenter
  • Audio cue
  • Owner
  • Trigger

A streaming operator may need:

  • Time
  • Channel
  • Segment
  • Platform cue
  • Graphics
  • Remote guest
  • Asset link
  • Contingency

A stage manager may need:

  • Time
  • Room
  • Presenter
  • Entrance
  • Furniture
  • Stage action
  • Handoff
  • Notes

Filtered views reduce unnecessary information while keeping every department connected to the same schedule. This is a central part of effective production management services because it gives each team member the information needed for their role without removing the broader context.

Treat Hybrid Timing as Its Own Production Layer

Hybrid events require more than adding a streaming link to an in-person schedule. The in-room experience and remote experience have different technical and timing requirements.

For example, an audience break may require:

  • House music in the room
  • A holding slide on the stream
  • A break graphic with the return time
  • A platform operator monitoring chat
  • A remote presenter moved into a virtual green room
  • A camera operator preparing the next shot

Write these actions into the run of show. Use shared cue IDs and time references so the in-room and remote teams can coordinate.

You should also list the assets needed for each channel. Include presentation files, videos, graphics, stream scenes, meeting links, scripts, and remote guest information. If an operator must search through multiple folders to find the correct file, the run of show is not doing enough work.

Our live event production services include technical planning and live streaming support built around the room, the program, and the audience experience.

Add Dependencies and Backup Actions

A cue is only useful when the crew knows what must happen before it.

Dependencies may include:

  • Presenter checked in
  • Slides approved
  • Video loaded and tested
  • Wireless microphone assigned
  • Remote guest connected
  • Translation feed confirmed
  • Camera position clear
  • Sponsor approval received
  • Stage furniture reset

Add a contingency for any item that could significantly affect the program.

Examples:

  • If presenter is late: hold with MC and skip opening video.
  • If remote guest disconnects: move to prepared audience Q&A.
  • If presentation fails: use PDF backup from show computer.
  • If video does not roll: continue with presenter remarks and return to video during the next transition.
  • If the schedule runs long: reduce networking break by five minutes.

Contingencies should be practical and authorized. Your crew should know who can make the decision to hold, skip, shorten, or move a segment.

Review the Document in Rehearsal

Do not wait until show time to test the run of show. Use it during the technical rehearsal and cue-to-cue.

During rehearsal, confirm:

  • Every segment has an owner
  • Cue language is understood
  • Files open correctly
  • Presenters know their entrances and exits
  • Audio assignments are accurate
  • Lighting looks are labeled consistently
  • Video and stream actions align
  • Room changes are documented
  • Contingencies are realistic
  • Timing matches the actual program

Version the document clearly. Use a date and revision number, such as Event_ROS_2026-10-14_v04. Share one approved version with the crew, and identify who is authorized to make live updates.

A run of show is a living production document, but uncontrolled edits create risk. Keep changes visible and communicate them directly during rehearsal and show calls.

Build a Run of Show Your Crew Can Trust

The best run of show is not the longest document. It is the one that gives the right person the right information at the right time.

It connects your creative vision to practical execution. It gives technical teams a common language. It helps presenters understand where they need to be. It gives producers a way to manage timing, dependencies, and change.

At Blueprint Resource Group, we combine technical event management, production coordination, and creative execution to help clients move from concept to show day with a clear plan. As a live event production company, we can support the full production environment, including corporate AV services, streaming, audio, video, lighting, stage management, and technical consultation.

If you are building a major event or need a production partner to manage the details, talk to Blueprint Resource Group about production management services. We will work closely with you to understand your vision, define the requirements, and create a customized plan your entire crew can follow.