Working context
A run of show is more than a list of performance times. It connects access, load-in, technical preparation, rehearsal, public opening, cues, transitions, close, and load-out. It should make important dependencies visible early enough to resolve them, while remaining readable when time is short and attention is divided.
The document works best as a shared operational model. Each team contributes verified information, open questions have owners, and changes are recorded in one authoritative place. The goal is not to predict every possibility; it is to give the production a common sequence and a disciplined way to respond when reality differs from the plan.
SECTION 01Advance the facts and the unknowns
Begin with event format, venue access, stage and room dimensions, power, rigging limits, equipment, staffing, performer needs, public schedule, accessibility, and local restrictions. Mark each item as confirmed, assumed, or unresolved. Assign an owner and deadline to every unresolved dependency. This prevents an optimistic draft from being mistaken for a completed advance.
SECTION 02Write handoffs as operational cues
For each milestone, identify who is responsible, who needs advance notice, what must already be true, and what confirms completion. Include setup, checks, rehearsal, doors, programme segments, transitions, breaks, and close. Use consistent time notation and cue language. Separate public timing from technical detail where necessary, but keep the relationship between them obvious.
SECTION 03Prepare safe recovery paths
Identify decisions that may need a fallback: delayed access, unavailable equipment, a late performer, a failed signal path, weather, shortened changeover, or restricted audience movement. Define who can authorise a change and which priorities must be protected. A fallback should preserve safety, communication, and the essential audience experience rather than attempt to reproduce every original detail.
Carry these checks into the decision.
- Confirm venue, access, schedule, stage, power, and staffing facts.
- Assign an owner and deadline to every open dependency.
- Use consistent cue language and one authoritative timeline.
- Show prerequisites and verification points for critical handoffs.
- Record fallback authority, communication, and safety priorities.
Keep evidence, context, and limitations together.
This guide is designed to organise a practical review. Confirm important facts with the responsible venue, provider, manufacturer, public authority, or qualified professional. Record the date and source of information that can change, and distinguish verified requirements from preferences or estimates.
Good planning does not remove uncertainty. It makes assumptions visible, gives open questions an owner, and creates a clearer point for responsible decisions.
Questions to test
Useful answers begin with a precise question.
How much detail belongs in the main timeline?
Include the information needed to coordinate disciplines and decisions. Dense patch, focus, or equipment detail can live in linked documents, but their milestones and dependencies should remain visible.
Who should own the run of show?
One responsible role should maintain the authoritative version, while every discipline verifies its own information and reports changes through the agreed communication path.
When should the timeline be frozen?
Set a controlled version before execution, but continue recording necessary changes. A freeze means changes are managed deliberately, not that new information is ignored.
Bring the whole decision back into view.
A useful run of show reduces ambiguity without pretending that live work is predictable. It gives people the same sequence, exposes dependencies, and makes responsible changes easier to communicate.
This page provides general educational information. It does not replace technical, legal, medical, financial, safety, or other professional advice for a particular situation.