SENTINEL // WATCHMAN

MODULE 01 · SENTINEL

OPSCON Level Definitions

Define the five readiness conditions — what each one means, what the threat picture looks like, and how your group should orient.

SENTINEL uses a 5-to-1 descending scale modeled on DEFCON and the NIMS EOC Activation Framework (IS-700.b). Level 5 is normal baseline. Level 1 is immediate action — A Failure of Civility. Each level has a color code, threat picture, and posture statement. Edit these fields to match your specific AO. Doctrinal basis: NIMS IS-700.b, CPG 101 V2, A Failure of Civility (Lawson), SHTF Intelligence (Culper), Survival Theory II (Hollerman).

MODULE 02 · SENTINEL

Trigger Events

Document the specific observable conditions that justify a level change. Vague triggers get ignored. Specific triggers get followed.

Trigger events are observable, specific, confirmable conditions — not feelings. "Civil unrest spreading to neighboring county" is a trigger. "Things feel tense" is not. Each trigger is tied to a specific OPSCON level change. Doctrinal basis: SHTF Intelligence indicator framework (Culper), Survival Theory II threat timeline (Hollerman), CPG 101 V2 threshold events, A Failure of Civility alert criteria (Lawson).

+ ADD TRIGGER EVENT

MODULE 03 · SENTINEL

Actions by Level

For each OPSCON level, document the specific actions required — what to activate, stage, suspend, and who to notify.

Actions are what make SENTINEL operationally relevant. Without defined actions, a level change is just a number. For each level: what systems activate, what gear is staged, what personnel posture changes, which WATCHMAN modules to reference, and what comms are initiated. Doctrinal basis: AFOC Low/Mid/High Alert procedures (Lawson Ch. 6), NIMS EOC activation protocol (IS-700.b), Retreat Security (Kobler/Goodwin), Contact! stand-to protocol (Max Velocity).

+ ADD ACTION ITEM

MODULE 04 · SENTINEL

Current Status Log

Log every OPSCON level change with date, time, who called it, why, and what triggered it.

The status log creates accountability and a record for after-action review. When you look back at a crisis, you need to know what you knew, when you knew it, and what decisions were made. Log every level change — including routine returns to baseline. This data feeds the Status Log Report output. Doctrinal basis: TC 25-20 AAR doctrine; NIMS documentation standards (IS-700.b).

CURRENT OPSCON LEVEL

— UNSET —

+ LOG LEVEL CHANGE

MODULE 05 · SENTINEL

Laminate Card Data

Condensed per-level data for the pocket reference card every group member carries.

Every group member carries a laminated OPSCON reference card — wallet-sized, with the five levels, their plain-language meaning, key trigger summary, and 2–3 immediate actions for each. This card is the entire operational point of the module. Enter your condensed language here and generate from the Outputs panel. Doctrinal basis: A Failure of Civility level dress/posture codes (Lawson); NIMS simplified activation language (IS-700.b).

MODULE 06 · SENTINEL

Grid & Nuclear Intel

Infrastructure alerts pushed from the Area Intel Map. Review, promote to triggers, or dismiss.

OUTPUTS · SENTINEL

Generate Documents

Print-ready reference outputs from your SENTINEL data.

OUTPUT 1

OPSCON Laminate Card

Wallet-sized card with all 5 levels, trigger summaries, and immediate actions. One per group member. Print, laminate, distribute.

OUTPUT 2

Level Action Checklist

Full action checklist for each OPSCON level. Post in your operations center or watch station.

OUTPUT 3

Status Log Report

Printed record of all level changes with timestamps, callers, reasons, and triggers. For AAR and documentation.

OUTPUT 4

Full OPSCON Document

Complete readiness condition framework — all levels, triggers, and actions in one reference document.

Data Management

Key: ao_sentinel_v1 · Export before clearing.