Strategy
Part of Crisis communications: what to keep and what to drop
Nine message functions every crisis communications plan needs
crisis communications examples show how to confirm an event, direct action, update service, correct errors, assist families, address allegations, and close recovery.
What to take away
- Adapt the message function, never invented facts or borrowed promises.
- Protective action and human assistance come before organizational image.
- Every example needs a date, source, help route, and next update.
Crisis communications examples are useful as structures, not scripts. This article covers the nine message functions every crisis communications plan needs, each matched to a different reader and decision. Replace every bracketed field with verified information and remove any section that does not fit.
A template should force a decision about action, evidence, assistance, uncertainty, and timing rather than produce generic reassurance.
Use nine distinct message functions
Situation / Opening line to adapt
- Initial confirmation
- We are responding to [verified event] affecting [known scope] as of [time].
- Protective action
- People in [location or group] should [specific action] until [condition or update].
- Service interruption
- [Service] is unavailable for [confirmed scope]; use [safe alternative].
- Data incident
- Our investigation confirms [data category or system]; take [protective step].
- Product action
- Stop using [exact product and identifier] and follow [return or safety route].
- Employee direction
- Employees assigned to [site or team] should [reporting, safety, or work action].
- Material correction
- Our [time] update incorrectly stated [error]; the verified information is [correction].
- Family assistance
- Affected families can reach trained support at [direct route and hours].
- Recovery close
- [Service or operation] has reached [verified state]; these limits and support options remain.
FEMA's 2024 preparedness document on communication after a nuclear detonation includes ten guiding principles for emergency communication, such as involving trained communicators throughout response and using short, ordered message maps. Its extreme hazard context should not be presented as a routine business scenario.
In late September and early October 1982, seven people in the Chicago area died after taking Tylenol capsules laced with cyanide. Johnson & Johnson recalled the capsules nationwide, and the FDA's tamper resistant packaging rule followed in November 1982.
Equifax disclosed on September 7, 2017 that a breach had exposed data on about 143 million U.S. consumers, after finding the intrusion on July 29. The six-week gap shaped the coverage as much as the breach did.
For a protective message, put the action first and identify who, where, when, and why. For service or product updates, use exact identifiers and tested alternatives. For a correction, do not hide the original mistake behind updated copy. State the wrong information, provide the verified replacement, and distribute it through the exposed channels.
The NTSB's page on federal family assistance for aviation accidents explains the coordinated roles created by the Aviation Disaster Family Assistance Act of 1996 and the board's framework for family support after aviation disasters. It demonstrates that family assistance is a specialized operation with defined responsibilities, not simply a media message.
Family, employee, and customer messages need care capacity behind them. Staff the phone or in-person route, prepare language support, protect personal information, and give consistent updates even if the investigation is incomplete.
Do not disclose a person's identity publicly before the responsible process confirms notification. Slow approvals and vague empathy are among the crisis communications mistakes that family assistance planning prevents.
Test each draft with five questions: Is every fact sourced? Can the intended reader tell whether it applies to them? Is the next action safe and possible? Does the support route work now? Is the next update specific? If one answer is no, the example is not ready.
Sequence and time the nine messages
Order the nine by risk to the reader, not by the order in the table. Initial confirmation goes first. Protective action follows in the same statement or the next one, and it does not wait for a confirmed cause.
Family assistance and employee direction go out before any public identification of victims. Data incident, product action, and service interruption messages follow the facts you can verify. Material correction goes out once the error is known. Recovery close waits for a verified condition.
Timing is set by the risk to people, the evidence in hand, and the disclosure duties that apply. A typical planning target is a first holding statement within 30 to 60 minutes of internal confirmation, but safety outranks the clock.
Turn each function into a test case
The NIST Privacy Framework starting guide outlines a voluntary process for identifying and managing privacy risk; NIST published version 1.0 in January 2020. Use it to assign data and response owners, not as legal clearance.
The W3C information and relationships explanation says visual structure and relationships should also be programmatically available; WCAG 2.2 became a W3C recommendation in October 2023. Apply that check to the message page you publish.
Keep the evidence record beside the decision so a reviewer can reproduce the reasoning without relying on memory. Set the next review date and name the change that would trigger an earlier check.
Common questions
Can a company copy a crisis statement from another business?
No. It can study the structure, but the facts, duties, affected people, assistance, and operating promises must come from its own response.
What should a correction say?
Identify the earlier statement and error, give the verified information, explain any changed action, show the correction time, and notify exposed audiences.
Should the CEO deliver every message?
No. Use the person with the right authority, subject knowledge, credibility, availability, and responsibility for the specific update.
