Status Page Updates
A template and cadence for status updates during incidents.
Published:
Admin User
Updated:
published
Status Page Updates
Clear, consistent updates reduce support load and build trust during incidents.
Template
- What happened (brief)
- Current impact
- What we’re doing
- Next update time
- Workarounds (if any)
Related
Incident Response Runbook Incident Communication Postmortem TemplateFAQ
How often should we update?
Set a cadence (e.g., every 30–60 minutes) and stick to it to reduce uncertainty.
What should we avoid saying?
Speculation. Share facts, impact, and next update time.
Should we share root cause during incident?
Only if confirmed. Otherwise share what is known and what is being investigated.
What reduces support load most?
Clear impact statement + workaround + next update time.
What’s the first improvement?
Use a fixed template and assign an update owner.