[OPERATION - ENGAGEMENT REF] - Warning Order Build Map
EP-026 Warning Order - build workspace. Central topic = the movement or detail being alerted before the full order package (EP-010 Detail Operations Order) is ready. Branches are the five WARNO paragraphs plus the process gates that bound issue and the admin tail that tracks acknowledgement. Tick each leaf as the fragment is drafted; where a branch executes an EP-010 paragraph, the WARNO carries a placeholder or best-current-estimate for that content pending the full order. → feeds EP-026 Warning Order; seeds EP-010 Detail Operations Order (EP-010 lists EP-026 as an input). Sibling reference: OSINT-030 collection-map style. Use: import to XMind, work top to bottom. Clone the serial blocks under 03 per Be-Prepared-To (BPT) task or subordinate element. Close 99 before the full OPORD (EP-010) supersedes this WARNO.
00 * Process Plan - Gates & Triggers
The trigger that starts WARNO drafting and the gate checklist it must clear before issue. → EP-010 Order Control (Order Control table: OPORD Reference, DTG Issued, Detail Identifier, Principal, Deployment Period, AO, Distribution) and EP-010 inputs list (EP-026 feeds EP-010).
Issue trigger
- Triggering event identified: [new tasking / engagement order / principal movement notified / threat change]
- Time available for planning (TAP) estimated: [ ]
- LTIOV (latest time information of value) set: [DDHHMMZ MON YY]
- Decision: [ ] issue WARNO now vs. wait for fuller order package
Gate checklist before issue
- Detail Identifier assigned → EP-010 Order Control
- Principal designator confirmed (codename/initials only, no real name) → EP-010 Order Control
- Deployment period (start/end) known or best estimate stated → EP-010 Order Control
- Area of operations named at least at country/region level → EP-010 Order Control / ART-region-package
- Classification / handling level set → EP-010 Order Control handling block
- Distribution list drafted (roster / named recipients) → EP-010 Order Control
- Reference products identified even if not yet received: ART-protective-intel-assessment, EP-001, EP-002, EP-004, EP-009, EP-011, EP-012 → EP-010 Reference Products and Annexes table
Open pre-issue gaps / RFIs
- [gap] → route to [tasking authority / D-01 collection / EP-002 advance]
- [gap]
01 * Situation Snapshot
Best-current-estimate of threat, principal, and operating environment at WARNO time; not the full assessment. → EP-010 Section 1 Situation (1.1 Threat, 1.2 Principal and Party, 1.3 Supporting/Adjacent Elements, 1.4 Attachments/Detachments, 1.5 Operating Environment).
Threat snapshot (1.1)
- Assessed threat actors and intent (interim): [ ]
- Most likely course of action (interim): [ ]
- Most dangerous course of action (interim): [ ]
- Current posture: [Low / Moderate / Elevated / High / Critical] (L x I [1-25])
- Source: [ART-protective-intel-assessment reference or interim D-01 product]
- Confirm/replace at full OPORD → EP-010 1.1
Principal and party snapshot (1.2)
- Principal designator / initials: [ ]
- Party under protection (initials only): [ ]
- Known pattern-of-life sensitivities to carry forward: [ ] → EP-001 (do not restate protected detail here)
Supporting and adjacent elements (1.3)
- Local law enforcement liaison (if known): [ ]
- Venue/event security point of contact (if known): [ ]
- Other details or advance elements already tasked: [ ]
Attachments and detachments (1.4)
- Augmentation expected (operators, vendors, medic): [ ] → ART-vendor-roster
- Elements detaching, if known: [ ]
Operating environment (1.5)
- Area of operations and jurisdiction boundaries (interim): [ ]
- Common operating picture access confirmed: [ ] → ART-common-operating-picture
02 * Draft Mission
One sentence, who/what/when/where/why, no compound tasks. → EP-010 Section 2 Mission.
- Draft mission statement: [The (Detail Identifier) protects (Principal) during (Period / Movement) within (AO) in order to (purpose).]
- Decision: [ ] mission statement locked for WARNO issue vs. flagged as provisional pending EP-010 finalization
- Mission statement carried forward unchanged into EP-010 Section 2 at full-order drafting
03 * Execution - General Concept, Timeline, Be-Prepared-To Tasks
Detail Leader’s provisional intent, the phase concept, and BPT tasks issued to each subordinate element so preparation starts before the full order. → EP-010 Section 3 Execution (3.1 Intent, 3.2 Concept of Protection by Phase, 3.3 Tasks to Subordinate Elements, 3.4 Coordinating Instructions).
General concept (3.1 / 3.2)
- Purpose (provisional intent): [ ] → EP-010 3.1
- Key tasks (3-5, provisional): [ ]
- End state: [ ] → EP-010 3.1
- Phase concept snapshot: [Residence/RON → Movement → Venue/Advance → Return/Recovery] → EP-010 3.2 phase table
- Governing products expected per phase: [EP-009 / EP-004+EP-003 / EP-002 / EP-009] → EP-010 3.2
Timeline (3.2 / coordinating instructions)
- Key timings known now: [muster / step-off / no-later-than] → EP-010 3.4
- Rehearsals anticipated: [embus under threat / evacuation / medical] → EP-010 3.4
- No-go / abort criteria (provisional): [ ] → EP-010 3.4
Be-Prepared-To (BPT) task serial
Clone per subordinate element (Detail Leader, Shift Lead, CPO, Driver, Advance, Detail Intelligence Officer, Static Posts). → EP-010 3.3 Tasks to Subordinate Elements.
- [element - e.g. Close Protection Officer(s)]
- BPT task: [ ]
- Preparation required before full order: [kit / rehearsal / liaison]
- Governing EP-010 subparagraph: → 3.3 [role line]
- Confirmation of receipt: [ ] initials / time
- Notes: [ ]
- [element 2 - e.g. Driver(s)]
- BPT task: [ ]
- Preparation required before full order: [ ]
- Governing EP-010 subparagraph: → 3.3 [role line]
- Confirmation of receipt: [ ]
- Notes: [ ]
Surveillance detection and ROE flag (coordinating instructions)
- Surveillance detection posture anticipated: [deployed / not deployed - reference EP-007/EP-008] → EP-010 3.4
- Use-of-force posture anticipated: [unarmed defensive / armed per local license - reference region package legal annex] → EP-010 3.4
04 * Admin & Logistics to Initiate
The sustainment actions that must start now so the detail is postured when the full order issues. → EP-010 Section 4 Administration and Logistics (4.1 Personnel, 4.2 Logistics, 4.3 Medical, 4.4 Legal and Administrative).
Personnel actions to initiate (4.1)
- Roster / shift structure drafted → EP-010 4.1
- Duty-hour / relief limits set (no operator exceeds [N] hours without relief) → EP-010 4.1
- Accountability reporting cadence set → EP-010 4.1
Logistics actions to initiate (4.2)
- Vehicle tasking initiated (count, type, armor rating) → EP-010 4.2 / EP-004
- Equipment and loadout list issued (comms, protective, medical) → EP-010 4.2
- Weapons/munitions status confirmed against jurisdiction licensing, or unarmed stated → EP-010 4.2
- Billeting and sustenance arranged → EP-010 4.2
Medical actions to initiate (4.3)
- Detail medic and kit tasked → EP-010 4.3
- Nearest Level 1 trauma facility identified (interim, pending EP-002) → EP-010 4.3
- CASEVAC sequence referenced from EP-012 confirmed available → EP-010 4.3
Legal and administrative actions to initiate (4.4)
- Jurisdiction and licensing basis confirmed (armed/unarmed authority) → EP-010 4.4 / region package legal annex
- After-action and incident documentation process confirmed ready → EP-010 4.4 / EP-017
05 * Command & Signal
Who is in charge for the interim period and how the detail communicates before the full PACE plan is confirmed. → EP-010 Section 5 Command and Signal (5.1 Command, 5.2 Signal).
Command (5.1)
- Chain of command (provisional): [Team Leader → Detail Leader → Shift Lead → operators] → EP-010 5.1
- Succession of command if Detail Leader unavailable: [ ] → EP-010 5.1
- Decision authority split (Shift Lead vs. Detail Leader): [ ] → EP-010 5.1
Signal (5.2)
- Nets/channels confirmed active: [Command / Detail / Transport] → EP-010 5.2 / EP-011
- Call signs confirmed: [ ] → EP-010 5.2
- Next communications check time: [ ] → EP-010 5.2
- Duress and lost-comms procedure referenced and understood: [ ] → EP-010 5.2 / EP-011
- Next order time (time and format of the follow-on order or full OPORD): [DDHHMMZ MON YY]
99 * Execution Admin
Acknowledgement tracker for this WARNO, the running deviation log, and the handoff point to the full EP-010 order; not itself a deliverable section. → EP-010 Order Control and Reference Products and Annexes table.
Acknowledgement tracker
Clone per recipient.
- [recipient - initials / role]
- WARNO received: [ ] time
- Acknowledged: [ ] time
- Questions / RFIs raised: [ ]
- [recipient 2]
- WARNO received: [ ]
- Acknowledged: [ ]
- Questions / RFIs raised: [ ]
Deviation / change log (running)
- [change since issue - e.g. mission, timeline, principal status]: [ ] time / who authorized
Product register
- WARNO issued: [ ] DTG
- Superseding EP-010 Detail Operations Order status: [not started / in progress / issued] → EP-010
- Referenced products received to date: [ART-protective-intel-assessment / EP-001 / EP-002 / EP-004 / EP-009 / EP-011 / EP-012]