After-action review template: turn a team debrief into a next step

Get the free after-action review template

Download the editable after-action review template (.txt). Open it in a text editor, paste it into your organisation’s approved shared document, or print it. No account or purchase is required.

The template is for ordinary workplace learning, such as reviewing an online workshop, a training pilot or a recurring handover. It includes space for evidence, unresolved questions and follow-up. It is not an official incident-investigation form; use your organisation’s required process for safety incidents, complaints or disciplinary matters.

The four questions to work through

The Wharton guide to after-action reviews describes a four-question discussion covering intention, execution, explanation and adaptation. The prompts below turn that structure into a practical record.

When an after-action review is useful

Use it when people can learn from a specific shared event and influence what happens next. A completed online training session is a useful unit; “everything wrong with our learning culture” is too broad for one short review. Include successful events so the team can identify practices worth repeating.

A review is the conversation; a report is its written record. A retrospective may serve a similar purpose, depending on how your team uses the term. Choose the process by the learning task, rather than treating a meeting label as a guarantee of quality.

For the wider system that helps lessons travel between teams, read how learning organisations turn experience into decisions. This guide concentrates on running and recording one review.

Prepare a small, useful evidence pack

I would begin with one question the team can act on: “Why did learners struggle to complete the practice task?” Bring the original learning objective, the instructions participants received and a sample of task outputs. Add relevant support notes or timing records, where available and appropriate.

Separate three things in the notes: an observation you can check, a participant’s account of their experience, and a proposed explanation. All three can help, but they should not be presented as interchangeable facts. If records disagree, retain the disagreement and assign a check rather than smoothing it away.

• Invite people who delivered the activity and people who experienced it; do not rely only on the organiser’s perspective.
• Name a facilitator and a note-taker. In a small team one person can do both, but check that note-taking does not silence the discussion.
• Agree what will be recorded, who can access it and which findings can be shared. Do not promise confidentiality that your workplace rules cannot provide.
• Use the minimum necessary personal information. Avoid copying identifiable learner work or private chat messages into a widely accessible file.

A practical 30-minute agenda

For one routine event, I would try the agenda below and shorten the scope if it cannot be covered properly. Thirty minutes is a suggested meeting design, not a research-backed optimum. A complex or sensitive event may need a different process and a trained facilitator.

Give people a quiet minute to note their observations before discussion. Ask for a different perspective before moving on. Keep the conversation on the work and its conditions; record a missing instruction or access problem precisely rather than labelling a colleague careless.

Worked example: an online training session

This is a fictional example, not a client result or a product test. A team has introduced a digital case-record system and runs a practice workshop for 12 colleagues. Its aim is for each learner to create a correct sample record without help by the end of the session.

Turn the finding into an action you can check

In the example, seven of 12 learners completed independently, about 58%. The three prompted completions do not satisfy the original “without help” standard. Keep assisted and independent completion separate rather than making the headline result look better.

A later improvement would be worth investigating, but would not by itself prove that the revised instruction caused it. Learners, task difficulty and trainer support might also differ. Record those conditions and keep the conclusion proportionate.

I would prefer one change that has an owner and a usable check over ten vague lessons. The action tracker should make it possible for someone who missed the meeting to see what happens next.

Keep the digital record findable and usable

Use an approved shared document for the discussion record and the team’s existing task list for follow-up. A simple title such as “Training pilot: case-record practice, 5 October” is easier to retrieve than “Meeting notes final v3”. Link the review to the instruction or training material that needs changing.

Store the current version of the working instruction in one agreed place. The review explains why it changed; it should not become a competing set of instructions. Restrict access where the record contains personal or sensitive information.

If you use an AI tool to tidy the notes, use only an approved service with permitted data. Check the summary against the original record, particularly action owners, numbers and unresolved disagreements. A fluent summary cannot establish what happened.

Before buying another tool, use the learning-technology selection framework to check whether your current document and task tools already meet the need.

What the evidence supports, and what it does not

The World Health Organization’s AAR guidance sets out several formats for structured review and follow-up, developed for public-health responses and also described as a management tool for learning. That is methodological guidance, not proof that this short workplace template will produce a particular gain.

A completed form is not evidence that learning transferred into work. Check whether the agreed practice changed and whether the relevant problem improved. If participants cannot raise a concern safely, a template alone will not resolve that problem. If the discussion concerns a serious incident, use the responsible organisation’s specialist process.

Run one review, then revisit the action

Choose one recent learning activity, download the template, and bring the original aim plus enough evidence to examine it. Finish with a clear owner and follow-up point. At that follow-up, ask what changed in practice, not only whether the document was completed.

For a way to frame the resulting small experiment, continue with Kaizen as a learning loop. Keep the review narrow enough that the team can do something with it.