Conference Run of Show Template: How to Plan Transitions, Cues, and Backup Time

A conference run of show is the single document that keeps your stage crew, AV team, speakers, and event staff synchronized from doors open to load-out. Without one, speaker transitions drag, slides fail to advance, and microphones go dead while someone scrambles to find the right input. After running production for conferences ranging from 150-attendee single-track events to multi-day programs with concurrent breakout rooms across Baltimore, Orlando, and national conference venues, our production team has refined the run of show format that actually works on show day.

This guide covers the structure of a production-ready run of show, how to build realistic transition times between sessions, what AV cues to include, and how much backup time to build into your schedule. Includes a template table you can adapt for your event.

Key Takeaways

• A conference run of show should be a spreadsheet, not a paragraph document. Every row is a moment. Every column answers a question the crew needs answered without asking you.
• Build 5 to 10 minutes of transition time between every session on stage. The AV team needs it for microphone swaps, laptop changes, and slide testing.
• AV cues should use consistent, simple language that any technician can interpret under pressure. “Fade house music, bring up podium mic, advance slide to title” is a complete cue.
• Schedule buffer blocks of 15 to 20 minutes in the morning and afternoon, not at the end of the day. A morning session that runs 8 minutes long needs to be absorbed without cascading delays through the afternoon.
• The run of show is a living document. Update it during rehearsals, distribute version-controlled copies, and have a printed backup on show day.

What should a conference run of show include?

A production-ready run of show answers six questions for every moment of the event. If your current document does not answer all six, it is an agenda, not a run of show.

The six columns every run of show needs:

Additional columns that larger productions benefit from include lighting state (house at 50 percent, stage at full), audio routing (which microphones are live), graphics and lower thirds (what is on screen), and a backup plan note (what happens if the presenter runs short or long).

How do you build realistic session transition times?

Transition time is the gap between one session ending and the next one starting. Underestimating it is the most common scheduling mistake in conference production. Here is what actually happens in a transition:

1. Previous speaker finishes and leaves the stage. (1 minute)
2. AV team swaps the laptop or switches inputs to the next presenter’s machine. (2 to 3 minutes)
3. Next presenter’s slides are loaded and tested on the main screen. (2 minutes)
4. Microphone assignments change. The previous speaker’s lav is collected. The next speaker’s mic is set and tested. (2 minutes)
5. Stage is reset: water glass replaced, chair position adjusted, notes placed on podium. (1 minute)
6. Next presenter is mic’d, briefed on timer, and staged at the entrance. (1 to 2 minutes)

That is 9 to 11 minutes of real work. If your run of show schedules zero transition time between sessions, your day is already running behind by 10:00 AM.

Build these minimum transition buffers into your schedule:

• Speaker-to-speaker on the same laptop and mic setup: 3 to 5 minutes. Enough time for one speaker to exit, the next to enter, and the MC to introduce them.
• Speaker-to-speaker with computer change and mic swap: 7 to 10 minutes. Full AV reset between presenters with different tech setups.
• Session-to-panel or vice versa: 10 to 15 minutes. Chairs need to be added or removed from the stage. Multiple microphones need to be set and tested.
• Morning-to-break and break-to-session: Your break time should include 5 minutes of transition buffer on each end. A 30-minute coffee break needs 5 minutes to clear the stage and 5 minutes to reset before the next session starts, meaning the actual break is 20 minutes.

Communicate these transition times to your speakers during the prep call. A speaker who knows they have 40 minutes for a 45-minute slot because 5 minutes are reserved for transition is a speaker who finishes on time.

What AV cues does the run of show need to specify?

AV cues are the instructions that tell your production team what to do with sound, video, and lighting at each moment. Write them in plain, action-oriented language. Every cue should describe the action, the target, and the result.

Here is how to write AV cues for common conference moments:

Session start: “Fade out house music over 3 seconds. Bring up podium microphone. Switch main screen to conference laptop, input 1. Advance to session title slide. Cue walk-up music track 4 at 0:15. House lights to 50 percent. Stage wash to full.”

Video playback: “Fade out stage wash. House lights to 10 percent. Switch main screen to playback laptop, input 2. Audio from playback laptop to house at 80 percent. When video ends, switch main screen back to conference laptop, input 1. Stage wash to full. House lights to 50 percent.”

Panel discussion: “Set 4 handheld wireless mics on stands at panel chairs. Test all 4 before session starts. Audio engineer rides faders (only the speaking panelist’s mic is live). Confidence monitor ON with timer visible. House lights at 50 percent. Stage wash at full.”

Session end: “Fade podium mic out as speaker finishes. Bring up house music to 40 percent. House lights to 80 percent for transition. Switch main screen to holding slide. Collect wireless mics from stage.”

Note the specific numbers: “house lights to 50 percent” not “dim the lights.” “fade over 3 seconds” not “slow fade.” Technicians working under time pressure need precision. Ambiguous cues create hesitation, and hesitation during a live event is visible to the audience.

Conference Run of Show Template

Below is a template for a single-track morning session at a conference. Adapt the columns and timing to your event. Distribute it to your AV team, stage manager, emcee, and every speaker at least one week before the event.

Afternoon sessions follow the same structure. Add additional rows for afternoon break, closing keynote, closing remarks, and the event end time with load-out instructions for the AV crew.

How do you build buffer time into a conference schedule?

Buffer time is the slack in your schedule that absorbs delays without cascading through the rest of the day. The rule our production team uses: build buffers where delays happen, not where you hope they will not.

Delays concentrate at these points in a conference schedule:

• Morning start. Registration lines, late arrivals, coffee runs. A 9:00 AM start that really begins at 9:10 AM is normal. Schedule your first high-stakes content no earlier than 9:15 AM with a low-stakes welcome or housekeeping block in the first 10 to 15 minutes.
• Post-lunch sessions. Lunch runs long, people trickle back slowly, and the afternoon energy dip is real. Schedule an interactive or high-energy session after lunch rather than a dense keynote. Build an extra 5 minutes of transition after the lunch break ends.
• Speaker Q&A overruns. Every speaker who says “I will leave 10 minutes for questions” takes questions for 15 minutes. Build the extra 5 minutes into the transition after their session, not into their scheduled block. If they finish on time, the buffer becomes a longer break. If they run over, the schedule absorbs it.

Schedule at least two buffer blocks per conference day: one mid-morning (10 to 15 minutes) and one mid-afternoon (10 to 15 minutes). These blocks are not breaks. They are labeled “BUFFER” in the run of show and the AV team knows they can be shortened or skipped if the schedule is on track, or used as catch-up time if it is not.

Total buffer time should equal roughly 10 to 15 percent of your total session time. For a 6-hour conference day (9:00 AM to 3:00 PM with breaks), that means 30 to 50 minutes of buffer distributed across the day.

How do you manage the run of show on show day?

The run of show is only as useful as the team’s ability to follow it under pressure. Here is what works on show day:

Printed copies at every technical position. Front-of-house audio, lighting console, video switcher, stage manager, and green room each get a printed copy. Phones die, screens crack, and WiFi drops. Paper does not fail. Use a large font. Highlight every AV cue in yellow.

One person owns the clock. The stage manager or show caller tracks the actual time against the run of show and communicates adjustments. Every time check is announced over comms: “We are at 10:32, keynote should end at 10:35, we are 3 minutes behind. Lighting, prepare to fade to break at my call.” No one else calls time. Multiple timekeepers create confusion.

Version control. If the run of show changes during rehearsals, every copy gets replaced. Old copies get collected and destroyed. A single outdated copy at the lighting console that still has the old session order creates a visible mistake on stage. Date- and time-stamp the file name: “Conference_RunOfShow_2026-10-15_v3_FINAL.pdf”

Communication protocol. Agree on the comms channel and protocol before doors open. Our crews use a simple three-step call for every transition: standby (“Standby to fade house music and bring up podium mic”), go (“Fade house music. Podium mic live.”), and confirm (“Podium mic hot, slide 1 on screen.”). Every action gets confirmed. Silence on comms during a transition means something is wrong.

Frequently Asked Questions

How is a run of show different from an agenda?

An agenda tells attendees what is happening. A run of show tells the production team how to execute it. An agenda says “9:00 AM, Keynote.” A run of show says “9:00 AM, fade house music, bring up lav mic, advance slide to title, house lights to 50 percent, timer set to 40 minutes with 5-minute warning, confidence monitor ON.” The agenda is for the audience. The run of show is for the crew.

Who should create the run of show?

The event planner or producer creates the first draft with session titles, speaker names, and desired timing. Then the AV provider and stage manager add the technical detail: AV cues, transition times, buffer blocks, lighting states, and any venue-specific notes. The final document should be reviewed by the planner, the AV lead, and the stage manager before it is distributed.

How far in advance should the run of show be finalized?

A near-final draft should be circulating two weeks before the event. The final version with all AV cues, confirmed speaker names, and precise timing should be locked one week out. Changes after that point happen, but they should be version-controlled and communicated to every vendor immediately. Last-minute speaker cancellations or session swaps are the most common pre-event change. Have a backup plan for each session slot in case a speaker drops.

What happens if a session runs over time?

The stage manager communicates the overage to the show caller. The show caller decides whether to absorb the delay in the next transition (shave 2 to 3 minutes), use a scheduled buffer block (shave 10 to 15 minutes), or shorten a break (last resort). Never cut a speaker off mid-sentence on stage unless the overage threatens a hard stop time like a venue curfew or meal service window. Give speakers a 5-minute warning and a 2-minute warning so they can wrap gracefully.

How do you handle a run of show for a multi-track conference?

Each track gets its own run of show document. The documents share a master timeline so you can see at a glance what is happening in every room at any time. The AV team in each room only needs their track’s run of show, but the show caller and event producer need the master document that shows all tracks. Label each track clearly: “Track A, Ballroom,” “Track B, Salon C,” “Track C, Room 204.” Color-code the master document by track.

Do I need a different run of show for rehearsals?

Yes. The rehearsal run of show should match the show-day run of show in structure and timing, but it includes additional detail: which speakers are rehearsing at which time, where the backup laptop is staged, and any technical checks that need to happen before speakers arrive. Speakers rehearse in the order they appear on stage, not in the order they arrive. That way each speaker walks their actual entrance, tech setup, and exit in sequence.

What is the most common run of show mistake?

Scheduling zero transition time between sessions. Planners see a 45-minute keynote that ends at 9:45 AM and schedule the next session to start at 9:45 AM. The AV team needs 7 to 10 minutes to reset. The audience needs time to process what they just heard. The speaker needs to exit the stage. Build real transition time into the schedule and the day breathes. Skip it and every session after the first one starts late, compounding through the afternoon until you cut the closing session short or run into the venue’s hard stop time.

A solid run of show is the difference between a conference that feels smooth and one where the audience watches the AV team scramble between every session. If you are planning a conference and want production support that includes a detailed run of show with every AV cue, transition, and buffer built in, contact Event Solutions Group. We provide full conference production services across Baltimore, Orlando, and nationwide conference venues, including run of show development, AV design, stage management, and day-of technical direction.