The After Action Review (AAR) is the structured practice of extracting lessons from a completed action. It is not emotional debriefing nor a blame session: it is an organisational learning tool. A unit that runs systematic AARs improves survival and effectiveness; a unit that skips them repeats the same mistakes.
The four questions
The AAR structures around four standard questions, in this precise order. Skipping or inverting the order collapses the process.
- What was supposed to happen? (assigned mission, intent, plan)
- What actually happened? (facts, not interpretations)
- Why was there a difference? (analysis of causes, individual and systemic)
- What do we improve for next time? (concrete actions, assigned, dated)
What happened is a factual reconstruction built by everyone present, comparing memories, radio logs, video. It is not 'what you thought happened'. Perceptual distortions in combat inevitably produce discrepancies between witnesses — the AAR reconciles them explicitly.
No-blame rule
AAR works only if every participant can declare an error without punitive consequences. No-blame does not mean errors are accepted: it means public analysis of error is separated from possible disciplinary sanction (handled in a separate channel, if necessary). If error confessed in AAR produces punishment, next time no one will confess anything — and the unit will stop learning.
- Who speaks first: the lowest-ranking subordinate (so as not to be intimidated later)
- Who speaks last: the commander of the action (so as not to condition others)
- No rank named in AAR — analysis is of actions, not of persons
- Critiques are on specific behaviours, not personal traits
- No discussion outside AAR — what is said stays, what is unsaid does not return
A leader who uses AAR to humiliate a specific subordinate destroys not only that subordinate but the value of all subsequent AARs. It is a mistake paid for months. Severe individual critique, if necessary, is done in private after the public AAR, not during.
Session structure
An AAR session for a tactical event (assault, patrol, contact) lasts 30–60 minutes. For larger operations it may extend to 2 hours. The facilitator should not be the action's commander — preferably the deputy or an external observer. Support tools are a visual sequence: timeline, map, drone video if available.
| Phase | Duration | Content | Output |
|---|---|---|---|
| Opening | 5 min | Recap no-blame rules, assigned mission | Alignment |
| What should have happened | 5–10 min | Plan, intent, victory conditions | Reference |
| What happened | 15–25 min | Factual timeline reconstructed | Shared narrative |
| Why difference | 10–15 min | Individual, systemic, external causes | Diagnosis |
| What we improve | 5–10 min | Concrete actions assigned | To-do list |
| Closing | 5 min | Summary, written lessons learned | Document |
Types of lessons
Lessons extracted from an AAR fall into three categories, each with a different destination. Mixing them confuses corrective actions.
- Individual technical: corrected in training (e.g. 'MG exposed 90% of body during mag change — prone reload drill')
- Team procedures: modify the SOP (e.g. 'react-to-FPV did not include immobility order — add step 0')
- Systemic: communicated to higher level (e.g. 'brigade EW did not cover assault axis for 8 minutes — escalate to S3')
A lesson without an action is useless. Every to-do list item must have: concrete action, owner, deadline, completion criterion. 'Improve drone coordination' is not a lesson — it is a title. 'Drone pilot receives a standardised preflight checklist by Friday, validated by team leader' is a lesson.
AAR under operational stress
In continuous operations, the full AAR (30–60 min) is not always feasible. Compressed variants exist. The hot-wash is a 5-minute AAR immediately after action, with three questions only: what went well, what went badly, what we change immediately. Hot-wash does not replace formal AAR (held when conditions permit) but avoids losing urgent information.
- Hot-wash (5 min, immediately after): captures urgencies, aligns team
- Formal AAR (30–60 min, within 12–24 h): full analysis, no-blame, documented
- Rotation AAR (2 h, end of operational cycle): consolidation, lessons to propagate
- Mission AAR (varies, end of overall mission): for higher level
Common mistakes
- Turning AAR into a tribunal — the next AAR becomes silence
- Skipping AAR because 'everything went well' — success must also be analysed
- Letting the commander speak first — conditions everyone else
- Confusing factual description with causal interpretation
- Producing lessons without concrete actions and owners
- Not documenting — the lesson is lost with personnel rotation
Lessons learned Ukraine
The most effective Ukrainian battalions document written AARs for every assault, stored in a repository accessible to all commanders. The tactical evolution of Ukrainian units — from static 2022 defence to precision fires in 2024 — is largely the result of this cumulative process. International volunteers who integrate into units with a mature AAR culture learn in weeks what elsewhere takes months. Those who integrate into units that skip AAR repeat predecessors' mistakes and risk paying with their lives.