Business Continuity & Risk

Crisis Communication Plan: Communicate Clearly When Facts Are Incomplete

Create a crisis communication plan covering activation, audiences, authority, facts, message templates, channels, accessibility, updates, monitoring, and correction.

FIELD GUIDECommunication guide

Built for practical decisions, implementation, and review.

The short version

Key takeaways

  • Communicate verified facts, uncertainty, action, and next update.
  • Design for audience decisions, accessibility, privacy, and channel failure.
  • Maintain one fact log and a visible correction path.

Define the crisis communication outcome

During a crisis, silence, speculation, conflicting messages, and unclear ownership can worsen the original event. A plan should help the organization communicate verified information at the speed stakeholders need while protecting people, investigations, privacy, security, and legal obligations.

Map likely scenarios and the audiences affected: employees, customers, families, suppliers, responders, authorities, insurers, owners, communities, and media. Record their practical questions, urgency, accessible channels, language needs, trusted senders, privacy constraints, and what the organization may not yet know.

Decision rule

Communicate when an audience needs information to protect people, make a decision, or understand the service impact, using verified facts, explicit uncertainty, the next action, and a promised update time.

Build the crisis communication decision model

Use four review areas to make the choice visible. Give each area an owner, evidence, and an explicit threshold rather than relying on a general impression.

Review areaQuestion and evidence
ActivationDefine triggers, incident lead, communication lead, alternates, approvals, and emergency authority.
AudiencePrioritize who needs what information, through which accessible channel, and how receipt is confirmed.
MessageSeparate known facts, unknowns, actions, customer impact, help, and next update.
ControlMaintain source logs, versioning, monitoring, correction, privacy, security, and after-action review.

Put the workflow into practice

Prepare adaptable templates, not prewritten claims. Establish a single fact log with time, source, confidence, approval, and distribution record. Give local teams instructions for routing questions and correcting old material without inventing details.

  1. Define crisis roles, alternates, contact methods, authority, and activation triggers.
  2. Map audiences, decision needs, channels, accessibility, language, and privacy constraints.
  3. Create holding, service-impact, employee, customer, correction, and resolution templates.
  4. Exercise fact collection, approval, distribution, monitoring, and update timing.
  5. Archive messages, correct errors promptly, and incorporate lessons into plans and training.

Connected decisions worth reviewing next: Small-Business Incident Response Plan: Prepare Before the Crisis; How to Build a Customer Complaint Process That Restores Trust; Business Continuity Plan Guide: Keep Critical Services Running Through Disruption.

Handle exceptions and failure paths

Working example

A service outage affects transactions, but the cause is unknown. The first message confirms the affected service and start time, tells customers what not to retry, gives a safe alternative, states that investigation is underway, and commits to a specific update. It does not speculate about a cyberattack or promise restoration before evidence exists.

Common mistakes to prevent

  • Waiting for perfect certainty while people lack necessary action.
  • Letting multiple teams publish different causes, times, or instructions.
  • Using legal or technical language that hides the practical customer impact.
  • Deleting an incorrect post without issuing a visible correction.
Control point

Do not reveal sensitive personal data, exploitable security detail, unverified blame, or information that compromises safety or an authorized investigation. Obtain qualified guidance for notification obligations and protected communications.

Measure and improve crisis communication

Choose a small set of signals that show quality, flow, risk, and outcome. Record the baseline before changing the process so improvement can be distinguished from activity.

SignalHow to use it
Time to first useful messageMeasures when stakeholders received actionable verified information.
Update reliabilityTracks whether promised updates happened on time.
Message consistencyFinds conflicting facts or instructions across channels.
Reach and accessibilityChecks whether priority audiences could receive and understand the message.
Correction and question themesShows where facts, wording, channels, or preparation failed.

Review performance after exercises and real events. Update contacts, permissions, channel access, templates, audience maps, and approval rules. Share substantiated lessons without exposing protected information or turning the review into blame.

Common questions

Frequently asked questions

Who should approve crisis communications?

Predefine authority by scenario and urgency. The incident and communication leads need usable emergency authority, with legal, safety, security, privacy, operations, and executive input according to the consequence.

What should a holding statement include?

State what happened at the level verified, who or what is affected, immediate protective or service action, where to get help, what remains under investigation, and when the next update will be provided.

References and examples

Primary sources and product examples used to ground this guide. Product links are editorial references, not endorsements.

Written and reviewed by

Smarter Business Results Editorial Team

We turn source research and operational questions into independent, practical frameworks. We do not invent product capabilities, credentials, or results.

Search the library

What decision are you working through?

Try “automation,” “electronic signatures,” “modular home,” or “product feedback.”