In a crisis, speed and consistency matter more than polish. This builder turns the facts of an incident into a disciplined internal brief so every spokesperson says the same accurate thing — and avoids the remarks that turn a problem into a scandal.
How it works
The tool structures the essentials of crisis communications into headed Markdown. You set a severity level and write a short, agreed incident summary. You then list only confirmed facts — never assumptions — and draft your talking points. The builder enforces a maximum of three, trimming extras, because a small set of messages is what survives the pressure of a live response.
Crucially, it captures a what not to say list, a single designated spokesperson, and a media monitoring plan. Keeping confirmed facts separate from messaging, and naming one voice, is what prevents the contradictory statements that escalate a crisis. The output is a one-page internal brief everyone can align on in minutes.
Tips and example
Separate “confirmed” from “believed” ruthlessly. Saying “we detected the issue at 14:10 and patched it by 14:55” is defensible; saying “no data was accessed” before forensics finish is a hostage to fortune.
Anchor each talking point in an action you took (“we fixed it within 45 minutes”, “we are notifying affected users directly”), not a reassurance you cannot prove. Brief everyone, but let only the named spokesperson speak — everyone else routes questions to them and references this brief.