The show run sheet is the document that keeps every department synchronised from load-in through strike. It’s not a call sheet (which handles logistics), not a cue sheet (which handles technical execution), and not a production schedule (which maps the weeks before the show). It’s the minute-by-minute operating document for the day of show — and a poorly constructed one creates more problems than it solves. Here’s how to build one that crew actually use.
What a Run Sheet Is Not
Before establishing what a run sheet should contain, it’s worth being explicit about what it shouldn’t be. A run sheet is not an internal monologue for the stage manager. It’s not a document so detailed that finding any specific piece of information requires reading paragraphs of context. It’s not formatted for the production manager’s reference while the crew are navigating it under pressure at seven minutes to doors. And it’s absolutely not a living document that exists only on one person’s laptop — it must be physically printed or accessible via a show control system at every relevant position.
The Architecture: Columns That Actually Matter
A functional run sheet operates on a time-column structure. Essential columns include: Time (the absolute clock time or show time reference); Duration (how long this item runs); Action (what happens); Department (who is responsible for the action); and Notes (any relevant operational context that doesn’t fit the action column). Optional but frequently useful: Cue References linking the run sheet moment to the LX, sound, or automation cue that fires.
The time column should always express both absolute time (’20:47′) and show time (‘T+47:00’), accounting for the fact that a show that was called for 20:00 and started at 20:12 will have crew calculating elapsed time from two different reference points. Timecode references should appear wherever the run sheet moment correlates to a SMPTE timecode cue in the show — this connects the operational document to the technical document.
Language: Clarity Over Elegance
Run sheet language should be imperative, unambiguous, and minimal. ‘SM calls places for Act 2’ is clear. ‘Stage management to initiate the process of calling performers to their positions for the commencement of the second act’ is a run sheet written by someone who has never used one under pressure. Every crew member reading a run sheet is managing multiple concurrent responsibilities — the document must give them what they need in the time it takes to glance at it.
Avoid internal jargon that isn’t universal across departments. ‘Pre-set to Act 2 trim’ makes sense to the fly operator but may mean nothing to the automation operator who needs to reset their system simultaneously. Where actions are department-specific, mark them clearly with department codes in the action or department column so crew members can filter for their relevant rows.
Incorporating Technical Cue References
The run sheet bridges the operational and technical worlds of a production. For shows running timecode — whether SMPTE or MIDI timecode from the audio system — the run sheet should reference the timecode address corresponding to each major event. For manually-called shows, references to console cue numbers (‘LX Q420’, ‘Sound Q12’) give the operator a cross-reference to their technical document that speeds up troubleshooting when something misaligns.
Productions using show control systems — QLab driving audio, video, and automation cues from a single platform, or Medialon or Alcorn McBride ShowTouch for complex multi-system coordination — should reference show control cue IDs in the run sheet. This creates the chain from Stage Manager’s go button to QLab cue to all-systems execution that can be audited when something fires at the wrong moment.
Versioning: The Run Sheet Is Always Wrong
Accept from the start that the run sheet will change. Every technical rehearsal generates edits, every production meeting produces adjustments, and every day of show creates unexpected scenarios. A disciplined versioning system — run sheet v1.0, v1.1, v2.0 — with dated distribution records ensures that crew aren’t working from a document superseded two days ago. Change highlights in subsequent versions (track changes or colour coding) help crew identify what’s new without re-reading the entire document.
The final show run sheet should be distributed to all department heads and key operational positions before crew call on show day — not during load-in, not during soundcheck, before the day begins. Crew who arrive to find a run sheet on their console position, read it, and ask questions before the pressure is on are crew who run the show well. Crew handed a run sheet at doors are crew managing the document and the show simultaneously — which always benefits one at the expense of the other.
