A run of show is an event production document: the minute-by-minute plan for an event day. It lists every segment in order with its time, who leads it, the cue that starts it and what to do if it goes wrong. The event team, venue and suppliers use it; guests receive the agenda, not the run of show.
You can meet a run of show when you host a conference, a gala dinner or an incentive day out for a group. It is not the event agenda, the list of sessions guests receive. Nor is it the event timeline, the plan of tasks that leads up to the event.
Key points
- A run of show is the team’s plan for the live event, moment by moment, not the guests’ agenda
- Each row carries six columns: time, activity, lead, cue, contingency and guest message
- Transfer and outdoor rows name their own fallback and the person who decides to use it
- The guest message column holds confirmed information only, so a change reaches guests once
What is a run of show?
A run of show is the sheet your team runs the event from while it happens. Each row is one moment, in time order. It says what starts that moment, who leads it and what happens if it fails.
Nearby terms to keep apart:
- Event agenda: the guest-facing list of sessions and times, without cues or names of who does what. Swapcard’s guide to the run of show keeps the two apart.
- Production schedule: the high-level tasks leading up to the event, such as setup, rehearsal and teardown times. AVAD3’s run of show guide treats it as a separate document.
- Event timeline: the schedule of planning tasks in the weeks before the event.
- Event planning: the work from the first request to the event; the run of show takes over on the day itself.
How a run of show works in practice
A run of show works as one sheet, read top to bottom. Our Tourism Events Manager sets its shape in one line: “A run of show lists time, activity, lead, cue, contingency and guest message.”
The six columns of a run of show
| Column | What to write |
|---|---|
| Time | When the moment starts, and when it should end |
| Activity | What happens, in a few words |
| Lead | The one person who runs this moment |
| Cue | What starts it: a signal, a call or the end of the row before |
| Contingency | The fallback if it goes wrong, and who decides to use it |
| Guest message | What guests are told at this moment, from confirmed details only |
Two rules for an event that leaves the room
A conference can stay in one building. An incentive day, a vineyard visit or a gala dinner across town moves people between places, and each move can fail. This page adds two rules for those rows.
- Transfer and outdoor rows carry their own fallback and a named decider. Write the fallback for weather, delay and a supplier who fails, then the person who decides to use it and by when. Our Inbound Operations Specialist covers the same risks: “Prepare weather, delay, missed connection, overbooking and supplier-failure contingencies.”
- The guest message column holds confirmed information only. A change goes to guests once, from the same sheet, after the switch is confirmed. Our Tourism Events Manager draws the line: “Prepare confirmed announcements, sponsor communications and attendee updates from one current schedule.”
An illustrative example (not a real business)
A destination management company runs the day of a sales team’s incentive trip. Its run of show has one card per moment:
- Hotel breakfast – Time: [breakfast time] – Lead: [hotel host] – Cue: the restaurant opens for the group – Contingency: if breakfast service is delayed, [hotel host] confirms an alternative with the hotel and [operations lead] decides whether departure must change – Guest message: the coach leaves from the hotel entrance at [departure time]
- Coach transfer to the vineyard – Time: [departure time] – Lead: [coach host] – Cue: headcount done at the door – Contingency: for a delay or breakdown, [coach host] checks availability with [backup coach company]; [operations lead] decides by [decision deadline] – Guest message: the welcome on board, read by the coach host
- Tasting in the garden – Time: [tasting time] – Lead: [vineyard host] – Cue: the coach reaches the vineyard gate – Contingency: rain, move to the cellar room; [operations lead] decides by mid-morning – Guest message: where the tasting takes place, once confirmed
- Lunch at the vineyard – Time: [lunch time] – Lead: [vineyard host] – Cue: the tasting ends – Contingency: a late tasting shortens lunch, not the return – Guest message: none needed
- Return transfer – Time: [return time] – Lead: [coach host] – Cue: headcount done after lunch – Contingency: if the return is delayed, [operations lead] confirms a workable dinner time with [dinner venue manager] before changing the sheet and guest message – Guest message: the time and place of the gala dinner
- Gala dinner in town – Time: [dinner time] – Lead: [dinner venue manager] – Cue: the group arrives at the door – Contingency: a late coach moves the first course, agreed with the venue – Guest message: none needed
That morning, rain is forecast. The operations lead switches the tasting to the cellar room and confirms it with the vineyard. Only then does the guest message change, and the coach host announces it on the way:
Today’s tasting takes place in the cellar room, out of the rain. Lunch and the return stay as planned.
Nothing went to guests before the switch was confirmed. They heard about the change once, from the sheet the whole team used.
Why a run of show matters for event teams and destination companies
A run of show gives the team, the venue and every supplier the same rows to work from. When something moves, it moves in one place.
An event that leaves the room depends on roads, weather and suppliers you do not control. Without a named decider, nobody owns the call on the day, while guests wait. Our MICE Manager builds the run of show with contingency for last-minute changes: “Build a run of show, supplier matrix, communications plan, attendee segmentation and contingency for last-minute changes.”
The guest message column protects trust. A guest who hears one plan, then a second, has to ask which one holds. One message from confirmed rows spares them that. Our Travel Tour Operator & DMC Specialist designs weather and disruption contingencies that protect travelers and partners.
Name the fallback and the decider before the day, and tell guests only what is confirmed.
How to get started with a run of show
- Start from your confirmed program. One row per moment, in time order.
- Fill the six columns for each row, with one lead per row.
- Mark every transfer and outdoor row with its fallback, who decides and by when.
- Write guest messages from confirmed rows only.
- Walk the sheet with each lead before the day, so everyone knows their cue.
For a blank sheet to start from, see our event run of show template.
How we help. The Tourism Events Manager drafts an event concept, timeline or run of show for destinations and operators. The MICE Manager drafts an event RFP, proposal, budget, run of show or vendor matrix. The Travel Tour Operator & DMC Specialist prepares the supplier handoff, contingency and guest information for live service.
Apply it with your AI assistant. Copy this into the assistant you already use:
I'm reading this page about run of show: https://traveltech.digital/glossary/run-of-show/ Can you help me see how it applies to my work, and what I could do first? Use what you already know about me. If something important is missing, ask me instead of guessing.
Put AI to work in your tourism business
Frequently asked questions
What does a run of show mean?
A run of show is the working plan for an event day, minute by minute. Each row is one moment, in time order, with who leads it, the cue that starts it and what happens if it fails. The event team, the venue and suppliers work from it, while guests get the agenda.
For an event that moves between places, the run of show also holds each transfer, with its own fallback and the person who decides to use it.
What is the difference between a run of show, event agenda, and event schedule?
The agenda is for guests: sessions and times, without cues or names of who does what. The run of show is for the team: the same day, minute by minute, with leads, cues and fallbacks.
Sources use “event schedule” and “production schedule” for different things. Swapcard describes an event schedule as the internal logistics list for staff and vendors, such as setup and catering. AVAD3 calls the setup, rehearsal and teardown plan a production schedule, kept apart from the run of show. Our advice: when someone asks for “the schedule”, check which document they mean before you send it.
What should a run of show include?
A run of show includes six columns for each moment of the day: time, activity, lead, cue, contingency and guest message. Our Tourism Events Manager uses the same six.
For an event that leaves the venue, add two things to every transfer and outdoor row. Name the fallback for weather, delay or a supplier who fails, and name the person who decides to use it. Then keep the guest message column for confirmed details only.
When should a run of show be created?
Our advice: start a draft once the program has its main moments and suppliers, then update it as each line is confirmed. A row that is still unconfirmed stays out of the guest message column.
Before the day, walk through the sheet with each lead so everyone knows their cue and their fallback. Close to the event, keep one current version and make every change in that one place, so nobody on the team reads an old sheet.
Who is responsible for creating and managing the run of show?
Our advice: name one person who owns the sheet and its changes, and give each row its own lead. The owner does not run every moment. They keep one current version that the team, the venue and suppliers all read.
On a day out, also name who decides on each fallback, such as the operations lead for a garden tasting that may move indoors. Guests then hear about a change once, from that same sheet.
Sources
- Swapcard, “Run of show”, checked 2026-10-19.
- AVAD3, “What is a run of show?”, checked 2026-10-19.
