1
Active major incident
Active Sev-1 Example
Run major incidents with clear roles, timing, and controlled communication.
Major incident command is now route-native in `apps/web`, bringing the highest-discipline response surface into the production shell instead of leaving it in demo-only HTML.
140+
Estimated impacted users
12 min
To next stakeholder update
2
Pending command decisions
Incident Command Summary
The command view should reduce ambiguity by showing the single agreed operational picture.
| Command Element | Current State | Why It Matters |
|---|---|---|
| Service status | Degraded remote access across 3 divisions | Confirms this is a shared service incident, not a local endpoint issue |
| Vendor state | Evidence pack sent; vendor on active review | Shows external dependency and sets expectation for escalation timing |
| Current workaround | No service-impacting workaround approved yet | Keeps command pressure on safe decision-making instead of rushed action |
| Next checkpoint | 10:30 AM bridge review and stakeholder update | Maintains communication rhythm and decision cadence |
Live Bridge Timeline
The command view should keep the event narrative current enough that people stop asking for recap.
09:06 AM
Sev-1 declared. Command bridge opened and core roles assigned.
09:14 AM
AI-assisted diagnostics bundle assembled and attached. Vendor escalation packet drafted.
09:26 AM
Vendor engaged. No safe workaround approved yet because routing-change risk is still under review.
09:44 AM
Support update issued internally. Stakeholder holding statement approved but not yet sent publicly.
10:18 AM
Current checkpoint: waiting on vendor confirmation and commander decision on contingency communication.