01
The SOP is the mission
Tasks come from your procedure template, not a blank form. Open the arrival SOP, set the principal, flight, vehicle and driver, and the eight tasks, their owners and their timings are already in place.
Executive protection software
Executive protection software built for the moment the plan changes.
Most EP platforms are built around the advance: surveys, routes, positions on a map, a briefing PDF. LiveSOP™ takes over where they stop. The detail runs as a live mission, so when the inbound is delayed 90 minutes the plan re-times itself, the right people are told, and the one decision that needs a human is routed to the duty officer.
- Tasks timed off the itinerary, not typed by hand
- Changes arrive with their consequences attached
- An after-action report nobody has to write
Where EP software usually stops
The advance is the easy part.
An advance survey, a route, a hotel review, positions on a map. The field has good tools for that now, and they have replaced a lot of spreadsheets and group chats.
But an advance is a description of the plan. It cannot tell you that the inbound is delayed, that six tasks just moved, that the driver’s duty window no longer covers the new arrival, or who is supposed to decide what to do about it. At 13:48 the plan is back in the team lead’s head and the chat thread.
LiveSOP is built for 13:48.
Activity Rail · executive transport, LAX arrival
- 13:20 Mission live Eight tasks, four rules armed, five recipients on the distribution. Completed
- 13:48 Inbound delayed 90 minutes Six dependent tasks re-time themselves. The rule tells the five people it concerns. Change
- 13:49 Cover decision routed Three options the SOP allows, the one the duty-time rule forbids marked, in front of the duty officer. Change
- 13:51 Swap authorized Duty officer authorizes K. Reyes. Downstream timings update. Basis and owner recorded. Completed
- 16:45 Closed After-action report filed. Nothing reconstructed. Completed
From the interactive walkthrough. Every timing is derived from the 14:20 arrival, then from the delay.
What is different
Six things a detail gets from LiveSOP that an advance tool cannot give it.
02
Timing is derived, not typed
Every task is timed off the mission variables. Move the arrival and every dependent task moves with it. Nobody edits a timeline by hand at 13:48.
03
A change arrives with its consequences
A flight delay is not an alert to interpret. It lands as what moved, who is affected and what the procedure says to do, waiting for one approval.
04
Decisions are routed, never made for you
Re-timing is automatic. Who stands the detail for the extra 90 minutes is not. LiveSOP lists the options the SOP allows, marks the one the duty-time rule forbids, and puts the choice in front of the duty officer.
05
Rules that read as sentences
When inbound flight is delayed, notify Ops desk, Driver and Embassy liaison by email and push. Hide principal detail from external participants. Decided in planning, checked by anyone, enforced while it runs.
06
The record writes itself
Assignments, confirmations, changes and the authorization join the Activity Rail as they happen. The after-action report is an export. Fix the step that failed in the template once, and every future detail inherits it.
Side by side
What the detail gets, compared.
The left column describes the EP platforms built around the advance. The right is LiveSOP. Where the information is the same, the difference is what happens to it once the movement is under way.
Mission timeline
Typical EP platform
Built by hand for each movement, and updated by hand when it changes.
LiveSOP
Generated from the SOP template and timed off the mission variables. Re-timed when they change.
Sites, routes and contacts
Typical EP platform
Captured in survey forms and a briefing PDF.
LiveSOP
Held as mission items the tasks reference. When the arrival point moves, the step that says “collect principal at arrival point” is still correct.
The team on the map
Typical EP platform
Positions of people and vehicles.
LiveSOP
Positions, plus status against the clock: which task is late, which is blocked, and what that breaks next.
The flight is delayed
Typical EP platform
A notification. The team lead works out what it means and messages the detail.
LiveSOP
Six dependent tasks re-time. The rule notifies the five people it concerns. The cover decision is routed to the duty officer with the forbidden option marked.
Who gets told
Typical EP platform
Whoever is in the group chat.
LiveSOP
Notification and visibility rules written in planning: who is told, on which channel, and what an external participant is not allowed to see.
Outside the team
Typical EP platform
Contacts in a notes field.
LiveSOP
The driver, the hotel and the embassy liaison join as participants without accounts, see only their assignment, and their confirmations land in the mission.
After the movement
Typical EP platform
A report someone writes from memory and the chat log.
LiveSOP
The Activity Rail is the report: owners, timings, decisions and their basis, exported.
Beyond the detail
Typical EP platform
Executive protection only.
LiveSOP
The same operating model runs the rest of the security function: travel risk, a facility threat, accounting for a workforce after an incident, an event.
Interactive walkthrough · 11 steps · 2–4 minutes
Watch it handle a 90-minute delay.
Plan the LAX arrival from a saved SOP, go live, handle a missed driver check-in and a delayed inbound, decide who covers the new window, and read the report. Runs in your browser, no sign-up.
Beyond the detail
One operating layer for the whole security function.
A movement is one procedure the GSOC runs. LiveSOP runs the rest with the same model: a traveller in a disrupted region, a threat to a facility, a workforce to account for after an incident abroad, an event. Not a silo for the EP team; one system the duty officer, the travel desk and the detail work from, with one record at the end.
See the other five marketsQuestions
Asked by people who have been oversold before.
- What is executive protection software?
- Software a protective detail uses to plan and run a movement: the itinerary, the advance, the team, the record. Most of it is organized around the advance and the map. LiveSOP is organized around the procedure. The detail runs as a live mission whose tasks, timings and notifications come from your SOP and update when the facts of the movement change.
- Does LiveSOP replace our advance tools?
- Not necessarily. Sites, routes, vehicles and contacts become mission items that the tasks reference, so a change to one of them reaches every task that depends on it. Which systems feed a mission, and which facts an operator enters directly, is scoped during implementation rather than promised here.
- Does it decide anything on its own?
- No. LiveSOP re-times the plan and drafts the response the SOP prescribes, but anything that is a judgment, such as who stands the detail for a new window or whether to change the arrival point, is routed to a named person and waits for their approval. The decision, its basis and its owner are recorded in the mission.
- Can the driver or the hotel see the mission?
- They can join as participants without accounts. Visibility rules written in planning decide what an external participant sees, so the driver has the pickup point and the timings and does not have the principal’s detail.
- How do we evaluate it?
- Bring the movement you think will break it. In a demonstration we activate your procedure, delay the inbound and show what the operator sees and decides. The interactive walkthrough covers the same ground in about four minutes with our scenario, and needs no sign-up.
Bring the movement you think will break it.
The walkthrough uses our scenario. A demonstration uses your itinerary, your SOP and your escalation path, with the inbound delayed on purpose.