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

Interactive walkthrough · 11 steps

Walk through a data center shift turnover.

Build the turnover, activate it, handle two exceptions, and leave the client evidence record behind.

  • Contract security, armed and unarmed posts
  • Eleven steps, turnover through evidence record
Opens full screen. Press Esc to come back.

What happens in the walkthrough.

One shift turnover, from the post order to the evidence it leaves behind.

  1. 01 Start from the post order The turnover opens from a template that already carries the sequence, the posts and the rules. In practice it fires on a schedule, twice a day, for every site under contract, so turnover happens the same way whoever is supervising.
  2. 02 Set the turnover variables Change the post plan and the officers required, the armed count and the billable hours move with it. Rosters, credentials and the armory are filtered to who is actually eligible tonight, so nobody is assigned who cannot lawfully stand the post.
  3. 03 Review the task timeline The turnover sequence with real hooks into the state licensing registry, the armory and the badge readers at each post. It is the riskiest 45 minutes of the day and usually the least documented; here every step carries evidence.
  4. 04 Arm the notification rules These come with the template, and the last two protect the contract. Unfilled posts and credential lapses are what cost SLA credits and audit findings, and the rules catch both before the shift starts.
  5. 05 Activate One button turns the agreed procedure into a monitored shift that writes its own evidence. The sequence runs and the board goes live.
  6. 06 Run it, and handle two exceptions An officer calls out 40 minutes before shift — one SOP path, so LiveSOP drafts the fill and the coverage gap never happens. Then the officer assigned to the armed lobby post has a lapsed armed endorsement: LiveSOP will not issue the weapon, shows the options the SOP allows, and stops.
  7. 07 Leave the evidence record Arming an officer without a current endorsement is a licensing determination, not a software one, so the system surfaces, matches and routes but does not decide. The authorization, its basis and its owner land in the client evidence record without anyone assembling it.

Bring the procedure you think will break it.

The walkthrough uses our scenario. A demonstration uses yours, with your terminology and your escalation path.

Request a demo All walkthroughs