Reviewing Communications After the Incident: Turning Radio Traffic Into Lessons

Why Communications Is a Recurring Theme

Read enough serious incident reviews and a pattern jumps out. The tactics were often reasonable. The staffing was often adequate. But the communications broke down somewhere, and that breakdown either caused the problem or made it worse. This is not because radio operators are careless. It is because communication is the connective tissue of the whole operation, and connective tissue is where stress shows up first.

Under pressure, people talk faster, key up longer, and forget to confirm that a message was received. Channels get crowded. Background noise climbs. The very moment you most need clean, disciplined radio traffic is the moment it is hardest to produce. That is why comms deserves its own attention in the after-action process rather than being folded into a single general debrief where it gets a passing mention.

The core reason to review comms separately: almost every other fireground decision depends on information moving correctly. If accountability, water supply, or a rapid intervention deployment failed, there is a strong chance a communications gap sits underneath it. Reviewing the traffic is often the fastest way to understand what the crews actually knew, and when they knew it.

What to Look At: The Comms Review Checklist

A good comms review is not a vague conversation about whether the radios worked. It is a structured look at specific, answerable questions. Walk through these areas for any incident worth reviewing.

• Channel plan. Was the right channel or talkgroup plan used for the size and type of the incident? Did the incident move to a tactical channel when it should have, or did everything stay on the dispatch channel? Did everyone actually make the move, or did some units get left behind on the old channel?
• Key message reception. Did the critical messages get heard and acknowledged? A benchmark report, a change in strategy from offensive to defensive, an evacuation order. An order that is transmitted but not acknowledged is not communication, it is hope.
• Missed and stepped-on transmissions. How often did two units key up at the same time and cancel each other out? Were there transmissions that clearly went unanswered? These show up plainly in a recording.
• Dead spots and coverage. Were there locations, such as basements, high-rise interiors, or large-area structures, where portables could not reach the incident or dispatch? Coverage problems are equipment and infrastructure issues, not discipline issues, and they need to be logged as such.
• Span of control and channel loading. Were too many people trying to talk to one person on one channel? When a single channel carries more traffic than it can hold, important messages get buried. This is a command structure issue as much as a radio issue.
• Mayday handling. If a mayday was declared, how was it received and managed? Did the channel get cleared for it? Was the sequence orderly, or did routine traffic keep interrupting? Even if no mayday occurred, review whether the plan for one is understood.
• Interoperability with mutual aid. When outside units arrived, could they talk to your incident and to each other? Did they have to relay through their own dispatch? Interop gaps are one of the most common and most consequential findings.
• Dispatch and field coordination. Did the dispatch center and the incident stay in sync on units, assignments, and timeline? Were requests acknowledged and filled promptly?

Working From the Record, Not From Memory

Memory of a chaotic incident is unreliable, and everyone's memory is unreliable in a slightly different direction. This is where the comms review has a real advantage over most other parts of an after-action. You usually have two objective records to work from: the recorded radio traffic and the computer aided dispatch timeline.

The recorded radio traffic is the actual audio of what was said, in what order, and by whom. The CAD timeline is the timestamped record of dispatch, unit status changes, and requests. Laid side by side, these two records let you reconstruct the incident minute by minute without relying on anyone's recollection.

Use the record to build a simple timeline before the debrief, not during it. Note the times of the significant events: dispatch, arrival, the first size-up, the move to a tactical channel, any benchmark reports, any strategy change, and the return to service. Mark the moments where the audio shows a stepped-on transmission, a long unanswered call, or an order without an acknowledgement. You are not writing a novel. You are creating a spine that the discussion can hang on.

Keeping It Constructive and Blame-Free

Here is the trap. The moment you play back a recording of someone's worst radio moment in front of a room, you can turn a learning tool into a punishment tool. Do that once and you will never get honest participation again. People will clam up, get defensive, and quietly stop keying up when they are unsure, which is exactly the opposite of what you want.

The recording is a picture of the system under load, not a highlight reel of individual mistakes. When you find a stepped-on transmission, the useful question is not who stepped on whom. It is why the channel was loaded to the point where collisions were likely, and what would reduce that. When you find an order that was never acknowledged, the question is what made acknowledgement hard, whether it was noise, workload, or an unclear expectation.

• Focus on the system, not the person. Ask what conditions made the error likely, and how to change those conditions.
• Assume good faith. People on scene were doing their best with the information and workload they had at that moment. Review from that starting point.
• Separate discipline from learning. If a genuine conduct issue exists, handle it through the appropriate channel, privately. Do not use the group debrief to deliver it. Mixing the two poisons both.
• Include the good. Point out the transmissions that were clear, calm, and well timed. People learn from strong examples as much as from weak ones.

Structuring a Short Comms Debrief

A comms debrief does not need to be long. A focused thirty minutes usually beats a rambling two hours. The goal is to surface a handful of real findings, not to relitigate the entire call. A simple structure keeps it moving.

• Set the frame, two minutes. State the purpose out loud: this is about improving the system, findings are not blame, and everyone's input matters. Say it every time. Culture is built by repetition.
• Walk the timeline, ten minutes. Move through the spine you built from the record. Pause at the significant comms moments. Let people add context the record cannot show, such as what they were seeing or dealing with when a transmission happened.
• Surface the findings, ten minutes. For each rough spot, ask two questions. What happened, and what would make it better next time? Keep answers concrete. Vague findings produce vague fixes.
• Assign the follow-up, five minutes. Turn findings into owned actions with a name and a rough timeframe. A finding with no owner is a finding that will reappear at the next incident.
• Close, two minutes. Restate the two or three things that will change, and thank the crew for the honesty. End on forward motion.

Run the debrief while the incident is still fresh, ideally within a shift or two. The longer you wait, the more memory fades and the more the record has to carry alone.

Capturing Findings and Closing the Loop

This is where most after-action processes quietly fail. The debrief happens, good points get made, everyone nods, and then nothing changes because nothing was written down and assigned. A comms review is only worth the time it takes if the findings actually land somewhere and drive a change. Broadly, comms findings resolve into one of a few buckets.

• Training. Many findings are skill and habit issues. Radio discipline, message and acknowledgement loops, mayday procedure, and channel management all improve with drilling. Turn the finding into a specific training objective, not a general reminder to do better.
• SOP or guideline updates. If the channel plan was unclear, or the point at which an incident moves to a tactical channel is not defined, that is a guideline gap. Update the written procedure so the expectation is explicit and teachable.
• Equipment and channel changes. Dead spots, coverage problems, and interoperability gaps usually cannot be trained away. They need infrastructure attention: a channel plan revision, a look at coverage, a fix to how mutual aid units get patched in. Route these to whoever owns your radio system.

Every finding gets an owner and a status. Write down the finding, the action, the person responsible, and a target date. Then, and this is the part that builds trust, report back at the next debrief on what actually got done. When crews see that last month's findings turned into this month's changes, they participate. When they see findings vanish into a drawer, they stop bothering.

Tracking Trends Across Incidents

One incident tells you what happened once. Ten incidents tell you what your department does under pressure. The real value of a comms review program compounds when you look across incidents rather than at each one in isolation.

Keep a simple running log of comms findings by category. Over time, patterns emerge that no single review would reveal. Maybe stepped-on transmissions cluster on a particular channel that is chronically overloaded. Maybe dead spots keep showing up in the same type of structure. Maybe interoperability with a specific mutual aid partner fails the same way every time. Maybe the move to a tactical channel is consistently late or incomplete.

• Categorize consistently. Use the same finding categories every time so trends actually aggregate. Channel plan, reception, coverage, span of control, mayday, interoperability, dispatch coordination.
• Watch for repeats. A finding that appears once is an incident. The same finding three times is a systemic issue that deserves a bigger fix than a training reminder.
• Let trends drive priorities. Recurring coverage problems justify an infrastructure conversation. Recurring discipline findings justify a dedicated training cycle. Data makes those cases far better than anecdote does.

You do not need a sophisticated system to start. A shared, well-organized record of incidents, findings, and their status is enough to begin seeing the shape of your department's real communications challenges.

Building a Learning Culture

Everything above works or fails on one thing: whether people believe the review is there to help them or to catch them. That belief is built slowly, through consistency, and destroyed quickly, through a single review that turns into a public reprimand.

A learning culture around comms has a few visible signs. People volunteer their own rough moments before anyone points them out, because they know it is safe. Newer members ask questions in the debrief instead of staying quiet. Findings from officers get the same scrutiny as findings from probationary members. And the phrase you hear most is not who did that, but how do we make that easier next time.

• Lead by example. When officers openly review their own transmissions and name their own improvements, it gives everyone else permission to do the same.
• Reward candor. The person who raises a mistake nobody caught should be thanked, not corrected. That single reaction, repeated, shapes the whole program.
• Keep it routine. A comms review that only happens after a disaster becomes associated with disaster. Review ordinary incidents too, so the process is normal, low stakes, and practiced when it matters.

The payoff is compounding. Departments that review communications honestly get better at communications, and better communications quietly prevents the next serious incident from becoming a review of its own.

Takeaways

• Give comms its own review. It is a recurring theme in serious incidents because it is the connective tissue of the whole operation, and it fails first under stress.
• Work from the record. Recorded radio traffic and the CAD timeline let you reconstruct what really happened without relying on unreliable memory.
• Chase acknowledgement. A message is not complete until it is confirmed received. Unacknowledged orders reveal more than garbled words do.
• Keep it blame-free. Review the system under load, not individuals' worst moments. Handle genuine conduct issues privately and separately.
• Close the loop. Every finding gets an owner, an action, and a target date, resolved through training, SOP updates, or equipment and channel changes. Report back on progress.
• Track trends. Categorize findings consistently and look across incidents. Repeats point to systemic fixes that a single review would miss.
• Protect the culture. Consistency and candor build a program people believe in. One punitive review can undo it.