Learn how to create a crisis communication plan, from roles and escalation paths to secure fallback channels, templates, testing, and a practical checklist
A crisis can hit an organization in a matter of minutes and cause significant damage if not addressed effectively. This can include a ransomware attack, data breach, critical service outage, or any other event that disrupts operations or puts sensitive information, people, or business at risk. The true test of resilience is how well you manage its impact, minimize damage, and recover.
An effective crisis communications plan prepares for these situations before they happen. It defines responsibilities, audiences, escalation paths, approved messaging, secure communication channels, fallback systems, and testing procedures.
In this guide, we'll cover what a crisis communication plan should include, how to create one, and how to test it. We’ll also cover some best practices for communicating during a crisis and how a secure messaging platform like Wire can help you maintain secure, reliable communication throughout the incident.
Key takeaways
- A crisis communication plan defines who communicates, with which audiences, through which channels, under what authority, and with which pre-approved messages during a security incident.
- The plan should include clear activation criteria, assigned roles and backups, escalation paths, secure communication channels, message templates, and a process for testing and updating the plan.
- Testing the plan through tabletop exercises at least once a year, and reviewing it after every incident or organizational change, keeps contacts, roles, and channels current.
- Wire can support both primary and out-of-band crisis communication with always-on end-to-end encryption, enterprise identity and access controls, secure external collaboration, and access across mobile, desktop, and web.
What Is a Crisis Communication Plan?
A crisis communication plan is a documented framework that defines how an organization communicates during an incident that threatens its people, operations, finances, or reputation. It establishes:
- Who is authorized to speak for the organization in a crisis, and who would cover for that person when they are unavailable?
- Which audiences need information first (internal or external?
- Which channels will the team use for communicating, including the ones that remain available if primary systems fail?
- Under what circumstances does the plan activate, and who makes that call?
- With what authority can a message be released, and who must approve it?
- Which approved messages are ready to be sent out so nobody drafts from a blank page?
The CDC's Crisis and Emergency Risk Communication guidance describes the plan as a focused reference that keeps everyone on track and advises keeping it short enough to use in the middle of an emergency.
Why is a Crisis Communication Plan Important?
Crisis communication planning is important for most organizations because the plan provides a predefined framework to respond quickly, maintain secure communications, and protect the organization’s reputation during a security incident. It also supports clearer decision-making, protects trust, and helps teams meet regulatory and incident-response obligations by defining roles, channels, approvals, and communication procedures in advance.
In our recent survey, we found that 62% of security leaders feel prepared for NIS2 / DORA, yet 48% still share sensitive information through non-secure tools. This creates a gap in how compliant your organization really is. Read the full report to see how you can ensure you’re meeting regulatory requirements while maintaining secure communication at your company.
Crisis Communication Plan vs. Crisis Management Plan vs. Communication Policy and Protocol
In any kind of security breach, you need a few documents and protocols ready for an effective incident response plan. Here are some documents used in security plans and how they differ.
|
Document
|
Purpose
|
What it covers
|
Typical owner
|
|
Crisis communication plan
|
Coordinates the flow of information during a crisis
|
Audiences, responsibilities, channels, messaging, approvals, escalation, and updates
|
Communications lead with security and legal
|
|
Crisis management plan
|
Coordinates the broader organizational response
|
The full operational response, including risk assessment, decision authority, recovery steps, and resource allocation
|
Executive leadership or a designated crisis manager
|
|
Crisis communication policy
|
Establishes rules for crisis communication
|
Standing rules on who may speak publicly, how social media is used and which statements need approval
|
Communications, legal and HR
|
|
Crisis communication protocol
|
Defines the procedure teams follow during a security event
|
Step-by-step procedure for a specific action, such as activating the team or issuing the first notice
|
Communications lead
|
To sum it up, the crisis communication plan will usually operate as one part of the wider crisis management and business continuity framework.
For example, an incident response team may be working to isolate compromised systems while the business continuity team maintains critical operations. The crisis communication plan tells both groups how to exchange trusted information and how updates reach employees, executives, customers, and other relevant stakeholders.
How to Create a Crisis Communication Plan & What it Should Include
Some of the key components of a company crisis communication plan include establishing activation criteria, a communication team and priorities, and drafting pre-approved messages and holding statements.
Step 1: Crisis Scenarios and Activation Criteria
Start with the events the organization is most likely to face and the events that would cause the most damage. For example, an enterprise scenario list may cover cyber incidents, infrastructure outages, ransomware attacks, natural disasters, data breaches, operational disruptions, product incidents, and reputational crises.
Each scenario changes the audience, the channel, and the message, so your plan should have separate communication paths for different crises since every incident has its own characteristics.
You should also avoid treating every operational issue as the same level of crisis. For instance, a short interruption affecting one internal team may remain within the normal IT incident process, whereas a widespread outage affecting customers across several regions may activate executive leadership, legal, communications, and business continuity teams.
Consider the following to establish the activation criteria
- Number of people or locations affected
- Impact on critical services
- Expected downtime
- Exposure of sensitive information
- Risk to employee or public safety
- Legal or regulatory implications
- Media or public attention
- Impact on major customers or partners
Write these thresholds into the plan so the person assessing the initial incident has guidance for deciding when to escalate.
Also read: A practical guide to cyber resilience covering NIST, NIS2, DORA, recovery plan, secure communication, and resilience best practices for security leaders.
Step 2: Define Crisis Communication Team, Roles and Backups
Identify the people responsible for coordinating communication during an incident. When creating the plan, ask who within the organization will spearhead the response effort. Who will take charge of which tasks? Who will be the face of the company to external and internal audiences?
Once you have the answers, create a cross-functional response team that will be primarily responsible for coordinating during the emergency.
- The team must include the CEO, CISO, and heads of departments.
- It must also have representatives from departments like legal, IT, HR, and Public Relations.
- Define roles for each member and assign specific responsibilities.
- Designate a team lead to oversee the response effort and a spokesperson for conveying timely updates to key stakeholders. This ensures coordinated efforts and accountability during incidents.
You should also assign backup owners because a crisis can occur outside business hours, while employees are traveling, or when a primary decision-maker cannot be reached. Every critical role should therefore have a deputy who understands the process and has the permissions required to take over.
Step 3: Stakeholder Map and Communication Priorities
Different stakeholders need different information during a crisis. Therefore, creating a stakeholder map helps you define what each role needs first and who owns the relationship.
Here’s an example:
|
Audience
|
What they need first
|
Typical owner
|
|
Employees
|
Safety instructions, guidance on what to tell customers and where updates will appear
|
Communications lead with HR
|
|
Leadership and board
|
Verified facts, business impact, and decisions awaiting approval
|
Crisis lead
|
|
Customers
|
What is affected, what they should do, and when the next update arrives
|
Communications lead with account managers
|
|
Regulators
|
Formal notifications within statutory deadlines
|
Legal and compliance
|
|
Emergency services and authorities
|
Incident details needed to coordinate support
|
Security or facilities lead
|
|
Media
|
A single approved statement and a named contact
|
Spokesperson
|
Step 4: Establish Crisis Communication Decision Tree and Escalation Paths
Establish a clearly defined communication tree that specifies roles, channels, and how information should flow during a negative event. The typical flow includes:
- Event detected: Someone reports an anomaly through a defined route, such as the security operations team or a service desk ticket.
- Verify: The security or operations lead confirms what happened, where the information originated, and whether the source is credible.
- Classify severity: The crisis lead assigns a severity level based on the activation criteria.
- Activate the team: The crisis lead calls the team together through the fallback channel.
- Choose the audience: The communications lead decides which stakeholder groups need information first.
- Choose an approved channel: The team selects the channel that is available and trusted for that audience.
- Communicate: The spokesperson releases the approved message and records the time of release.
- Escalate or update: The team either escalates to the next severity level or issues the next scheduled update.
Just make sure to keep the decision tree simple enough for people to follow quickly. You don’t need a twenty-page flowchart with dozens of exceptions, as that would become too difficult to use during an incident.
Step 5: Select Primary and Fallback Communication Channels
Crisis communication 101 requires that you define a secure primary communication channel and a separate fallback option if normal systems become unavailable or untrusted.
Choose an enterprise communication solution that reduces the chances of a security breach in the first place while also keeping in mind that emergency coordination should not take place on consumer apps like WhatsApp. When making a choice, look for:
- End-to-end encryption across messages, calls, conferences, files, and documents.
- Strong user and device verification, with appropriate access controls.
- Protection against unauthorized participants and excessive administrative access.
- Enterprise governance for users, devices, permissions, and organizational access.
- An intuitive interface that employees can use quickly under pressure, reducing the risk of shadow IT.
- Reliable access across the devices and locations crisis teams may need to use.
Your plan should also define what happens if the primary environment is compromised.
For example, an attacker may gain access to the organization’s identity infrastructure, email, network, or collaboration platform. Continuing to discuss containment measures there could expose the response itself.
Organizations should therefore prepare a fallback communication channel in advance that operates independently of the primary environment, maintains the same high security standards, and supports required devices.
Wire Pro Tip
Wire can support both your primary crisis communication channel and out-of-band fallback channel. It provides secure team messaging with end-to-end encryption, enterprise access controls, and support across messaging, calls, conferencing, and file sharing. Learn more about secure team messaging software from Wire.
Step 6: Create Pre-approved Messages and Holding Statements
Quick responses and updates are invaluable for reassuring stakeholders, ensuring there is no miscommunication or speculation, and maintaining trust. It is a good idea to templatize certain routine messages and holding statements to be used quickly during a crisis.
- Include key messages, clearly define who sends each message, identify the target audience, and specify the channels for dissemination.
- Include directions for those seeking further information – a helpline number or a portal/channel that is updated regularly.
- All message templates must be pre-approved by legal and Public Relations teams as well as the CEO to ensure consistent messaging and compliance.
Step 7: Define Verification and Approval Process
During a crisis, teams often receive updates from multiple sources at once, including security tools, employees, vendors, customers, and external responders. Your plan should define how that information is validated and where confirmed facts are recorded.
Create a single source of truth for the response team that tracks:
- What has been confirmed
- What is still under investigation
- Who verified each update
- When the information was last reviewed
- Which stakeholder messages have already been issued
- What the next scheduled update should address
This helps prevent different teams from working with outdated or conflicting information.
Make sure the plan includes which sources are considered authoritative for different types of updates. For example, the security team may validate technical findings, while HR confirms employee-related information and legal or compliance teams confirm regulatory details.
Step 8: Feedback and Testing
Continuously review your plan to ensure it will work in practice and that all team members are well-versed in their roles and duties.
- You could conduct a full run-through of all processes and test the tools and platforms
- This helps identify gaps in processes, inefficiencies, and areas for improvement, allowing you to revise the framework accordingly
You should also update the plan after leadership changes, acquisitions, new regulations, platform changes, and every real incident.
Step 9: Conduct Post-Crisis Review
Finally, as the last step, conduct a post-crisis review to assess how communication worked and where you can improve crisis planning further. You may notice gaps in contact lists, channels, templates, or approvals. Or, your team may realize that there was a delay in response metrics such as time to activation and time to the first holding statement. It's always better to find such gaps during training than during an actual security incident.
Crisis Communication Plan Template and Checklist
Here’s a checklist you can use as the basis for a new plan or to audit your current one.
|
Section
|
What to document
|
|
Purpose and scope
|
Which incidents the plan covers, which entities and locations it applies to, and who signed it off
|
|
Activation criteria
|
Triggers, severity levels and who declares activation
|
|
Team and backups
|
Roles, names, deputies and out-of-hours contact details
|
|
Stakeholder map
|
Audiences, information needs, channels and owners
|
|
Decision tree
|
Verification, escalation and communication sequence
|
|
Channels
|
Primary communication channels, fallback channel and access instructions
|
|
Message library
|
Holding statements, audience variants and approved answers
|
|
Approval workflow
|
Who verifies, drafts, reviews and approves messages
|
|
Monitoring and testing
|
Monitoring owner, drill schedule and review triggers
|
|
Post-crisis review
|
Process for capturing lessons and updating the plan
|
Here are some specific questions to ask when reviewing your plan.
- Have you created a designated incident response team with defined roles?
- Is everyone on the team aware of their responsibilities? Have they received focused training on crisis management?
- Are hierarchies and escalation paths established?
- Are secure and fallback messaging tools in place?
- Is your messaging tool fully encrypted? Does it ensure role-based access?
- Are all team members familiar with the platform?
- Do pre-written, customizable templates exist for various scenarios? Have they been approved by the relevant authorities?
- Is there a schedule for regular testing and strategy updates?
- Does the approach comply with relevant regulations, such as NIS2?
Wire Pro Tip
Learn from real-world crisis failures in healthcare, finance, and government, and walk away with 7 actionable steps to build a stronger crisis communication strategy. Download the Protecting Crisis Communications whitepaper.
Communicating in Crisis: Best Practices
Here are some best practices to follow when executing and developing a crisis comms plan:
- Communicate verified information quickly: Create a process that allows verified facts to move quickly from responders to communication owners. If important details are still unknown, say so clearly and give stakeholders a time or channel for the next update.
- Keep internal and external messaging consistent: Employees talk to customers and external partners, so a single source of truth reduces the chance of contradictions. Share the approved message with staff at the same time as, or before, the external release.
- Use secure communication for sensitive response information: Security teams may discuss vulnerabilities, compromised accounts, affected infrastructure, customer exposure, containment actions, credentials, investigation findings, and upcoming remediation steps. Your enterprise messaging platform should provide encryption, controlled access, clear participant identity, and appropriate administrative governance for the sensitivity of the incident.
- Prepare an out-of-band channel before an incident: The EU's recent resilience guidance for critical entities recommends primary and alternative communication channels as part of crisis-management procedures. Include the fallback platform in exercises so users know how to access it from the devices they are likely to have available.
- Make the system easy enough to use under pressure: A secure tool that people find difficult to use pushes them toward unapproved consumer apps like Telegram or other shadow IT, which can further increase the security risk.
Common Crisis Communication Planning Mistakes
The biggest mistake in developing a crisis communication plan includes:
- Inadequate planning and testing: A plan that nobody has rehearsed tends to fail on details such as outdated phone numbers, missing approvals, or accounts that were never provisioned. Every team member needs to know their responsibilities, the protocols, and be able to easily access copies of the roadmap. Gaps in planning lead to delays, confusion, and miscommunication, which only make the situation worse. Test all messaging channels regularly to ensure they are reliable and secure.
- Inappropriate Collaboration Channels: The Trump administration faced a serious security lapse in March 2024 where senior cabinet members inadvertently added a journalist to a Signal chat group where they discussed military operations. The journalist remained undetected and was privy to sensitive information shared. You can read more about the SignalGate crisis here, but the premise is that consumer messaging apps like WhatsApp or Signal may be convenient; however, they have significant security gaps that malicious actors can exploit. That’s why it is crucial to deploy fully encrypted channels that also enforce role-based access controls to ensure security.
- Difficult-to-use platforms: Effective emergency management demands quick response and seamless coordination. A highly secure but difficult-to-use channel will slow teams down, and they may turn to unauthorized consumer applications to collaborate. Enterprise communication channels must be intuitive by design and allow users to use them quickly in an emergency.
- Insufficient debrief and analysis: Conduct a detailed debrief of the situation and analyze the response effort. Identify what worked well and what could be improved, and update the blueprint accordingly. Ensure that your messaging platform stores detailed logs and records for audit and regulatory submission.
How Wire Supports Secure Crisis Communication
Wire is a secure communication and collaboration platform that organizations can use as the trusted channel for coordination and communication before, during, and after a security incident. Our messenger supports both day-to-day crisis coordination and out-of-band communication when normal systems become unavailable or untrusted. Some of the key features include:
- End-to-end encryption: Wire applies always-on E2EE to messaging, calls, video conferencing, and file sharing, with no opt-in step during an emergency. Messaging Layer Security (MLS) gives the platform forward secrecy and post-compromise security, which limits what an attacker can read if a key is compromised.
- Keep crisis communication private from platform administrators: Our platform prevents infrastructure operators and administrators from accessing message content, which protects sensitive response conversations even from privileged platform roles.
- Coordinate securely across organizations: Secure federation and guest links let you bring in external counsel, forensic firms, government agencies, suppliers, and partners without giving up administrative control. Guests can join a specific conversation without a Wire account, and administrators can disable guest links for a team.
- Support crisis teams across devices and locations: Wire runs on Android, iOS, desktop, and web, making it easier for teams to access and use quickly.
Most consumer messaging apps, and even platforms like Slack or MS Teams, don’t provide this level of security and crisis communication management. See how Wire compares to other tools here.
More than 1,800 organizations already use Wire for secure communication. Here’s what one of our customers has to say about using the platform:
Because we no longer have to worry about data privacy or complex communication barriers, our team can share updates, coordinate treatment plans, and make decisions much faster.
Read the full IPW case study.
Or, get in touch with our team to see how you can deploy Wire as a secure messenger at your company.
Frequently Asked Questions