Playbooks
Major incidents and reporting clocks
Running a major incident when regulators, patients and the public may need to know.
Why public sector major incidents are different
A major incident in a public body can also be a personal data breach, a NIS incident, a patient safety incident and a public communications event, each with its own clock and recipient. Missing one is a second incident.
The reporting clocks
| Trigger | Report to | Deadline | Applies to |
|---|---|---|---|
| Personal data breach likely to risk people's rights and freedoms | ICO | Within 72 hours of becoming aware | Everyone (UK GDPR) |
| High-risk personal data breach | The people affected | Without undue delay | Everyone |
| Significant impact on an essential service | Competent authority | Without undue delay, within 72 hours | Operators of essential services (NIS) |
| Data security and protection incident | Through the DSPT incident reporting tool | As the current DSPT guidance sets out | NHS England bodies and others using the DSPT |
| Incident affecting patient safety | Clinical incident reporting system | Local and national policy | Health bodies |
| Significant cyber incident | NCSC | As early as possible | Anyone, voluntarily or as required |
| Incident caused or affecting a supplier | The customer | As the contract says | Suppliers |
The 72 hours run from when you become aware, including weekends. Decide in advance who can declare a breach or a NIS incident out of hours, and who makes the reports.
Running the incident
- Declare and mobilise. Use clear criteria for a major incident. Name an incident manager and a communications lead.
- Run the regulatory checks at the first bridge, and again at every update:
- Is personal data affected? Call the DPO.
- Is an essential service affected? Call the NIS lead.
- Could patients or service users come to harm? Call the Clinical Safety Officer or safeguarding lead.
- Is this a cyber attack? Call the security team and consider the NCSC.
- Protect people first. In health and care, start business continuity (paper processes, diversion) early; don't wait for the technical fix.
- Preserve evidence if there's any chance of a cyber attack or criminal act.
- Communicate. Staff, service users, partners, commissioners, regulators and, if needed, the public and media. Keep a log of what was said, when and by whom.
- Recover and verify. Check data integrity and reconcile any work done on paper.
- Review. A blameless post-incident review within weeks, with actions tracked through problem management.
Keep a one-page regulatory decision log in every major incident record: each test above, the answer, who decided and when. It's your evidence that you met your duties, and it makes the review much easier.
See also personal data breach triage.