The after-action review: compare one event and receive the next actions
The transformer lift finished three hours later than expected. The superintendent wants to record what worked and what needs attention before the next event, but participants disagree about the receiving and traffic-control sequence. A short review needs evidence and follow-through without becoming an improvised redesign of the lifting plan.
Review one defined event against its intended and actual sequence, then turn supported learning into owned next actions. The US Army's public after-action review guidance uses that intended-versus-actual comparison and a discussion of improvement. Here it is a method illustration, not a construction timing standard. Choose a suitable review time and attendance after immediate responsibilities are secure; thirty minutes or the same day is not a required limit.
Ask what was intended, observed, supported and next
- Define the event and intended arrangement. Bring the actual plan, relevant commitments and people with different views of the work. Confirm what the review covers and which questions follow another required investigation or technical process. Do not use an informal learning discussion to close an incident duty or authorize the next operation.
- Establish the observed sequence. Compare dated records and participant accounts, noting agreements and unresolved differences. Record useful successes as well as departures. A reported late arrival needs its actual time and affected handover checked before it becomes the explanation for the entire overrun. Keep suspected causes separate from observed events.
- Discuss what contributed and what to retain. Examine the evidence for differences and the conditions that supported successful work. Follow multiple contributions where appropriate. Avoid both personal accusation and an assumption that no individual action matters. Identify missing facts and route technical uncertainties to responsible reviewers rather than deciding a new lift method in the discussion.
- Receive the changes into the next preparation. Give each proposed action an owner, required review and next-plan receiving point. Confirm accepted changes reach the people preparing the next event. Record how their actual effect will be checked. A rewritten checklist cannot guarantee an on-time result or replace the complete current plan and release arrangements.
Common mistakes
- Turning an account of events into an unverified cause verdict.
- Using a learning review to replace required investigation.
- Changing a technical method through an informal checklist.
- Recording actions without their next-plan receiver.
Action list
The event review leaves
- An intended sequence and observed record.
- Supported differences and evidence still needed.
- Useful practices worth retaining.
- Assessed actions with owners and receiving points.
- A next-event result check and remaining responsibilities.
Check your understanding
The next event finishes on time after two checklist changes. Does that prove both changes caused the improvement?
