ADVANCE PLANNING CYCLE
[ENGAGEMENT NAME - ENGAGEMENT REF]
The ADVANCE PLANNING CYCLE governs how a protective advance is planned: the trigger conditions, the D-minus milestone schedule from tasking to brief-out, the decision gates with entry and exit criteria, and the compressed variants when notice is short. It schedules and sequences the advance production chain (EP-003 route analysis, EP-002 advance survey, EP-018 travel security package) and hands the finished plan to execution under EP-022. This is the planning process; the conduct of the physical advance is EP-022 Advance Mission Playbook. This is a repeatable process standard. All engagement-specific values are bracketed placeholders. Do not assert fictional findings or invent data.
Document Control
| Field | Value |
|---|---|
| Report Reference | [REF-YYYY-###] |
| Date of Report | [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 & Legal Caveat
Handling: [internal / CONFIDENTIAL]. Access restricted to detail command, advance, and operations roles.
Nature of this product: This is a planning process standard. It does not deliver legal advice or guarantee prevention of incidents. Operational language renders to lawful protective effects only, within the jurisdiction and licensing of the area of operations.
Engagement Snapshot
| Field | Value |
|---|---|
| Engagement Reference | [ENGAGEMENT REF] |
| Movement / Visit | [CITY, VENUE SET, DATES] |
| Notice Available | [Standard (14+ days) / Compressed (72 h) / Crash (24 h)] |
| Advance Lead | [INITIALS] |
| Cycle Start (tasking received) | [YYYY-MM-DD HH:MM] |
| D-Day (principal arrival / first movement) | [YYYY-MM-DD] |
Table of Contents
- Purpose and Authority
- Cycle Triggers and Required Inputs
- Standard Cycle: D-14 Baseline Timeline
- Compressed Cycles: 72-Hour and 24-Hour Variants
- Decision Gates
- Product Dependency Chain
- Roles and Responsibilities
- Planning Quality Standard
- Cycle Metrics and Feedback
1. Purpose and Authority
Instructional tradecraft: Fix who owns the cycle, who approves each gate, and what this process governs versus defers.
- This cycle governs planning for any principal movement or venue activity that requires an advance: travel, event attendance, recurring venue visits, and residence changes.
- Ownership: the designated Advance Lead runs the cycle for the tasked movement. The Operations Manager (BR) owns scheduling, logistics coordination, and calendar deconfliction across concurrent advances.
- Approval authority: the Team Leader (RF) approves gate transitions G2 through G5 and any compressed-cycle risk acceptance.
- Deference: conduct of the physical site advance is EP-022; motorcade-specific planning method is EP-004; the finished travel product standard is EP-018.
2. Cycle Triggers and Required Inputs
Instructional tradecraft: A cycle instance starts only on a defined trigger, and no gate is passed on missing mandatory inputs without recorded risk acceptance.
Triggers (any one starts the cycle):
- ART-engagement-order activates a new engagement with movement requirements.
- A movement or venue activity is added to the principal calendar inside the standing engagement.
- A threat-driven replan: a change in assessed threat forces a new advance of an already-surveyed venue.
Mandatory inputs and their sources:
| Input | Source | Needed By |
|---|---|---|
| Engagement scope, party size, dates | ART-engagement-order / client calendar | Cycle start |
| Area of operations baseline (legal annex, medical, LE liaison) | ART-region-package | Gate G1 |
| Protective intelligence assessment | ART-protective-intel-assessment (D-01) | Gate G2 |
| Travel risk assessment (for cross-border movement) | ART-travel-risk-assessment (D-01) | Gate G2 |
| Principal profile and party composition | EP-001 | Gate G1 |
| Venue list and itinerary draft | Client / Operations Manager | Gate G1 |
3. Standard Cycle: D-14 Baseline Timeline
Instructional tradecraft: D-day is the principal’s arrival or first protected movement. Milestones are latest-completion times; earlier is always acceptable. Adjust day offsets to the engagement and record deviations in Section 9.
| Day | Milestone | Product / Action | Responsible | Gate |
|---|---|---|---|---|
| D-14 | Tasking validated; Advance Lead designated; itinerary draft received | Cycle instance opened; RFIs issued to D-01 | Team Leader / Ops Manager | G1 |
| D-12 | Intelligence tasking confirmed; region package pulled | ART-protective-intel-assessment and ART-travel-risk-assessment tasked with LTIOV D-10 | Advance Lead | - |
| D-10 | Intelligence baseline on hand | D-01 assessments received and read on to the advance team | Advance Lead | G2 |
| D-9 | Route desk study complete | EP-003 draft: candidate primary and alternate routes, chokepoints, safe havens | Advance Lead | - |
| D-7 | Physical advance begins on site | Venue surveys per EP-002 method; route ground-truth per EP-003; lodging assessment (BIZ-008) coordinated via Ops Manager | Advance Lead (+1 operator where staffing allows) | - |
| D-5 | Advance survey reports drafted | EP-002 per venue; EP-003 finalized with driven routes | Advance Lead | G3 |
| D-4 | Motorcade movement plan drafted | EP-004 built from EP-003; vehicle and driver allocation confirmed (BIZ-009) | Advance Lead / Ops Manager | - |
| D-3 | Travel security package assembled | EP-018 integrating EP-002/EP-003/EP-004; comms plan confirmed per EP-011 | Advance Lead | G4 |
| D-2 | OPORD issued | EP-010 issued by Team Leader; post orders (EP-009) and EAP (EP-012) annexes attached | Team Leader | - |
| D-1 | Confirmation brief and rehearsals | Detail briefed; immediate-action drills rehearsed; kit checks per SYS-009/SYS-010 checklists | Team Leader / Shift Lead | G5 |
| D-0 | Execution handoff | Cycle closes; execution governed by EP-023 and EP-022 | Team Leader | - |
4. Compressed Cycles: 72-Hour and 24-Hour Variants
Instructional tradecraft: Compression removes calendar, never mandatory content. Each variant states what merges, what drops, and who accepts the residual risk. A dropped item is a recorded risk, not a silent omission.
4.1 72-Hour Variant
| Window | Actions Merged | Notes |
|---|---|---|
| H-72 to H-60 | G1 + G2: tasking validated while intelligence reachback runs concurrently | D-01 delivers a threat snapshot from standing holdings (OSINT-053 stream) instead of a fresh assessment; gap logged as RFI |
| H-60 to H-36 | Desk study + physical advance merged: routes ground-truthed same day as venue survey | Single-visit advance; EP-002 short-form sections mandatory, annex sections as time allows |
| H-36 to H-12 | G3 + G4: survey, movement plan, and package review in one sitting | EP-018 assembled from short-form products |
| H-12 to H-0 | G5: brief and rehearse minimum drill set | Embus/debus under threat, medical, evacuation drills mandatory |
4.2 24-Hour (Crash) Variant
- Mandatory minimum set, no exceptions: threat snapshot from standing D-01 holdings; drive of the primary route and one alternate; walkthrough of each venue’s arrival point, hold, and evacuation path; EP-011 comms check; verbal OPORD with written mission, execution, and actions-on sections; G5 confirmation brief.
- Everything else is dropped by default and recorded in the deviation log (Section 9).
- Risk acceptance: the Team Leader personally accepts the crash-cycle residual risk and records it; where the client imposes the compression, that fact is recorded in the engagement file.
4.3 No-Go Floor
If the crash-variant mandatory minimum cannot be completed before the movement, the movement is postponed, rescoped (venue substitution, reduced exposure), or declined. The floor is a client-communicated policy at engagement start, not negotiated per movement.
5. Decision Gates
Instructional tradecraft: Gates are pass/fail checks with a named approver. A failed gate loops back with a corrective action, or escalates to risk acceptance recorded by name and date.
| Gate | Name | Entry Criteria | Exit Criteria | Approver |
|---|---|---|---|---|
| G1 | Tasking Validated | Trigger confirmed; itinerary draft; party composition; region package on hand | Scope, dates, venues, and staffing fixed; Advance Lead designated; RFIs issued | Team Leader |
| G2 | Intelligence Baseline | D-01 products received or snapshot delivered | Threat posture set (L x I, 1-25); PIRs tailored from EP-019 standing set; collection gaps logged | Team Leader |
| G3 | Advance Complete | Physical advance conducted | EP-002 per venue and EP-003 drafted; no unsurveyed venue remains on itinerary | Team Leader |
| G4 | Plan Approved | EP-018 package assembled; EP-004 and EP-011 confirmed | Package internally consistent; open risks enumerated with owners; cold-start operator test passed | Team Leader |
| G5 | Detail Ready | OPORD issued; briefs and rehearsals held | Every operator briefed on mission, actions-on, and comms; kit checks complete; abort criteria understood | Team Leader |
6. Product Dependency Chain
Instructional tradecraft: The chain is the build order. A downstream product is not drafted before its upstream input exists, except in compressed cycles where the merge is recorded.
ART-engagement-order --> [G1 Tasking]
ART-region-package ----> |
ART-protective-intel-assessment --> [G2 Intel Baseline]
ART-travel-risk-assessment ------> |
v
EP-003 Route Analysis (desk, then ground)
v
EP-002 Advance Survey (per venue)
v
EP-004 Motorcade Plan BIZ-008 Lodging / BIZ-009 Transport
v
EP-018 Travel Security Package [G4]
v
EP-010 OPORD + EP-009 / EP-011 / EP-012 annexes
v
[G5 Detail Ready] --> execution per EP-022 / EP-023
7. Roles and Responsibilities
| Role | Cycle Responsibilities |
|---|---|
| Team Leader (RF) | Gate approvals G1-G5; risk acceptance; OPORD issue; client interface on no-go floor |
| Advance Lead (designated per cycle) | Runs the cycle; conducts the physical advance; drafts EP-002/EP-003/EP-018; owns the deviation log |
| Operations Manager (BR) | Scheduling and deconfliction; lodging and transport coordination (BIZ-008/BIZ-009); vendor surge via ART-vendor-roster; kit logistics |
| Detail Intelligence Officer | D-01 tasking and reachback; PIR tailoring per EP-019; threat posture recommendation at G2 |
| Operators (MR/JM) | Advance support tasks; rehearsals; kit checks per SYS-009/SYS-010 |
8. Planning Quality Standard
- Every product in the chain is complete against its own template standard; a compressed short-form is a defined subset, not an improvisation.
- Cold-start operator test at G4: an operator not involved in planning can execute from the package and its referenced artifacts alone.
- Likelihood and confidence language in planning products carries D-01 grading unchanged; the advance never upgrades an assessment.
- No unsurveyed venue, undriven primary route, or unbriefed operator crosses G5 without named risk acceptance.
9. Cycle Metrics and Feedback
Instructional tradecraft: The cycle improves through measured deviations, not memory. Metrics feed EP-017 after-action reporting and quarterly process review.
| Metric | Definition | Target |
|---|---|---|
| Cycle lead time | Tasking receipt to G5 | Within variant timeline |
| Gate first-pass rate | Gates passed without loop-back | [>= 80 percent] |
| Deviation count | Logged drops/merges per cycle | Trend down quarter over quarter |
| Intelligence timeliness | D-01 delivery vs. LTIOV | 100 percent by LTIOV |
| Rework | Products revised after G4 | [⇐ 1 per engagement] |
- Deviation log: every dropped, merged, or late milestone with reason and approver.
- Feedback path: EP-017 after-action findings that implicate planning (missed survey item, route failure, timing miss) open a corrective action against this cycle; changes version this document.
END OF REPORT
Model wiring
Generated from cell frontmatter at publish time.