EP-023-detail-execution-playbook-collection

[DETAIL - ENGAGEMENT REF] - Detail Execution Map

EP-023 Detail Execution Playbook - day-of-operations workspace for a deployed overt protective detail. Central topic = today’s detail (one engagement reference, one 24-hour cycle). Branches = the playbook’s phases and gates in execution order, from shift start to rest-overnight reset. Tick each leaf as the element completes it; log deviations and decisions where the branch calls for it, not after the fact. → executes EP-023 Detail Execution Playbook in full; runs inside the EP-021 battle rhythm and under the EP-010 OPORD, which this map does not replan. Clone this whole map per detail-day.

00 * Process Plan - Gates & Triggers

The trigger that opens today’s detail cycle and the boundary conditions that must hold before any movement is committed. → EP-023 SS1 Purpose and Boundaries.

Boundary check

• Governing OPORD confirmed current: EP-010 ref [ ]
• Today’s brief (EP-016) read by all posted personnel before the principal’s day starts
• Comms settings (EP-011) and standing post orders (EP-009) confirmed unchanged since last cycle
• No-go / abort criteria for today’s movements extracted from the OPORD and briefed
• Decision: [ ] Detail cleared to open today’s cycle - authority: Team Leader

Handoff boundaries (do not improvise these)

• Immediate-action triggers (contact / medical / fire / evacuation) mapped to EP-025 drills under the EP-012 plan - confirmed briefed, not exercised ad hoc
• Handoff point and resume point for an EP-025 drill understood by every position
• Notes / boundary exceptions today: [ ]

00b * Battle Rhythm & Triggers

Where today’s cycle sits inside the standing battle rhythm; the cadence and handover triggers this detail-day inherits and closes out. → EP-023 SS2 step 1 (arrival per EP-021 cycle) and SS8 step 4 (daily log closure, next-day M-hour) - binds to EP-021 in full.

• Today’s M-hour and first movement time confirmed against the EP-021 daily cycle
• Posture band for today read from the daily brief: [Low / Moderate / Elevated / High / Critical]
• Escalation trigger (posture step-up on band crossing): → 06 Running Decision Points
• Evening sync scheduled - time: [ ]
• Daily log carried forward from prior cycle reviewed for open items

01 * Shift Start / Handover

Arrival, kit, comms, and handover sequence before any element takes post or the principal’s day begins. → EP-023 SS2 Shift Start.

• Arrived per EP-021 daily cycle; daily brief (EP-016) read before taking post
• Kit and vehicle checks complete per SYS-009 / SYS-010 checklists
• Deficiencies reported to Shift Lead: [ ] - before principal’s day starts, not after
• Comms check all nets per EP-011 complete
• Duress word confirmed: [ ]
• Common operating picture (ART-common-operating-picture) live on all required devices
• Today’s movement set, arrival geometry (EP-002 venue advance), and no-go/abort criteria confirmed

Handover serial

Clone per relieving element / post. → EP-023 SS2 step 4; procedure per EP-021 SS3.

• [position / net - e.g. Post 2 / Command net]
  • Outgoing element briefs status, open items, and any unresolved deviation
  • Oncoming Shift Lead accepts handover by name on the command net
  • Post orders (EP-009) reconfirmed current for this position
  • Time of handover: [ ]
  • Notes / discrepancies: [ ]
• [position / net 2]
  • Outgoing element briefs status, open items, and any unresolved deviation
  • Oncoming Shift Lead accepts handover by name on the command net
  • Post orders (EP-009) reconfirmed current for this position
  • Time of handover: [ ]
  • Notes / discrepancies: [ ]

02 * Static / RON Posture

Venue occupation while static and rest-overnight posture at day’s close - the two states where the detail is not moving. → EP-023 SS6 Venue Occupation and SS8 Rest-Overnight (RON) Reset.

Venue occupation (static posture)

• Posts assigned per EP-009 and OPORD task matrix: access point coverage, hold security, close cover
• Hold route walked by at least one operator on arrival; door state and egress confirmed
• Crowd / access rhythm watched against advance baseline (staff flow, badge status)
• Anomaly observed: [unscheduled staff / unbadged access / fixated person - ATAP indicator] → reported on detail net and logged
• Principal internal movements announced on net before they happen
• Formation collapse/expand executed per space and OPORD defaults
• Net discipline maintained - routine traffic held, net clear for exception traffic

RON reset (end of cycle)

• Residence / hotel posture established per EP-009 before manning reduces
• Vehicles: fuel level [>=3/4], faults reported: [ ], kit restowed per SYS-010, then secured
• Radios and handsets on charge
• Medical kit seals checked - discrepancies logged
• Daily log closed per EP-021
• Next-day M-hour and first movement confirmed at evening sync
• Overnight watch posted: [Yes / No] - handover per EP-021 SS3 if yes
• Overnight exception reporting channel confirmed per EP-011

03 * Movement Serials

En-route crew discipline for every leg run today. Governed by EP-004; this branch is the execution checklist, not the movement plan itself. → EP-023 SS4 Movement Execution.

Movement leg serial

Clone per leg run today.

• [leg - e.g. Residence → Venue A (Route Bravo)]
  • Positions and spacing set per EP-004 for today’s vehicle count
  • Protection vehicle maintains sight of principal vehicle throughout
  • Waypoint calls made at OPORD-designated points
  • Route deviation called before the turn: [Yes / N-A]
  • Driver drives only; escort observes and communicates; navigation load off the wheel
  • Planned halts only, at EP-003 surveyed points: [ ]
  • Unplanned halt occurred: [Yes / No] - if yes, minimum duration, escort dismount per formation drill
  • Route deviation authority exercised: → 06 Running Decision Points
  • Forced deviation (blockage / police direction): [ ] - new route letter reported immediately: [ ]
  • Possible-follow indicator logged: [ ] - format per EP-008; confirmation run tasked to EP-024, not improvised with principal aboard
  • Departure call made (element / principal count / route letter / ETA): [ ]
  • Notes / decision log: [ ]
• [leg 2]
  • Positions and spacing set per EP-004 for today’s vehicle count
  • Protection vehicle maintains sight of principal vehicle throughout
  • Waypoint calls made at OPORD-designated points
  • Route deviation called before the turn: [Yes / N-A]
  • Driver drives only; escort observes and communicates; navigation load off the wheel
  • Planned halts only, at EP-003 surveyed points: [ ]
  • Unplanned halt occurred: [Yes / No] - if yes, minimum duration, escort dismount per formation drill
  • Route deviation authority exercised: → 06 Running Decision Points
  • Forced deviation (blockage / police direction): [ ] - new route letter reported immediately: [ ]
  • Possible-follow indicator logged: [ ] - format per EP-008; confirmation run tasked to EP-024, not improvised with principal aboard
  • Departure call made (element / principal count / route letter / ETA): [ ]
  • Notes / decision log: [ ]

04 * Arrival / Departure Sequences

The three point-transitions of the day: leaving the residence, arriving at a venue, and the departure/return leg. → EP-023 SS3 Residence Departure Sequence, SS5 Arrival Sequence, SS7 Departure and Return.

Departure point serial

Clone per departure from a controlled point (residence or venue).

• [point - e.g. Residence]
  • Exterior check of departure point and vehicle line complete before principal is committed (EP-009 residence posts where manned)
  • Vehicles staged per EP-004: engines running, protected-side doors unlocked, driver with vehicle
  • Route confirmed valid against current picture (traffic, closures, EP-016 alerts) - alternate selected if not
  • Advance vehicle departure lead time: [X minutes] - N-A if none assigned
  • Principal door-to-vehicle move in OPORD close-escort formation - no curb wait
  • Embus order executed per EP-004
  • Departure call made on detail net: element / principal count / route letter / ETA

Arrival point serial

Clone per arrival at a venue or controlled point.

• [point - e.g. Venue A]
  • Arrival point cleared against EP-002 advance geometry: box controlled, door confirmed, hold route open
  • Two-minute-out call made on venue net
  • Venue contact alerted per liaison record
  • Debus per EP-004 order: escort out first, principal moves on escort signal, no open-air wait
  • Vehicles repositioned to staging point per EP-002; drivers remain on net
  • One vehicle held in immediate-recall state for the duration of the visit

Departure and return serial

Clone per venue departure back toward a controlled point.

• [leg - e.g. Venue A → Residence]
  • Exposed segment re-cleared before principal is committed (conditions re-checked, not assumed unchanged from arrival)
  • Return route confirmed against current picture - alternate used over default inbound route where OPORD provides one (pattern avoidance)
  • Departure call made on detail net
  • Arrival-home call made on detail net
  • Accountability confirmed: principal, party, all elements

05 * Principal Interface Standard

How the detail communicates with the principal and family office today - who speaks, what gets logged. → EP-023 SS9 Principal Interface Standard.

• Single interface confirmed: Detail Leader / designated Shift Lead - name/initials: [ ]
• All schedule and security requests redirected to that channel by other operators
• Protective advice given today: [topic] - risk stated: [ ] - principal decision: [accepted / declined] - posture adjustment made: [ ] - logged: [Yes]
• Client-imposed risk acceptance today (declined escort / unscheduled stop): [Yes / No]
  • If yes: logged same day: [ ] - routed to EP-017 reporting: [ ]
  • Chronic-acceptance pattern flagged: [Yes / No] → if yes, Team Leader-client conversation, not silent absorption
• Discretion maintained - no detail conversation on the principal beyond operational need, in vehicles or venues
• Family / staff treated per OPORD party scope

06 * Running Decision Points

The in-the-moment authorities that keep deviations lawful and logged rather than improvised. → EP-023 SS10 Running Decision Points.

Decision log entry serial

Clone per decision exercised today.

• [decision - e.g. switch to briefed alternate route]
  • Authority exercised: [Shift Lead / Detail Leader / Team Leader / Any operator]
  • Decision type: [route switch / unbriefed improvisation / movement delay / itinerary cancel-reorder / posture step-up / emergency declaration / stand-down]
  • Basis: [ ]
  • Reported to: [ ] - method: [ ]
  • Time: [ ]
  • Notes: [ ]

Standing authority table (reference - do not edit in field)

• Switch to briefed alternate route: Shift Lead (driver executes) - report with route letter

• Unbriefed route improvisation: Detail Leader only - only when all briefed alternates are invalid

• Delay a movement inside itinerary slack: Shift Lead - inform principal interface

• Cancel or reorder an itinerary item: Team Leader with principal - per OPORD no-go criteria

• Posture step up (band crossing): Shift Lead up, Team Leader confirms - per EP-021 threat-change rule

• Declare emergency / execute EP-025 drill: Any operator - net goes flash per EP-011

• Stand down from emergency posture: Detail Leader - after accountability and assessment

• Decision: [ ] EP-025 drill triggered today - [Yes / No] - if yes, hand off to EP-025 map, resume this map at recovery per SS00 boundary check

99 * Execution Admin

The audit trail for today’s cycle - not a deliverable section itself; feeds EP-017 reporting and the next EP-021 cycle. → EP-023 running admin across all sections; closes SS00 gates opened at cycle start.

Deviation / decision log (running, this cycle)

• [deviation or decision - ref branch/leaf] → logged time [ ] - reported to [ ]
• [item 2]

Product / report register

• EP-017 client report items queued from today’s risk acceptances or deviations
• EP-025 after-action items if a drill fired today
• Daily log (EP-021) closed and filed

Sign-offs

• Shift Lead sign-off: [initials / time]
• Team Leader sign-off (if escalation occurred): [initials / time]
• Detail Leader sign-off (cycle close): [initials / time]

Open actions / RFIs carried to next cycle

• [open item]
• [open item 2]