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 covered here 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 have not received the latest update; decisions made by the incident commander may be based on an incomplete picture (Federal Emergency Management Agency [FEMA], 2010; Department of Homeland Security [DHS], 2017).

A defined information flow framework specifies who should report what information, to whom, by what means, and under what circumstances. Ground-level staff report incidents and conditions to their direct supervisor using defined report formats, not directly to the command center — this maintains span-of-control discipline and prevents the command center from becoming a direct-access inbox for every field worker on the site. 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, in turn, 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 reaching staff simultaneously from different sources. Cross-functional communications between departments, such as medical to security or security to operations, are routed through the command center or through designated liaison positions, not directly between departments at field level (DHS, 2017; FEMA, 2010).

The precision required in specifying these procedures matters. A procedure that states “the incident control room must be informed” is not adequate. An effective procedure specifies: “The deputy incident commander must inform the incident control room immediately upon receiving a report of a crowd incident involving more than ten people.” The who, what, when, and how must all be defined for the procedure to be executable by any trained personnel member in the command center without requiring additional judgment about what the procedure requires (FEMA, 2010).

Information flow procedures must also address what happens when the standard chain is unavailable — when the designated supervisor cannot be reached, when the command center is managing a concurrent major incident and cannot receive routine reports, or when a field worker witnesses an incident that requires immediate escalation beyond their normal reporting chain. Each of these contingencies requires a defined alternative path. A framework that functions only under normal conditions provides limited operational value precisely in the circumstances where clear, rapid information flow matters most.

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 most.

Using designated call signs consistently for all transmissions is the foundation of radio discipline. Call signs identify the transmitting and receiving party clearly and 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 on the same channel. Before any transmission, the transmitting party must check that the channel is clear: transmitting over an ongoing conversation on the same channel blocks both the original transmission and the new one, creating gaps in communication for all users. The standard message structure — identifying the recipient’s call sign, waiting for acknowledgement that the channel is monitored, then delivering the message concisely — ensures that transmissions reach the intended recipient without wasting channel time (DHS, 2017; FEMA, 2010).

Concise message delivery is not optional at busy events. Long-winded transmissions block the channel for all other users. Messages should contain exactly the information required and nothing else. 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 — prevents the recipient from having to seek clarification before they can act. An action instruction that has not been confirmed as received cannot be assumed to have been acted upon; receipt confirmation is the final step in every action-requiring transmission (FEMA, 2010).

Radio communication during an emergency produces a specific failure mode that pre-event training must address directly: personnel under high stress tend to transmit at length, rapidly, and with emotional tone rather than delivering structured, concise reports. This degrades channel quality at exactly the moment when clean, rapid communication is most critical. Training that includes practice delivering structured reports under simulated pressure — not just explanation of the correct format — produces measurably better performance during actual incidents. At minimum, a brief walk-through practice scenario should be part of every pre-event briefing for supervisory and command personnel (DHS, 2017).

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, without relying on memory to recall what information the command center needs. A familiar structure helps the command center receiver anticipate and record each element immediately, ready for action without needing to ask follow-up questions that delay response (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. Briefing materials — a laminated quick-reference card that fits in a staff member’s vest pocket — provide a reliable memory aid for personnel who may not use the format frequently enough to have it memorized. The goal is not that personnel recite the acronym under pressure but that they do not omit critical information when reporting an incident to the command center.

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 maintained in real time from the opening of the event site through the end of load-out serves multiple functions simultaneously.

For 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 managing a different situation when an incident was first reported can review the log to understand the current status without interrupting other personnel or requesting a verbal update that consumes communication channel time. During a major incident where multiple significant situations are developing simultaneously, the log is the only mechanism by which any individual command staff member can maintain an accurate overall picture of all active events (FEMA, 2010).

For decision accountability, the event log records who made each significant decision, when, and based on what information was available at the time. This is the contemporaneous record that answers, in post-event review or litigation, the questions “When did you first know about this?” and “What did you do in response?” A log entry made at 19:47 recording that the incident commander was informed of crowd density building at the north barrier, and a subsequent entry at 19:52 recording the decision to open the secondary viewing area, documents a timely and proportionate response. The absence of such entries, or their reconstruction after the fact, cannot provide equivalent accountability (FEMA, 2010; DHS, 2017).

Resource tracking via the log enables command staff to account for deployed resources across the event at any point. Logging when resources are dispatched, when they arrive at an incident location, when they clear and return to availability, and what actions they took enables command staff to understand current resource availability without polling each resource individually. This becomes critical during periods of concurrent high demand, where the command center must allocate limited medical, security, and operations resources across multiple active situations.

Pattern recognition is a less obvious but significant value of comprehensive logging. 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 a command-level response but collectively indicate a developing problem requiring intervention before it escalates. An event that generates twelve individual incident entries across two hours may or may not reveal a pattern; a command center without a log that enables review of those twelve entries as a sequence cannot make that determination (FEMA, 2010).

Log Retention and Legal Implications

The event log is a legal document from the moment it is created. Entries are contemporaneous records that may be subpoenaed in personal injury litigation or regulatory investigation arising from any event-related incident. The log must be maintained without alteration after the event closes, and preserved for a period consistent with the applicable statute of limitations for personal injury claims in the relevant jurisdiction. Given that statutes of limitations for personal injury commonly run for two or more years, and that complex litigation may involve multiple parties across extended timelines, a minimum two-year retention policy is appropriate for events of significant scale (FEMA, 2010).

Log entries must be factual and attributable. Each entry must record what was communicated or decided, by whom, and when — not a characterization or interpretation of events. An entry that records “Medical reported patient with heat exhaustion at grid D4 at 15:32; Incident Commander requested ambulance standby at 15:33” is a factual record of two events. An entry that records “Medical handled a heat case efficiently” is a characterization that carries no evidentiary value and may be challenged. Personnel assigned to log-keeping roles must understand that they are creating a legal record, and that accuracy, specificity, and absence of editorial comment are the standards to which every entry must be held (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, command center staff, supervisors, gate staff, security, and medical personnel.

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, and the alerting cascade for different types of incidents — who to call, how, and in what sequence. Personnel must know the location of the command center and how to contact it by both radio and telephone, and must be briefed on any event-specific terminology or coded language in the communications plan. Coded language in particular presents a training risk: codes that are not universally understood across all organizations operating at the event — event staff, venue staff, contracted security, medical provider — create communication breakdowns in the multi-agency environment where clear communication is most critical. NIMS explicitly requires plain language rather than codes in inter-agency communications precisely because of this failure mode; the same principle applies to any event where multiple organizations share radio channels (FEMA, 2010; DHS, 2017).

Personnel who work at remote locations — off-site command positions, remote parking operations, 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 to confirm that connectivity is reliable and that they can reach the command center through the designated channel. A remote position that cannot reliably contact the command center is operationally disconnected from the event’s coordination structure, and its communications plan failures will only become apparent at the moment they are needed most.

A formal communication test — conducted before the event opens with all departments and all remote positions actively participating — serves both as a technical connectivity test and as a confirmation that personnel in each position know how to reach the command center and how to use the communication tools they have been issued. A test that reveals a radio dead zone, a misassigned channel, or a gap in the call sign directory before the event opens can be corrected with time to spare; the same discovery during an active incident cannot. The test should be documented: which positions completed a successful check-in, which were unreachable and what corrective action was taken, and the time at which the full communication system was confirmed operational for the event period (FEMA, 2010; DHS, 2017).

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.