What is a run of show, and why every event needs one

A run of show is the minute-by-minute operational master document that tells every person and crew member exactly what to do and when to do it. It’s the working script behind the scenes, distinct from any agenda a guest might see, and it exists to keep timing, cues and responsibility locked together across the whole event.

The people who live and breathe this document are the stage manager, the AV lead, the production lead and whoever is keeping time on the day. When those roles are working from the same minute-by-minute master document, cues land on time and nobody has to guess who’s responsible for the next handover.

Build one properly and you get:

• A single source of truth for timing, so no two people are working from different versions of the schedule
• Named ownership on every task, removing the “I thought someone else had that” moment
• A record you can mark up live and use for post-event reconciliation

Key takeaways

A run of show succeeds when every cue has a named owner, timings include buffers verified in rehearsal, and one locked version is distributed to the whole team.

Table of Contents

• What is a run of show and how does it differ from an agenda?
• How do you format times, owners, cues and dependencies?
• What does a run of show template actually look like?
• How do you build a run of show from scratch?
• What should a technical rehearsal cover?
• How do you call a show and handle drift on the day?
• What are the most common run-of-show mistakes?
• How Connections Entertainment uses run of show planning day to day
• Ready to put your run of show into practice?
• Why named owners and version control matter more than the template itself
• Sources
• FAQ

What is a run of show and how does it differ from an agenda?

An agenda is written for guests. It tells them when the ceremony starts, when the meal is served, when the band comes on. A run of show is written for the team, and it goes into far more granular detail than any attendee ever needs to see.

Where an agenda might say “Speeches, 7.30pm”, a proper run of show breaks that same moment into cue points, backup contacts and technical notes. The columns that matter most are:

• Start and end time (and duration, calculated separately so nobody has to do mental arithmetic under pressure)
• Segment label describing exactly what’s happening
• Owner — one named person, not a department
• AV cues — sound, lighting, slides, video triggers
• Location — stage, foyer, breakout room, or stream channel for virtual events
• Dependencies and notes — what has to happen before this segment can start

Use 24-hour time throughout and build in buffers between segments rather than assuming everything runs exactly to plan, because it never quite does.

How do you format times, owners, cues and dependencies?

Ambiguity is the enemy of a good run of show. A row that reads “band plays” tells nobody anything useful. A row that reads “Band 1: first dance, 3-minute set, cue lighting to warm wash at 19:42” tells the lighting operator precisely what to do and when.

Work through these four fields with the same discipline every time:

1. Time — always 24-hour notation (19:42, not 7.42pm), with duration shown in minutes so gaps are obvious at a glance
2. Owner — one name, one phone number, never “AV team” or “front of house”. Assigning a named individual to each cue rather than a department is standard production practice precisely because departments don’t answer their phones when a cue is late.
3. AV cues — state the trigger, the action and the expected result (“Cue 14: fade house lights to 20%, confirm via headset”)
4. Dependencies — note what must be true before the row can start (“Requires: caterer clearance from top table”)

Pro Tip: Give every row a status field too, even if it’s just a colour or a word: Not started, In progress, Complete, Delayed. A quick scan tells the whole team where drift is happening before it cascades into the next segment.

Production teams consistently find that a single named owner per row speeds up troubleshooting the moment something goes wrong, because there’s no back-and-forth working out whose problem it actually is.

What does a run of show template actually look like?

A landscape spreadsheet is still the most workable layout most production teams reach for, and for good reason: it fits a lot of columns without forcing anyone to scroll sideways constantly. The practical default layout runs Time, Item, Owner, AV Cues, Location and Notes across the top, with one row per segment underneath.

Three sample rows show how this works in practice:

• 07:30 to 08:15, Pre-show setup. Owner: venue technician. AV cues: sound check, mic levels for lectern and lapel. Location: main hall. Notes: caterer access restricted until 08:00.
• 09:00 to 09:20, Opening keynote. Owner: stage manager. AV cues: slide deck cue 1, spotlight up on lectern. Location: main stage. Dependencies: speaker confirmed backstage by 08:50.
• 09:20 to 09:25, Transition to panel. Owner: floor manager. AV cues: lighting shift, panel mic check. Notes: five-minute buffer built in for seating change.

Virtual and hybrid events need three extra columns beyond the standard set: a stream cue column for what the broadcast operator triggers, a moderator chat cue for when the online host prompts audience questions, and a stream backup link in case the primary feed drops. A production task like this is exactly where a dedicated AV production hire service earns its fee, because the margin for error on a live stream is much smaller than on an in-room segment.

How do you build a run of show from scratch?

Start with the constraints you can’t move, not the ones you’d like to control. Working from fixed points outwards produces a far more realistic schedule than starting at 9am and hoping the day fits.

1. List your anchors first. Venue access times, a hard curfew, a keynote speaker’s flight window, catering service slots. These are non-negotiable, so they go on the page before anything else.
2. Work backwards to build load-in and tech windows. If doors open at 18:00 and the AV rig needs two hours to test, load-in starts no later than 15:30, with a buffer built in for anything that goes wrong.
3. Populate every segment and assign a named owner with a working phone number. No department names, no “TBC”.
4. Lock your media file paths and version numbers before rehearsal. If slide decks or video files are still moving folders on the morning of the event, something will play the wrong file at the wrong moment.
5. Hold a final review with every department lead, ideally 48 to 72 hours out, so anyone who spots a clash has time to fix it rather than discover it live.

This is also the point at which many organisers realise their entertainment timings need adjusting around a wider schedule. Looking at real wedding entertainment timeline examples is a useful sanity check before you finalise anchor points.

What should a technical rehearsal cover?

A tech run-through exists to find the problems before an audience does. Most events of medium complexity need one to two hours for this, and it consistently uncovers transitions that take longer in practice than they looked on paper, according to guidance from XTimer. That extra time has to be built back into the run of show, not just noted and forgotten.

Work through this checklist during rehearsal:

• Microphone levels for every speaker and performer, not just the first one to test
• Playback files, confirmed to open and run from the correct, final version
• Slide and video control handovers between operators
• Lighting transitions, cued at actual speed rather than assumed speed
• Streaming feed and camera routing, tested end to end including the backup path

Pro Tip: Run the rehearsal at the same time of day as the real event wherever possible. Natural light, room acoustics and even Wi-Fi congestion can behave differently at 7am than at 7pm.

Once rehearsal wraps, update the run of show immediately while the findings are fresh, and confirm the amended version is the one that gets distributed.

How do you call a show and handle drift on the day?

Calling the show is a discipline, not a formality. The standard protocol runs standby, confirm, go, and it should be called by one person, usually the stage manager or production lead, so cues never come from two directions at once.

Through the day itself:

• Call each cue with a standby warning before the “go”, giving the operator a moment to prepare
• Record actual times against the planned times as you go, because that marked-up copy becomes your post-event reconciliation record
• If the schedule drifts, know in advance which segments can be trimmed, which optional content can be cut, and who has the authority to make that call

What are the most common run-of-show mistakes?

Most failures trace back to a handful of repeat offenders. Unnamed owners, missing file paths, timings written in inconsistent formats, and zero buffer between segments all show up again and again in post-event debriefs.

Watch for these red flags during rehearsal and on the day:

• A row with a department name instead of a person
• Any segment with no buffer before or after it
• File paths that reference a folder rather than a specific, versioned file
• Two people both believing they’re calling the same cue

Pro Tip: If you spot any of these during rehearsal, fix them there and then. A red flag caught in rehearsal costs five minutes. The same problem caught live costs the segment.

Escalate fast to the named owner on the row in question, not to a general group chat.

How Connections Entertainment uses run of show planning day to day

Connections Entertainment builds run-of-show documents into every wedding and corporate booking across Norfolk, Suffolk and East Anglia, because timing entertainment against catering, speeches and venue curfews is where events genuinely succeed or come unstuck. This article draws on editorial analysis from Darren Flynn, alongside the site’s wider planning resources.

For readers building their own document, a few related guides are worth pairing with this one:

• How to book event entertainment: a planner’s checklist for rehearsal and mic-check timing
• Types of event equipment for venues for lighting and playback specifics
• Audio visual hire in Norwich and Norfolk for events where the AV load justifies bringing in a dedicated crew

Ready to put your run of show into practice?

A template is only as good as the entertainment timings it’s built around, and that’s usually where couples and corporate planners get stuck first. If you’re mapping out the drinks reception, first dance or evening entertainment slots on your own run of show, unique wedding venue entertainment ideas is a good starting point for filling those rows with something concrete rather than a placeholder. Connections Entertainment works directly from client run-of-show documents when booking DJs, live bands, photo booths and full event production across Norfolk, Suffolk and East Anglia, fitting entertainment cues around the timings you’ve already locked in.

Why named owners and version control matter more than the template itself

Most advice on this topic obsesses over the spreadsheet layout, as though the right column headers are what make an event run smoothly. They aren’t.

The conventional advice undersells rehearsal, too. Treating the tech run-through as a formality rather than a genuine discovery process is where most on-day drift originates, because the gaps between planned and actual transition times don’t announce themselves until you run them at full speed. A rehearsal that finds three timing problems and gets them fixed on paper is worth more than a beautifully formatted template that’s never been tested.

If you take one thing from this: prioritise ownership and version control before you worry about which columns to include. A messy spreadsheet with named owners and a locked final version beats a polished one that three people are editing simultaneously, with nobody quite sure which copy is live.

— Darren Flynn

Sources

• Building an Effective Run of Show for Live Events — CTS AVL
• How to Create a Run of Show – XTimer
• Event run of show: what to include and how to build it — Legal Clarity
• Run of Show – momencio
• Events

FAQ

What does run of show mean?

A run of show is the detailed, minute-by-minute internal document that lists every segment, cue, owner and technical action needed to deliver an event, used by production teams rather than guests.

What is another term for run of show?

It’s often called a production schedule, show itinerary, or program flow, though “run of show” remains the standard term among stage managers and AV crews.

What is a run of a show?

It’s the operational schedule crews follow backstage, mapping timing, cues and responsibilities segment by segment, distinct from the public-facing agenda guests see.

What is the meaning of “run off show”?

This is a common misspelling of “run of show”. The correct term describes the master timing and cue document used to coordinate a live, virtual or hybrid event.

How long should a technical rehearsal take?

Most events of medium complexity need one to two hours for a full technical run-through, which typically reveals transitions running longer than planned.

Recommended

• What does an emcee do? Your complete UK guide
• How to coordinate event logistics: run sheet & checklist
• What is a venue entertainment calendar?
• How to book event entertainment: a planner’s checklist

Write in natural British English for Connections Entertainment, an established event entertainment and event services company serving Norwich, Norfolk, Suffolk, East Anglia and the wider UK where appropriate. Write for real customers planning weddings, corporate events, private parties and celebrations.

Use a professional, friendly and knowledgeable tone. Prioritise genuinely useful information and search intent rather than keyword stuffing. Use clear headings, short paragraphs and natural tran