After-action review: how teams debrief and learn from an operation
An after-action review (AAR), often simply called a debrief, is a structured conversation held after an operation, exercise or event. It compares the plan with what actually happened, looks for the reasons behind the difference, and ends with actions that someone owns.
The four questions of an after-action review
The method comes from military training and has spread to emergency services, healthcare and project teams. Its core is four questions, asked in this order:
- What was supposed to happen?
- What actually happened?
- Why was there a difference?
- What will we keep doing, and what will we change?
Hot debrief and structured debrief
Many teams run two kinds. A hot debrief (in American usage, a hot wash) takes ten to twenty minutes straight after the event, while memories are fresh and people are still on site. A structured debrief follows days later with a facilitator, data and everyone who had a role, including partner organisations.
A good AAR looks at the work and leaves blame out of it. Personal accounts are welcome but stay separate from established facts, and each finding should point to evidence such as a timestamp, a track, a message or a photo.
UK fire and rescue services work this way. The NFCC’s guidance treats an on-scene debrief, led by an officer in attendance, as good practice, followed by a structured debrief that runs from the first call to fire control through to post-incident actions. Where several agencies were involved, lessons about working together go into JESIP’s Joint Organisational Learning (JOL Online), the national store for interoperability lessons, so that another area does not have to learn them again.
A missing-person search, reviewed
A search for an elderly man ends well after nine hours. At the review, the plan shows sector C was to be cleared by 16:00. The recorded tracks show it was cleared at 18:20, because two teams were sent to the same sector after a radio message was misheard. The finding is tied to the tracks and the message log. From now on assignments go out as tasks on the map as well as by voice; the search coordinator owns that action, and it will be tested at the next exercise. Our missing-person search checklist includes the debrief step.
Debriefs in Sinkaos
Built from the record
Messages, tasks, incidents, tracks, plan versions, alerts and media, with a replay of the operation on the map.
Plan versus actual
Shows where timings, routes and resources drifted from the plan, and lets you record why.
Findings and lessons
Findings tied to evidence, validated lessons with an owner, and improvement actions with deadlines and proof they were done.
Packages and reports
After-action packages with a checksum manifest, and reports for different audiences with redaction before sharing.
Debrief questions
How soon after an operation should the review happen?
Who should attend?
Is an AAR the same as an incident report?
Try it on your next operation.
Early access is free. We set up the first operation with you and stay close while you use it.