EP-022-advance-mission-playbook-collection

[OPERATION - ENGAGEMENT REF] - Advance Mission Map

EP-022 Advance Mission Playbook - execution workspace for the physical advance. Central topic = the tasked advance mission (venues, route, window). Branches = the ordered phases and gates the advance element runs from tasking to brief-back. Tick each leaf as completed; fill bracketed fields as ground truth replaces the desk study. Clone the recursive serial blocks (venue walk, route recon, liaison contact) once per venue/route/contact. → executes EP-022 in full; seeded by EP-020 gate G2 (venues and window fixed); feeds EP-002, EP-003, and EP-020 gate G3.

00 * Process Plan - Gates & Triggers

The trigger that starts this advance and the boundary checks it must clear before any leaf below is worked. → EP-022 SS1 Purpose and Boundaries, Mission Snapshot.

Entry trigger

• EP-020 gate G2 passed (confirmed with Team Leader / Ops Manager)
• Intelligence baseline on hand (ART-protective-intel-assessment, ART-travel-risk-assessment)
• Venues and on-site window fixed and logged: Venues Tasked: [ ] / On-Site Window: [ ]
• Advance Lead (initials): [ ]
• Element size: [1 / 2 operators]
• Cycle instance / gate state: [EP-020 REF - post-G2]

Boundary check (do not proceed if any is false)

• Decision: [ ] The advance observes, records, coordinates only - no contract negotiation (routes to Operations Manager / BIZ)
• Decision: [ ] No surveillance of persons undertaken here (that is EP-007/EP-008 tasking)
• Decision: [ ] No security posture committed beyond what G4 has approved

Output contract (what this advance must produce to close)

• Completed EP-002 per venue
• Ground-truthed EP-003
• Liaison record
• Brief-back that carries gate G3

01 * Advance Tasking & Kit

Preparation before departure; incomplete preparation is a logged deviation per EP-020. → EP-022 SS2 Phase 1: Preparation.

Read-on register

• Itinerary reviewed
• EP-001 principal profile extract reviewed
• ART-protective-intel-assessment reviewed
• ART-travel-risk-assessment (cross-border) reviewed
• Region package legal annex reviewed
• Region package medical infrastructure section reviewed
• Region package LE liaison protocol reviewed

Desk study per venue

Clone per venue.

• [venue - e.g. Hotel Meridian, Site A]
  • Imagery / mapping pass complete
  • Draft site diagram produced
  • Access points, parking, adjacent structures noted
  • Open questions only ground truth can answer: [ ]

Route desk study

• Candidate primary route identified per EP-003 method
• Candidate alternate route(s) identified per EP-003 method
• Hospital / trauma set drawn from region package
• Chokepoints to ground-truth: [ ]

Appointments & documentation

• Venue security/management contact windows booked (→ Branch 04 Liaison)
• Access authority confirmed in writing where required
• Credentials on hand
• Engagement letter extract / authority-to-survey on hand where required
• Jurisdiction licensing cards on hand
• Kit checked per Branch 99 Advance Kit register
• Comms check complete per EP-011

Itinerary filed with Operations Manager

• Travel plan filed
• Lodging filed (BIZ-008 assessment referenced where applicable)
• Daily check-in schedule agreed
• Overdue procedure: [ ]

02 * Deployment & Arrival

Travel and first-day orientation before any venue appointment. → EP-022 SS3 Phase 2: Deployment and Arrival.

• Travel conducted low profile - nothing in dress, luggage, or conversation identifies client or purpose
• Checked in with Operations Manager on the engagement net
• Local SIM/data plan confirmed; comms check per EP-011
• Orientation drive of the area of operations completed before first appointment
  • General layout / traffic rhythm: [ ]
  • Police presence and posture: [ ]
  • Current events on ground vs. assessment: [ ]
• Fast-aging facts verified: construction, closures, event calendars overlapping visit window

03 * Venue Walk (per venue)

The fixed 8-step walk sequence so nothing is skipped under time pressure. Record against the EP-002 skeleton as you go; do not reconstruct from memory. → EP-022 SS4 Phase 3: Venue Survey Conduct.

Venue walk serial

Clone per venue. Complete all 8 steps in order.

• [venue - e.g. Site A]
  • Step 1 - Exterior orbit: approaches, sightlines, standoff, adjacent occupancies, surveillance perches, camera coverage, lighting state at visit hour
  • Step 2 - Arrival point: embus/debus geometry, cover from view, door-to-door distance, control of arrival box, alternate arrival point
  • Step 3 - Access control: entrances in use, screening posture, credentialing, who controls the door, badge/escort rules
  • Step 4 - Interior route: door to function space; primary and alternate holds with lock state and egress; elevators vs. stairs; nearest principal restroom option
  • Step 5 - Function space: seating relative to exits, backdrop exposure (photography, windows), crowd configuration, staff access during activity
  • Step 6 - Emergency egress: two routes minimum from every principal location walked physically; doors that lock behind noted; alarm-on-exit noted
  • Step 7 - Life safety: nearest AED located, fire posture noted, venue medical room located, nearest trauma center confirmed by drive time at visit hour
  • Step 8 - Comms dead spots: detail net and cellular checked at hold, function space, and egress stairwells; failures logged for EP-011
  • Per-venue minimum record: [ ] annotated diagram / [ ] photo set keyed to diagram / [ ] contact list / [ ] completed EP-002 sections
  • Gaps (marked as gaps, never guessed): [ ]
• [venue 2]

04 * Route Reconnaissance (per route)

Ground-truth every primary and alternate route at the planned movement hour. → EP-022 SS5 Phase 4: Route Reconnaissance.

Route recon serial

Clone per route: primary / alternate / emergency.

• [route - e.g. Lodging → Site A, primary]
  • Driven at planned movement hour (or timing delta noted for other hours)
  • Chokepoints recorded per EP-003
  • One-way sections recorded
  • Illegal-turn traps recorded
  • Overpasses / tunnels recorded
  • Ambush-favorable geometry recorded
  • Safe havens recorded (staffed 24h, vehicle-accessible)
  • Fuel points recorded
  • Trauma centers on route recorded
  • Embus/debus at both ends validated against venue arrival geometry (→ Branch 03)
  • Route time: [ ] / Variance drivers (school hours, market days, events): [ ]
  • Decision: [ ] Alternate diverges early enough to matter (rejoins-before-chokepoint fails this test)
• [route 2 - alternate]
• [route 3 - emergency]

05 * Liaison

Liaison is conducted to the region package protocol; commitments are recorded, not remembered. → EP-022 SS6 Phase 5: Liaison.

Liaison contact serial

Clone per contact: venue security/management, law enforcement, medical, vendor.

• [contact - e.g. Venue Security Manager]
  • Category: [venue security-management / law enforcement / medical / vendor]
  • Visit mechanics agreed
  • Screening exceptions for the party agreed (where applicable)
  • Staff notification scope agreed (minimum necessary)
  • House emergency procedures obtained
  • Points of contact for visit day recorded
  • Identity / agreement / limits (LE contacts only, per region package annex): [ ]
  • Commitment recorded in liaison record attached to EP-002: [ ]
• [contact 2]

Medical and vendor checks

• Trauma center capabilities confirmed where region package flags them unverified
• Locally contracted support validated against ART-vendor-roster via Operations Manager (advance validates, does not procure)

06 * Vulnerabilities & Mitigations

Operational security posture the advance element itself maintains while conducting the survey. → EP-022 SS8 Advance Profile and Operational Security.

• Cover for status: [business travel / event logistics] consistent with venue’s normal traffic
• Client not named to third parties absent an approved liaison script
• Pattern discipline maintained - times/order of repeated venue visits varied
• No repeated parking that would draw notice
• Passive surveillance awareness run for hostile pre-attack indicators (EP-008 indicator set); no dedicated detection run unless separately tasked under EP-024
• Photos, diagrams, notes held on encrypted devices per SYS-003 baseline
• No venue material posted, synced, or emailed outside the engagement file

07 * Advance Report Handoff (EP-002/EP-003)

Drafting while observations are fresh, and the brief-back that carries the mission’s gate. → EP-022 SS7 Phase 6: Drafting and Brief-Back.

• EP-002 drafted per venue same day while observations are fresh
• EP-003 finalized while on site
• Open items flagged (each with a recommendation):
  • [open item] - Recommendation: [accept / mitigate / re-survey]
  • [open item 2] - Recommendation: [ ]
• Brief-back delivered to Team Leader within [24] hours of return
  • Format used: EP-002 summary + open items + advance’s posture recommendation per venue
• G3 review outcome (EP-020): [ ] Accepted / [ ] Corrective action looped - detail: [ ]

08 * Actions-On

Immediate actions and follow-through for the things that go wrong on an advance; keep this branch open throughout Branches 02-07. → EP-022 SS9 Actions-On.

Actions-on serial

Clone per triggered event; log time and disposition.

• [event - e.g. Access denied at venue]
  • Trigger matched: [Access denied / Advance element challenged / Advance compromised / Suspected hostile surveillance / Overdue-lost comms / Serious incident in AO]
  • Immediate action taken: [ ]
  • Then / escalation: [ ]
  • Time logged: [ ]
  • Reported to: [Ops Manager / Team Leader]
• [event 2]

Reference table (do not deviate from these immediate actions)

• Access denied at venue → Do not force or argue past a refusal; withdraw politely → Escalate to Ops Manager for client-channel authorization; reschedule
• Advance element challenged (venue/security/LE) → Identify per approved script and credentials; comply with lawful direction → Log; assess whether profile is blown
• Advance compromised (purpose exposed) → Cease survey activity; unremarkable exit → Report to Team Leader; assess itinerary/venue change per EP-020 replan trigger
• Suspected hostile surveillance of the advance → Do not confront; break contact by routine means; note descriptors → Report per EP-008 indicator format; Team Leader decides SD tasking
• Overdue / lost comms with firm → Execute filed overdue procedure → Ops Manager initiates welfare sequence at [T+X h]
• Serious incident in AO during advance → Move to safe location; account for element → Report; Team Leader decides continue/abort per EP-020 no-go floor

99 * Execution Admin

Running decision/deviation log, product register, sign-offs, and open actions for this advance. → EP-022 SS10 Advance Kit and overall mission closure against EP-020.

Advance kit register (verify before departure, → Branch 01)

• Individual loadout per SYS-009 (jurisdiction-adjusted; armed carriage only where licensed, otherwise explicitly unarmed)
• Comms per SYS-003: hardened handset, engagement comms plan loaded, local SIM/data arranged
• Survey tools: laser measurer or pacing standard, camera, diagram templates, printed venue imagery
• SA kit (SYS-004) - deploy only if static hold / extended pre-positioning tasked; otherwise stages with detail
• Individual IFAK per SYS-009

Decision / deviation log (running)

• [date/time] - [decision or deviation] - [rationale] - [logged by]

Product register

• EP-002 (per venue): [status - drafted / reviewed / final]
• EP-003: [status]
• Liaison record: [status]
• Brief-back package: [status]

Sign-offs

• Advance Lead: [initials / date]
• Team Leader (G3 acceptance): [initials / date]

Open actions / RFIs

• [open item] → route to [Branch / EP-020 replan / external product]
• [open item 2]

END OF MAP