WARNING ORDER
[DETAIL IDENTIFIER - ENGAGEMENT REF]
The WARNING ORDER (WARNO) is the abbreviated advance order that alerts the detail and initiates planning before the full DETAIL OPERATIONS ORDER (OPORD, [EP-010]) is issued. It is written as the same five-paragraph field order as the OPORD (Situation, Mission, Execution, Administration and Logistics, Command and Signal), compressed to what must move now: a provisional mission, the tasks that begin immediately, and the timeline that governs planning per the [EP-020] Advance Planning Cycle. It does not supersede the OPORD and carries no findings of its own; it points to the products building toward Gate G1 and states when the OPORD will supersede it. This is a repeatable template. All engagement-specific values are bracketed placeholders. Do not assert fictional findings or invent data.
Order Control
| Field | Value |
|---|---|
| WARNO Reference | [REF-YYYY-###] |
| Date-Time Group Issued | [DDHHMMZ MON YY] |
| Detail Identifier | [ ] |
| Principal | [PRINCIPAL DESIGNATOR / INITIALS] |
| Anticipated Deployment Period | [YYYY-MM-DD] to [YYYY-MM-DD] (provisional) |
| Area of Operations | [CITY / REGION - reference ART-region-package] |
| Classification / Handling | [internal / CONFIDENTIAL - CLIENT EYES ONLY] |
| Issued By (Team Leader) | [INITIALS] |
| Advance Lead Designated | [INITIALS] |
| Distribution | [DETAIL ROSTER / NAMED RECIPIENTS] |
| Supersedes | None (initiating order for this engagement instance) |
| Superseded By | [EP-010] OPORD, planned [DDHHMMZ MON YY] (Gate G5, [EP-020]) |
Handling: [internal / CONFIDENTIAL]. Disseminate only to assigned and prospectively assigned personnel. Contains personal data on the principal and staff: store and transmit per the data-processing agreement. Control and recover printed copies.
Nature of this product: This is a provisional alerting order, not the controlling order for the detail. Values marked provisional are subject to change before the OPORD is issued. Operational language renders to lawful protective effects only, within the jurisdiction and licensing of the area of operations.
Reference Products and Annexes
| Ref | Product | Role in this order |
|---|---|---|
| A | [ART-engagement-order] | Trigger and scope basis (Paragraph 1) |
| B | [EP-001] Principal Profile | Principal and party (Paragraph 1) |
| C | [ART-region-package] | Area of operations baseline (Paragraph 1) |
| D | [EP-020] Advance Planning Cycle | Timeline, gates, and product dependency chain (Paragraph 3) |
| E | [ART-protective-intel-assessment] | Threat snapshot when available (Paragraph 1) |
| F | [EP-011] Communications Plan (PACE) | Planning-phase signal (Paragraph 5) |
| G | [EP-010] Detail Operations Order | Order this WARNO alerts toward and will be superseded by (Paragraph 5) |
1. Situation
Instructional tradecraft: Keep this short. State only what has changed and why a WARNO is issued now; do not re-derive the threat assessment or duplicate the principal profile. Where a formal D-01 product is not yet on hand, say so and flag it as a gap rather than filling the gap with assumption.
1.1 Threat Snapshot
- Assessed threat posture at time of issue: [Low / Moderate / Elevated / High / Critical] (L x I [1-25]), or [NOT YET ASSESSED - reachback tasked, see 3.4].
- Source: [ART-protective-intel-assessment REF, if on hand] or [standing D-01 holdings, snapshot only].
- Known change driving this order: [new engagement / calendar addition / threat-driven replan - state which].
1.2 Principal and Party
- Principal: [designator / initials]; profile per [EP-001].
- Party under protection: [family members / staff in scope, by initials, as currently known].
1.3 Area of Operations Snapshot
- Area of operations and jurisdiction: [CITY / REGION, reference ART-region-package].
- Notice available: [Standard (14+ days) / Compressed (72 h) / Crash (24 h) - per EP-020 Section 4].
1.4 Why This Order Is Issued Now
- Trigger: [ART-engagement-order activation / calendar addition inside a standing engagement / threat-driven replan of an already-surveyed venue - per EP-020 Section 2].
- What is not yet known: [gaps in threat, itinerary, or venue list to be closed before the OPORD].
2. Mission (Provisional)
Instructional tradecraft: One sentence, marked provisional. This statement will be refined, not replaced, by the OPORD mission statement. If the draft changes materially before the OPORD, that is a planning finding, not a WARNO defect.
PROVISIONAL: The [DETAIL IDENTIFIER] will protect [PRINCIPAL] during [ANTICIPATED PERIOD / MOVEMENT] within [AREA OF OPERATIONS] in order to [PURPOSE, e.g. deter and defeat hostile action and preserve normal principal activity]. Subject to confirmation at Gate G1 ([EP-020]).
3. Execution
Instructional tradecraft: State the concept in general terms only; detail belongs in the OPORD. The purpose of this paragraph is to start the clock: what begins now, what the detail should be prepared to do, and the rules that bound movement before the OPORD is issued.
3.1 Concept of the Operation (General)
- General concept: [protective coverage of a residence / movement / venue set consistent with the provisional mission; state the operation type only, not the detailed scheme of maneuver].
- Detail Leader (designate or acting): [INITIALS], pending confirmation at Gate G1.
- Relationship to the OPORD: this concept is refined through the planning cycle and finalized in [EP-010] at Gate G5.
3.2 Planning Timeline and Key Gates
From [EP-020]. State the applicable variant and the gates relevant to this instance; do not restate the full cycle.
| Cycle Variant | [Standard D-14 / Compressed 72-Hour / Crash 24-Hour - select one, per EP-020 Section 3/4] |
|---|
| Gate | Name | Target Date/Time | Status |
|---|---|---|---|
| G1 | Tasking Validated | [D-14 / H-72 / H-24 target] | [PENDING / MET] |
| G2 | Intelligence Baseline | [target] | [PENDING] |
| G3 | Advance Complete | [target] | [PENDING] |
| G4 | Plan Approved | [target] | [PENDING] |
| G5 | Detail Ready (OPORD issued) | [target] | [PENDING] |
3.3 Be Prepared To (BPT) Tasks
- BPT provide [N] additional operators for surge staffing on [DATE RANGE], pending G1 scope confirmation.
- BPT support a compressed or crash planning variant if notice shortens per [EP-020] Section 4.
- BPT stage a second venue survey if the itinerary expands beyond [N] venues.
- BPT [ADDITIONAL BPT TASK AS THE ENGAGEMENT REQUIRES].
3.4 Tasks to Begin Now
Instructional tradecraft: These are the only tasks that start before Gate G1 confirms scope. Each carries an owner and a latest time information is of value (LTIOV) where applicable.
- Advance Lead designation: [NAME/INITIALS] designated Advance Lead effective [DDHHMMZ MON YY]; runs the cycle per [EP-020] Section 7.
- Detail Intelligence Officer to task D-01 for a threat snapshot / protective intelligence assessment now; LTIOV [DDHHMMZ MON YY] (target Gate G2, [EP-020] Section 3).
- Detail Intelligence Officer to task D-01 for a travel risk assessment if cross-border movement is anticipated; LTIOV [DDHHMMZ MON YY].
- Operations Manager to begin vendor and kit surge coordination via [ART-vendor-roster]: [vehicles, lodging holds, local security liaison - state which].
- Operators alerted for possible tasking: [ROSTER / NAMED INDIVIDUALS], stand by for confirmation at Gate G1.
- Region package pull: [ART-region-package] requested for [AREA OF OPERATIONS] if not already on hand.
3.5 Coordinating Instructions
- Earliest anticipated movement: [DDHHMMZ MON YY]; no movement is authorized before this order is superseded by the OPORD, except reconnaissance and advance tasks explicitly listed above.
- No-move-before time: [DDHHMMZ MON YY] for the detail as a whole; advance elements may move earlier per 3.4.
- Rehearsal windows (provisional): [DATE/TIME WINDOW], immediate-action drills to be confirmed at Gate G5 per [EP-020].
- Uniform and posture pending OPORD: [state interim posture, e.g. plainclothes advance only, no client-facing presence until briefed].
- This order does not authorize use of force procedures beyond those already standing for the detail; force posture is fixed in the OPORD per the region package legal annex.
4. Administration and Logistics
Instructional tradecraft: Only the logistics that must start now to make the timeline in 3.2. Full sustainment planning is finalized in the OPORD.
4.1 Movement, Lodging, and Transport Coordination
- Transport coordination: initiate vehicle tasking per [BIZ-009]; confirm availability against the anticipated deployment period.
- Lodging coordination: initiate lodging hold per [BIZ-008] for the advance element and, if confirmed, the detail.
- Travel booking for advance personnel: [NAMES/INITIALS], [DATES], [ROUTING].
4.2 Kit and Equipment Prep
- Kit checks to begin now per [SYS-009] / [SYS-010] checklists: communications, protective, and medical equipment.
- Equipment gaps identified for surge procurement: [LIST OR NONE IDENTIFIED].
4.3 Medical Prep
- Detail medic tasking (if not already assigned): [INITIALS], confirm availability for the anticipated period.
- Preliminary trauma facility check for the area of operations: [reference ART-region-package]; full casualty evacuation sequence is fixed in the OPORD per [EP-012].
4.4 Administrative
- Engagement file opened: [REF-YYYY-###]; deviation log opened per [EP-020] Section 9 if a compressed variant applies.
5. Command and Signal
Instructional tradecraft: State who runs planning and how the planning effort communicates. Full command and signal for execution is fixed in the OPORD.
5.1 Command (Planning Phase)
- Cycle ownership: Advance Lead (designated 3.4) runs the planning cycle per [EP-020] Section 7.
- Gate approval authority: Team Leader [INITIALS] approves Gates G1 through G5.
- Escalation: [Advance Lead] to [Team Leader] for any scope, timeline, or risk-acceptance decision outside the Advance Lead’s authority.
5.2 Signal (Planning Phase)
From [EP-011] Communications Plan (PACE). State only the planning-phase settings in effect until the OPORD is issued.
- Planning coordination net/channel: [reference EP-011 planning-phase net].
- Point of contact for RFIs and taskings: [INITIALS / role].
- Communications check cadence during planning: [frequency].
5.3 OPORD Issue
- The full DETAIL OPERATIONS ORDER ([EP-010]) supersedes this WARNO at Gate G5.
- Planned time and place of OPORD issue: [DDHHMMZ MON YY], [LOCATION / BRIEF FORMAT], per [EP-020] Section 3.
- Any operator or role not present at OPORD issue must be individually briefed before assuming a tasked role.
5.4 Acknowledgement of Receipt
Mandatory. Every named recipient acknowledges receipt of this WARNO. Non-acknowledgement by [TIME] is escalated to the Team Leader.
| Recipient (Initials/Role) | Method (voice/net/in person) | Time Acknowledged | Acknowledged By |
|---|---|---|---|
| [ ] | [ ] | [DDHHMMZ MON YY] | [ ] |
| [ ] | [ ] | [DDHHMMZ MON YY] | [ ] |
Annex A: Grading Matrices
NATO Admiralty source reliability (A-F): A Completely reliable; B Usually reliable; C Fairly reliable; D Not usually reliable; E Unreliable; F Reliability cannot be judged.
NATO Admiralty information credibility (1-6): 1 Confirmed by other sources; 2 Probably true; 3 Possibly true; 4 Doubtful; 5 Improbable; 6 Truth cannot be judged.
Risk scoring key: Likelihood (1-5) x Impact (1-5) = 1-25; 1-5 Low; 6-10 Moderate; 11-15 Elevated; 16-20 High; 21-25 Critical.
END OF REPORT
Model wiring
Generated from cell frontmatter at publish time.