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

Interactive walkthrough · 11 steps

Walk through a state EOC activation.

Stand up the activation, task it, handle two exceptions, and leave the after-action record behind.

  • State emergency operations center, ESF desks
  • Eleven steps, activation through after-action
Opens full screen. Press Esc to come back.

What happens in the walkthrough.

One activation, from the watch that triggers it to the record it leaves behind.

  1. 01 Start from the threshold, not the binder The activation opens from a plan that already carries the tasks, the desks and the rules. In practice a watch or warning crosses your threshold and the matching SOP applies itself. LiveSOP does not replace WebEOC; it runs the procedure across the boards you already keep.
  2. 02 Set the activation variables The ESF set is derived from the threat and the activation level. Change the level and the desks that staff change with it, drawn from counties with a declaration and staff whose qualifications are current.
  3. 03 Review the task timeline The whole procedure in order, with real hooks into NWS feeds, county declarations and the state resource inventory. The EOP stops being a binder and becomes a running procedure that knows what has already happened.
  4. 04 Arm the notification rules These come with the template, and the last one keeps authority where it belongs. Escalation is settled before the event rather than argued about at 16:40 with a county on the phone.
  5. 05 Activate One action turns a plan into a monitored activation. The ESF desks are notified and the clocks start.
  6. 06 Run it, and handle two exceptions A county 213RR for search and rescue has one SOP path, so LiveSOP drafts the mission assignment and the county gets a state mission number inside two minutes. Then a casualty surge the region cannot absorb: LiveSOP shows the request, the impact and the options the SOP allows, and stops.
  7. 07 Leave the after-action record There is no button that commits the Guard, because that decision belongs to a person. The decision, its reason and its owner are captured as it happens, so the after-action report is an export rather than a reconstruction.

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