
For your company
Governance & Compliance
Module · The first 24 hours decide it
The AI Crisis Communication Check
When an AI failure becomes public, the damage is set less by the failure than by how you respond in the first day. Silence reads as guilt, a bad statement reads as evasion, and both are hard to walk back. This module checks the five things that decide whether you can speak fast and well: prepared statements, a ready spokesperson, an escalation path to comms, clarity on who you must notify, and the discipline to hold one honest story.
What the five levels look like
Every dimension in this assessment is scored 1 to 5. This is what the levels mean, dimension by dimension. The graded report diagnoses where your own answers land and what to do about it.
Statements are drafted
- 1Nothing prepared
- 2General crisis plan
- 3AI mentioned vaguely
- 4Draft holding statements
- 5Scenario-specific drafts
At the low end: With nothing written, your first public words get drafted under maximum pressure and minimum time. Draft holding statements for two or three plausible AI failure scenarios while nobody is panicking. What good looks like: Scenario-specific drafts mean hour one is spent editing, not authoring. Review them as your AI use changes; a holding statement about a system you no longer run is a false start.
A spokesperson is ready
- 1No one identified
- 2Whoever is around
- 3Named, unprepared
- 4Named and briefed
- 5Named and media-trained
At the low end: Without a named spokesperson, the crisis chooses one for you, usually badly. Name who speaks for the company on an AI failure, and make sure they understand the systems well enough to be credible. What good looks like: A named, media-trained spokesperson is a genuine asset in the first hour. Keep them briefed on your current AI systems; credibility collapses fast when the spokesperson does not understand what failed.
Escalation reaches comms fast
- 1No path
- 2Word of mouth
- 3Path exists, unknown
- 4Known escalation path
- 5Fast, tested path
At the low end: With no escalation path, hours can pass between an engineer noticing and comms finding out, and those are the hours that matter. Define who a spotted AI problem goes to, and how, before you need it. What good looks like: A fast, tested escalation path means comms is working the problem while it is still small. Drill it occasionally; an escalation route that has never been used tends to break at the first real test.
Notification duties are clear
- 1No idea
- 2Assume none
- 3Roughly aware
- 4Documented per scenario
- 5Documented with timelines
At the low end: Not knowing your notification duties means an AI incident can quietly become a regulatory breach on top of the original problem. Map who must be told, and within what window, for your likely incident types. What good looks like: Documented notification duties with timelines mean the legal clock is managed, not discovered. Keep them current as regulations and contracts change; notification windows tighten more often than they loosen.
One story, held straight
- 1No coordination
- 2Everyone improvises
- 3Loosely aligned
- 4One owned narrative
- 5One narrative, disciplined
At the low end: Without a single owned account, different parts of the company will contradict each other in public, and the inconsistency becomes the story. Put one person in charge of the narrative and route all statements through them. What good looks like: A single, disciplined narrative that updates honestly as facts emerge is what rebuilds trust after a failure. Rehearse the discipline; the instinct to minimise or over-promise is strongest exactly when it does the most damage.