Event command centres are not “security rooms”; they are operations centres that connect incident reporting, guest experience, and real-time response.
The objective is incident prevention and continuity: detect early, decide fast, and communicate clearly.
The Minimum Dashboard Stack
A command centre works when every dashboard answers a decision question. Avoid vanity screens that look impressive but don’t drive action.
- Ingress / egress flow with queue pressure indicators
- Incident log with categorisation and escalation timers
- Medical desk status (assets, response times, hotspots)
- Credential exceptions and access-control overrides
- Weather and venue ops updates (if applicable)
- Comms status (radio nets, redundancy, key contacts)
- CCTV / video wall priorities (what’s watched, by whom, and when it rotates)
- Resource tracker (teams, locations, response times, out-of-service notes)
- Fire & life safety status (alarms, exits, muster points, extinguisher coverage)
- Social / guest sentiment and rumour monitoring (optional; use for early warning, not enforcement)
Shift Routine
The routine matters more than the tooling: short shift briefings, clear triggers for escalation, and a single source of truth for incident status.
Define what qualifies as “major incident” before doors open. Don’t discover thresholds during a surge.
Roles, Escalation, and Seating Plan
A command centre fails when it’s unclear who decides and who communicates. Make authority explicit and keep communications consistent.
- Incident commander: decision authority for pause/evacuate/resume triggers
- Ops lead: coordinates security + venue operations actions on the ground
- Comms lead: owns radio discipline, message consistency, stakeholder updates
- Recorder: maintains the incident log, timestamps, and decision notes
- Liaisons: medical, venue ops, vendor management, and VIP liaison (as needed)
Playbooks That Actually Work
Playbooks should be written for the person on shift, not for a committee. One page, plain language, clear roles, and communications templates.
- Trigger → action → owner → comms template
- Fallback options if primary channel fails
- Decision authority map (who can pause / evacuate / resume)
Checklist
- Define incident thresholds and decision authority.
- Stand up a single incident log and comms matrix.
- Validate redundancy: power, radios, internet, key contacts.
- Run a 20-minute tabletop for top 3 scenarios.
- Confirm command centre roles, seating plan, and escalation ladder.
- Align security actions with guest experience goals.
Operational design must follow local regulations and venue authority requirements.