You Had the After-Action Review. Now What?

The Meeting Is Not the Improvement

After a significant incident, most fire departments know the value of talking about what happened.

Crews sit down after the call. Officers walk through the response. Someone asks what went well, what did not, and what should be done differently next time. Sometimes that conversation happens informally at the kitchen table. Other times it becomes a formal after-action review.

Either way, the discussion can be valuable.

But the meeting itself is not the improvement.

A department can identify ten legitimate problems during an after-action review and still change nothing if those observations are never turned into action. A communication issue can be recognized, a training gap can be discussed, an SOP can be questioned, and an equipment problem can be noted, but if nobody owns the follow-up, the department may be right back in the same position on the next incident.

That is where many after-action processes lose their value.

The organization successfully identifies the lesson, but never builds the administrative process needed to carry that lesson forward.

The difference between talking about a problem and correcting it is follow-through.

What needs to change?

Who is responsible for changing it?

What is the expected timeline?

Does the finding require training, a policy revision, an equipment change, a communications fix, or something else?

How will leadership know when the corrective action is complete?

And most importantly, how will the department know whether the change actually worked?

Those questions move the conversation beyond reflection and into improvement.

An after-action review should not end with everyone agreeing that something needs to be better next time.

It should create a clear path for making sure “better next time” actually happens.

Lessons Identified Are Not Lessons Learned

There is an important difference between identifying a lesson and actually learning from it.

A department may leave an after-action review with a clear understanding of what went wrong. Crews may agree that accountability broke down, radio traffic became confusing, apparatus placement created access problems, or a particular tactic did not work as intended.

That recognition matters, but recognition alone does not create change.

If the department identifies an accountability problem, what happens next? Is the accountability procedure reviewed? Is additional training scheduled? Is the equipment evaluated? Is someone assigned to own the corrective action? Is there a deadline or review point? Does leadership later verify that the issue improved?

If none of those things happen, the lesson was identified.

It was not learned.

That distinction matters because fire departments often operate in environments where the consequences of repeating the same mistake can be significant. A problem discussed once and forgotten can easily reappear months later under the same or worse conditions.

A meaningful after-action process should therefore create a bridge between observation and implementation.

Some findings may require a policy change. Others may call for focused training, new equipment, a change in communications procedures, a revision to mutual-aid expectations, or additional officer development. Some may reveal that the original problem was not tactical at all, but administrative.

The specific response will vary.

What should not vary is whether someone is responsible for making sure the issue moves forward.

That is where the department begins turning experience into organizational learning.

The goal is not to produce a perfect report after every incident. The goal is to make sure that the important lessons do not disappear once the meeting ends.

Ask yourself:

What was the last problem your department identified after an incident, and can you show what actually changed because of it?

Every Corrective Action Needs an Owner

One of the easiest ways for an after-action item to disappear is for everyone to agree that “we need to fix that” without assigning the fix to anyone.

Shared awareness is not the same as assigned responsibility.

If a department identifies a communication problem, policy conflict, equipment deficiency, training gap, or mutual-aid issue, someone should be responsible for carrying that item forward. That does not necessarily mean one person has to solve the entire problem alone. It means there should be a clearly identified owner who is accountable for making sure the corrective action does not stall.

That owner might be a training officer, company officer, chief officer, apparatus committee member, communications coordinator, or another person appropriate to the issue. The exact title matters less than the clarity of the assignment.

The same is true for timelines.

A corrective action without a due date, target date, or formal review point can remain open indefinitely. Departments do not need to create arbitrary deadlines for every issue, but they should establish some expectation for when the item will be revisited.

That creates accountability without turning the process into unnecessary bureaucracy.

The corrective-action record should make it easy to answer a few basic questions: What was identified? What needs to change? Who owns the follow-up? What is the expected timeline? What is the current status? What documentation shows that the issue was addressed?

Without those answers, the improvement process becomes dependent on memory.

That is especially risky when multiple findings come out of the same incident. A department may remember the most obvious problem and quietly lose track of three others that were just as important.

Assigning ownership also makes follow-up conversations more productive. Instead of asking, “Did we ever do anything about that radio issue?” leadership can ask the responsible person for a status update on a specific corrective action.

That is a much stronger administrative process.

The goal is not to create a blame list.

The goal is to create a completion path.

Ask yourself:

When your department identifies a problem after an incident, is there always one clearly identified person responsible for making sure the follow-up actually happens?

Not Every Finding Needs the Same Fix

One of the most important parts of an after-action process is correctly identifying what kind of problem was actually uncovered.

Not every issue should result in more training.

That is an easy default because training is familiar, visible, and relatively simple to schedule. But if the root problem was an outdated SOP, missing equipment, unclear radio procedures, unrealistic staffing assumptions, or a breakdown in mutual-aid coordination, another drill may not solve anything.

The corrective action should match the problem.

A policy issue may require an SOP or SOG review. A recurring skill deficiency may point toward targeted training. An equipment problem may require inspection, replacement, repositioning, or a change in how that equipment is deployed. A communication issue may require work with dispatch, radio programming, or clearer operational expectations. A mutual-aid problem may need to be addressed with the neighboring agency rather than internally.

Some findings may involve more than one category.

For example, an accountability breakdown may expose a training problem, a policy problem, and an equipment problem at the same time. Fixing only one piece may improve the situation without actually correcting the larger system.

That is why the department should resist jumping immediately from observation to solution.

First identify what happened.

Then determine why it happened.

Only then decide what needs to change.

This also helps prevent corrective actions from becoming superficial. “Train on this more” may sound productive, but it is not particularly useful if leadership cannot explain what specifically needs improvement, who needs the training, or what should be different afterward.

The same principle applies to policy changes. Rewriting an SOP after every unusual incident can create its own problems if the department reacts to one event without considering whether the existing policy was actually deficient.

The purpose of the after-action process is not to create activity.

It is to create improvement.

That means selecting corrective actions that address the actual cause of the problem rather than the easiest response to assign.

Ask yourself:

When your department identifies a problem, do you take the time to determine what actually caused it, or do you default to the same solution every time?

Corrective Actions Need to Stay Open Until They Are Actually Closed

Identifying a corrective action is only the beginning.

Once an issue has been assigned to someone, the department still needs a way to track it until the work is actually complete. Otherwise, the action item can quietly disappear into meeting notes, email threads, or someone’s memory.

That is where a corrective-action log or similar tracking process becomes valuable.

The system does not need to be complicated. At a minimum, leadership should be able to see what issue was identified, what action was assigned, who owns it, when it was opened, the expected completion or review date, its current status, and what evidence supports closing it.

The word closed should also mean something.

A policy item is not necessarily complete because someone opened the SOP and made an edit. Was the revision reviewed, approved, distributed, and communicated to the people expected to follow it?

A training item is not complete because a drill was scheduled. Did the intended personnel actually receive the training, and did the training address the deficiency that prompted it?

An equipment issue is not resolved because a purchase request was submitted. Was the equipment obtained, placed in service, and incorporated into the way crews operate?

Those distinctions matter because administrative activity can easily be mistaken for corrective action.

Checking the box should represent the point where the department can reasonably say the identified issue has been addressed, not simply that someone started working on it.

Leadership should also review open items periodically. Some actions will move quickly. Others may require funding, outside agencies, procurement, policy approval, or additional planning. The important part is that they remain visible until someone intentionally decides what happens next.

That visibility prevents the same issue from being rediscovered months later with everyone wondering why nothing changed.

A well-managed corrective-action process should make unfinished work difficult to forget.

Ask yourself:

If I asked for every open corrective action from our last three after-action reviews, could we produce that list and explain exactly where each item stands today?

Closing the Item Does Not Mean the Problem Is Solved

A corrective action can be completed on paper and still fail in practice.

That is why closeout should not be confused with verification.

If an after-action review identifies a radio communication problem and the department responds by changing a procedure, that may be a reasonable corrective action. But the real question is whether communications actually improved during the next comparable incident or training evolution.

The same applies to training. A department may schedule a drill in response to a deficiency, document attendance, and mark the action complete. That proves the training occurred. It does not automatically prove the original problem was corrected.

Verification requires another step.

Leadership should decide how it will determine whether the corrective action produced the intended result. Depending on the issue, that may involve observing future training, reviewing subsequent incidents, testing equipment, checking policy compliance, soliciting feedback from crews, or conducting another focused evaluation.

The method does not need to be complicated.

It does need to answer the question that matters most:

Did this change actually improve the problem we were trying to fix?

That question protects the department from false closure. It also helps identify when a corrective action was incomplete, poorly targeted, or based on the wrong assumption about the original problem.

Sometimes the first fix will work.

Sometimes it will only solve part of the issue.

Sometimes the department will learn that the problem was more complicated than it initially appeared.

That is not a failure of the process.

That is the process working.

Continuous improvement depends on being willing to revisit an issue when the evidence shows that the first response was not enough.

A strong after-action system should therefore create a full loop: identify the issue, assign the corrective action, track it to completion, and verify that the outcome actually changed.

Only then has the department moved from discussion to improvement.

Ask yourself:

When your department closes a corrective action, are you verifying that the problem improved, or simply documenting that someone completed the assigned task?

The AAR Should Feed the Rest of the Department

An after-action review should not exist in isolation.

If the process identifies something important, that information should move into the part of the organization capable of addressing it. A training issue should influence the training plan. A policy issue should trigger a policy review. An equipment problem should reach whoever manages procurement or apparatus. A communications problem may need involvement from dispatch, radio administrators, or mutual-aid partners.

Otherwise, the department risks creating two separate systems: one that identifies problems and another that continues operating as though those problems were never identified.

That disconnect is where valuable lessons get lost.

Imagine an after-action review identifies repeated difficulty with a particular fireground task. The finding is documented, but the annual training calendar remains unchanged. Six months later, crews encounter the same problem again.

Or the review identifies language in an SOP that caused confusion during the incident. Everyone agrees the policy needs clarification, but the document is never placed into the department’s policy-review process.

The department recognized the problem.

The organization simply failed to carry the information far enough to change anything.

A mature improvement process should create clear connections between after-action findings and the department’s existing administrative systems. Corrective actions should not disappear once they leave the meeting. They should become visible assignments within training, policy management, equipment planning, communications, or whichever function is responsible for implementing the change.

That also allows departments to identify patterns over time.

One radio problem may be an isolated event. Similar communication findings across several incidents may point toward a larger issue. The same is true for accountability, command, apparatus placement, water supply, training deficiencies, equipment concerns, or policy confusion.

If every after-action review is treated as a standalone event, those patterns can be difficult to see. When findings are documented consistently and tracked across incidents, leadership gains a much clearer picture of where recurring weaknesses may exist.

That is where after-action documentation becomes more than recordkeeping.

It becomes organizational intelligence.

The goal should be to create a feedback loop where incidents influence training, training influences performance, performance generates new observations, and those observations continue improving the organization.

Ask yourself:

When your department identifies a lesson after an incident, where does that information go next, and can you show how it becomes part of the way the organization trains, operates, and improves?

If Your AAR Ends With Meeting Notes, the Process Is Incomplete

A department can conduct a thoughtful after-action review, document important findings, and still lose much of the value if the process ends when the notes are filed away.

The administrative follow-through matters just as much as the discussion itself.

A strong process should create a clear path from the original observation to the corrective action, the person responsible, the expected timeline, the related policy or training issue, and the point where leadership can verify that the item was actually resolved.

That does not require an elaborate software platform or a complicated bureaucracy.

It requires a process that people can consistently use.

Fire Service Administrative Solutions can help departments build that structure. Depending on the organization, that may include standardized AAR forms, corrective-action logs, ownership and status tracking, links between findings and related SOP/SOG revisions, training follow-up, closeout documentation, and a defined process for reviewing open items.

The goal is not for FSAS to tell a department whether its tactical decisions were right or wrong.

The people who were there, the department’s leadership, subject-matter experts, and the organization’s own review process should drive those conclusions.

FSAS focuses on what happens after the department identifies the lesson.

How is it documented?

Who owns it?

Where is it tracked?

What other systems need to change because of it?

How does leadership know when the work is complete?

And how does the department verify that the original problem actually improved?

Those are administrative questions, but they have operational consequences.

When the administrative system is weak, good lessons can disappear.

When the system is strong, the department has a much better chance of turning experience into lasting improvement.

Ask yourself:

If your department identified a critical lesson tonight, do you already have a reliable process for making sure that lesson is still being acted on six months from now?

Show Me What Changed

At the end of the day, the value of an after-action review is not measured by how good the meeting was.

It is measured by what changed because of it.

A department may hold a detailed discussion, identify several valid concerns, and produce a polished report. But if the same problems remain six months later, the process did not create meaningful improvement.

That is the standard leadership should be willing to apply.

Show me what changed.

Was the policy revised?

Was the training completed?

Was the equipment issue corrected?

Was the communication problem addressed?

Was the mutual-aid concern resolved?

Was the corrective action verified?

Can the department show that the issue moved from observation to action and from action to improvement?

If the answer is yes, the after-action process is doing what it is supposed to do.

If the answer is no, the department may be collecting lessons without actually learning from them.

That does not mean every finding needs an immediate fix. Some problems take time, funding, coordination, or multiple steps to resolve. What matters is that the issue remains visible, ownership is clear, progress is tracked, and leadership can explain where the corrective action stands.

Fire Service Administrative Solutions can help departments build the administrative structure behind that process.

That may mean creating standardized AAR documentation, corrective-action tracking, ownership and due-date systems, policy and training follow-up, closeout criteria, or a complete workflow that carries lessons from the initial review through final verification.

The objective is simple: make sure the lesson does not disappear when the meeting ends.

Before your next after-action review, look back at the last one.

Pick one issue your department identified.

Then ask:

What changed because we identified it?

If that question is difficult to answer, the problem may not be the after-action review itself.

The problem may be what happens after it.

Bring FSAS the lesson your department already identified. We will help you build the process that makes sure something actually changes because of it.