Drafting an After Action Report

Drafting an After Action Report

 

Overview

Following a significant incident, commanding officers must file a Post Incident Analysis (PIA) and an After Action Report (AAR).
Any incident involving a near miss requires completion of the Human Performance Improvement Form (Survey123) in addition to the PIA.

Incidents Requiring a PIA

• Greater than a first alarm

• Any rescue incident

• Civilian death

• Working fire rekindle

• Equipment damage, injury, or near miss requiring a Level Two investigation per SOP 11.09.00 – Risk Management Investigation Procedures

• At the request of the Incident Commander or Senior Staff

• Any technical rescue incident

Step 1: Collect Post Incident Analysis Fact Sheets

Each unit completes a Post Incident Analysis Fact Sheet capturing:

• Arrival Conditions: Describe scene, pre-arrival orders, size-up, placement, and assignments.

• Actions and Benchmarks: Chronological list of assignments, actions, and benchmarks.

• Obstacles: Communication issues, equipment failures, or resource challenges.

• Alternative Actions: What could have been done differently.

• Self-Critique: Evaluate personal and crew decisions.

• Overall Incident Critique: Assess overall operation effectiveness.

• Additional Comments: Any relevant observations not covered elsewhere.

Step 2: Compile and Process the Data

Gather all completed fact sheets and upload them — along with the blank AAR template — into your AI workspace.
Use the master prompt below to generate a complete, formatted report.

Master Prompt (Copy and Paste)

 

Role: You are an analyst drafting an After Action Report (AAR) from multiple unit fact sheets and a blank AAR template.
Goal: Produce a clean, approval-ready draft that follows the provided section headings exactly.

Inputs

• Multiple Incident Analysis Fact Sheets

• Blank AAR Template (Appendix B)

Objectives

1. Merge all unit inputs into one concise AAR.

2. Preserve identifiers, times, and accurate phrasing.

3. Highlight contradictions or missing info as Gaps.

4. Generate actionable follow-ups with owners and due dates.

Method

• Extract key details from each fact sheet (size-ups, benchmarks, issues, safety, improvements).

• Build a single integrated timeline.

• Resolve duplicates and note discrepancies as “Gaps.”

• Write under template headings only.

• Ensure clarity, neutrality, and traceability.

Output

• A completed AAR with “Gaps” section at the top.

• Action Items table with at least 5 tasks (each with owner, due date, and success measure).

Example: After Action Report (Sample)

GAPS IDENTIFIED

• Missing exact timestamps for dispatch, water on fire, and cleared case

• Patient outcome post-transport not recorded

• No data from second/third alarm units

• PIA completion status not confirmed

AFTER ACTION REPORT

Incident Location: Ocean View Grand Hotel – 9th Floor Fire
Date of Incident: [Placeholder]
Incident Number: [Placeholder]
First Alarm Units: Engine 12, Ladder 9, Medic 12, Engine 14, Battalion 2

Times

• Received: [Placeholder]

• Dispatched: [Placeholder]

• First Arrival: Engine 12 – [Time Needed]

• Water on Fire: ~6 min after arrival

• Fire Under Control: 21 min post-arrival

• Cleared: [Placeholder]

INCIDENT SUMMARY

Upon arrival, Engine 12 reported light smoke from the 9th floor. Civilians were self-evacuating. Engine 12 secured a hydrant, advanced via stairwell, and began fire attack.
Ladder 9 forced entry to Room 916, removed one unconscious victim, and transferred care to Medic 12.
Battalion 2 established command; Engine 14 served as RIC. Fire knockdown achieved in six minutes; control declared at 21 minutes.

TACTICAL OBSERVATIONS

Rescue

• Civilian rescued from Room 916 by Ladder 9

• ALS care and transport by Medic 12

• Minor delay in forcible entry due to door reinforcement

Exposures & Confinement

• No vertical spread; contained to origin room

• Positive pressure ventilation prevented smoke travel

Extinguishment

• Knockdown achieved in six minutes

• Secondary search and overhaul completed

Command & Communication

• Benchmarks called in sequence

• Radio traffic congestion early on TAC channels

• Delay accessing elevator override panel

ACTION ITEMS

SUMMARY

This high-rise incident demonstrated effective coordination under smoke-limited visibility.
The rescue was successful, containment rapid, and benchmarks achieved.
Improvements focus on radio discipline, pre-incident planning, and elevator system familiarity.

ATTACHMENTS & REFERENCES

• Unit Fact Sheets: Engine 12, Ladder 9, Medic 12, Engine 14, Battalion 2

• AAR Template: SOP 2.02.02 Appendix B

• SOP Reference: Incident Command System SOP 5.01.00

Pro Tip

For real-world use, attach the generated AAR PDF to your department’s SharePoint or Drive and link it to the corresponding incident number for audit trail continuity.