Incident Communication Template Generator
Generate copy-ready incident updates by severity, audience, and channel; copy Markdown, Slack, or HTML in one click.
What this generator produces
Two versions of an incident update tailored to your audience: a short headline message and a detailed update with scope, status, and next-update timing. Output formats include plain text, Markdown (for docs and status notes), Slack formatting, and simple HTML. You can also download a Word-compatible .doc or a .md file.
Inputs cover incident type, affected systems, customer impact, severity, start time, next update ETA, audience (engineering/executive/customer), and channel (email/Slack/status page). Everything runs in your browser; nothing you enter is sent to a server.
A concrete example
For a SEV2 checkout issue affecting ~20% of users since 14:10 UTC, with a rollback in progress and queues draining, the brief output reads: "SEV2 – Checkout errors impacting users. Started: 2026-08-25 14:10 UTC. Status: Investigating and rolling back; queues draining. Next update in 30 min." The detailed output includes scope/cause and actions with the same next-update commitment.
When teams use it
On-call responders posting customer status updates at a steady cadence.
Executives needing a clear internal summary during a major incident.
Engineering leads coordinating Slack updates across time zones.
Put the number into an operating plan
Frequently asked questions
How often should we post updates?
Use a severity-based cadence: SEV0 every 10–15 minutes, SEV1 every 20–30 minutes, SEV2 every 30–60 minutes, and SEV3 every 60–120 minutes. Communicate the next update time in every post and keep it.
Can we customize the tone for different audiences?
Yes. Pick the audience to adapt phrasing for engineering, executives, or customers. You can further edit the generated text before sending.
Does the tool store any data?
No. It runs entirely in your browser and does not send inputs to a server.