How to Build a Run of Show: The Day-of Document That Keeps Your Event on Time

A run of show is the document that tells every person working your event what is happening, where, when and who is responsible, from load-in to load-out. It is different from a schedule, which is what you publish for attendees, and different from a production plan, which is what you hand to the AV company. The run of show is the version that lives in the stage manager's hand, the volunteer coordinator's pocket, and the production office wall, and it answers the question every crew member asks fifty times a day: what happens next? This guide covers how to build one from scratch, what goes in each column, how to structure it so each person sees only their part, how to share it on the day, and how to update it when the plan changes, because it will.

Key takeaways

• A run of show is a crew document, not a public schedule; it contains cues, contacts and responsibilities that attendees should not see.
• Every timed element of the event belongs in it: not just performances and speeches, but doors, soundchecks, meal breaks, changeovers, weather holds and teardown.
• The document should be structured so each crew member can read only their column without scanning fifty pages of someone else's cues.
• A run of show that cannot be updated in real time on the day is a historical document by noon; share it digitally where crew can see changes as they happen.
• The best time to build the first draft is when the schedule is locked, not the night before the event.

What a run of show is and what it is not

A public event schedule tells attendees what they can see and when. A production plan tells the AV company what gear goes where and how it connects. A run of show tells the crew what happens in what order, who makes it happen, and what has to be true before the next thing starts. It is the connective tissue between the schedule the audience sees and the work the crew does to deliver it.

A run of show for a single-stage concert might be one page. A run of show for a multi-day festival with four stages, a vendor village, a volunteer program and a VIP area might be twenty pages, and each person should only ever read the two or three that are theirs. The document is not a script; it is a timeline with owners.

What goes in a run of show

Every run of show is a table. The columns vary by event, but these appear in nearly all of them:

• Time. Start time of the block, to the minute. Use a 24-hour clock so there is no AM/PM confusion on a long day.
• End time or duration. Crew need to know how long they have, not just when something starts.
• Stage or area. Which physical space this block happens in.
• What. The name of the act, the speech, the ceremony, the changeover, the meal break, the doors-open, the soundcheck. Be specific: "DJ set: Mariana Vega" is useful; "music" is not.
• Who is responsible. The person who owns this block: the stage manager, the emcee, the volunteer lead, the production manager. Name and phone number.
• Notes and cues. What needs to happen before this block starts (the previous act's gear is struck, the house lights are down, the video roll begins), what happens during it (lighting cue at minute three, walk-on music plays, the screen shows a slide), and anything the person responsible needs to know.
• Status. On the day, a column for marking each block as done, delayed or skipped.

For festivals and multi-track conferences, add a column for the crew channel or radio frequency, so a stage manager knows they are on Channel 3 and the gate is on Channel 1.

Step 1: List every timed element

Walk through your event from the moment the first person arrives at the venue to the moment the last truck leaves. Everything that happens at a specific time goes on the list:

• Load-in windows for vendors, production and performers
• Soundchecks
• Doors open (and the pre-doors briefing for staff)
• Each performance, speech, panel or ceremony
• Changeover windows between acts
• Meal and rest breaks for crew
• Announcements (sponsors, safety, weather updates)
• Technical cues (lighting changes, video rolls, pyro)
• Intermissions
• Last call and bar close (if licensed)
• Encore window
• House lights up
• Load-out start

Do not skip the unglamorous items. The ten-minute changeover between bands is the block the audience never sees and the stage manager lives in; if it is not in the run of show, it does not exist, and the next act starts late. The how to book performers guide covers what performers expect from the changeover and advance; the run of show is where those expectations become timed blocks.

Step 2: Organize by stage or area and time block

For a single-stage event, the document is one long timeline. For anything with more than one simultaneous area, you need either separate pages per area or a columnar layout where each area has its own column and time runs down the left side. The choice depends on how the crew works:

• Separate pages per stage are better for stage managers and AV crews who never leave their post. A stage manager standing side-stage should be able to read one page that covers their entire day.
• A combined timeline is better for the production manager, the event director and the security lead, who need to see everything at once: what is happening on every stage at 3:15 p.m., where the crowd is moving, and which changeover is about to stack up.

Build both. The combined timeline is the master; the per-area pages are filtered views of it. When the master changes, the views change with it.

Step 3: Add cues and contacts

Every block should answer three questions: who owns it, what has to be true before it starts, and what technical cue triggers it. Examples:

• 10:00 Doors open. Owner: Gate Lead (name, phone). Pre-condition: staff briefing complete, scanners tested, bar stocked. Cue: gate lead radios "gates open" on Channel 1.
• 14:30 Keynote: Dr. Anika Patel. Owner: Stage Manager (name, phone). Pre-condition: AV check complete, slides loaded, speaker in the green room. Cue: house lights to 50%, walk-on music plays, emcee introduction.
• 16:00 Changeover. Owner: Stage Tech (name, phone). Duration: 15 minutes. Pre-condition: previous act struck. Cue: house music up, stage lights to work mode.

The contact column seems redundant until it is 2 p.m. and the person you need is not in the room. A phone number beside every block saves a radio call.

Step 4: Create filtered versions for each crew role

Nobody should read the entire run of show. A volunteer at the gate does not need the lighting cues; the AV engineer does not need the volunteer shift changes. Create a filtered version for each role:

• Stage managers: their stage only, with full cue detail.
• AV and lighting: cue sheets pulled from the run of show, with technical detail added.
• Gate and check-in staff: doors, re-entry, capacity counts and the VIP lane, with nothing else.
• Volunteer coordinators: shift start and end times, post assignments and break schedule.
• Emcees and hosts: their call times, the order of speakers or acts, pronunciation guides and sponsor mentions.
• The event director: the full combined timeline, because they are the person who decides when a delay on Stage B means Stage A holds for five minutes.

The event check-in operations playbook is effectively the gate crew's run of show, focused on throughput and lanes.

Step 5: Share it where crew can read it on the day

A printed run of show is wet, lost or outdated by noon. A shared spreadsheet works if everyone has wifi and remembers the link. The best version is a digital document that is:

• Readable on a phone in daylight. Stage managers and volunteers are not at desks. The font, the contrast and the column width must work on a five-inch screen in direct sun.
• Read-only for most people. The stage manager reads it; the event director edits it. Nobody else should be able to change the master accidentally.
• Updateable in real time. When the 2 p.m. act is running ten minutes long, every downstream block shifts, and every crew member should see the update without a radio call.

Eventist's run-of-show portal does this: a read-only view of the schedule and cue sheet that crew access from a phone, filtered to their stage or role, updated live when the event director moves a block. The festival operations guide covers the broader operations context; the run of show is the document that makes the plan executable minute by minute.

Updating the run of show on the day

No event runs exactly on schedule. The keynote runs long, the band is late to soundcheck, the weather hold pauses Stage B for thirty minutes. The run of show absorbs these changes by shifting blocks, not by pretending they did not happen. The person who edits the master (usually the event director or the production manager) updates the time, and every filtered view reflects the change.

Three rules for day-of updates:

1. Announce the change on radio before it appears on screen. Crew who are mid-task should not learn about a schedule shift by glancing at their phone.

2. Shift downstream blocks, do not delete them. A delayed act that pushes the next changeover by ten minutes is different from a cancelled act that opens a gap; the run of show should show which one happened.

3. Mark completed blocks as done. The status column turns the run of show into a live progress tracker; anyone glancing at it can see where the event is right now.

Frequently Asked Questions

What is a run of show?

A run of show is a timed document that lists every element of an event in order, from load-in to load-out, with the responsible person, the technical cues and the pre-conditions for each block. It is the crew's version of the schedule, distinct from the public schedule attendees see.

What is the difference between a run of show and an event schedule?

An event schedule is what you publish for attendees: act names, times and stages. A run of show is what the crew uses: it includes changeovers, soundchecks, technical cues, responsible contacts, meal breaks and load-out, none of which the audience sees.

How far in advance should you build a run of show?

Start the first draft when the schedule is locked, which for most events is two to four weeks before the event. Refine it as advancing with performers and vendors fills in the detail, and finalize it at the production meeting, typically three to five days out. It will change on the day; that is expected.

Who is responsible for the run of show?

The event director or production manager owns the master document. Stage managers own the execution of their area's blocks. The event director is the person who updates the master when the plan changes and decides how delays cascade across stages.

Can I use a spreadsheet for a run of show?

You can, and many events start there. It stops working when you need filtered views per role, real-time updates on the day, or a phone-readable format for crew standing in the sun. A digital run-of-show tool solves all three; Eventist's run-of-show portal is one option that ties the document to the schedule, the task board and the site map in the same platform.

The run of show is the document that turns a plan into a day. Build it when the schedule locks, filter it so each person reads only their part, share it where it can be updated live, and update it honestly when the plan changes. If you want the run of show, the schedule, the task board and the performer dashboards in one place, the Eventist festival management platform is where they live.