After Action Reviews: How to Debrief Calls Without Pointing Fingers

We ran a second alarm at a commercial strip mall a few years back. Heavy fire on arrival, wind-driven conditions, multiple exposures threatened. We got it stopped but not before it extended into two adjacent businesses. Nobody got hurt, which was the most important thing, but there were some decisions made during that fire that deserved a closer look. The problem was, when we tried to debrief it, the whole thing turned into a blame session. People got defensive. Fingers got pointed. By the end, nobody wanted to talk about what actually happened, and we missed an opportunity to learn from a significant incident.

That experience taught me more about after action reviews than any class ever did. The debrief process is only as good as the culture that supports it, and building that culture is the hard part.

Why Most Debriefs Fail

The fire service has a complicated relationship with after action reviews. We know we should do them. Every leadership course tells us to do them. USFA at usfa.fema.gov publishes resources on conducting effective AARs, and most departments have some kind of debrief policy on the books. But the actual practice of sitting down after a call and honestly discussing what happened, what worked, and what did not, that is where most departments fall apart.

The most common failure mode is turning the debrief into a performance evaluation. When people feel like the AAR is really about identifying who messed up so they can be disciplined or embarrassed, they stop being honest. They become defensive. They minimize their mistakes and exaggerate their contributions. The conversation becomes political rather than educational, and the whole exercise becomes a waste of time or worse, actively harmful to team trust.

The second failure mode is not doing debriefs at all. Many departments only debrief major incidents, and even then, only when something went visibly wrong. That means the vast majority of calls, including the ones where you got lucky, where you made small mistakes that did not result in bad outcomes, never get examined. You miss the chance to catch trends and patterns before they lead to a serious problem.

The third failure mode is doing debriefs that are so superficial they do not accomplish anything. "Good job everyone, we did great out there." If that is the extent of your AAR, you are checking a box, not learning.

Building a Blame-Free Environment

The foundation of effective after action reviews is psychological safety. That is a term from organizational psychology that means people feel safe to speak up, admit mistakes, and ask questions without fear of punishment or humiliation. In the fire service, we might call it trust. Do the members of your crew trust that if they admit a mistake during a debrief, it will not be used against them?

Building that trust starts at the top. The officer running the debrief has to model vulnerability. You go first. You talk about what you did, what decisions you made, and where you think you could have done better. When the crew sees the officer honestly examining their own performance, it gives everyone else permission to do the same.

Set ground rules at the beginning of every debrief. This is not about blame. This is about learning. We are discussing the decisions and actions, not judging the people who made them. Everyone here was doing their best with the information they had at the time. The goal is to get better, not to punish.

Those ground rules only work if you actually enforce them. If someone starts pointing fingers or getting personal, the officer running the debrief has to redirect the conversation immediately. "Let us focus on the decision that was made and what information was available at that point, not on who made it."

The AAR Framework

The best after action review format I have found is straightforward. Four questions, asked in order, with honest discussion around each one.

What did we plan to do? This establishes the baseline. What was the initial action plan? What were we trying to accomplish? What resources did we have? This is not about what we wanted to happen in a perfect world. It is about what we actually planned and communicated at the time.

What actually happened? This is the objective recounting of events. Walk through the incident chronologically. What actions were taken and in what order? This is where you might use dispatch recordings, radio traffic, body camera footage, or other documentation to establish the facts. The goal is to build a shared picture of what actually occurred, because different people in different positions often have very different perspectives on the same incident.

What went well? Start with the positives. What actions contributed to a good outcome? What decisions were sound? What skills were executed properly? This is not feel-good filler. Identifying what went well is just as important as identifying problems, because you want to reinforce effective behaviors and make sure they are repeated.

What do we need to improve? This is where the real learning happens. What decisions, in hindsight, could have been better? What information was missing? What skills need work? What equipment failed or was inadequate? What communication breakdowns occurred?

Notice that the question is "what do we need to improve," not "who messed up." The focus is on behaviors, decisions, and systems, not on individual blame. If the hoseline took too long to stretch, the question is why. Was it a training issue, an equipment issue, a communication issue, or a situation that was just inherently difficult? Understanding the why leads to solutions. Blaming someone for being slow leads to resentment.

When to Debrief

The ideal answer is after every call, but that is not realistic for busy departments running 15 or 20 calls a shift. A practical approach is to debrief based on the significance and learning potential of the call.

Working incidents should always get a formal debrief. Any call where you actually put crews to work, advanced hoselines, conducted searches, performed rescues, or managed a significant EMS incident should be reviewed. These are the calls where the most learning happens because the most decisions were made.

Near-miss events should be debriefed immediately. If something almost went wrong, if a crew was almost trapped, if a collapse almost occurred, if a patient almost coded because of a delayed intervention, that is a critical learning opportunity. Near misses are gifts. They give you the lesson without the consequences. Do not waste them.

Routine calls can be debriefed informally around the kitchen table. "Hey, that medical call we ran earlier, did anyone else notice that the patient's medication list did not match what the family told us? Let us talk about that." These short, casual debriefs build a culture where reviewing calls is normal, not something that only happens after disasters.

Major incidents, including second alarms and above, mutual aid incidents, line-of-duty injuries, and any call with significant property loss or civilian casualties, should get a formal, documented AAR. These debriefs should include all units that operated on the incident and should happen within a few days of the event while memories are still fresh.

Documentation and Follow-Through

A debrief without follow-through is just a conversation. The insights that come out of an after action review need to be captured and acted on. Assign someone to take notes during the debrief. Document the key findings, both positive and negative. Identify specific action items, assign responsibility for each one, and set a timeline.

If the debrief reveals a training need, schedule the training. If it reveals an equipment deficiency, start the process to address it. If it reveals a policy gap, draft the policy revision. When people see that their input during the AAR actually leads to changes, they buy into the process. When they see that nothing ever changes despite the debrief, they stop participating.

Share the findings. Obviously, protect confidentiality where appropriate, but the lessons learned from one crew's debrief can benefit the entire department. Some departments publish a monthly lessons-learned bulletin that highlights findings from recent AARs without identifying specific individuals. That spreads the learning across all shifts and stations.

Handling Emotional Calls

Some calls are hard. Pediatric deaths, line-of-duty injuries, mass casualty incidents, and calls where the outcome was bad despite everyone's best efforts. These calls need debriefs too, but they need to be handled differently.

For emotionally charged incidents, consider separating the operational debrief from the emotional processing. The operational AAR focuses on tactics, decisions, and performance. The emotional processing focuses on how people are doing and whether they need additional support. Both are important. Both deserve dedicated time and attention. But mixing them together often means neither gets done well.

For the operational debrief of a difficult call, it is especially important to emphasize that the goal is learning, not blame. When the outcome is bad, the natural human tendency is to look for someone to hold responsible. Resist that. Focus on systems, decisions, and information, not on individuals.

The after action review is one of the most powerful tools available to any fire department. Done right, it creates a culture of continuous improvement where every call makes you better. Done wrong, it destroys trust and teaches people to hide their mistakes. The difference comes down to leadership, and that is on you.

First Due Co. builds training tools that help you practice the decision-making skills that show up in every debrief. Sharper size-ups, faster tactical thinking, and better command decisions. Train with us at firstdueco.com.