← Back to blog

Incident Response Communication Plan: What to Prepare

November 10, 2026
Incident Response Communication Plan: What to Prepare

An incident response communication plan is the part of your incident plan that says who tells whom what, through which channel, and with whose approval, when a cyber incident hits. To build one, name a communications lead with sign-off authority, list every audience, pre-write holding statements, set up backup channels that do not rely on your own systems, and agree in advance how you will meet the ICO's reporting deadline. Then rehearse it.

The NCSC points out that you cannot predict when a cyber incident will happen or what form it will take. What you can control is whether roles, protocols and templates exist before it does. This guide walks through each piece in the order you would build it, written for small businesses, schools, colleges and charities that do not have a press office.

Solusec
Strengthen Your Defences Before an Incident
Solusec provides expert-led penetration testing and practical cybersecurity advice to help identify vulnerabilities before they can be exploited.
Explore penetration testing

Key Takeaways

  • Decide who approves every message before an incident. One named communications lead with a deputy avoids contradictory statements.
  • Map your audiences (staff, board, customers, regulators, insurers, funders, media) and keep the core facts the same while tailoring tone and detail for each.
  • Pre-approve templates and holding statements, and set up backup channels that still work if email and chat are down.
  • If personal data is involved, the ICO must be told no later than 72 hours after you become aware of a notifiable breach, so build that clock into the plan.
  • Test the plan with a tabletop exercise and review it after every real incident.

Table of Contents

What an incident communication plan actually covers

The plan is not a press release template. It is a short, usable document that sits inside your wider incident response plan and answers four questions: who speaks, who is told, what is said and when, and how you reach people if your normal tools are down.

Four essential incident communication plan questions

The Emergency Planning Society's crisis communications checklist says a plan needs to be written so it can be picked up and used quickly and easily in an emergency. For a small organisation, that usually means two to six pages, not a forty-page policy nobody has opened since it was approved. Someone who has never seen it should be able to follow it at 2am with a ransomware note on screen.

It also needs to treat communication as sustained work. A cyber incident is rarely a single announcement. Computer Weekly makes the practical point that handling a story means scheduling updates, issuing authorised statements and answering enquiries over days or weeks. Your plan should give someone the job of doing that, and a rota so the same person is not awake for 72 hours.

Step 1: Assign roles and sign-off

Most messy incident communication comes from unclear authority: the IT manager tells staff one thing, the director tells a customer another, and a member of staff posts something on social media. Fix that first.

A workable minimum is three roles:

  • Incident lead: runs the technical and operational response and feeds facts to the communications lead.
  • Communications lead: drafts and approves every message, internal and external. The NCSC-NZ framework describes this person as the final sign-off for communication, even where they report into a wider leadership group.
  • Spokesperson: the only person who speaks to media, customers or the public. The NCSC advises identifying trained official spokespeople in advance.

Joint guidance from CISA and partner agencies recommends exactly this kind of clarity: a designated incident lead, communications lead and spokesperson, with predefined approval paths and escalation criteria. It is US-led guidance, but the principle carries over to any organisation.

In a ten-person firm one person may hold two roles. That is fine, provided the plan names a deputy for each and the deputy has the contact details and access they need. FIRST says roles should be settled well ahead of time and listed in the overall incident response plan, and that the communications lead needs visibility of all communications between internal teams and external stakeholders. That visibility is what stops people on the same incident giving different versions of events.

For a deeper look at who should sit in each seat, and the point at which an SME should bring in outside help, see our guide to NCSC-aligned incident response roles.

A simple approval path

Write the path as a sentence, not a flowchart. For example: the incident lead confirms the facts, the communications lead drafts, one named director approves anything that mentions customer data, legal exposure or regulators, and the spokesperson sends. Add what happens if the approver cannot be reached within an hour. Without that fallback, a missed phone call delays every update.

Step 2: Map your audiences

The NCSC advises defining procedures for notifying employees, board members and external parties such as customers and stakeholders, and tailoring each message to the concerns of that group while keeping the core points consistent. Build a one-page table to do this. Here is a starting point for a small organisation:

AudienceWhat they need firstTypical ownerChannel
StaffWhat to do and not do (for example, do not switch machines back on, do not discuss on personal social media)Communications leadOut-of-band group message, phone tree
Board or trusteesScale, risk, decisions neededIncident lead via directorPhone, then written summary
Customers, parents or service usersWhat happened, what it means for them, what to doSpokespersonEmail, website notice, phone
ICO and other regulatorsNotification of a qualifying breachData protection leadICO online reporting
InsurerNotice of the incident, in line with policy termsFinance director or ownerPhone, policy hotline
Funders, local authority, trustImpact on service and dataDirector or chief executiveEmail, call
MediaA short, factual statementSpokesperson onlyWritten statement
Suppliers and MSPWhat access or services are affectedIncident leadPhone, agreed secure channel

For schools and universities, the UCISA cyber incident response toolkit notes that post-incident work includes reports to external partners such as funders and liaison with insurers on any claims process. Charities with grant conditions should check the same: some funders expect to hear about a serious incident quickly.

Keep the facts identical across audiences. Staff, customers and journalists will compare notes. Change the order and the level of detail, never the substance.

Step 3: Prepare templates and holding statements in advance

The NCSC recommends drafting pre-approved templates for media requests, internal updates and customer notifications. The UK Government Communications crisis planning guide similarly suggests having templates ready for things like media monitoring and Q&As.

For a small organisation, the minimum set is:

  1. Internal alert: two or three sentences telling staff there is an incident, what to do now, and who to ask.
  2. Holding statement for media and public: confirms you are aware of an issue, that you are investigating with specialists, that you will update when you can, and gives one contact.
  3. Customer or parent notification: plain wording on what happened, what data may be involved, what you are doing and what the recipient should do.
  4. Regulator notification notes: the facts the ICO report asks for, gathered in a form you can fill in quickly.
  5. Update template: a standing format (what we know, what we do not know yet, what we are doing, when you will hear from us next).

What a good holding statement does

A holding statement buys time without lying. It acknowledges the problem, avoids speculating about cause or attacker, and commits to a next update. The NCSC advises giving the clear information that stakeholders, customers and the media need while avoiding disclosures that increase risk. In practice that means no technical details about the vulnerability, no names of affected individuals and no guess at when systems will be back.

Write these templates with blanks, have the communications lead and a director approve them now, and store printed copies and an offline copy. Approval in calm conditions is the point: during an incident you only fill in the gaps.

Step 4: Plan for channels that still work

The NCSC advises understanding which channels you can use to reach stakeholders, including mailing lists, internal newsletters, social media channels and journalist contacts, and establishing alternative ways to stay in touch if usual channels are unavailable. This is where many small organisations are caught out: ransomware that takes down email, file shares and a chat tool takes your communications with it.

The CISA-led guidance recommends establishing and regularly testing backup methods, such as backup email and messaging, SMS and phone trees, and conference bridges, for when primary systems are degraded or compromised. A realistic SME setup:

  • A printed or offline contact sheet for staff, directors, your IT provider, insurer and solicitor, with personal mobile numbers.
  • A group messaging app on personal phones, set up in advance and agreed as the fallback.
  • A pre-agreed phone tree so each manager calls three or four people.
  • A way to post a notice on your website or social media that does not depend on the compromised network. Check who holds those logins.
  • A separate email account or mailing tool for customer notifications, ideally not tied to the same tenant that has been compromised.

Test the fallback at least once a year. A phone tree with outdated numbers is worse than none because it creates false confidence.

Step 5: Build the regulatory clock into the plan

If an incident involves personal data, the communications plan is also a legal compliance plan. The ICO says a notifiable personal data breach must be reported to it without undue delay and no later than 72 hours after you become aware of it. If the breach is likely to result in a high risk to people's rights and freedoms, you must also tell the affected individuals directly and without undue delay.

Three things to write into the plan:

  • Who decides whether it is notifiable. Usually your data protection lead or director, with advice from your IT provider or incident responder. Name them, and name a deputy.
  • When the clock starts. The ICO measures from when you become aware, so the plan should say who records the time of awareness and where it is logged.
  • Who tells individuals, and which template and channel they use. The notification should describe in plain language what happened and what people can do to protect themselves.

Regulator reporting under time pressure is easier when parts of the process are automated or at least pre-structured. Our piece on meeting the ICO 72-hour reporting window covers how far automation can help at different organisation sizes.

The ICO is not the only body you may need to contact. Depending on your sector, you may have duties to a funder, a local authority, an awarding body or an insurer with notification conditions in your policy. List them in the audience table above and note any deadlines you know about from your contracts and policy documents.

Step 6: Communicate as the incident develops

The NCSC describes the start of an incident as a shockwave: the organisation rushes to find technical causes and deal with operational impact, and communication can be squeezed. A plan that is already written lets you speak early without improvising.

In the first hours:

  1. Confirm the facts with the incident lead and record the time you became aware.
  2. Send the internal alert so staff stop doing things that make matters worse and stop talking to outsiders.
  3. Decide which external audiences need to know now. Customers who may be at risk come before journalists.
  4. Issue the holding statement only if you need one, for example if the disruption is visible to customers or the press has called.
  5. Set the time of your next update and keep to it, even if the update is that nothing has changed.

In the following days and weeks, the NCSC advises regular updates on progress with milestones and expected timelines, updates on the assessment of impact (including how far data may be compromised) and the status of recovery and remediation, and open channels with the media in a timely and transparent way to counter misinformation. It also notes that recovery can take anywhere from days to months, so build a sustainable update rhythm: a daily staff note, a customer update every few days, a fuller summary at each milestone.

Phishing and account compromise

Not every incident is a headline ransomware attack. A compromised mailbox that sends fraudulent invoices to your customers needs a fast, specific message to those customers. If that is a likely scenario for you, prepare a variant template for it. Our practical UK guide to phishing incident response covers the response steps that sit behind that message.

Step 7: Test it, then review it

A plan that has never been run is a hypothesis. The NCSC advises regular tabletop exercises and simulations, and reviewing and updating the strategy to reflect lessons learned and changes in threats or regulation. After a real incident it advises reviewing the communications response and speaking to stakeholders, internal and external, about how messages were received and what could be improved.

A good first exercise takes 90 minutes. Give the group a scenario (for example, your finance mailbox is compromised and a supplier has been paid into the wrong account), then feed in complications: a journalist calls, a customer posts on social media, the ICO question comes up, email goes down. Watch for:

  • Who assumed someone else was telling the board?
  • How long did it take to find the backup contact list?
  • Did the draft statement say anything you could not stand behind?
  • Did two people try to approve at once, or nobody?

We publish a copyable tabletop agenda with sample injects you can adapt. Record the gaps, assign owners and dates, and update the plan within a fortnight while the lessons are fresh.

Where outside help fits

Most small organisations cannot staff an incident around the clock, and few have forensic skills in-house. That is a communications issue as well as a technical one: you cannot tell customers what was taken until someone has worked it out. Having an incident response provider lined up before you need one gives your communications lead a reliable source of facts.

At Solusec, our incident response service is delivered by CREST-accredited professionals, and you speak directly to the people doing the work rather than a sales team. Plain-English findings are the aim, because your communications lead needs facts they can repeat accurately to staff, parents, customers or a regulator. We do not publish a price for incident response, so contact us to discuss your situation.

If you would rather reduce the chance of ever using the plan, our penetration testing is listed from £2,500 for a CMS website test and £3,000 for an external IP test. Cyber Essentials certification is £320 to £600, depending on organisation size.

Solusec

A one-page checklist you can copy

Use this as the skeleton of your own document:

  1. Named incident lead, communications lead and spokesperson, each with a deputy and mobile number.
  2. Approval path written in one sentence, with a fallback if the approver is unavailable.
  3. Audience table with owner and channel for each group.
  4. Pre-approved templates: internal alert, holding statement, customer notice, update format.
  5. Backup channels and an offline contact sheet with insurer, solicitor, IT provider and incident responder.
  6. ICO decision-maker, awareness-time log and 72-hour reminder.
  7. Update rhythm for the first week and a named rota.
  8. Exercise date and review date in the diary.

FAQ

What is the difference between an incident response plan and an incident communication plan?

The incident response plan covers how you detect, contain, investigate and recover from an incident. The communication plan is a part of it that covers who is told what, by whom and when. They should be written together so the technical lead and communications lead work from the same facts.

Who should approve messages during a cyber incident?

One named communications lead should be the final sign-off for all internal and external messages, with a deputy for when they are unavailable. Official guidance from NCSC-NZ and CISA both support clear approval paths. Messages touching on personal data or legal exposure usually also need a director's agreement.

Do we have to tell customers about a cyber incident?

Not every incident requires notification. Under the ICO's guidance, you must inform affected individuals directly and without undue delay if a personal data breach is likely to result in a high risk to them. Contracts and sector rules may add duties, so list those in your plan.

How often should we test the plan?

The NCSC advises regular tabletop exercises and a review after every real incident. For a small organisation, once a year plus after any significant change in systems, suppliers or staff is a sensible rhythm.

What should a holding statement say?

It should confirm that you are aware of an issue and are investigating with specialists, avoid speculation about cause or impact, and say when you will next update. Include a single contact point. Pre-approve the wording so it can go out quickly.

Sources

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.