A command centre is not a room filled with radios. It is a decision system. Its value appears when information arrives faster than any one person can process it and the event still needs one coherent direction.
Without structure, every issue is repeated loudly, senior people become an audience, and nobody is certain who may decide. A strong command centre does the opposite: it filters noise, protects authority and gives each workstream a reliable operating rhythm.
Command is a system
Start with decision rights, not furniture. Name the event director, safety lead and operational deputies. Define who may open or hold doors, pause an activity, change the programme, approve unplanned cost, communicate with authorities and activate an emergency response. Record these limits in the event operations plan and brief them before show day.
The command team should distinguish three kinds of work:
- Routine control: milestones, guest flow, production status, transport and supplier coordination.
- Exception management: a deviation that can be resolved within an agreed tolerance.
- Incident command: a safety, security or business-continuity issue requiring a named incident lead and formal escalation.
This distinction prevents a delayed delivery from consuming the same channel and senior attention as a medical incident.
The operating model
A practical model has five layers. Each layer has one accountable owner even when several teams contribute.
- Sense: workstream leads monitor their zone, people, equipment and next milestone.
- Verify: the command desk separates an observed fact from an assumption and confirms the source.
- Assess: the relevant lead states impact on safety, guest experience, programme, cost and dependent teams.
- Decide: the authorised person selects an option and sets the next review time.
- Close: the action owner confirms completion; the logger records the result and any residual risk.
Use a RACI-style responsibility map for critical decisions, but keep live-event language simple: owner, approver, informed parties and deadline. A decision that requires six approvals in the final hour is not governed; it is trapped.
The command channel carries verified, event-wide information. Separate channels can serve production, front of house, transport, protocol, venue, logistics and safety. Workstream leads consolidate updates rather than allowing every radio user to report directly into command.
Information rhythm
Before doors, run scheduled readiness calls at intervals suited to the event: for example T-120, T-60, T-30 and T-15. During live operation, use a short status cycle based on programme complexity. Each lead reports only five fields:
- Current status against the next milestone.
- Change since the previous report.
- New or increasing risk.
- Decision or resource required.
- Time of the next meaningful update.
During an incident, move from scheduled to event-driven reporting. Radio calls should use location, fact, impact, request and confirmation. “West entrance, queue has reached the second barrier, estimated wait twelve minutes, request two stewards” is actionable. “The entrance is getting bad” is not.
The decision log should capture timestamp, source, issue, options, decision, approver, owner, review point and closure. This protects handovers and creates evidence for the debrief without turning the live room into a paperwork exercise.
KPI dashboard
The ranges below are recommended operating targets, not universal standards. Teams must calibrate them to venue capacity, authority requirements, event risk, technology and contract obligations.
| Metric | Formula | Cadence | Recommended target |
|---|---|---|---|
| Milestone readiness | Ready critical milestones ÷ due critical milestones × 100 | Each readiness call | 100% for safety-critical; at least 95% overall |
| Decision response time | Decision timestamp − verified escalation timestamp | Per escalation; 30-minute trend | Under 5 minutes for priority-one operational decisions |
| Incident acknowledgement | Acknowledgement time − first report time | Per incident | Under 60 seconds on the command channel |
| Action closure rate | Actions closed by due time ÷ actions due × 100 | Every 30 minutes | At least 90%; 100% for critical actions |
| Information accuracy | Verified updates requiring correction ÷ verified updates × 100 | Hourly | Below 5% correction rate |
| Radio congestion | Blocked, repeated or non-actionable calls ÷ sampled calls × 100 | 15-minute sample each hour | Below 10% |
| Open high risks | Count of untreated high risks past review time | Each readiness call | Zero before doors |
A dashboard is a prompt for attention, not a substitute for judgement. A green average must never hide one unresolved life-safety control.
Leading and lagging indicators
Leading indicators reveal whether control is weakening before the audience feels it. Examples include missed readiness checks, actions nearing deadline, increasing radio repetition, an unresolved permit condition, falling steward coverage or a queue approaching its intervention threshold.
Lagging indicators describe what has already happened: incidents, programme delay, guest complaints, unplanned cost, medical cases or a missed opening time. Both matter, but command teams should spend most of their live attention on leading signals because that is where intervention can still change the outcome.
Illustrative worked example
Illustrative scenario only; this is not an Ahmed or client result. A 6,000-person conference is due to open at 18:00. At T-30, seven of eight critical milestones are ready: registration, security, medical, front of house, transport, venue and catering. The final production content check remains open.
Milestone readiness is therefore 7 ÷ 8 × 100 = 87.5%, below the recommended 95% overall target and below the 100% expectation if that content is classified as show-critical. The production lead verifies that a backup version is approved and can run immediately. Command selects the backup at 17:34, records the content correction for later, and closes the action at 17:39. Decision response time is five minutes; the critical milestone reaches ready status before T-15.
The lesson is not that every deviation requires a delay. It is that the decision threshold, backup and authority were established before pressure arrived.
Room and tools
Give the room only what helps decisions: controlled run sheet, venue and evacuation maps, contact directory, risk and incident forms, programme clock, weather and transport status, CCTV or counting information where lawful and available, chargers, backup communications and a quiet position for critical calls.
Control access. People in the room should decide, log or provide essential information. Curious stakeholders can receive a scheduled situation report elsewhere. When a significant incident starts, appoint an incident lead and keep routine operations under a deputy; otherwise one problem can pull the entire event off course.
A good command centre makes the event feel quieter as complexity increases. Calm is not a personality trait here. It is the visible result of clear authority, verified information and disciplined closure.
Evidence and standards
This operating model is informed by authoritative frameworks, adapted for event delivery rather than presented as certification advice:
- FEMA/USFA National Incident Management System: Command and Coordination, which separates tactical activity, incident support, policy decisions and public communication.
- UK Health and Safety Executive event safety guidance, covering planning, management, crowd controls and post-event review.
- ISO 31000:2018 Risk management guidelines, for identifying, treating, monitoring and communicating risk.
- ISO 22301:2019 Business continuity management systems, for preparedness, response and recovery from disruption.
