VSI GLOBAL // ENTERPRISE ARCHITECTURE

Detail Execution Playbook

6 min read

DETAIL EXECUTION PLAYBOOK

[DETAIL IDENTIFIER - ENGAGEMENT REF]

The DETAIL EXECUTION PLAYBOOK is the day-of-operations runbook for an overt protective detail: shift start through residence departure, movement execution, venue occupation, returns, and rest-overnight reset. It executes the OPORD (EP-010) inside the battle rhythm (EP-021); it does not replan either. Formations and post tasks are stated as defaults the OPORD may override. Contrast: covert protection execution is EP-024. A cold-start operator runs a detail day 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]. Disseminate to assigned detail personnel only.

Nature of this product: This is an operational runbook. Operational language renders to lawful protective effects only. Force posture is defensive and graduated per the OPORD coordinating instructions and the jurisdiction’s licensing; nothing here authorizes what the region package legal annex does not.

Detail Snapshot

FieldValue
Engagement Reference[ENGAGEMENT REF]
Governing OPORD[EP-010 REF]
Detail Strength Today[N operators / N vehicles]
Posture[Low / Moderate / Elevated / High / Critical]
Movements Today[COUNT - itinerary ref]

Table of Contents

  1. Purpose and Boundaries
  2. Shift Start
  3. Residence Departure Sequence
  4. Movement Execution
  5. Arrival Sequence
  6. Venue Occupation
  7. Departure and Return
  8. Rest-Overnight (RON) Reset
  9. Principal Interface Standard
  10. Running Decision Points

1. Purpose and Boundaries

  • This playbook executes: the current EP-010 OPORD, today’s EP-016 brief, the comms settings of EP-011, and the standing post orders EP-009.
  • Immediate actions on contact, medical, fire, and evacuation are EP-025 drills executed under the EP-012 plan; this playbook hands off to them at the trigger and resumes at recovery.
  • Nothing in this playbook overrides an OPORD-specific instruction; deviations en route are decided per Section 10 authorities.

2. Shift Start

  1. Arrive per the battle rhythm daily cycle (EP-021); read the daily brief (EP-016) before taking post.
  2. Kit and vehicle checks per SYS-009/SYS-010 checklists; deficiencies to Shift Lead before the principal’s day starts, not after.
  3. Comms check all nets per EP-011; confirm duress word; confirm ATAK common operating picture is live on required devices (ART-common-operating-picture).
  4. Shift handover per EP-021 Section 3 when relieving a standing shift; the oncoming Shift Lead accepts by name on the command net.
  5. Confirm today’s movement set, arrival geometry per venue advance (EP-002), and the no-go/abort criteria from the OPORD.

3. Residence Departure Sequence

  1. Exterior check of the departure point and vehicle line before the principal is committed (per EP-009 residence posts where manned).
  2. Vehicles staged per EP-004: engines running, doors unlocked on the protected side only, driver stays with vehicle.
  3. Route confirmation: driver and Shift Lead confirm primary route still valid against the morning picture (traffic, closures, alerts from EP-016); alternate selected if not.
  4. Advance vehicle departs [X] minutes ahead where the OPORD assigns one.
  5. Principal movement door-to-vehicle: close escort in the OPORD formation; no principal wait time at the curb; embus order per EP-004.
  6. Departure call on the detail net: element, principal count, route letter, ETA.

4. Movement Execution

Movement is governed by EP-004; this section is the crew discipline that makes it work.

  • Positions and spacing per EP-004 for today’s vehicle count; the protection vehicle never loses sight of the principal vehicle.
  • Communication: waypoint calls at OPORD-designated points; deviation from route called before the turn, not after.
  • The driver drives, the escort observes and communicates; navigation load goes to the escort or the following vehicle, never the wheel.
  • Halts: planned halts only at surveyed points from EP-003; unplanned halts treated as elevated exposure, minimum duration, escort dismounts per formation drill.
  • Route deviation authority per Section 10; forced deviations (blockage, police direction) reported immediately with new route letter.
  • Surveillance awareness en route: possible-follow indicators logged and reported per EP-008 format; confirmation runs are an EP-024 tasking, not an improvised maneuver with the principal aboard.

5. Arrival Sequence

  1. Advance element (or arriving escort where no advance is posted) clears the arrival point against the EP-002 geometry: box controlled, door confirmed, hold route open.
  2. Arrival call: two-minute-out on the venue net; venue contact alerted per the liaison record.
  3. Debus per EP-004 order: escort out first, principal moves on the escort’s signal, shortest exposed distance, no principal wait in the open.
  4. Vehicles: reposition to the staging point per EP-002; drivers stay on net; one vehicle remains in immediate-recall state throughout the visit.

6. Venue Occupation

  • Posts per EP-009 and the OPORD task matrix: access point coverage, hold security, close cover with the principal.
  • The hold is kept ready the entire visit: route to it walked by at least one operator on arrival, door state confirmed, egress from it confirmed.
  • Crowd and access rhythm: staff and guest flow watched against the advance baseline; anomalies (unscheduled staff, unbadged access, fixated persons per ATAP indicators) reported on the detail net and logged.
  • Principal moves inside the venue: announced on net before they happen; formation collapses and expands per the space, per OPORD defaults.
  • Comms discipline: routine traffic minimal during occupation; the net stays clear for exception traffic.

7. Departure and Return

  1. Departure mirrors arrival in reverse; the exposed segment is re-cleared before the principal is committed (conditions change during a visit).
  2. Route selection for the return leg confirmed against the current picture; do not default to the inbound route when the OPORD provides alternates (pattern avoidance).
  3. Departure and arrival-home calls on the detail net; accountability confirmed: principal, party, all elements.

8. Rest-Overnight (RON) Reset

  1. Residence or hotel posture per EP-009 established before the detail reduces manning.
  2. Vehicles: fueled above [3/4], faults reported, kit per SYS-010 restowed, then secured.
  3. Equipment: radios and handsets to charge; medical kit seals checked; discrepancies into the daily log.
  4. Daily log closed per EP-021; next-day M-hour and first movement confirmed at the evening sync.
  5. Overnight watch (where manned): handover per EP-021 Section 3; overnight exception reporting per EP-011.

9. Principal Interface Standard

  • One voice: the Detail Leader (or designated Shift Lead) is the single interface for schedule and security conversation with the principal and family office; operators redirect requests to that channel.
  • Protective advice is given once, clearly, with the risk stated; the principal’s lawful decision is then executed with the posture adjusted to compensate, and the exchange is logged.
  • Client-imposed risk acceptances (declined escort, unscheduled stop) are logged the same day and roll into EP-017 reporting; chronic acceptances trigger a Team Leader-client conversation, not silent absorption.
  • Discretion: no detail conversation about the principal in vehicles or venues beyond operational need; family and staff are treated per the OPORD party scope.

10. Running Decision Points

DecisionAuthorityNotes
Switch to briefed alternate routeShift Lead (driver executes)Report with route letter
Unbriefed route improvisationDetail Leader onlyOnly when all briefed alternates are invalid
Delay a movement inside itinerary slackShift LeadInform principal interface
Cancel or reorder an itinerary itemTeam Leader with principalPer OPORD no-go criteria
Posture step up (band crossing)Shift Lead up, Team Leader confirmsPer EP-021 threat-change rule
Declare emergency / execute EP-025 drillAny operatorNet goes flash per EP-011
Stand down from emergency postureDetail LeaderAfter accountability and assessment

END OF REPORT

Model wiring

Generated from cell frontmatter at publish time.

Graph View

Backlinks