Interactive walkthrough · 11 steps
Walk through an executive protection mission.
Plan a mission, run it, handle two exceptions and an authorization the system will not make for you, then close it out.
- Executive transport, LAX arrival
- Eleven steps, planning through after-action
Opens full screen. Press Esc to come back.
What happens in the walkthrough.
One mission, from the moment someone opens the template to the moment the report is filed.
- 01 Start from a saved SOP The mission opens from a template that already carries the tasks, the timing and the rules. The procedure is not rebuilt each time it is needed.
- 02 Set the mission variables The who, what, where and when. Each field searches records the system already holds: the vehicle list is scoped to in-region, in-service fleet, the driver list to cleared people on shift.
- 03 Review the task timeline Eight tasks, timed off the 14:20 arrival. Mission variables appear inline in the tasks that use them, so changing one value updates every task that depends on it.
- 04 Arm the notification rules Rules read as sentences, so escalation is settled in planning rather than during the incident. When the mission goes live, the duty officer and the principal’s executive assistant are notified by email and push.
- 05 Go live Eight tasks, four rules armed, five recipients on the distribution.
- 06 Run it, and handle two exceptions The dashboard carries tasks, comms and alerts in one view. A driver check-in is missed, and the inbound flight is delayed by 90 minutes — the timeline re-times itself and everyone is told. Then the new arrival window collides with a street closure the advance team has not cleared, and LiveSOP™ stops.
- 07 Close it out Moving the principal onto a route the advance team has not cleared is a protective decision, so the system surfaces the options and routes them to the detail leader rather than picking one. The authorization, its basis and its owner land in the after-action report alongside the tasks and exceptions, with nothing reconstructed afterwards.
Bring the procedure you think will break it.
The walkthrough uses our scenario. A demonstration uses yours, with your terminology and your escalation path.