Use the incident overview

Scan the incident's next step, scope, signals, work, timeline, and Diagnosis state.

GuideLast verified 2026-08-29Open Markdown version

On this page

Before you start

Responders who need a fast operational handoff.

You need permission to view the incident.

Step 1 of 7
Read the next step
For a fast scan, use this order: Next step → scope, impact, and owner → Response signals → Open work → Timeline highlights → Diagnosis. Open Next step when you need full context.
Step 2 of 7
Review identity and scope
Review severity, status, affected service, regions, customer impact, ownership, and last update.

Step 3 of 7
Review response signals
Use Response signals to find open questions, evidence, and event counts.
Step 4 of 7
Review open work
Review Open work in urgency and due-date order.
Scan the Overview for the next action, affected scope, and the latest operational evidence. Open full-size image(opens in a new tab)
Step 5 of 7
Review timeline highlights
Read Timeline highlights. Select View timeline for the complete event record.
Step 6 of 7
Review Diagnosis
Review the Diagnosis summary. Open Diagnosis for its evidence and saved result.

Step 7 of 7
Fill missing context
Use Set service, Set regions, or Assess impact when a critical value is missing.

You can state the incident scope, impact, owner, next action, and latest evidence from one screen.

Use the adjacent Set or Assess action. Do not infer missing incident context. The Overview keeps the gap visible until a responder fills it.

Review the timeline and incident scope directly. Open work only lists response actions that have been added to that panel.

Open the linked workspace for the complete record.