How to Prepare a Crisis Management and Crisis Communication Plan

The crisis management team and its authority, meeting rhythm, decision log, stakeholder communication matrix, prepared message templates and legal notification deadlines in a cyber incident.
Technical summary
Technology
ISO 22301, ISO 22361, KVKK, NIS2
Topic
Crisis management and stakeholder communication
Level
Intermediate
Prerequisites
  • A defined business continuity plan
  • An incident management procedure
In this article7 sections

The file servers are encrypted, production has stopped, a customer is on the phone asking “Has our data leaked?”, and at the same time three managers are giving three different answers. In a crisis, what makes things worse is often not the technical failure but this disarray: it’s unclear who decides, and the legal notification deadline quietly runs out. Once a disruption starts to threaten customer trust, legal obligations or the company’s reputation, crisis management is needed. Below we explain the crisis management team’s structure, meeting rhythm, decision log and internal/external stakeholder communication, in implementation order for top management, business continuity managers and corporate communications teams.

The difference between an incident, a disruption and a crisis

Declaring every incident a crisis wears the team out; treating no incident as a crisis delays strategic decisions. The distinction is made according to the incident’s impact and the level of decision it requires:

Status Definition Governed by Example
Event A deviation that can be managed with normal procedures Operations / IT / security team A single server failure, a suspicious sign-in on a single account
Outage A prioritized activity falling below its planned level Business continuity coordinator, BCP The ERP being unavailable for hours
Crisis A situation that threatens the organization’s objectives, reputation or existence and requires strategic decisions Crisis management team Production stopping because of ransomware, and a claim that customer data has been leaked

Write crisis declaration criteria in advance: interest from the media or social media, suspicion of a personal data breach, being unable to meet a contractual commitment to a key customer, approaching the MTPD in the BIA, a risk to life safety, an obligation to notify the authorities arising. When one of these criteria is met, the business continuity coordinator calls the crisis team to a meeting. The crisis team doesn’t replace the business continuity plan: the plan runs operations, the crisis team manages strategic decisions and external communication. For the plan’s structure, see the guide business continuity plan contents.

The crisis management team and its authority

Keep the crisis team small. A twelve-person team holds meetings; it doesn’t make decisions. The core structure usually consists of these roles:

  • Crisis leader: The general manager or a senior executive they authorize. Final decision authority rests with them.
  • Crisis coordinator: Runs meetings, keeps the decision log and tracks actions. Often the business continuity manager.
  • Operations representative: Reports on the status of affected business units and progress of the BCP.
  • IT / information security representative: Conveys the technical situation, recovery estimates and the course of the security incident in management language. Instead of “The domain controllers are affected”, they say “Nobody can sign in to the systems; estimated recovery tomorrow at noon.”
  • Legal: Assesses contractual and legal obligations, notification deadlines and the legal risk of statements.
  • Communications: Prepares messages, manages channels and monitors the media and social media.
  • Human resources: Employee safety, briefings and, where necessary, decisions on working arrangements.

Authorities are written down in advance: a spending limit outside normal approval processes, emergency contracts with suppliers, stopping production or a service, disconnecting systems from the network, calling in external experts or legal support. If it isn’t written down who decides to separate the production network from the office network at 02:00, that decision gets made in the morning. At least one deputy is defined for each role. How the team meets (a physical meeting place and a virtual meeting channel independent of corporate systems) is also written into the plan; how to reach the team is covered separately in the article call tree and emergency communication.

Crisis meeting rhythm and the decision log

In the first hours of a crisis, information changes fast; irregular meetings keep the team in the meeting room all the time and take the people who should do the work away from it. The rhythm is set like this: the first meeting is held shortly after the crisis is declared, subsequent ones are scheduled at fixed intervals (for the first day, for example, every 2–4 hours), and the interval is lengthened as the crisis calms down. Every meeting follows the same agenda:

  1. Situation summary: what do we know, what don’t we know, what’s changed since the last meeting?
  2. Impact: current assessment of customer, operational, legal and reputational impact.
  3. Status of previous actions.
  4. Decisions to be made, and the options.
  5. Communication: to whom, when, with what message?
  6. Time of the next meeting.

The decision log is the most valuable document of a crisis. In a later review, in insurance or legal proceedings and in legal notifications, the answer to “With what information, when, did we make which decision?” is here. The log is kept in a simple structure:

CRISIS DECISION LOG
No | Date-time | Situation (at the time) | Decision | Rationale / alternatives | Decided by | Action owner | Due
---+-----------+-------------------------+----------+--------------------------+------------+--------------+-----
07 | [dd.mm hh:mm] | Encryption detected on file servers, spread unknown | Cut the connection between the production network and the office network | Against the risk of spread; 4 hours of production impact accepted | Crisis leader | IT representative | Immediately

As corporate systems may be affected, the log is kept in an independent environment or on paper and updated by the crisis coordinator at every meeting. A decision log on an encrypted file server isn’t a log.

Stakeholder communication matrix

The core of the communication plan is the matrix that brings together stakeholders, the purpose of the message, the channel and the approver in a single table. The matrix is prepared before a crisis starts; during the crisis it’s only updated:

Stakeholder Purpose of the message Channel Prepared by / approved by
Employees What they should do, what they shouldn’t do, who they’ll get information from SMS, through managers, a non-corporate channel HR / crisis leader
Key customers Impact, delivery status, time of the next update Account manager’s phone, email Sales / crisis leader + legal
Suppliers Changes to orders and deliveries, connection restrictions Phone, email Purchasing / operations
Regulators Legal notification The authority’s official notification channel Legal / crisis leader
Media A short, verified statement Press statement, authorized spokesperson only Communications / crisis leader + legal
Insurance Claim notification, compliance with policy terms The channel specified in the policy Finance / legal

Internal communication happens before external communication, or at the latest at the same time. If employees learn about their company’s situation from the press or social media, trust is lost and posts employees make on their own channels become uncontrollable. A screenshot an employee drops into a WhatsApp group spreads faster than the approved press statement.

Prepared message templates and authority limits

Writing text from scratch in a crisis wastes time and creates legal risk. That’s why pre-approved templates are prepared for common scenarios (system outage, loss of site access, cyber incident, product/service delay). A template isn’t a filled-in text but a fixed structure with blanks: what happened (as far as verified), the impact on the customer/employee, what the company is doing, what’s expected of the stakeholder and when the next update will be. Templates contain no speculation, no blame and no firm commitment to a timeframe.

Authority limits for social media and the press are written clearly:

  • Only the designated spokesperson makes statements on behalf of the company; other employees refer press and social media questions to the communications department.
  • Only approved text is posted on social media accounts; whether to reply to individual comments is a crisis team decision.
  • Scheduled advertising and campaign posts are reviewed or stopped during the crisis.
  • Instead of “no comment”, a short statement with verified information and the time of the next update is given.

Communication sensitivities in a cyber incident

Cyber incidents add three extra challenges to crisis communication. First, corporate email and messaging systems may be within the attacker’s reach. If the attacker has accessed the Exchange or Microsoft 365 account, they read the crisis team’s “here is our response plan” email too. Throughout the incident, the crisis team’s communication must run through a pre-prepared channel independent of the corporate infrastructure.

Second, legal notification deadlines are short and incident-specific. For personal data breaches, Decision No. 2019/10 of Turkey’s Personal Data Protection Board requires notification to the Board without delay and within 72 hours at the latest from learning of the breach, and to the affected data subjects within the shortest reasonable time; the official KVKK website should be taken as the basis for the current procedure. For organizations operating in the EU and within NIS2 scope, Article 23 of the NIS2 Directive defines, for significant incidents, an early warning within 24 hours of becoming aware of the incident, an incident notification within 72 hours and a final report no later than one month after the incident notification; national implementing legislation may change the details. NIS2 obligations from the continuity and crisis management angle are covered in the article NIS2 business continuity requirements. Notification deadlines don’t wait for a crisis to be declared. The clock starts during incident response, and the crisis team keeps this timeline on the agenda. For the structure of incident response and notification processes, see the guide incident management procedure.

Third, statements have legal and forensic consequences. Unverified statements about the source and scope of the incident and about data leakage can be used against the company in insurance, contractual and possible legal proceedings. That’s why, in cyber incidents, external statements aren’t published without legal approval; there’s a single verification point (the crisis coordinator) between the technical investigation team’s findings and communication messages. Nobody says “no data was leaked” before the log review is finished.

To design response and notification processes for cyber incidents, see the cyber incident response plan service page; to build the crisis structure together with the business continuity plan, see the business continuity plan and BIA service page.

Frequently asked questions

Should the crisis management team and the business continuity team be the same?

In small companies, the people may overlap, but the roles must be written separately. The crisis team manages strategic decisions and external communication; business continuity teams keep activities going by carrying out the plan. If the same people try to do both jobs at once, decision speed drops.

Is a press statement mandatory during a crisis?

Not every crisis needs a press statement. If the matter has become public, a short statement with verified information and the time of the next update usually carries less risk than staying silent. The crisis team makes the decision with input from legal and communications.

How often should prepared message templates be updated?

They’re reviewed at least once a year and after every exercise. When legislation, contractual obligations, communication channels or the spokesperson change, templates are updated and reapproved.

How does the crisis team communicate when corporate email goes down?

A pre-agreed channel independent of the corporate infrastructure is used: a separate messaging group, a phone conference line or an independent meeting account. This channel is tried in exercises, and access details are also kept on paper.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles