# After-Action Analysis and Improvement Planning

After every significant incident, emergency management teams conduct an After-Action Review (AAR) to identify what worked, what did not, and what needs to change. This process is critical but often done poorly — reports sit on shelves, findings are vague ("improve communication"), and corrective actions lack accountability. AI can make this process dramatically more rigorous.

Structuring the After-Action Review

AI helps organize the massive amount of information generated during an incident:

AFTER-ACTION REVIEW FRAMEWORK
Incident: [Winter storm — 72-hour power outage affecting 45,000 residents]
Duration: [Date/time start to date/time end]

Using the following source materials:
- EOC log entries [paste or summarize]
- Situation reports [paste or summarize]
- Agency reports from [fire, police, public works, health dept]
- Media coverage summary
- Social media monitoring summary
- Public complaints received

Structure an After-Action Report covering:
1. INCIDENT TIMELINE: Key events, decisions, and milestones in chronological order
2. WHAT WENT WELL: Specific actions, decisions, or capabilities that were effective
3. AREAS FOR IMPROVEMENT: Specific shortfalls organized by function
   (command/coordination, operations, logistics, planning, communications)
4. ROOT CAUSES: For each major shortfall, identify the underlying cause
   (was it a plan deficiency, training gap, resource shortage, or decision error?)
5. CORRECTIVE ACTIONS: Specific, measurable actions with responsible
   party and target completion date