After Action Reporting and Improvement Plans
In the face of an emergency, the urge to swiftly resume normal operations can be overwhelming. However, it is essential not to rush past the crucial steps of conducting an After Action Report (AAR) and developing an Improvement Plan (IP). These often-overlooked processes are the keys to learning and evolving in the wake of a crisis, ensuring an organization's future resilience and success.
Take a moment to reflect: How did communication flow during the crisis? Who assumed leadership roles? Did your actions align with your pre-established plans? What should be your next steps? After Action Reporting offers a clear and comprehensive understanding of the incident, highlights lessons learned in the context of response and recovery, and lays out strategies for continuous improvement in preparation for future challenges.
What Is an After Action Report (AAR)?
An After Action Report is a structured review process conducted after an emergency, incident, exercise, or other significant event. Rooted in military practice and adopted widely across emergency management and EHS, the AAR provides a disciplined framework for examining what happened, why it happened, and how the organization can improve.
The AAR is typically paired with an Improvement Plan (IP) to form the AAR/IP, which together serve as the foundation for organizational learning. While the AAR documents and analyzes the event, the IP translates those findings into concrete, trackable corrective actions.
When Should an AAR Be Conducted?
An AAR should be conducted after any event where there is an opportunity to learn and improve. Common triggers include:
- Any real emergency or crisis (fires, chemical releases, severe weather events, medical emergencies, etc.)
- Near misses with significant potential for harm or damage
- Exercises, drills, and tabletop simulations
- Any incident that activated all or part of the emergency response plan
- Regulatory inspections or audits that revealed significant gaps
- Events at other facilities in your industry that could have happened at yours
The AAR Process
A well-structured AAR follows a systematic process to ensure thorough analysis and actionable outcomes:
Step 1 - Gather Information
Collect all relevant data before the formal review meeting. This includes:
- Incident reports, logs, and timelines
- Communication records (radio logs, emails, notifications)
- Photos, video, or other documentation
- Relevant plans, procedures, and checklists that were (or should have been) followed
- Input from external responders (fire department, hazmat teams, regulatory agencies)
Step 2 - Conduct the Hot Wash
A hot wash is an immediate, informal debriefing conducted within 24-72 hours of the event. The purpose is to capture initial observations while they are fresh. Keep the hot wash focused and concise. Capture key takeaways and areas for further analysis without assigning blame.
Step 3 - Conduct the Formal AAR Meeting
Bring together all relevant participants for a structured review. This meeting should:
- Walk through the event chronologically using the established timeline
- Compare actual actions to planned procedures and expected outcomes
- Identify what went well (sustains) and what needs improvement (areas for improvement)
- Discuss root causes, not just surface-level observations
- Ensure all functional areas are represented (operations, safety, management, communications, etc.)
Step 4 - Document the AAR
Compile findings into a written report. The AAR document should include:
- Executive summary of the event and key findings
- Incident overview, including a detailed timeline of events
- Analysis organized by functional area (notification, communication, evacuation, containment, medical response, etc.)
- Strengths and areas for improvement for each functional area
- Root cause analysis for significant issues
- Lessons learned with supporting evidence
Step 5 - Develop the Improvement Plan
Translate findings into specific, measurable corrective actions. Each action item in the IP should include:
- A clear description of the corrective action
- The functional area or capability it addresses
- A responsible party assigned to complete it
- A target completion date
- Required resources or budget
- A method for verifying completion and effectiveness
Step 6 - Track and Verify Completion
The Improvement Plan is only as valuable as its execution. Assign ownership for tracking progress, review status at regular intervals, verify that completed actions are effective, and update emergency plans and procedures accordingly.
Key Questions to Ask During the AAR
Effective AARs are built around the right questions. Consider organizing your review around these core areas:
What Is an Improvement Plan (IP)?
The Improvement Plan is the action-oriented companion to the AAR. It translates lessons learned into specific, measurable corrective actions that prevent the same issues from recurring. Without an IP, the AAR becomes an academic exercise that sits on a shelf.
An effective Improvement Plan typically tracks items in a structured format:
| Finding | Corrective Action | Responsible Party | Target Date | Status |
|---|---|---|---|---|
| Delayed notification to plant manager | Update emergency notification procedure; add backup contacts | Safety Manager | 30 days | Open |
| Employees unsure of evacuation assembly points | Conduct evacuation drill; update signage at all exits | EHS Coordinator | 45 days | Open |
| Spill kit contents insufficient for incident size | Upgrade spill kits in chemical storage areas; add secondary kits | Environmental Manager | 60 days | Open |
AAR Best Practices
To maximize the value of your After Action Reporting process, follow these best practices:
Create a Blame-Free Environment
Focus on systems and processes, not individuals. Participants will be more forthcoming when they feel safe sharing honest observations.
Include All Perspectives
Involve personnel from all levels and functions that participated in or were affected by the event. Include external responders when appropriate.
Use a Facilitator
An experienced facilitator, ideally someone who was not directly involved in the response, can guide the discussion objectively and keep it productive.
Document Both Strengths and Weaknesses
It is just as important to identify and reinforce what went well as it is to identify areas for improvement. Recognizing strengths keeps teams motivated.
Be Specific and Actionable
Vague findings like "communication needs improvement" are not helpful. Specify what communication, between whom, at what point, and what the corrective action should be.
Set Realistic Timelines
Improvement Plan items should have achievable target dates. Prioritize high-risk items and phase implementation of longer-term improvements.
Follow Through
The most common failure mode for AARs is lack of follow-through on the Improvement Plan. Assign clear ownership and review progress at regular intervals.
Share Lessons Learned
Distribute findings across the organization and to other facilities where applicable. Lessons learned at one location can prevent incidents at another.
How Can EHS Software Help?
EHS software streamlines the entire AAR/IP lifecycle, from initial incident documentation through corrective action tracking and verification. Ecesis provides integrated tools to support every phase of the process:
Incident Management
Document incidents, build timelines, and conduct root cause analysis in a centralized system.
Task Management
Track Improvement Plan corrective actions with assigned owners, due dates, and status updates.
Emergency Planning
Maintain and update emergency response plans based on AAR findings.
Training Management
Schedule and track training identified as corrective actions in the Improvement Plan.
Document Management
Store AAR reports, improvement plans, and updated procedures in a centralized repository.
Inspections & Audits
Verify corrective action completion through follow-up inspections and audits.
