VSI GLOBAL // ENTERPRISE ARCHITECTURE

Advance Mission Playbook

7 min read

ADVANCE MISSION PLAYBOOK

[ENGAGEMENT NAME - ENGAGEMENT REF]

The ADVANCE MISSION PLAYBOOK is the execution runbook for the physical advance: what the advance element does from the moment the planning cycle (EP-020) tasks the mission until the survey products are drafted and briefed back. It sequences preparation, deployment, venue survey conduct, route reconnaissance, liaison, and brief-back, with actions-on for the things that go wrong on an advance. The written product standard is EP-002; the schedule and gates are EP-020. A cold-start operator executes the advance from this playbook plus the referenced artifacts alone. This is a repeatable runbook. All engagement-specific values are bracketed placeholders. Do not assert fictional findings or invent data.

Document Control

FieldValue
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]. The advance reveals protective intent, timing, and venues; protect this document and its outputs accordingly.

Nature of this product: This is an operational runbook. Operational language renders to lawful protective effects only. The advance element holds no law enforcement powers; access, photography, and inquiries stay within the law and venue consent of the jurisdiction, per the region package legal annex.

Mission Snapshot

FieldValue
Engagement Reference[ENGAGEMENT REF]
Cycle Instance / Gate State[EP-020 REF - post-G2]
Advance Lead[INITIALS]
Element Size[1 / 2 operators]
Venues Tasked[LIST]
On-Site Window[D-7 to D-5 / compressed]

Table of Contents

  1. Purpose and Boundaries
  2. Phase 1: Preparation
  3. Phase 2: Deployment and Arrival
  4. Phase 3: Venue Survey Conduct
  5. Phase 4: Route Reconnaissance
  6. Phase 5: Liaison
  7. Phase 6: Drafting and Brief-Back
  8. Advance Profile and Operational Security
  9. Actions-On
  10. Advance Kit

1. Purpose and Boundaries

  • Trigger: EP-020 gate G2 passed; intelligence baseline on hand; venues and window fixed.
  • Output: completed EP-002 per venue, ground-truthed EP-003, liaison record, and the brief-back that carries gate G3.
  • Boundaries: the advance observes, records, and coordinates. It does not negotiate contracts (Operations Manager, per BIZ cells), does not conduct surveillance of persons (EP-007/EP-008 govern that), and does not commit the firm to security postures not yet approved at G4.

2. Phase 1: Preparation

Complete before departure; incomplete preparation is a logged deviation per EP-020.

  1. Read on: itinerary, EP-001 principal profile extract, ART-protective-intel-assessment, ART-travel-risk-assessment (cross-border), region package (legal annex, medical infrastructure, LE liaison protocol).
  2. Desk study per venue: imagery and mapping pass; draft site diagram; access points, parking, adjacent structures; note what only ground truth can answer.
  3. Route desk study: candidate primary and alternates per EP-003 method; hospital set from the region package; note chokepoints to ground-truth.
  4. Appointments: venue security or management contact windows booked (Section 6); confirm access authority in writing where required.
  5. Documentation: credentials, engagement letter extract or authority-to-survey where the venue requires it, licensing cards per jurisdiction.
  6. Kit check per Section 10; comms check per EP-011 before departure.
  7. File the advance itinerary with the Operations Manager: travel, lodging (per BIZ-008 assessment where applicable), daily check-in schedule, overdue procedure.

3. Phase 2: Deployment and Arrival

  1. Travel low profile; nothing in dress, luggage, or conversation identifies the client or purpose.
  2. On arrival: check in with Operations Manager on the engagement net; confirm local SIM/data plan and comms per EP-011.
  3. Orientation drive of the area of operations before any appointment: general layout, traffic rhythm, police presence and posture, current events on the ground vs. the assessment.
  4. Verify baseline facts that age fastest: construction, closures, event calendars overlapping the visit window.

4. Phase 3: Venue Survey Conduct

The walk sequence is fixed so nothing is skipped under time pressure. Record against the EP-002 skeleton as you go; do not reconstruct from memory.

Walk sequence per venue:

  1. Exterior orbit first: approaches, sightlines, standoff, adjacent occupancies, surveillance perches covering entrances, camera coverage, lighting state at the visit’s actual hour where feasible.
  2. Arrival point: embus/debus geometry, cover from view, door-to-door distance, control of the arrival box, alternate arrival point.
  3. Access control: entrances in use, screening posture, credentialing, who controls the door, badge/escort rules for the party.
  4. Interior route: door to function space; holds (primary and alternate) with lock state and egress; elevators vs. stairs; principal restroom option nearest the hold.
  5. Function space: seating relative to exits, backdrop exposure (photography, windows), crowd configuration, staff access during the activity.
  6. Emergency egress: two routes minimum from every principal location to vehicles or shelter; walk them physically; note doors that lock behind, alarm on exit.
  7. Life safety: nearest AED, fire posture, venue medical room; nearest trauma center from the region package confirmed by drive time at the visit hour.
  8. Comms dead spots: check detail net and cellular at hold, function space, and egress stairwells; note failures for EP-011.

Per-venue minimum record: annotated diagram, photo set keyed to the diagram, contact list, and the completed EP-002 sections; gaps marked as gaps, never guessed.

5. Phase 4: Route Reconnaissance

  1. Drive every primary and alternate at the planned movement hour where possible; note timing deltas at other hours.
  2. Record per EP-003: chokepoints, one-way sections, illegal-turn traps, overpasses/tunnels, ambush-favorable geometry, safe havens (staffed 24 h, vehicle-accessible), fuel, trauma centers on route.
  3. Validate embus/debus at both ends against the venue survey arrival geometry.
  4. Time the routes; record variance drivers (school hours, market days, event calendars).
  5. Confirm alternates diverge early enough to matter; an alternate that rejoins before the chokepoint is not an alternate.

6. Phase 5: Liaison

Liaison is conducted to the region package protocol; commitments are recorded, not remembered.

  • Venue security/management: visit mechanics, screening exceptions for the party, staff notification scope (minimum necessary), house emergency procedures, points of contact for the visit day.
  • Law enforcement: per the region package liaison annex and engagement policy; where contact is made, record identity, agreement, and limits; no operational detail beyond need.
  • Medical: confirm trauma center capabilities where noted in the region package as unverified.
  • Vendors: locally contracted support (transport, static staffing) is coordinated via the Operations Manager against ART-vendor-roster; the advance validates, it does not procure.
  • Every liaison contact and commitment goes in the liaison record attached to EP-002.

7. Phase 6: Drafting and Brief-Back

  1. Draft EP-002 per venue and finalize EP-003 while on site; same-day drafting while observations are fresh.
  2. Flag every unresolved gap as an explicit open item with a recommendation (accept / mitigate / re-survey).
  3. Brief-back to the Team Leader within [24] hours of return: format is the EP-002 summary, open items, and the advance’s recommendation on posture per venue.
  4. G3 review per EP-020: the Team Leader accepts or loops corrective actions.

8. Advance Profile and Operational Security

  • Cover for status: the advance presents as [business travel / event logistics] consistent with the venue’s normal traffic; the client is never named to third parties absent an approved liaison script.
  • Pattern discipline: vary times and order of repeated venue visits; do not park where repetition would be noticed.
  • Surveillance awareness: the advance runs passive awareness for hostile pre-attack surveillance on the venues (indicators per EP-008); it does not run dedicated detection runs unless tasked under EP-024.
  • Data handling: photos, diagrams, and notes on encrypted devices per SYS-003 baseline; no venue material posted, synced, or emailed outside the engagement file.

9. Actions-On

EventImmediate ActionThen
Access denied at venueDo not force or argue past a refusal; withdraw politelyEscalate to Ops Manager for client-channel authorization; reschedule
Advance element challenged (venue/security/LE)Identify per the approved script and credentials; comply with lawful directionLog; assess whether profile is blown (see next)
Advance compromised (purpose exposed)Cease survey activity; unremarkable exitReport to Team Leader; assess itinerary/venue change per EP-020 replan trigger
Suspected hostile surveillance of the advanceDo not confront; break contact by routine means; note descriptorsReport per EP-008 indicator format; Team Leader decides SD tasking
Overdue / lost comms with firmExecute the filed overdue procedureOps Manager initiates the welfare sequence at [T+X h]
Serious incident in AO during advanceMove to safe location; account for elementReport; Team Leader decides continue/abort per EP-020 no-go floor

10. Advance Kit

  • Individual loadout per SYS-009 (jurisdiction-adjusted; armed carriage only where licensed per region package legal annex, 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 (handset), diagram templates, printed venue imagery.
  • SA kit (SYS-004) deploys with the advance only when a static hold or extended pre-positioning is tasked; otherwise it stages with the detail.
  • Medical: individual IFAK per SYS-009.

END OF REPORT

Model wiring

Generated from cell frontmatter at publish time.

Graph View

Backlinks