run-an-event-command-center

name	run-an-event-command-center
category	start
description	Coordinate live event decisions, incidents, resources, communication, and recovery through one operating structure. Use when a large, distributed, high-profile, or high-consequence event needs real-time cross-team control.

run-an-event-command-center

When to use

• Use when multiple rooms, venues, suppliers, audiences, or incident functions need shared live coordination.
• Use a run of show and single event lead for a small event with one bounded delivery team.

Preconditions

• Confirm event scope, operating periods, command location, decision authority, emergency-service boundary, venue and safety leadership, safeguarding, medical, accessibility, security, communications, privacy, and recovery owners.

Procedure

1. Create a command structure record with primary, alternate, role, authority, contact, shift, location, and conflict information.
2. Define decision authority for normal operation, pause, room closure, access response, evacuation, medical escalation, cancellation, communication, spending, and recovery.
3. Build a common operating picture from program, attendance, staffing, venue, weather, transport, access, production, security, medical, supplier, and communications sources.
4. Establish incident triage by immediate life safety, safeguarding, accessibility, service impact, spread, evidence risk, and decision deadline.
5. Use one live decision log for time, report, source, confidence, owner, alternatives, decision, action, communication, review, and closure.
6. Set radio, phone, digital, runner, backup-power, translation, and accessible communication protocols with message discipline.
7. Hold brief operating cycles to reconcile status, open incidents, resource conflicts, forecast risk, and decisions without obstructing urgent response.
8. Coordinate operational handoff across shifts and teams using open actions, exact state, changed assumptions, authority, and acknowledgement.
9. Rehearse lost communications, simultaneous medical and access incidents, severe delay, unsafe density, venue loss, misinformation, and leader absence.
10. Demobilize through participant support, evidence preservation, supplier and venue handoff, incident follow-up, public commitments, welfare, and improvement review.

Failure plan

• Defer immediately to emergency services, venue safety authority, or qualified incident owners where their authority applies.
• Stop rumor, unverified cause, personal data, medical detail, blame, and security-sensitive information from entering broad channels.
• Do not let commercial, schedule, executive, or publicity pressure override life safety, safeguarding, access, or evidence-based pause decisions.

Done

• A command structure record proves primary and alternate roles, decision authority, channels, shifts, and escalation
• A common operating picture and live decision log preserve sourced status, incidents, actions, communications, reviews, and unresolved uncertainty
• Incident triage and operational handoff are exercised under simultaneous failure and leader absence
• A recovery and closeout report verifies participant support, service disposition, evidence, commitments, welfare, corrective actions, and owner acceptance