Data Breach Notification Steps for UK Organisations
A lost laptop, a misaddressed email or an employee’s compromised Microsoft 365 account can create an uncomfortable question very quickly: does this need a data breach notification? The first hours matter. Decisions made under pressure can protect the people affected, preserve evidence and keep your organisation in control – or create unnecessary risk, delay and confusion.
For UK businesses, schools, charities and public-sector organisations, the answer is rarely as simple as “report everything” or “keep it quiet”. A proportionate, documented response is what the UK GDPR expects. It is also what staff, parents, customers and governors expect from an organisation trusted with their information.
What counts as a personal data breach?
A personal data breach is a security incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. It is broader than a cyber attack.
That means a ransomware incident may be a breach, but so can a paper pupil record left on public transport, a payroll spreadsheet sent to the wrong recipient, or an ex-employee whose account remains active. A failed hard drive can also be relevant if it contains personal data and no usable backup is available.
The practical question is whether personal data has been affected and, if so, what may have happened to it. Do not assume that encrypted data, a recalled email or a device recovered later automatically removes the issue. Encryption, access controls, audit logs and prompt recovery may significantly reduce risk, but your team still needs to assess and record the incident.
For schools and colleges, the stakes can be particularly high. Records may include safeguarding information, special educational needs data, health details, behavioural records and contact information relating to children. For businesses, finance, HR and customer data can expose people to fraud, identity theft, distress or discrimination. Context matters as much as volume.
When is data breach notification required?
Under the UK GDPR, an organisation acting as the data controller must notify the Information Commissioner’s Office (ICO) without undue delay and, where feasible, within 72 hours of becoming aware of a personal data breach – unless the breach is unlikely to result in a risk to individuals’ rights and freedoms.
If the breach is likely to result in a high risk to those rights and freedoms, the affected individuals must also be told without undue delay. That communication should be clear, practical and honest: what happened, what data was involved, what the likely consequences are, what you have done and what they can do to protect themselves.
The 72-hour window is often misunderstood. It starts when you have a reasonable degree of certainty that a personal data breach has occurred, not when every technical detail has been established. You should not wait for a complete forensic investigation before taking action. An initial report can be updated as the facts become clearer.
Not every incident meets the reporting threshold. An email sent internally to the wrong colleague, quickly deleted without being opened, may present little or no risk. Conversely, a small data set can trigger notification if it contains sensitive health data, bank details, passwords or information about vulnerable individuals.
Where a supplier processes personal data on your behalf, it must tell you, as controller, without undue delay after becoming aware of a breach. The controller remains responsible for deciding whether to notify the ICO and affected people. This is why contracts, escalation routes and named contacts must be agreed before an incident happens.
The first day: contain, assess and keep a record
A calm response needs clear ownership. Your incident plan should identify who can make operational decisions, who leads technical containment, who speaks to insurers or legal advisers, and who approves communications. In a smaller organisation, one person may hold several of these responsibilities, but there should always be a deputy.
Start by containing the problem without destroying evidence. Disable a compromised account, revoke active sessions, isolate an affected device from the network, remove harmful sharing permissions or stop a suspicious data transfer. At the same time, preserve relevant logs, email headers, endpoint alerts and timestamps. A rushed clean-up that wipes the trail can make a proper risk assessment much harder.
Then establish the essentials. What happened? When was it detected? Which systems, files and people are involved? Is access ongoing? Was data merely exposed, or is there evidence it was copied, changed or removed? What security measures were in place, such as multi-factor authentication, encryption or conditional access policies?
Keep an incident log from the first report. Record decisions as well as technical facts, including why you judged notification was or was not required. UK GDPR requires controllers to document personal data breaches, even where they are not reported to the ICO. Good records demonstrate accountability and save valuable time if questions arise later.
How to assess the risk to people
Risk assessment should focus on the likely effect on individuals, rather than the inconvenience to the organisation. Consider the type and sensitivity of information, how easily people can be identified, the number of people affected, whether the data could be misused and whether the individuals are vulnerable.
A stolen encrypted laptop with a strong, separately held encryption key is not the same as an unprotected laptop containing staff bank details. A phishing attack that exposed email addresses may be lower risk than one that captured Microsoft 365 credentials and gave an attacker access to mailboxes, OneDrive files and payroll data.
Also consider the safeguards that worked. If endpoint security blocked a malicious process, multi-factor authentication stopped account takeover, or a recipient securely deleted an email before opening it, this may reduce the likely impact. Be precise, however. “We have antivirus” is not evidence that data was protected. Technical logs and a clear timeline are far more useful.
It is sensible to involve your data protection officer, senior leadership and specialist IT or cyber security support early. They bring different perspectives: legal obligations, organisational impact, technical evidence and the human consequences for affected individuals. For high-risk cases, external legal advice and cyber incident response support may be appropriate.
Tell people in a way they can act on
When communication with affected people is required, plain language is a security control in its own right. Avoid vague statements such as “there has been an IT issue”. Explain the incident without speculation, identify the data involved and give practical advice relevant to the risk.
If login details may have been compromised, tell people how to reset passwords and watch for suspicious sign-in prompts. If financial information is involved, explain sensible steps around bank monitoring and fraud reporting. If the incident concerns pupils or vulnerable people, consider safeguarding procedures, the audience receiving the message and whether direct communication could itself create harm.
Do not make promises you cannot keep. It is better to say that an investigation is continuing and give a realistic next update than to offer certainty before the facts support it. Prepare your front-line staff too. Reception, service desk and pastoral teams may receive the first anxious calls, and they need a simple, approved response.
A notification process is only as good as the preparation behind it
The strongest data breach notification process starts long before an incident. An organisation that does not know where its sensitive data lives will struggle to assess impact quickly. One that has no tested backups, unclear supplier responsibilities or shared administrator accounts will find containment harder than it needs to be.
Useful preparation includes maintaining an asset register, reviewing privileged access, enforcing multi-factor authentication, securing Microsoft 365, testing backups and rehearsing incident scenarios. For schools and multi-academy trusts, include central teams and individual sites in that rehearsal. For businesses, include HR, finance, operations and anyone responsible for customer communications.
A tabletop exercise can reveal gaps without disrupting the working day. Walk through a realistic scenario: a staff member approves a convincing phishing prompt, an attacker accesses a mailbox, and a supplier reports unusual activity overnight. Who receives the alert? Who can disable the account? Who decides whether the ICO threshold is met? How will you contact people if normal email is unavailable?
This preparation is not about creating paperwork for its own sake. It creates peace of mind when pressure is highest. Your staff know who to call, leaders have clear accountability, and technical teams can focus on stopping the incident rather than debating the next step.
Make the response part of everyday resilience
A breach does not have to become a reputational crisis. People understand that mistakes and sophisticated attacks happen. What they judge is whether the organisation responds quickly, treats them fairly and learns from what went wrong.
After the immediate response, turn the findings into practical improvements. Close the technical gap, review permissions, strengthen monitoring, update training or amend the supplier process that delayed escalation. Then test the changed process. A well-rehearsed data breach notification plan gives your organisation the best chance of protecting people while keeping essential work moving.




