Run of Show Definition: What It Is and Who Owns It
By RunCue · · 10 min read
Key takeaways
- A run of show is the minute-by-minute document your team runs event day from, with a start time, an owner and a trigger for every segment.
- It's different from the agenda guests see, the AV cue sheet and the production schedule that covers several days, though one tool can hold all of them.
- A complete run of show has eight fields: time, duration, segment, owner, location, dependencies, cues and backup notes.
- One person owns the master copy and every change goes through them. Otherwise competing versions appear and nobody trusts the timings.
- How much detail you need depends on how complicated the event is. A small dinner you run yourself needs one page. A staged production needs numbered cues with triggers and fallbacks.
A run of show is the minute-by-minute plan for running an event: every cue, transition, speaker and handover in time order, owned by one person on the team. Guests see the agenda, the AV crew works from the cue sheet, and vendors build from the production schedule. The run of show is the one your own team runs the day from. This guide explains each of them, then shows the same 150-person gala at three levels of detail.
What is a run of show, exactly?
A run of show is a minute-by-minute plan for the event day. It lists every segment in time order, with a start time, an owner and the cue that starts it: doors open, vendor arrivals, a speaker walking on, the last guest leaving.
The term comes from broadcasting, where the run of show controls a live program down to the second. Event agencies borrowed it because a live event goes wrong the same way live TV does, when one missed cue knocks everything after it.
A good run of show tells you three things at a glance: what happens next, who's doing it, and what needs to be in place before it can start. If your document doesn't have an owner on every line, it's really an agenda.
What does run of show mean versus agenda, cue sheet, and production schedule?
A run of show is the internal, minute-by-minute plan for event day: who does what, where and when, from load-in until the last guest leaves. It often gets confused with three other documents.
Agenda
The agenda is the schedule guests see. It says "6:00 PM cocktails" and nothing about which member of staff sets up the bar or brings up the lights. Guests read the agenda, and your team works from the run of show.
Cue sheet
The cue sheet is the AV and production document. It lists the technical cues: passing a mic, advancing slides, audio levels, lighting changes. It's usually the technical crew's slice of the run of show.
Production schedule
The production schedule covers the wider build: vendor arrivals, load-in windows, rigging and strike. It can span several days, while the run of show focuses on the event day itself.
| Document | Who reads it | What it covers | Level of detail |
|---|---|---|---|
| Agenda | Guests | The program only | Broad |
| Cue sheet | AV crew | Technical cues | Minute by minute |
| Production schedule | Vendors and crew | Load-in through strike | Time windows |
| Run of show | Your whole team | The whole event day | Minute by minute |
In practice, one document can hold all of this. RunCue's run of show builder keeps the agenda, cues and staffing on the same timeline, so planners aren't copying between tabs.
What belongs in a run of show document?
A complete run of show has eight fields: time, duration, segment, owner, location, dependencies, cues and backup notes. Time is when the segment starts, duration is how long it lasts, and the segment is what the room experiences. The owner is one named person rather than a team, so nobody assumes someone else is watching the door.
Dependencies and cues are where most spreadsheets struggle. Vendor arrivals, mic handovers and lighting changes end up in different tools that stop matching, and the mistakes show up on the day (eventist.ca). Backup notes say what happens if the keynote runs long or a speaker doesn't turn up.
RunCue gives every cue a time, end time, owner, location and notes, and links it to the related tasks and vendors, so cues don't sit in a tab nobody checks (what is RunCue). If you already have a spreadsheet that works, keep its columns. The fields are what make it a run of show.
Who owns the run of show position on an event team?
Who owns it depends on the type of event, but the pattern is the same: one person holds the master copy and everyone else feeds into it.
Agency and corporate events
At an agency, the run of show usually belongs to the lead planner or producer, with an operations coordinator keeping it up to date in the weeks before load-in. On the day, it passes to a stage manager or lead for the day who calls the cues while the planner looks after the client. At corporate events, an event manager usually owns it and shares a read-only copy with AV, catering and speakers. The thing to avoid is two versions going round, so pick one owner and send every change through them.
Weddings and social events
At weddings, the planner or coordinator owns the timeline and the venue's coordinator carries it out on the day. If there's no coordinator, a friend or family member ends up holding it, and that's where most problems on the day start. Whoever has it should keep the version with every cue, not a simplified agenda, and the run of show template makes the handover clear.
What does a run of show look like at different levels of detail?
You could run the same 150-person gala from three very different documents. The right one depends on how many people are delivering the event and how much could go wrong without anyone noticing.
Level 1: simple
One page with the time, the segment and the owner. Doors at 6:00, dinner at 7:15, speeches at 8:00, last guest out by 10:30. This works if you're running the event yourself with two or three staff and no outside vendors. It stops working once a stage manager, a caterer and an AV lead all need to act on the same cue, because "8:00 speeches" doesn't say who dims the lights or gets the mic ready.
Level 2: standard
Each row adds the location, the owner and the dependencies: the speaker is confirmed, the mic is handheld, the slides need to be loaded by 7:45. This is what most agency planners mean by a run of show. RunCue's run of show is on every plan, and the number of cues you can have per event goes up with the plan (pricing). This level is enough for client events where your planners deal with vendors directly and one person can keep the whole day in their head.
Level 3: production-grade
Every cue gets a number, a trigger, a fallback and a radio channel. "Cue 14: house lights to half when the show caller says so; hold if the guest of honor isn't backstage by 7:58; radio channel 2." Venues and production crews expect this level on load-in day, and it's where a digital run of show pays for itself, because a printed copy is out of date the first time a speaker runs late. RunCue's live cue execution is built for this.
Which level fits your event
If it's just you and no vendors, Level 1 is enough. A client event with vendors needs Level 2. A staged production with AV, lighting and a show caller needs Level 3. RunCue is a good fit for Levels 2 and 3. A solo planner running a simple dinner doesn't need it, and a spreadsheet is the cheaper option there.
How do you turn a run of show definition into a working document?
Build it in four passes instead of all at once.
First, lock the agenda: doors open, catering times, speaker slots, load-in and vendor arrivals, in fixed time blocks. Don't add detail until the client has signed off this outline, because every later change affects the cues underneath it.
Second, add owners and dependencies. Every block gets one name, and anything that can't start until something else finishes gets that written down. "Badge printing waits for the final RSVP count" is a dependency. Leave it unwritten and you'll find out at check-in.
Third, add the cues. Audio, lighting, announcements and transitions get exact times and the name of the person who triggers them. This is the step that turns a schedule into something you can actually run the day from.
Fourth, test it with a walkthrough. Read it out from start to finish with all the owners in the room. Any cue without an owner, or any gap of more than five minutes with nothing planned, is a problem you've found on a Tuesday instead of on the day.
A document or spreadsheet holds the plan, but it can't tell you that a cue went late. That's what RunCue's live cue tracking is for.
Where can you get a free run of show template?
Start with a spreadsheet: one row per cue, with columns for time, segment, owner, location and status. That covers everything in the sections above and costs nothing. Google Sheets and Excel both work, and Airtable's help pages show how to turn the same columns into a shared base with a view for each owner.
Spreadsheets versus dedicated tools
A spreadsheet is free and flexible, but copies start to differ once three planners edit their own versions. Airtable makes sharing easier but isn't built for events, so you set up the cue logic again for every event. Event tools like RunCue come with owners and statuses built in, but they cost money (pricing has our current rates and Founder terms), and RunCue doesn't do ticketing. If your run of show lives in one document and rarely changes during the event, a spreadsheet is fine.
How do you keep a run of show accurate when plans change?
A run of show stops being useful as soon as there are two versions. If the producer has a PDF from Tuesday and the stage manager edited a spreadsheet on Wednesday, nobody knows which timings are right. Keep one document, give each event one owner, and log every change with the time it was made, so the whole team can see what moved and why.
Spreadsheets get out of step because copies are emailed, downloaded and edited offline, and those edits never make it back. On the day, the document needs to update for everyone at once. When a speaker runs long and a cue moves, everyone's copy should show it straight away, without someone having to send it round again.
RunCue does this with one shared run of show that updates live on the day. It won't replace your production radios or your ticketing, so judge it the way you'd judge any tool: what it costs in total, whether you can export your data, and how quickly support responds.
FAQ
Is it 'run of show' or 'run of the show'?
You'll hear both, but "run of show" is the standard term in broadcasting and event production. "Run of the show" sounds more natural when you're talking, so people do say it. On documents, templates and job descriptions, write "run of show" so searches and colleagues find the same thing.
How far in advance should you write a run of show?
Start the outline four to six weeks out, with the agenda blocks, load-in windows and vendor arrivals fixed. Add owners and dependencies once the client has signed off, then add the cues in the last two weeks. Do the walkthrough the week before, early enough to fix whatever you find without paying rush fees.
Do you send the run of show to clients and vendors?
Yes, but only the parts each person needs. Vendors get the rows that affect them, usually the production schedule part covering arrivals, load-in and strike. Speakers get their walk-on times and cues. Clients get the agenda rather than the internal document, because the run of show shows staffing decisions and backup plans you don't want a client second-guessing during the event.
What is the difference between a run of show and a call sheet?
A call sheet is an extract for one person or department: who needs to be where, when, and the numbers to call. The run of show is the master document covering the whole event day for the whole team. The call sheet is one filtered view of the run of show, made for a particular crew member, and it doesn't replace the master.