Skip to content
LiveSOP by Compass Island
Try a walkthrough Request a demo

Operational execution platform

The operating layer between your procedures and your people.

One structure holds the procedure, the facts of this operation, the tasks, the owners, the timing, who gets told what, and everything that happened.

LiveSOP, the Evolution of Operations.

Who runs it

Built for the person who gets called when it goes wrong.

  • Executive protection

    The call

    A principal is in motion and the inbound just slipped 95 minutes. Every downstream leg is coupled to it.

    What the first five minutes need

    The delay related to what it moves — drivers, meet points, the people waiting — before the phone rings.

  • Operations center

    The call

    Four operations running at once, and the shift changes in twenty minutes.

    What the first five minutes need

    A handover the incoming shift can read, instead of an hour of catching up.

  • Business continuity

    The call

    A systems outage, and the plan is a binder written by someone who left.

    What the first five minutes need

    The plan running as a mission with named owners and decision points.

  • Private events and hospitality

    The call

    Ninety minutes to doors at a private investor dinner, and four guests are added. Screening, seating, catering counts and car assignments all move at once.

    What the first five minutes need

    The change entered once and pushed to the door team, the kitchen and the drivers — each seeing only their own part of the list.

Preparation

The work is not building the operation. It is preparing for it.

Everything LiveSOP™ does at speed is paid for in advance. Templates carry the sequence and the rules; your vendors, sites, vehicles and people are described once. By the time something happens, the platform already knows what your organization considers a valid answer.

Prepared once

  • Procedure templates, versioned
  • Roles, sequence and timing
  • Notification and visibility rules
  • Approved vendors, sites and assets
  • People, teams and who deputizes for whom

So activation is this short

  • Template Executive arrival
  • Principal R. Okonjo
  • Location Panama City
  • Operations lead M. Reyes

Four selections, and the tasks, owners, timings, map and rules are in place. You decided all of it in advance.

Preparation becomes execution.

A LiveSOP mission in planning: an activity rail of planning steps above a task table whose steps reference mission variables by name
The plan a template produces: tasks reference variables by name, and one unassigned variable is holding the move to Pending.

The mission model

Five parts, each removing a specific way operations fail.

Systems provide the facts.

The procedure provides the rules.

LiveSOP connects them during execution.

Procedure templates

Your best operator’s knowledge stops leaving with them

Order, roles, timing and notification rules live in a versioned template. Improve it once; every mission after inherits it.

Without it Otherwise the procedure only really exists in one person’s head — and they are off shift.
A live LiveSOP mission dashboard showing open mission alerts and a geospatial view with the planned route
Mission #12 running live: open alerts and the geospatial view on the mission dashboard.

Notification and visibility rules

Who gets told what, decided before the pressure starts.

Deciding who needs to know is the work that gets skipped under pressure. Here it is part of the procedure: a plain sentence anyone can check, attached to a trigger.

Notification rules 4 rules · 2 enabled

When inbound flight is delayed, notify Ops desk, Driver, Embassy liaison via Email & push.

When arrival is confirmed, notify HQ briefing attendees via Push.

When a high-priority task passes its due time, notify Duty officer via SMS.

Hide principal detail and accommodation from External participants.

Illustrative rules. Available triggers and channels are scoped with you.

Ownership

Ownership is a property of the mission, not the last thing someone said on a call.

Every participant can answer

  • What needs to happen
  • Who owns it
  • When it is due
  • What is most urgent right now
  • What has been completed
  • What is blocked, and on what
  • What is at risk of being missed
Task 07

Confirm alternate route with local contact

Blocking

Owner

J. Alvarez

Due

15:40

Priority

High

Blocks

Tasks 08, 09

The task exists because a procedure said it must, it is bound to the mission’s facts, and it blocks named work downstream.

During and after the mission

The Activity Rail is the operation telling its own story.

Assignments, field confirmations, changes and decisions join the rail as they happen — readable mid-operation, and finished the moment the mission closes.

Mission 0412 · Activity Rail Completed
  1. Day −2 Mission built Completed
  2. 13:20 Live Completed
  3. 13:48 Inbound delayed Change
  4. 13:51 Operator approves Completed
  5. 14:05 Ground leg running Completed
  6. 15:26 Access restricted Change
  7. 15:31 Response applied Completed
  8. 16:45 Closed Completed

Mid-operation handover. Whoever joins reads the rail and is current, without a catch-up call.

After-action review. Walk the mission in order and see where time was actually lost.

Evidence. Show that the procedure was followed, with owners and timings attached.

Template change. Fix the step that failed, once, where every future mission will pick it up.

LiveSOP is built and supported by Compass Island, which builds software for organizations that have to operate under changing conditions.

Our sister product CI360 handles awareness — knowing what is happening. LiveSOP handles what comes after that: knowing what to do next, and making sure it gets done.

The parts only make sense running.

On a page these are architecture. Watch them absorb a change mid-operation and it becomes obvious what each one is for.