Back to Articles
Insights

Managing breach communications for each audience

Published:
managing communications during a data breach
Managing breach communications for each audience

A breach announcement is only one part of the response. Managing communications during a data breach means giving each audience clear, consistent information that reflects what it needs to know and do.

Customers need to understand what may have happened to their information and what actions they can take. Employees need timely internal updates and guidance on handling questions. Disclosure duties depend on the organisation, the incident and the relevant jurisdiction. According to the U.S. Securities and Exchange Commission, US public companies generally must file Form 8-K Item 1.05 within four business days after determining that a cybersecurity incident is material.

This article explains how to tailor messages for customers, employees, investors, regulators and the media without letting statements conflict. It covers coordinating facts and approvals, handling disclosure requirements and preparing a communications plan before an incident. You’ll also learn what to share while an investigation is under way, how to keep updates useful as facts change, and when specialist communications support can help.

Key Takeaways

  • Tailor each message to the audience, making clear what is known, what is being investigated and what people can do next.
  • Coordinate incident responders, communications, legal and leadership teams before releasing external statements.
  • Pause scheduled social media content until the organisation has an agreed communications plan and updates ready.
  • Map disclosure duties to the people affected and the jurisdictions involved; requirements and deadlines can differ.
  • Prepare audience plans and adaptable messages before an incident, then update them as verified facts change.

Table of Contents

How long does a public company have to disclose a data breach?

For a US public company, the disclosure clock depends on when it determines that a cybersecurity incident is material. The U.S. Securities and Exchange Commission generally requires a Form 8-K Item 1.05 filing within four business days of that determination. This is not a universal deadline for every breach or every audience; other notifications follow their own requirements.

During the first four hours, incident responders and communications staff need a shared process for exchanging updates. The response process includes an incident log, a named decision owner and security, legal and communications leads working together. Managing communications during a data breach requires a clear route between IT responders and communications, so confirmed facts remain separate from working theories as attacks are investigated.

Professional communications support after a breach is discovered helps turn incident updates into clear, consistent messages. It gathers confirmed details from technical teams, prepares holding language and aligns approvals, while the investigation continues. This coordination can include global corporate communications across teams and audiences.

Information gathering takes place alongside the technical response, not ahead of it. Responders establish which systems or data may be affected, whether activity is ongoing and which findings remain under investigation. Communications teams record what is confirmed, what is being assessed and when the next update is due. Claims about cause, scope or impact are avoided until the investigation supports them.

Scheduled social media content is reviewed before any public breach announcement. Unrelated posts and queued campaigns are paused until the communications plan is agreed; a routine celebratory post can conflict with an incident update. Social media and customer support teams receive approved wording, escalation routes and a clear way to pass new questions to response leads.

As the incident develops, confirmed information is shared as soon as it can be disclosed without unwarranted delay. Employees are told what is known, what remains under review and what response steps are under way. If investigators cannot confirm whether an attack is ongoing, statements remain cautious and factual rather than offering assurances that later evidence may contradict.

A practical coordination rhythm keeps the technical investigation and public messaging aligned: responders provide timed updates, communications staff log decisions, and the decision owner clears each statement. For example, a new finding about affected customer data should prompt a review of customer messages, staff guidance and scheduled social content before publication. The aim is accuracy across every channel, even as facts change.

How poor communication affects breach costs, recovery time, and reputation

Poor communication adds work during an already demanding response. Conflicting messages can lead to repeat enquiries, corrections and escalations, drawing staff away from recovery tasks. Recovery from a cyber incident can take from a few days to several months. Clear, consistent updates help affected people understand what has happened and where to seek support.

Reputation can suffer when an organisation’s actions seem out of step with its messages. During Equifax’s breach announcement, a customer-service employee tweeted “Happy Friday!” The company’s free credit-monitoring offer also required a credit card for activation and included a forced arbitration clause in the fine print, contributing to public outrage. Every customer-facing detail can shape how a response is received.

A breach can have a substantial financial impact, but communication alone does not determine the total cost. Clear messages cannot reverse the incident; they can help reduce avoidable confusion about the response, available support and actions people should take.

Empathy starts with acknowledging the disruption without making unsupported promises. A message to affected customers should explain what information may be at risk, what the organisation is doing and how people can protect themselves. For affected accounts, practical advice may include changing passwords. Communication about security or impact is best kept specific while the investigation continues.

Different groups need different information. Customers need direct, relevant guidance; employees need talking points and a way to escalate difficult questions. Business partners may need to know how the incident affects shared operations. Communication practice keeps the core facts consistent while tailoring the detail and next steps to each audience.

Professional communications support helps customer-facing teams respond consistently by preparing FAQs, phone scripts and escalation protocols. It can also identify recurring concerns and align answers with the organisation’s latest confirmed information. This reduces the risk of customers receiving conflicting explanations through different channels.

Practical support should make the next action easy to find. A customer notice can state which data may be affected, how to change passwords on relevant accounts, and where to raise a concern. A clear update schedule gives people a reason to return for new information. Specialist crisis communications planning can coordinate these messages with customer-service scripts and internal guidance.

What regulatory disclosures are required?

Disclosure duties depend on where affected people live, what data was involved and which rules apply. With legal counsel, the process maps each audience and deadline, then aligns public statements with formal notices. One breach can require separate communications for customers, regulators and business partners, each with relevant information.

In the United States, federal notification requirements depend on the sector and data involved. A breach involving sensitive personal data held by a healthcare organisation may trigger HIPAA notification duties; FTC and state-level compliance reporting may also apply. Businesses should assess relevant federal rules alongside state law and any applicable PCI DSS requirements.

For personal data of people in the EU, organisations must notify the supervisory authority within 72 hours of becoming aware of a breach under GDPR, according to the European Union. The notice should distinguish confirmed facts from details still under investigation. The communications record should capture when the organisation became aware and who approved the submission.

Businesses holding personal information of California residents must notify residents within 30 calendar days of discovering a breach under California Civil Code 1798.82, as amended by SB 446, according to the California Legislature. If a breach affects more than 500 California residents, the business must send the Attorney General a sample notice within 15 days of notifying residents.

Technical details are translated without distorting them. For example, a notice can explain that an unauthorised person accessed an account system, then state which information may be involved and what action people can take. A regulator’s submission may require more operational detail, while customers need a clear explanation without unexplained security terminology.

A holding statement can acknowledge the situation and explain that an investigation is under way, without guessing about cause or scope. The process sets a time for the next update, then shares verified changes with stakeholders, even when the investigation has produced no major new finding.

Legal review helps keep statements consistent with applicable notification rules. The communications team can maintain a single record of approved facts, audience-specific messages and submission dates. For example, if investigators identify another affected data type, the team can update customer wording and regulatory submissions without creating conflicts with earlier statements.

Coordinating facts and approval before external statements

A cross-functional crisis team gives each decision a clear owner. The team includes senior leadership, legal, communications, HR, IT and information security, with engineers or business leads added as needed. During a breach, engineers can explain affected systems; communications staff can turn their findings into language customers and employees understand. Legal review helps keep public statements aligned with approved facts.

Communications professionals coordinate internal notifications by agreeing what employees need to know, when they will hear it and where questions should go. Managers need consistent talking points and a route for escalating staff concerns. An internal notice should explain what is known, what remains under investigation and what employees should do if customers ask for information.

IT and engineering teams should provide updates through an agreed channel, rather than scattered messages that are difficult to verify. A shared incident record can distinguish confirmed findings, open questions and decisions awaiting approval. For example, if engineers identify another affected system, the communications lead can assess whether existing employee and customer messages need revision.

Before releasing an external statement, the response process assigns named reviewers for technical accuracy, legal approval and communications clarity. The decision owner resolves conflicting edits and records the approved version. A holding statement drafted during the first hours of a response should use confirmed facts only; later statements can add verified details without contradicting it.

The timing of employee notifications may need to be coordinated with law enforcement to avoid interfering with an investigation. The Federal Trade Commission recommends that organisations may coordinate timing for this reason. The crisis team records the decision and its rationale, then prepares an internal message for release once timing is agreed.

Social media needs the same approval discipline as a press statement. Scheduled posts are paused, incoming questions are routed to the response team and only authorised staff publish incident updates. A routine post queued before the breach could seem out of touch beside a customer notice, so the social media lead reviews scheduled content before anything goes live.

A single approved source of facts helps teams keep messages consistent across email, customer support and media channels. Communications staff should explain technical terms plainly, while engineers confirm the meaning remains accurate. If the known scope changes, the team can update employees and external audiences using the same reviewed facts.

Creating cyberattack and data-breach communication plans

A useful plan establishes clear roles before an incident, not just a statement template. Plan development maps employees, customers, regulators, investors, suppliers and media, then records each group’s information needs. This stakeholder map shows who approves messages, which channels remain available and what to communicate when usual systems fail.

The plan should name a decision owner and set an information route between IT, security, legal and communications. It should include adaptable templates for different scenarios, such as ransomware or unauthorised access. A prepared plan for managing communications during a data breach helps teams explain what happened without guessing at cause or impact.

Time-bound outputs make the response practical. During the first 4 hours, the team opens an incident log, names the decision owner and brings together key leads. Between hours 4 and 8, it drafts a holding statement based only on confirmed facts and prepares an employee notice. These steps create a working record and an initial message.

From hours 8 to 16, communications staff work with counsel to identify affected audiences and prepare notice drafts. Between hours 16 and 24, the plan calls for a dated incident page, briefings for customer support and executives, and a stated time for the next update. By the end of the first 24 hours, the team should have four outputs: an incident log, holding statement, audience list and live incident page.

Professional support with the plan can include audience-specific messages, FAQs, phone scripts and manager talking points. It can also define approval routes and escalation protocols, so customer questions reach the right decision-maker. Financial stakeholders may need an operational update, while affected people need clear information about exposed data and protective steps.

A provider can test the plan through tabletop exercises and simulations. For example, a scenario can introduce a new finding about affected customer data, then test how quickly teams update notices across email, support and social channels. The exercise can reveal where approvals stall, facts conflict or alternative channels are needed.

Testing should also account for employee needs during an attack. An all-hands briefing can explain the situation and what staff can share, while regular updates keep employees informed even when little has changed. The plan should explain how staff handle media enquiries and provide a route for escalating customer concerns. Exercise findings inform reviews of the templates.

BCM Public Relations: Crisis Communications

BCM Public Relations can help organisations prepare for a data breach or manage communications during an active incident. Its Crisis Communications service focuses on clear messaging for affected audiences and consistent updates as verified facts change. For manufacturing, engineering and technology businesses, that means explaining technical issues in language customers, employees and media can understand.

During the early response, communications support can help organise information from incident responders, legal teams and senior leaders. A clear record of confirmed facts, unresolved questions and approval responsibilities gives each statement a sound basis. Communications planning also helps teams decide which audiences need updates, what each group needs to know and how further information will be shared.

Strategic PR Planning can establish roles and communication routes before a breach happens. The plan can cover internal updates, customer messages, media enquiries and review of scheduled social content. It can also identify who approves statements and how teams will handle new information. This preparation gives employees and spokespeople a consistent reference during a fast-moving incident.

For an organisation facing press questions, Media Relations helps manage communication with journalists. A prepared spokesperson needs a clear account of what happened, what remains under investigation and what the organisation is doing next. Agreed messages help prevent technical uncertainty from becoming speculation, while regular updates give reporters a reliable point of reference.

Technical Copywriting can make complex incident information easier to follow without changing its meaning. This may include customer notices, holding statements, FAQs or updates for a live incident page. Each format has a different purpose: a customer notice should explain relevant risks and practical actions, while an executive update may focus on response progress and business impact.

Bring communications support in when the response team needs to align technical facts with audience needs, or before an incident to prepare a plan. The work depends on the nature of the incident, available information, affected groups and the organisation’s approval process. Legal and technical leads remain responsible for their assessments; communications support helps express agreed information clearly and consistently.

To discuss communications support for a data breach, contact BCM Public Relations.

Frequently Asked Questions

How can a communications team speak to each audience during a data breach?

A distribution plan records who receives each message, through which channel and at what point in the response. A controlled master version helps prevent staff from circulating outdated drafts. For example, a supplier update can focus on operational effects, while an investor briefing addresses business implications. The record can include who approved each version and its release time for later reference.

What belongs in a holding statement?

Alongside a concise account of the incident and response, a holding statement should identify an authorised spokesperson or enquiry route. This gives journalists and other stakeholders a clear destination for follow-up questions. A dated copy of every approved version can be retained, including the channels where it appeared. If the wording changes, a record of the revision helps staff distinguish current text from earlier statements.

What do past breaches teach?

TalkTalk received criticism in 2015 after publishing apparently contradictory statements about customer data theft. The practical lesson is to make corrections visible and explain which earlier detail has changed. A review of a past incident should examine the sequence of statements, approval records and unanswered questions, rather than judging one quote alone. That record can inform future message approvals and spokesperson preparation.

What information needs to be communicated, and when?

A dated communications record can show when each audience was informed, which version it received and which facts supported that wording. If a later finding changes an earlier account, a correction can be issued through the same channel where possible. The previous version can be preserved in the internal record. This gives the response team a clear history of decisions and helps explain how its account changed over time.

What communications support should be in place during the first 24 hours?

A decision log can record who approved each message, the evidence available at the time and any unresolved issues. This makes later reviews more useful than relying on email threads or memory. A communications lead can also maintain a single current set of approved materials for spokespeople and customer-facing staff, with a clear process for replacing outdated versions when new facts emerge.

What support should affected people get?

People can be given a private way to raise individual concerns, rather than being asked to post personal details on public channels. Customer-support staff should have a route for escalating account-specific or sensitive cases to the appropriate internal team. Recurring questions can be recorded without exposing personal information in general updates. This helps the organisation identify gaps in its explanations and improve later communications.

Share this article

Let's talk about
your PR future.

Get in touch