Write an after-action report and improvement plan
An after-action report that rates performance against each objective, finds root causes, and produces a tracked improvement plan.
The prompt
Help me write an after-action report (AAR) and improvement plan.
Event: [real incident or exercise; type, e.g. "tabletop", "functional exercise", "winter storm response"]
Dates and participating agencies: [DETAILS]
Objectives or core capabilities tested: [e.g. "operational communications", "mass care", "public information and warning"]
Timeline of key events: [PASTE]
Hot wash notes, evaluator feedback, participant surveys: [PASTE]
What went well and what didn't, in my words: [NOTES]
Structure the report following the Homeland Security Exercise and Evaluation Program (HSEEP) style:
1. Executive summary: scope, major strengths, and primary areas for improvement.
2. Event overview: dates, participants, scenario or incident summary.
3. Analysis by objective or capability: rate each objective (performed without challenges / with some challenges / with major challenges / unable to be performed), then list strengths and areas for improvement. For each area, give the observation, the analysis of root cause (plans, organization, equipment, training, or exercise design), and a recommendation.
4. Improvement plan table: Capability | Issue | Corrective action | Category (plan, organization, equipment, training, exercise) | Responsible organization | Point of contact (title) | Start date | Completion date.
5. Items to test in the next exercise.
Rules:
- Focus on systems and processes, not blaming individuals.
- Every finding must trace to an observation in my notes; never invent events, times, or quotes. Mark gaps [CONFIRM].
- Flag any sensitive security details that should be removed before public release.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- DETAILS
- PASTE
- NOTES
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Write a control plan for a production processA control plan that turns my product and process characteristics into what to check, how, how often, and what to do when it fails.
- Prepare a PPAP submission package for my customerA checklist of every PPAP element at my submission level, the status of each, and a plan to close gaps before the due date.
- Write a shift handover note so nothing falls through the cracksA structured handover from one shift to the next covering open issues, safety, status, and what the next shift must do first.