"When agencies work as one, the public is safe. When they work in silos, the gaps become vulnerabilities."
After-Action Review in Multi-Agency Operations
Professor Sele: An operation that is not reviewed is an operation that is not improved. The after-action review is how organisations convert experience into capability. Done properly, it is the most powerful learning tool available.
9.1 The Purpose of the After-Action Review (AAR)
An AAR is a structured debrief that answers four questions: What was supposed to happen? What actually happened? Why was there a difference? What will we do differently next time?
The AAR is not a blame exercise. Personnel must feel safe to report what went wrong without fear of punishment — otherwise the AAR produces only the narrative people think their superiors want to hear.
9.2 AAR Structure in Multi-Agency Operations
Phase 1 — Hot Wash (within 2 hours): brief verbal debrief with all agency representatives. Phase 2 — Individual Agency Reviews (within 48 hours): each agency reviews against its own standards. Phase 3 — Joint AAR (within 5 working days): all agencies together, neutral facilitator, focus on joint performance. Phase 4 — Lessons Identified Report: written report distinguishing lessons identified from lessons learned.
9.3 The AAR Report Structure
| Section | Content |
|---|---|
| Executive Summary | Key findings in 1 page |
| Operation Overview | What was planned, what occurred |
| What Went Well | Specific positives to be reinforced |
| Areas for Improvement | Specific gaps or failures — factual, not personal |
| Recommendations | Specific, actionable changes with assigned owners |
| Lessons Learned Status | Track implementation of prior recommendations |
9.4 Converting Lessons Identified to Lessons Learned
The most common failure in AAR processes is documenting lessons identified and never implementing changes. A Lessons Learned Register tracks the lesson, the owner, the change (SOP, training, equipment), the deadline, and confirmation of implementation.
- •The AAR answers four questions: what was supposed to happen, what happened, why the difference, what will change
- •Multi-agency AARs require a neutral facilitator and a safe, blame-free environment
- •Distinguish between lessons identified (known gap) and lessons learned (change implemented)
- •A Lessons Learned Register converts AARs from documentation exercises to operational improvements
"After a complex multi-agency event, SafeHaven's joint AAR identified that inter-agency radio communications had failed at a critical moment because different agencies were using different encryption keys despite having agreed on a shared channel. The lesson was identified on the day. But the lesson was only learned three weeks later, when a joint communications test — added to the pre-operation checklist — confirmed that all agencies' radios were fully interoperable before the next event. Documentation of the problem was step one. Changing the checklist was step two. Both steps were necessary."
What distinguishes a "lesson learned" from a "lesson identified" in the AAR process?