The decision

What should operators verify, document, escalate, and review for this incident pattern?

The workbench provides a neutral skeleton for common operating events. It helps teams compare an existing SOP with a consistent sequence of verification, safety, communication, evidence preservation, recovery, and after-action review.

Input

An incident pattern and optional sanitized context.

Output

A response sequence, note structure, and after-action prompts.

Owner

The incident commander or role named in the approved site procedure.

Before an event

Connect the template to real authority.

  • Identify the approved SOP and the role authorized to command the response.
  • Confirm emergency contacts, alternate communications, and escalation thresholds.
  • Define evidence-preservation and chain-of-custody requirements.
  • Document degraded-operation procedures for network, controller, power, or camera loss.
  • Remove confidential locations, identities, credentials, and vulnerabilities from portal inputs.

Working tool

Generate the response structure

Use a pattern to compare against an approved SOP, not as live emergency command.

Use the result

Turn the output into a tabletop, not a clipboard artifact.

Compare

Mark each generated step as covered, conflicting, missing, or not applicable in the approved SOP.

Assign

Name the role responsible for verification, command, communication, evidence, and recovery.

Time

Add response targets only when policy and operating conditions support them.

Exercise

Run a tabletop with normal, degraded, and ambiguous conditions.

Observe

Record delays, false assumptions, workarounds, and unavailable evidence.

Close

Assign corrective actions with owners, dates, and verification evidence.

Method and limits

Not emergency dispatch or site-specific instruction.

The generator uses deterministic templates for five common patterns. It cannot see the incident, confirm facts, assess threat, contact responders, preserve evidence, or understand local authority. Follow approved emergency procedures and professional direction.

Any site-specific playbook requires review by security leadership, emergency management, legal, privacy, IT, facilities, and public-safety partners as appropriate.