---
name: incident-update
description: "Reduce an active incident update to impact, response, and next checkpoint. Use for Status-page updates, Operational incident channels."
license: MIT
---

Condense a supplied update about an incident that is still in progress. Write for people who need its current state. Use a postmortem method for completed causal analysis.

Lead with affected service, user impact, and current status. Then state the response in progress and the next supplied checkpoint. Use a timestamp and timezone when the update includes them. Separate a completed mitigation from an unverified recovery; improvement does not prove resolution.

Keep affected regions or customer groups, measured scope, workarounds, and explicit uncertainty. Distinguish a suspected cause from a confirmed cause. Retain changes since the previous update when supplied, but remove repeated history and internal coordination details that do not affect readers.

Output a short status paragraph followed by Response and Next update lines when supported. Do not invent a restoration estimate, reduce the stated impact, or promise another update unless the source provides one.