Effective communication at a live event is not simply a matter of having enough radios and knowing who to call. It requires standardized procedures for how information is transmitted, how messages are structured, how incidents are reported, and how all of this is documented in real time. Without these standards, communication during normal operations is inefficient; during an incident, it can fail catastrophically.

The communication protocols, situation report formats, and logging practices described in this article are derived from both event safety guidance and the National Incident Management System (NIMS) framework — the same systems used by professional emergency responders. Applying these standards at live events is not bureaucratic overhead. It is the proven approach to maintaining coordinated situational awareness when the stakes are highest.

The Framework for Information Flow

Every organization involved in a live event — event production, venue operations, security, medical, catering, law enforcement, fire services — generates and needs to receive information. Without a defined information flow framework, each organization manages its own information independently, sharing selectively and inconsistently. This creates information silos: the command center may not know about a situation that medical and security are both already aware of; ground-level staff may act on outdated information because they haven’t received the latest update; decisions made by the incident commander may be based on an incomplete picture (Federal Emergency Management Agency [FEMA], 2010; DHS, 2017).

A defined information flow framework specifies: who should report what information, to whom, by what means, and under what circumstances. Specific examples from NIMS and FEMA guidance include (DHS, 2017; FEMA, 2010):

• Ground-level staff report incidents and conditions to their direct supervisor using defined report formats, not directly to the command center — maintaining span-of-control discipline and preventing the command center from becoming a direct-access inbox for every field worker
• Supervisors escalate reports to the command center when incidents exceed their authority to resolve, when they require resources beyond their allocation, or when they identify patterns that the command center needs to be aware of
• The command center communicates decisions and instructions downward through the same supervisory chain, not directly to individual ground-level workers — maintaining clear lines of authority and preventing conflicting instructions from different sources
• Cross-functional communications (medical to security, security to operations) are routed through the command center or through designated liaison positions, not directly between departments at the field level

The statement “the incident control room must be informed” is not adequate as a procedure. Effective procedures specify: “The deputy incident commander must inform the incident control room immediately upon receiving a report of a crowd incident involving more than 10 people.” The who, what, when, and how must all be specified (FEMA, 2010).

Radio Discipline

Radio discipline — the consistent application of correct radio communication practices by all radio users — is essential to the effective use of radio channels during events. Undisciplined radio use wastes channel time, obscures important messages, and degrades the ability of all users to communicate when it matters. The components of radio discipline include (FEMA, 2010; DHS, 2017):

• Call signs: using designated call signs consistently for all transmissions. Call signs identify the transmitting and receiving party clearly, without ambiguity. Using names, titles, or informal references introduces identification errors and creates confusion in multi-agency environments where the same name or title may apply to different people from different organizations.
• Listen before transmit: checking that the channel is clear before beginning a transmission. Transmitting over an ongoing conversation on the same channel blocks both the original transmission and the new one.
• Concise message delivery: identifying the recipient’s call sign, waiting for acknowledgement that the channel is monitored, then delivering the message concisely. Long-winded transmissions block the channel for all other users. Messages should contain exactly the information required and nothing else.
• Message purpose clarity: making the purpose of the message clear at the outset — whether it is a request for information, a report of a situation, a request for action, a command, or an advisory. A message whose purpose is unclear requires follow-up clarification, consuming additional channel time.
• Receipt confirmation: confirming that a message has been received and understood, particularly for action instructions. An action instruction that has not been confirmed as received cannot be assumed to have been acted upon.

The Situation Report: CHALET Format

When a field worker or supervisor is reporting an incident to the command center, a standardized situation report format ensures that all critical information is transmitted in a consistent, readily understood structure. The CHALET format, used in emergency services and recommended for live event communications, provides this structure (FEMA, 2010; DHS, 2017):

The CHALET format works equally well for any type of incident — medical, security, fire, structural, crowd — because it focuses on information categories rather than incident-specific content. A practiced format helps the person providing the report include all necessary details systematically, even under stress. A familiar structure helps the command center receiver anticipate and record each element, ready for immediate action (FEMA, 2010).

The CHALET format should be included in pre-event briefings for all supervisory personnel and for any staff who may be the first on-scene reporter of an incident. Practice — even a brief walk-through of an example situation report during the briefing — significantly improves the quality of actual situation reports during incidents.

Record Keeping and the Event Log

Keeping records and logging information throughout the event is one of the most important and most frequently neglected operational functions. A comprehensive event log serves multiple critical purposes (FEMA, 2010):

• Situational awareness: a running log of all significant communications, incidents, decisions, and actions maintains a shared picture of what is happening across the event. Command staff who were handling a different situation when an incident was first reported can review the log to understand the current status without interrupting other staff.
• Decision accountability: the event log records who made each significant decision, when, and based on what information. This is the contemporaneous record that answers the questions “When did you first know about this?” and “What did you do in response?” in post-event review or litigation.
• Resource tracking: logging when resources are dispatched, when they arrive at an incident location, when they clear, and what actions they took enables command staff to track resource availability and utilization throughout the event.
• Pattern recognition: a log that accumulates multiple similar incident reports over the course of an event enables command staff to recognize patterns — multiple heat illness presentations in a specific area, multiple reports of queue congestion at a specific gate — that individually might not trigger action but collectively indicate a developing problem requiring intervention (FEMA, 2010).

The event log must be contemporaneous — entries must be made at the time of the communication or decision, not reconstructed after the fact. The legal and operational value of a log that was written after the event is substantially lower than one maintained in real time. Log entries must include a timestamp, the call sign or name of the person making the entry, and a factual description of the communication, decision, or action recorded — not an interpretation or conclusion, just a factual account (FEMA, 2010; DHS, 2017).

Briefing and Training All Personnel

All organizations involved in the event are responsible for ensuring their workers are adequately trained and briefed before the event opens. This responsibility extends to all roles that involve communication: radio users, control room staff, supervisors, gate staff, security, and medical personnel (FEMA, 2010).

Adequate pre-event briefing covers:

• Each worker’s specific role and responsibilities at their assigned position
• The radio channel assignments and call signs relevant to their function
• The situation report format they will use to report incidents
• The alerting cascade for different types of incidents — who to call, how, in what sequence
• The location of the command center and how to contact it by radio and telephone
• Any event-specific terminology or coded language in the communications plan

Personnel who work at remote locations off-site — off-site command room staff, remote parking operations personnel, transportation coordinators — also require briefing on the event’s communication protocols, even though they will not be on the main venue site. Their communication links with the main command center must be tested before the event opens (FEMA, 2010).

References

Department of Homeland Security. (2017). National Incident Management System (3rd ed.). FEMA.

Federal Emergency Management Agency. (2010). Special events contingency planning job aids manual. U.S. Department of Homeland Security.