AO OVERWATCH : DEBRIEF
AFTER ACTION REVIEW SYSTEM  ·  MODULE 23
⌂ COMMAND SUITE
MODULE 01  ·  DEBRIEF
AAR Registry
All completed after-action reviews — indexed by event type, date, and severity.

DEBRIEF applies the military After Action Review format to real preparedness events: power outages, storms, medical incidents, security concerns, drills, and evacuations. The AAR is the learning mechanism of the entire suite. Every significant event — whether it went well or badly — is an opportunity to improve. An AAR that stays in a notebook and doesn't result in a corrective action wastes the event.

+ ADD ENTRY
MODULE 02  ·  DEBRIEF
New After Action Review
Start a structured AAR for a specific event — what was planned, what happened, what went well, what failed, and what changes are required.

The military AAR has four core questions: What was supposed to happen? (your plan, your preparedness posture) What actually happened? (the event as it unfolded) What went well and why? (sustain these) What needs improvement and why? (fix these). Every finding should produce a corrective action. A finding without an action is just a complaint.

+ ADD ENTRY
MODULE 03  ·  DEBRIEF
Corrective Action Tracker
Track all open corrective actions from AARs — assigned to a person, with a target date and current status.

The corrective action tracker is where AARs produce real change. For every finding that requires action: what specifically needs to change, who is responsible for changing it, by when, and what does done look like? Link each action to the specific module it affects — a medical supply gap links to Trauma One, a comms failure links to Comms Matrix. Close actions when the change is verified, not just planned.

+ ADD ENTRY
MODULE 04  ·  DEBRIEF
Module Update Log
Track which AO Overwatch modules have been flagged for update based on AAR findings.

An AAR finding that your bug-out bag is missing a water filter is useless if it never results in updating your LOADOUT module. The module update log connects DEBRIEF to the rest of the suite. When an AAR produces a finding that affects another module, log it here — which module, what needs updating, and who is responsible for making the update. This is the connective tissue that keeps the suite accurate to reality.

+ ADD ENTRY
MODULE 05  ·  DEBRIEF
Trend Analysis
Identify recurring issues that appear across multiple AARs — systemic problems that need systemic solutions.

A single AAR finding might be a one-time anomaly. The same finding appearing in three AARs is a systemic problem. The trend analysis reviews all completed AARs and looks for patterns: the same module flagged repeatedly, the same person identified as a bottleneck, the same resource found lacking. Systemic problems require systemic solutions — not individual corrective actions but changes to protocols, training, or equipment procurement.

+ ADD ENTRY
OUTPUTS  ·  DEBRIEF
Generate Documents
Print-ready reference outputs.
OUTPUT 1
AAR Summary Report

Single-page summary of a specific event with all findings and actions.

OUTPUT 2
Open Actions Report

All outstanding corrective actions across all AARs with due dates.

OUTPUT 3
Module Update List

Modules flagged for update with the specific changes required.

OUTPUT 4
Trend Analysis Report

Recurring themes across all AARs with recommended systemic fixes.

Key: ao_debrief_v1  ·  Export before clearing.