Use the Command Center

Before you start

• Open the active incident.
• Be ready to correct scope, severity, or status if the initial declaration was incomplete.

Do this

1. Read the incident header first and confirm the title, summary, severity, status, commander, and environment are still correct.
2. Check Impacted Scope and add or remove systems and functions until the page reflects the real blast radius.
3. Review Alert Occurrences to see whether the same alert is still repeating or has returned after an earlier incident.
4. Review the recent change summary if you need fast deployment or dependency context.
5. Use the AI summary and transcripts to bring new responders up to speed quickly.
6. Start a runbook from Runbook Orchestration if there is a repeatable workflow you want tracked inside the incident.
7. Keep the timeline current so responders and observers can follow the investigation without asking for verbal recaps.

Check it worked

• Responders can open the incident and understand the current state without extra explanation.
• The impacted scope matches the services actually under investigation.
• The command center shows the bridge links, alert context, and current actions needed to work the incident.

If it does not work

• If the page feels empty, tighten the incident summary and impacted scope first.
• If responders cannot tell what changed recently, add a timeline entry instead of relying on chat history.
• If the recommended runbook is wrong, fix the runbook targets so they match the incident scope.

Next

• Work status and communications
• Use bridge links and alert context