Version 1.1

After-Action Reviews & Data Hygiene

Learn how to run structured debriefs after actions, capture lessons without compromising security, and securely store or destroy sensitive data.

15 min readΒ·Qualified Lesson

πŸ—ƒοΈ After-Action Reviews & Data Hygiene

Observation & Legal Track
Court & Post-Raid Support

Important

24-Hour Rule: Debriefs and data triage should start within 24 hours of an action. Lingering files = lingering risk.


Why It Matters

Pods often collect photos, video, chat logs, and field notes during actions.
If not handled correctly, this data can endanger community members if devices are seized, hacked, or subpoenaed.
Structured debriefs also make pods smarter and more resilient by learning from mistakes without fracturing trust.


Core Protocols

1. Structured Debriefs (Blame-Free Zone)

Hold a debrief within 24–48 hours using this structure:

  1. Timeline Review – What happened, in order
  2. Gaps Identified – Where did plans break down?
  3. Successes – What worked well?
  4. Action Items – Who will fix or implement what, by when

Rules for Debrief Notes:

  • No personal names. Use role labels (e.g., β€œMedic 1,” β€œObserver 3”).
  • Take notes only on paper or encrypted pads (e.g., Signal Notes or VeraCrypt).
  • Destroy notes after 30 days unless they are required for legal or retraining.

2. Data Triage Flow

3. Secure Storage Guidelines

Data TypeStorage MethodRetention Period
Bodycam / videoVeraCrypt USB drive + 1 encrypted backup90 days (max)
Comms logs (Signal)Export to encrypted local drive (no cloud)30 days
Medical recordsPaper in locked safe, no digital copies1 year (or legal req.)

Risk Mitigation

RiskSolution
Device seizure during actionUse burner phones and auto-wipe apps (ObscuraCam for photos)
Subpoena for chat logsAvoid cloud services (iCloud/Google). Use Matrix or Signal only
Debrief leaksHold reviews in person or on encrypted voice (Signal/Jitsi)
Over-collection of footageFilm only when needed for legal proof, not documentation habit

Warning

The safest data is data you never collect. Only keep what is legally or tactically essential.


Tools & Templates

Debrief One-Pager

  • Timeline Review (15 min)
  • 3 Wins / 3 Gaps (15 min)
  • Next Steps (owner + deadline)

Data Hygiene Cheat Sheet

  • Day 0: Move all files off phones to encrypted storage
  • Day 1: Anonymize faces and scrub personal details
  • Day 3: Legal review completed, purge all non-essential data

Chain of Custody Form

[Description]____________________
[Collected By]___________________
[Time/Location]__________________
[Storage Method]_________________
[Accessed By]____________________
[Purpose]________________________


Roleplay Scenario (Certification Drill)

After a raid response, your pod has:

  • 12GB of protest footage
  • Medical intake forms with real names
  • Signal chat logs containing location data

Your task:

  1. Use the Data Triage Flow to decide what stays, gets anonymized, and what must be deleted.
  2. Draft a debrief agenda focusing on safety gaps without naming individuals.
  3. Identify which materials need a chain-of-custody record for court support.

Final Checklist

  • Ran a structured debrief within 48 hours of the action
  • Encrypted or destroyed all raw footage and logs within 3 days
  • Completed chain-of-custody forms for any evidence retained
  • Implemented at least one tactical improvement from lessons learned
  • Ensured no personal devices stored sensitive logs long-term

Success

The most secure pod is one that learns fast and leaves no unnecessary data behind.

πŸ“˜ Knowledge Check


🚫 You must register and log in to mark this lesson as qualified. Registering helps us track progress, verify training, and build trust across our network.

You can use your Dispatch login here if you already created an account there. Likewise, creating an account here will let you use the same credentials on Dispatch.

Complete and pass the quiz above to unlock this button. You’ll need at least 80% correct.