AFTER-ACTION REPORT

[DETAIL / ENGAGEMENT NAME - ENGAGEMENT REF]

The After-Action Report is the primary learning-loop document, detailing timeline reconstructions, metric deviations, corrective action registers, and doctrine feedback loops. Do not assert fictional findings or invent data.


Document Control

FieldValue
Report Reference[REF-YYYY-###]
Date of Report[YYYY-MM-DD]
Reporting Period / As-Of Date[YYYY-MM-DD]
Classification / Handling[internal / CONFIDENTIAL]
Client[CLIENT NAME]
Requesting Party[REQUESTER NAME / ID]
Prepared By[ANALYST NAME / ID]
Reviewed By[REVIEWER NAME / ID]
Approving Officer[APPROVER NAME / ID]
Version[0.1.0]
Distribution[NAMED RECIPIENTS]

Handling: [internal / CONFIDENTIAL]. Access restricted to active operational team.

Purpose: Document lessons learned and feed corrective actions back into standard planning cells.

Subject Snapshot

FieldValue
Incident Date[YYYY-MM-DD]
Detail Reference[DETAIL REF]
Incident Type[Standard AAR / EAP Activation / Security Breach]
Severity Level[Low / Moderate / Elevated / High / Critical]

Table of Contents

  1. AAR Policy
  2. Facilitation Method
  3. Metrics Block
  4. Incident Cross-Reference
  5. Corrective Action Register
  6. Doctrine Feedback Loop
  7. Distribution & Retention

1. AAR Policy

Instructional tradecraft: Define when an AAR is mandatory, draft timelines, and review deadlines.

  • Mandate: An AAR is mandatory within [N] hours of engagement termination, any EAP activation, or any reportable security incident.
  • Timelines: Draft completed within [N] hours by Detail Leader; Review Board convened by Operations Manager within [N] days.
  • Dissemination: The finalized AAR is the ART-after-action-report artifact; beyond the Review Board it feeds PIR management (EP-019), the training and readiness program (EP-029), and the lessons-ingestion pipeline (AGT-010), which proposes doctrine diffs for owner review.

2. Facilitation Method

Instructional tradecraft: Outline the timeline reconstruction and chronolog. Grade all sources per Admiralty.

  • Method: structured review answering:
    1. What was planned?
    2. What actually happened?
    3. Why was there a difference?
    4. What do we sustain?
    5. What do we improve?

2.1 Chronological Timeline Reconstruction

TimestampEvent DescriptionSourced FromAdmiralty Grade
[HH:MM:SS][Event Detail][Log / Audio / Video][A1-F6]
[HH:MM:SS][Event Detail][Log / Operator Account][B2]

3. Metrics Block

  • Medical Response latency: [MINUTES / SECONDS] from trigger to evacuation.
  • Comms Failures: [COUNT] radio drops or signal dropouts.
  • Advance Accuracy: [COUNT] discrepancies between advance report and actual site layout.
  • Near-Misses: [COUNT] security boundary close-calls.

4. Incident Cross-Reference

  • Related EAP log: [REF ID].
  • Related Daily Brief: [REF ID].

5. Corrective Action Register

Instructional tradecraft: Record all corrective actions, assigning owner roles and verification methods (I/A/D/T).

#FindingRoot CauseCorrective ActionOwner RoleDue DateVerificationStatus
1[e.g. Driver route error][GPS signal loss][Mandatory route card printout]Lead Driver[YYYY-MM-DD]Test[Open / Closed]

6. Doctrine Feedback Loop

Instructional tradecraft: Detail the trigger rules that update the parent post orders, PACE, and PIRs.

  • Rule A: Any communication failure updates the PACE plan (EP-011) failover triggers.
  • Rule B: Access control lapses directly update EP-009 Post Orders.
  • Rule C: New POI tactics immediately update the Standing PIRs in EP-019.

7. Distribution & Retention

  • Distribution: Operations Manager, Team Leader, Detail Leader.
  • Retention Period: Retained securely for [N] years post-engagement.

END OF REPORT

Model wiring

Generated from cell frontmatter at publish time.