After an event or project, teams need to capture what went wrong, what worked, and what should change before the same problems happen again. Without a proper structure, important observations, causes, and follow-up actions can easily be overlooked.
This is the exact problem an after-action report (AAR) solves. It provides a practical way to document the findings, particularly after emergencies, drills, or other fast-moving operations.
Instead of preparing such a document from scratch, you can utilize a pre-made after-action report template from WordLayouts. Available in Google Docs and Word, it helps teams conduct faster, more consistent reviews and clearly document the actions that should follow. Download this template and customize it to start your review.
What Is an After Action Report?
An after-action report (AAR) is a structured document prepared after a project, activity, event, exercise, operational period, or incident. It compares what was expected with what occurred, then records the findings that should guide future work.
A completed report explains the intended goals and activities, what worked, what could be improved, what failed and why, and what the participants learned. It also identifies the work that will follow the review, the person responsible for each action, and the agreed due date.
After-action review vs. after-action report
The after-action review is the discussion and analysis conducted with participants, observers, supervisors, and other relevant people. The after-action report is the written record produced from that process. Notes from the discussion are source material; they are not the finished report. Before entering a finding, check it against the plan, logs, measurements, or other available records.
How AARs Help Organizations
The following are different ways an after-action report can help organizations:
Creates a complete post-activity record
An AAR brings the original plan, observations, findings, decisions, and follow-up work in one dated document. It can also be used with other record-keeping documents as proof of evidence for audits, reviews, and similar activities.
Evaluates performance against expectations
The after-action report can be used as a comparison between what was planned and what actually happened. By comparing objectives and expectations, it becomes easy to identify the performance gaps and determine what needs to improve.
Preserves successful practices
An AAR records the practices that resulted in successful outcomes. Teams can refer to these actions and decisions to adapt them for similar situations.
Converts findings into accountable improvement
The report connects lessons and root causes with specific work, named owners and deadlines. Further, it captures immediate commitments. Complex recommendations can be broken down into small steps, making the process easier to track.
Supports future planning and organizational learning
For future projects or events, departments or teams can consult the finished AAR to make informed decisions about resources, timeline, training needs, and risk controls. This helps them avoid previous mistakes and make better plans.
When is an After Action Report Used
An after-action report template is usually used soon after an event, incident, project or drill. Common use cases include:
- Emergency responses and recovery operations
- Emergency drills and simulation exercises
- Completed projects or major project phases
- Production cycles and maintenance shutdowns
- Operational disruptions or service interruptions
- Training programs and organized events
- Marketing campaigns
- Military and tactical operations
The report should be prepared while records are available and participant observations remain fresh. If the review identifies a workplace injury or safety event that needs its own factual record, you may complete a workplace incident report template separately. In an emergency, however, immediate response and safety responsibilities take priority over reporting.
Key Features of This After Action Report Template
Here are the key features of this after-action report template:
- It is available in multiple formats. Use the Google Doc version for multi-team collaboration and the Word version for local storage.
- The standardized structure provides a consistent analytical sequence that is easy to understand for multiple reviewers.
- You can tailor this template to different events, use cases, and record multiple types of findings.
- It provides an elaborate structure to document findings, recommendations, assigned owners, and deadlines.
- The same template can be used to record cross-department participation by different reviewers.
How to Fill Out the After Action Report Template
The template can be used before an activity and completed after it. The managers, team leads, or coordinators may add the activity context, objectives, and expectations. The designated reviewer then documents everything in detail, including what occurred, what went right, and what can be improved. For unplanned events, both parts can be completed afterwards using the available records.
Report identification fields
This is essentially the identification or header section of the After Action Report. It establishes the basic administrative context of the report before the actual analysis begins.
After adding the report Date, the Project, Activity or Event will be added. For a warehouse evacuation exercise, it might read as “North Distribution Center Fire Evacuation Drill.” In case of a natural disaster, you might add “Hurricane Emergency Response.” Make sure that the title is detailed enough so that the reader can easily understand the context of this report.
Next, fill in Location, Prepared By, Submitted To, and Reporting Period. The report date is when the document is prepared or issued, while the reporting period is the time covered by the activity.

Participants/stakeholders
This section lists the personnel who were involved in the activity, including their name, functional role, and departments. Include people whose involvement affected the evidence or conclusions, such as planners, operators, supervisors, observers, and support staff.
Example: The following are a few examples of this section for different types of activities:
| Name | Role | Department |
|---|---|---|
| Maya Torres | Floor warden | Operations |
| Daniel Cho | Safety observer | Environmental health and safety |
| Michael Chen | Project manager | Information technology |
| Christopher Taylor | Safety officer | Operations |

Project/event overview
This section answers the following questions:
- What the activity was about
- What tasks were included
- What deliverables or outcomes were part of it
- Who was responsible for what
- What was within the agreed scope and what was outside it
It should tell a reader what activity was reviewed and what was inside or outside its scope.
Example:

What was expected
This is an important part of the template. It includes objectives, outcomes, standards, or performance benchmarks that are established beforehand. It also records intended goals, regulatory standards, and scheduled milestones. Describe the exact benchmark here that will be used as a standard for the rest of the activity.
For an emergency AAR, this section should record the pre-response expectations that existed before rather than pretending that the emergency itself was planned.
Example: Refer to the following screenshot for examples of planned activities on the left and unexpected emergencies on the right:

What went well
A good after-action report also focuses on the positive aspects. In the section, include the specific action, decision, resource, or practice that yielded a positive result. Describe what worked, why, and its overall effect on the outcome. Give priority to practices that can be repeated, rather than compliments about individual effort.
Example: An example of an emergency evacuation procedure can be:

Opportunities for improvement
This part discusses the areas where the team needs improvement. Use this area to discuss a process that met the basic needs but could become more effective. Discuss the specific practice that can improve the results.
For both the What Went Well and Opportunities for Improvement sections, compare the findings with the What Was Expected section. Then, document what met expectations and what needs to be improved.
Example: An example of this section for building fire or emergency evacuation:

Issues and root cause analysis
In this section, include the process or practices that didn’t work. Discuss what went wrong and how it affected the overall activity in the What Did Not Go Well column. Include the core reasons or causes in the root causes column. Remember that depth and clarity of the statement matter for the information in this section to be effective. Avoid blaming particular personnel here unless individual conduct is directly relevant to the finding.
Example:

Lessons learned
Based on the previous section’s root causes and issues, state the practical knowledge and the lessons that need to be carried forward for future activities. The key is to focus on what should be done differently or repeated to yield better future outcomes. Support each lesson with evidence where possible. You can also use a lessons learned template if you need to cover your information in detail.
Example:

Action items
This section is like the backbone of the report. It offers a pathway to implement the lessons learned by providing actionable steps, assigning responsibility, and including the due date.
The action items should be detailed and specific. The person can be a department or an individual. The due date sets the deadline by which the process will be completed. It also helps the stakeholders to track the progress towards improving future performance.
Example:

Conclusion
The conclusion is the summary of the entire after-action report. Discuss overall performance of the process or how the team handled the event. Then, you may briefly list the positive outcomes as well as shortcomings. Finally, you can discuss the immediate next steps or improvements. You have to be precise here, as this is the section that senior reviewers or decision-makers may read first before going through the entire report.
Example: An example of a conclusion is given below:

Approvals
This section is filled by the personnel who have the authority to approve this AAR. Depending on the project, these may vary. Some examples include:
- Project manager
- Emergency response manager
- Workplace incident manager
- Training or drill executive
- Someone who has organization-wide authority
The responsible personnel may add their name, title or role, signature, and the date of the approval.
Signature in this section confirms the formal review and sign-off according to the company’s policy. It also establishes accountability and creates a formal record.

Appendix A: Improvement plan matrix
The appendices sit after the Approvals block in the template, but they are not a post-approval task. Complete them along with the rest of the report before it goes for sign-off.
The designated person may utilize this section to add more details along with the Action Items section. The items that were prescribed in section 8 can be further classified and described in this table.
In the Task column, add each task and then discuss how to perform it in Recommendations. The Improvement Actions break the recommendations into concrete work. The Responsible part of the table contains the person responsible for carrying forward the task.
In short, the Action Items section is a quick commitment list, but Appendix A is the working plan for a change that needs more detail.
Example:

Appendix B: After-action report participating departments
Replace the bracketed prompt in this section with the names of additional departments that were involved in the process or activity as per this after-action report. It becomes useful when the number of departments or buildings increases. Instead of overwhelming the Participants / Stakeholders section, you can utilize this space as a supplemental space to record departments, facilities, or organizational units.
Example:

How to Customize the Template
You can customize the template to match the specific needs of your review. Depending on the activity being reviewed and the information you need to record, you may adjust its fields, tables, and formatting.
The following changes can be made without altering the template’s overall structure:
Modify rows
You may add more rows to any section, such as the participant, root-cause, action-item, or improvement-plan tables, according to the size of the review.
Adapt the existing labels
Change labels such as Project/Activity/Event, Submitted To, or Responsible Person to match the organization’s terms.
Add columns
Add a small Priority, Status, or Completion Date column if the organization will monitor actions after approval.
Apply organizational branding
You can also add a logo or change the sections’ header colors to match your organization’s brand identity.









