A run sheet is not a decorative attachment sent the evening before an event. It is the operating agreement between departments: what happens, when it happens, who owns it, what must already be true and who can change the plan.
When that agreement is weak, the team falls back to memory, private messages and individual assumptions. A five-minute delay then becomes a guest-holding problem, a speaker problem, a catering problem and eventually a client problem. A strong run sheet does more than describe the show. It creates one operational truth under pressure.
The operating model
I build the document through five controlled layers. First, define the immovable anchors: broadcast windows, doors, protocol arrivals, prayer times, transport departures, venue curfews and contracted performance slots. Second, work backwards to expose every prerequisite. Third, assign each action to one accountable role. Fourth, rehearse the normal sequence and its most credible exceptions. Fifth, freeze, distribute and govern the live version.
- Anchor: Record every externally fixed moment and its tolerance.
- Decompose: Turn each audience moment into the operational actions required to make it true.
- Integrate: Align show, front of house, protocol, transport, security, catering, venue and client actions on one clock.
- Assure: Test dependencies through desk checks, technical rehearsals and scenario exercises.
- Command: Issue one controlled version and define who may approve a live deviation.
This mirrors the logic of an incident action plan: objectives, assignments, communications and contingencies are made explicit for a defined operational period. The run sheet is not a substitute for a safety plan, emergency plan or technical cue sheet. It is the coordination spine that tells those plans when to activate and who makes the call.
Anatomy of a commandable line
“Stage ready” is not an action. “Stage manager confirms stage clear to show caller on radio channel 2” is. Every operational line should be understandable in ten seconds and contain enough information to be executed without interpretation.
- Planned time and duration: Use one time zone and a 24-hour clock for complex operations.
- Observable action: State what will be done or confirmed, not a vague status.
- Single owner: Name the accountable role, with a deputy in the contact plan.
- Location and channel: Identify where the action occurs and how completion is reported.
- Dependency: State the condition that must be true before release.
- Decision gate: Name the person who can hold, skip, shorten or proceed.
- Fallback: Define the first safe alternative, with a reference to the relevant plan.
Keep the public agenda separate. Guests may see “Dinner, 21:00.” Operations needs service briefing complete, dietary exceptions confirmed, VIP tables released, show lighting set and the first programme cue protected. One document cannot serve both audiences without becoming either too vague to operate or too dense to communicate.
Control time, versions and decisions
The master clock must be declared at the top of the sheet and synchronized across show control, radios, transport and venue operations. For each fixed anchor, record an allowable tolerance and the latest decision point. A broadcast may have zero tolerance; a networking segment may be compressible by ten minutes. That distinction creates recovery options before the show is late.
Every page should carry a version number, issue time and owner. During rehearsals, proposed changes enter a short change log showing the request, reason, affected departments, decision and approval time. Once the live version is frozen, only the designated show caller or event director should authorize timing changes. Superseded copies are removed from shared channels and printed control positions.
Use three states for each milestone: planned, confirmed ready and released. “Ready” means evidence exists. “Released” means the authorized controller has allowed the action to begin. This prevents a technical team interpreting readiness as permission while protocol is still holding movement.
Write transitions and exceptions
Most visible failures occur between programme items. A speaker finishes early, an award recipient is not at stage left, a video ends while the next microphone remains muted. Write transitions as deliberately as headline moments:
- who owns the handover;
- what the audience sees and hears;
- what production, front of house and hospitality do;
- the confirmation phrase that completes the handover; and
- the holding state if the next item is not ready.
Rehearse exceptions that are plausible and consequential: a principal arrives early, a speaker is absent, content fails, food service slips, weather crosses a trigger or a transport route closes. The objective is not to script every crisis. It is to prove that the team knows who decides, what information is required and which safe state protects the audience while the decision is made.
KPI dashboard
The ranges below are recommended operating targets, not universal standards. Teams must calibrate them to event scale, risk, venue, programme and authority requirements.
| KPI | Formula | Cadence | Recommended target |
|---|---|---|---|
| Line ownership completeness | Lines with owner ÷ total operational lines × 100 | Each issue | 100% |
| Dependency confirmation | Confirmed critical dependencies ÷ due critical dependencies × 100 | Daily, then each briefing | ≥98%; 100% before release |
| Milestone variance | Actual time − planned time | Live, at anchors | Within declared tolerance |
| Uncontrolled change rate | Unlogged live changes ÷ all live changes × 100 | Per operational period | 0% |
| First-call acknowledgement | Cues acknowledged first time ÷ cues issued × 100 | Rehearsal and live | ≥95% |
| Transition readiness | Transitions passed in rehearsal ÷ tested transitions × 100 | Each rehearsal | ≥95%, critical transitions 100% |
| Recovery consumption | Buffer minutes used ÷ planned buffer minutes × 100 | Live every 30 minutes | <50% before final anchor |
Illustrative worked example
Illustrative scenario only; this is not an Ahmed or client outcome. A conference has doors at 18:30, a live broadcast at 20:00 and a venue curfew at 22:30. Rehearsal reveals that an award transition takes four minutes rather than the planned two. There are six awards, creating a potential 12-minute overrun.
The team does not wait for showtime. The run-sheet owner records the variance, and the event director approves three controls: pre-position recipients two items earlier, combine stage photography into one final call and protect a six-minute recovery buffer before broadcast. At the final rehearsal, five transitions take two minutes and one takes three. Transition readiness is therefore 5 ÷ 6 = 83%, below the recommended 95% target. The failed transition is rehearsed again and the broadcast anchor remains unchanged.
During the live show, the opening speaker runs three minutes long. The show caller records a +3-minute variance and uses three of the six recovery minutes. Recovery consumption is 3 ÷ 6 = 50%. Because the threshold has been reached, no further discretionary extensions are accepted without event-director approval. The number is useful because it turns “we are running a little late” into a controlled decision.
Leading and lagging indicators
Leading indicators show whether the operation is becoming ready: ownership completeness, dependency confirmation, rehearsal pass rate, acknowledgement rate and unresolved change requests. They can still change the outcome. A falling confirmation rate 24 hours out should trigger focused follow-up, not optimistic reporting.
Lagging indicators describe what already happened: anchor variance, missed cues, unplanned holds, programme items skipped and actual finish time. They are essential for the post-event review, but they arrive too late to protect the current show. A useful dashboard pairs both types so leadership can see readiness before doors and delivery quality after close.
Evidence and standards
- FEMA: Incident Action Plan development and ICS forms describes objectives, assignments and dissemination through an operational planning cycle.
- UK Health and Safety Executive: Managing an event covers phased management systems, coordination, information, competence, monitoring and review.
- UK Health and Safety Executive: Planning for incidents and emergencies requires clear roles, proportionate procedures, testing and validation.
- ISO 20121:2024 provides the international management-system framework for responsible event delivery and continual improvement.
