Incident commander desk

The older incident commander page still sends one link to a status hostname that does not open. Use this note instead. Nothing is paged, and nothing is uploaded.

What to name before the first update

• One commander. A second person covers comms if the commander is in the bridge.
• A severity the team already uses. Do not invent a new scale on this page.
• The sentence a person will post, in words a customer can act on.
• The time of the next update, even if the next update is "no change".

Incident name Commander Comms owner Severity SEV1 — customers cannot complete the main job SEV2 — a major path is degraded SEV3 — a workaround exists Sentence a person will post Next update Write the handoff

Where the rest of the work lives

• Runbook desk — first check and stop rule.
• Status note — the customer update, written here.
• Error budget — how much of the window this incident spends.
• Service levels — a written SLA is scoped per engagement, not copied from a template.
• Cybersecurity desk — when the incident is a security event.

A scoped response is a Discovery $99 conversation, not a button on this page.