2.6 · The paper stack: run of show, cue sheet, production schedule

IntermediateDuration ~11 min readTools Your master sheet, new Run of Show tab, The program from 2.5

The big idea: show day runs on three documents with three different readers, and the fastest way to break it is to hand everyone the same paper.

The analogy

Think about what actually gets printed the night before a shoot day. Nobody hands the whole production book to everybody. The call sheet goes to every single person: the date, the location, who is needed and when, what you are shooting, where lunch is. The camera department works off a shot list that has been stripped of everything that is not a shot. And the grips, the truck, and the set build crew run on a different schedule entirely, one that starts hours before anyone says action and ends when the last case is loaded.

Three pieces of paper, three readers, one day. Nobody on a set finds this strange. It is only in events that people print one master document, hand the same copy to the venue, the MC, the sound guy and the volunteer on badges, and then wonder why the day drifted.

Watch

Watch for: This one is not here to teach you the three documents. It is here so you can see how granular a single cue gets when a professional writes it down. Listen at 1:36 as he lays out the two ways a speaker can be brought on stage, a formal voice of God or a soft handoff from whoever just finished. Then at 3:34 he speaks a full sample script out loud and tells you exactly which word the music swells on, which is the name. That whole thing is one row on a cue sheet. And stay for the condiment analogy at 8:00: nobody in the room compliments a transition that worked, they only notice the ones that did not. He is a freelance producer working corporate conferences, so take the granularity and leave the scale.

How it works

By the end of the last lesson you had a program. A program is the shape of the day, the openers and the peaks and the protected connect time, and it is genuinely the hard creative work. It also will not run your event. What runs your event is paper, and the paper is not one document.

Start with the master. The run of show is the whole day written minute by minute, one row per thing that happens, from the first person arriving to the last case going out the door. The columns that matter are start time, end time, duration, what happens, who owns it, where it happens, and anything that has to be true before that row can begin. It lives in a spreadsheet, which is still what the industry actually uses, and everyone reads it. This is the document that makes the answer to “what happens after the raffle” a cell instead of a memory.

Two things sit near the top of that sheet that beginners tend to collapse into one. The first is call time, the moment a named person has to be physically present and ready to work. It is never a single time for the whole event. Your AV supplier has one, your volunteers have another, your podcast guests have a third, and every one of them lands earlier than the event itself. A call time with no name next to it is a wish.

The second is doors, the moment the audience is allowed into the room. Doors is the hinge of the day. Everything before it is yours to fix quietly, in an empty room, with nobody watching. Everything after it gets fixed in front of a hundred people. Write it as its own row and treat it as a deadline, because that is exactly what it is.

Now the thing the run of show carries that nothing else does. A cue is a defined trigger for an action: mic goes live, music up, video rolls, slide advances, lights down. Cues come in two flavours, and the difference decides whether your show survives contact with real humans. A clock cue fires at a time. A dynamic cue fires on something observable, almost always a line somebody says. Clock cues assume the show is running exactly on schedule, and shows drift, because guests run long. Write it as “on ‘thanks for having me,’ music up” and it still works when the room has slipped four minutes.

Which brings us to the second document. The person calling your show does not need the whole day. They need a cue sheet, the stripped-down technical companion that holds four things and nothing else: mic cues, music cues, slide advances, and the lines that trigger them. No vendor arrivals, no badge counts, no raffle logistics. Just the triggers, in order, in the language of the room. The video you just watched is one row of that document opened all the way up, down to which word the music swells on.

The third document faces a completely different direction. A production schedule runs load-in through load-out and it is written for crew and suppliers, not for your audience. It exists because your sound company, your booth builder and your venue do not plan around your agenda. They plan around windows, the limited stretch in which they can get gear into a room and back out of it. If your venue is a hotel or a catered space, they will write their own version of this and call it a BEO, and your job is to make the two agree with each other before anyone shows up with a truck.

Here is the honest part about scale. At meetup size, the run of show and the cue sheet are usually one sheet with a cue column, and that is completely fine. It is fine because you are the person calling every cue, and the sheet is really a backup copy of what is already in your head. It stops being fine the second somebody other than you is calling cues. That moment arrives in August. A live podcast puts you in the chair with a mic on, which means you cannot also be the person deciding when the intro music fades or when the sponsor roll-in plays. Somebody else needs their own paper, and their paper has to be readable by a person who was not in your head last Tuesday.

So write the August day down. Not the pretty version. Every crew call time, doors, the walk-in music, the opening, the sponsor booth window, each podcast segment with its mic cues and its roll-ins, the raffle, the closing line, and load-out. Where you do not know something yet, write TBD. A TBD in a row is a question with a row number and an owner. A missing row is a question nobody has thought to ask, and those are the ones that find you at ten to seven on the day.

The pattern

Three documents, three readers. Run of show is the master, minute by minute, with an owner and a location on every row, and everyone reads it. Cue sheet is the show caller’s stripped copy: mics, music, slides, lines. Production schedule is load-in to load-out, written for crew and suppliers. Merge the first two only while you are the one calling every cue, and split them the moment you are not.

The receipts (evidence, if you want it)

• Minimum run-of-show columns, per SpotMe’s template guide: start time, end time and duration for each activity, the activity name, the stage or area, the speakers, the content, notes, and preparation status, all sitting under a header block carrying the event name, date, location, organizer contact and links to the brief and the script. Their own note on complex days: if sessions run in parallel you may need several run of show sheets, and they recommend keeping them all in the same file (SpotMe, event run of show template).
• Spreadsheets remain the format. “A run of show is traditionally built in a spreadsheet application like Microsoft Excel or Google Sheet. It presents its information in a neat table, with each row representing an event, action or cue in the running order” (Stagetimer, what is a run of show).
• Same guide, on why cues get written as spoken lines rather than clock times: a cue needs to be “easily recognizable” and “distinct enough for it to not be confused with another cue,” and because speakers overrun or underrun, producers use dynamic cues, meaning pointers that are independent of the clock. The reasoning is that for lighting and sound, “being even 10 seconds off can ruin the accuracy of those cues” (Stagetimer).
• The cue sheet as a separate document: “The person calling your show doesn’t need the full run of show but rather a cue sheet… focused on four things: mic cues, music cues, slide advances, and any lines” (We & Goliath, show flow templates).
• A naming conflict worth knowing about. Stagetimer’s guide opens by treating the two as one thing: “A run of show, also known as a cue sheet, refers to a document that provides a cue-by-cue sequence of what will be going on during a show.” That is accurate at small scale and stops being accurate the moment two people are reading two different papers. If a supplier uses the terms interchangeably, ask which one they mean rather than assuming.
• Why the production schedule is its own document: suppliers plan around the “limited window in which they can load in or out,” which is a different unit of time from your program (Venue Crew, event and catering glossary).
• The venue writes its own version. A banquet event order is “a central document distributed to the entire team involved in executing an event,” covering rooms, start and end times, headcount, the setup diagram, AV provision and an itemized cost list, signed by both sides (Cvent, banquet event orders). You met it in Lesson 1.6. It is the venue’s production schedule, written by them, which is why yours has to match it.
• The volunteer-conference version of the same instruction, stated plainly: “Prepare and share a team playbook of exactly what is scripted to happen when. Assign one or more MCs to kick off and orchestrate the event. Assign people to introduce specific speakers.” The same section recommends “on duty” shifts so one person is not the single point of failure for every last-minute decision (devopsdays.org/organizing).
• The cue rows are the rows you rehearse. TEDx tells organizers to walk each speaker through five specific things a day or two before the show, at the venue: where they get ready and receive their microphone, where they sit, how they step on stage, how you will cue them when their time runs out, and how they exit (TEDx Organizer Guide, rehearsals). Every one of those is a row on a cue sheet before it is a conversation.
• Why the person holding the paper is not the person on stage: “The producer makes the plan, the stage manager gets the presenters ready, and the show caller says when everything happens” (MeyerPro). That split gets taught properly in Lesson 3.1. It is named here because a live podcast is the thing that forces it.
• Dedicated tools exist if the spreadsheet ever stops coping: Stagetimer for speaker countdown clocks, Rundown Studio for live-synced rundowns (rundownstudio.app templates). Neither is needed at your scale. Both are worth knowing the names of.

Your one move

Open your master sheet and add a tab called Run of Show. Give it seven columns: Start, End, Duration, What happens, Owner, Location, Cue or notes. Now write the August event top to bottom, from the earliest call time to the last item going out the door. Where you do not know something, type TBD in the cell rather than leaving the row out. Thirty minutes, done when the timeline runs unbroken from call time to load-out and every row has either an owner or a TBD.

A worked example: part of the August run of show (illustrative timings, not real Filmmakers Connect ones)

Every time below is invented to show the shape. Do not reuse them as a schedule.

Start	End	What happens	Owner	Location	Cue or notes
12:00	14:00	AV and podcast rig load-in	Sound supplier	Main hall	Venue lift booked to 14:00
13:00	15:00	Sponsor booth build, four booths	Sponsor lead	Foyer	Booth map printed and taped to the floor
14:00	14:20	Volunteer call time and briefing	Volunteer coordinator	Foyer	Everyone hears the whole day, not just their slot
15:00	15:40	Podcast tech check, all three mics live	Sound supplier	Stage	Levels saved and labelled
16:00	16:30	Guest call time, podcast guests	Guest liaison	Green room	Water, running order, and who walks them out
17:00	17:00	Doors	Check-in lead	Entrance	Walk-in playlist already running
17:45	17:50	Welcome and house rules	MC	Stage	Music fades on MC’s first step out
18:10	18:55	Live podcast, segment one	Host	Stage	Roll intro sting, then mics 1 to 3 live
18:55	19:05	Sponsor roll-in and booth callout	MC	Stage	Cue: on “let’s take a short break”
21:30	23:00	Load-out	Producer	Main hall	Venue hard stop, confirm it in writing

Notice what the sound supplier actually needs out of that table. Three rows, maybe four, and none of them are the booth build or the volunteer briefing. That is the cue sheet, and pulling it out takes about five minutes once the master exists.

Want to go further?

Make a second tab called Cue Sheet and copy across only the rows that contain a trigger: mic cues, music cues, roll-ins, slide advances, and the lines that fire them. Then write the podcast walk-on out in full, the way Logan does in the video, and mark the word the music swells on. Hand that tab to whoever will be calling the show while you are on the mic, and ask them to read it back to you. Whatever they stumble on is the part that is not written clearly enough yet.

The needle: an event is won before doors open, and this is the lesson where “before doors” stops being a figure of speech and becomes a row on a spreadsheet with a time in it.

Terms introduced

Terms introduced in this lesson

• Run of show
• Call time
• Doors
• Cue
• Cue sheet
• Production schedule
• BEO (banquet event order)

Each term links to the glossary, where it is defined by the way you just used it.

Check

Check yourself

1. Your sound volunteer asks for the run of show, so you send him the whole sheet: vendor arrivals, booth build, badge printing, the raffle, load-out. During the podcast he misses the music cue under the guest walk-on. What actually went wrong?

   The run of show should never have listed vendor arrivals in the first placeNothing you could control. Cues get missed, that is live eventsHe should have read the document more carefully before doorsHe was handed the master document instead of a stripped-down cue sheet, so the handful of things he needed were buried in everything he did not

2. You have always run your meetups off one sheet that holds the schedule and the cues together, and it has worked fine. In August you are in the chair with a mic on for the live podcast while a volunteer runs sound. Does the one-sheet approach still hold?

   No. The moment somebody other than you is calling cues, the merged sheet stops working, because it was only ever fully readable to the person who already had the show in their head. Pull the cue rows into their own sheet for whoever is callingYes, as long as you colour the cue rows differently so they stand outYes. One sheet is simpler, and simpler is better under pressureNo, and the fix is to drop the cues entirely and let the volunteer read the room

3. Your run of show says the sponsor video rolls at 7:40. At 7:40 your guest is mid-story with about three minutes left. What does that moment tell you about how the cue was written?

   The video should have been cut from the programThe person calling should have rolled it at 7:40 anyway and let the guest talk over itNothing useful. The guest should have finished on timeIt was written against the clock, so it breaks the moment anything runs long. Cues that survive a live room hang off something observable instead, usually a line somebody says

Check answers

You can move on when you can… name the three documents and who reads each one, write a cue that survives a guest running long, and say out loud the moment at which your one merged sheet has to become two sheets.

Mark this lesson complete

Go deeper

• Next up: 2.7 · The volunteer engine, where the call times you just wrote turn into stations, shifts, and an actual number of people to recruit.
• 3 Lessons Learned in Events in 2024, same producer, worth it for one anecdote at 1:41. She asks a venue for a platform, gets a platform, and finds out on the day that nobody thought to ask for stairs up to it. Her fix is not “ask better questions,” it is to document every answer somewhere searchable so the question never has to be asked twice. That habit is what turns a run of show into an asset instead of a one-off document.
• The SpotMe run of show guide and the Stagetimer template are the two clearest free write-ups of the master document, and Stagetimer’s is the better one on cues specifically. Both are vendor content with a product at the end of them. The templates are still good.