Strategy
Part of Crisis communications: what to keep and what to drop
Recognizing a crisis communications failure before it repeats
crisis communications mistakes include guessing, hiding facts, vague empathy, slow approval, broken help routes, inconsistent updates, and silent corrections.
What to take away
- Most damaging message failures begin as governance or evidence failures.
- A comforting claim is dangerous when the team cannot support it.
- A silent edit leaves people who saw the first error exposed.
Crisis communications mistakes are often described as tone problems. The deeper causes are usually missing authority, poor fact control, legal misunderstanding, operational distance, or a promise that service teams cannot keep. Review the system that produced the sentence, not only the sentence itself.
Recognize the failure pattern before it repeats
Recognize the failure pattern
| Mistake | Why it fails | Better control |
|---|---|---|
| Speculating early | A guess becomes a public fact and redirects response | Confidence labels and fact owner |
| Saying everyone is safe | The claim may exceed the verified population | State who has been accounted for and what remains unknown |
| Leading with reputation | Affected people cannot find useful action | Put safety, assistance, and service first |
| Using one message for all | Different groups face different decisions | Audience-specific briefs from one fact log |
| Approval by committee | Delay grows while accountability disappears | Scoped decision authority |
| Promise without capacity | The support route fails when demand arrives | Load test and escalation trigger |
| Silent update | People retain the earlier error | Visible correction and redistribution |
| Declaring closure | Risk or unmet needs remain | Evidence-based recovery criteria |
Run this before release:
Recognize the failure pattern
- Verify all numbers, dates, locations, names, and scope
- Remove unsupported certainty and blame
- Confirm the promised remedy with its owner
- Test phone numbers, forms, and alternative channels
- Preserve the released version
- Correct the controlled record and notify exposed audiences
BP reported the Deepwater Horizon leak at about 1,000 barrels a day after the April 20, 2010 explosion. On April 28, 2010, federal officials put the figure near 5,000 barrels a day, per the National Commission report of January 2011.
United Airlines called a passenger belligerent in its first statement after Flight 3411 on April 9, 2017, then reversed within days as video spread, per contemporaneous news reports.
The SEC's announcement of cybersecurity incident disclosure rules requires covered registrants to report a material cybersecurity incident on Form 8-K within four business days of determining that the incident is material.
Public companies should use the rule and qualified securities advice, not a communications article, to decide a filing obligation. The rule sets filing duties; crisis communications examples show how to confirm an event and correct errors.
Do not let a public-relations timetable decide legal notice or materiality. The communication team should know which specialists assess the duty, what facts they require, who preserves the determination, and how an investor message stays consistent with customer, employee, regulatory, and operational communication.
Set approval thresholds before an incident: who may release a first statement on verified facts without legal review, and which claims need counsel. Set the clock too, for example a first statement within an hour of verification and a fuller update within four hours.
The FTC's breach and data security cases rest on Section 5 of the FTC Act, which bars unfair practices. An FTC analysis of effective breach disclosures discusses the consumer harm of delayed or inadequate disclosure and points to enforcement matters and business guidance. It does not establish a single notice deadline for every organization or incident.
Avoid minimizing language such as only, isolated, sophisticated, no evidence of misuse, or out of an abundance of caution unless the underlying record supports the exact meaning. No evidence can mean no search, a narrow search, or a completed investigation. State the evidence reviewed, the period, and the remaining limit when that detail helps people decide.
Correct the record and prevent recurrence
The GAO data reliability guide defines reliable data as accurate and complete enough for the intended use, and requires documented assessment. Use that test for crisis communications mistakes; the federal guide does not certify the local data. common crisis communications questions cover activation, first statements, and unknown facts.
The FTC advertising substantiation policy requires a reasonable basis, meaning the level of evidence experts in the field would accept, before an objective claim is disseminated. Apply that test to performance claims in crisis messages, with advice for the actual facts.
A mistake is not closed when a dashboard changes. Trace the correction from the source record through processing, reporting, exports, and the decision owner. Preserve the prior value, reason, date, reviewer, and affected actions.
Correction steps:
Correct the record
- Freeze the released version.
- Name the source record and the error.
- Approve replacement wording with the named owner.
- Republish to every channel that carried the error.
- Tell audiences who acted on it.
- Log the cause and the control change.
Then test whether the same defect can recur. This turns an error list into an operating control and gives later readers evidence the published conclusion was repaired.
Common questions
Is saying no comment always a mistake?
No. A clear limit may be responsible, but give verified facts, useful action, or a future update when possible and lawful.
Why are holding statements often weak?
They become empty when they express concern without confirming the event, offering action or help, or committing to an update. A short first statement can still be concrete.
Template: We are responding to [event] at [location], reported [date and time]. What we know: [three verified facts]. What we do not know: [named unknowns]. What we are doing: [action and owner]. Next update: [time and channel].
Should the company delete criticism?
Moderate according to published rules for threats, private data, or abuse. Do not remove legitimate criticism merely because it is uncomfortable.
