---
title: Free Data Breach Report Form (UK GDPR) | Trust Keith
description: Free data breach report form for UK GDPR. Log what happened, assess the risk, and work out fast whether it needs reporting to the ICO within 72 hours.
---

[![642bcbad7735490755580d8d\_trust-keith-logo](https://resources.trustkeith.co/hubfs/642bcbad7735490755580d8d_trust-keith-logo.svg "642bcbad7735490755580d8d_trust-keith-logo")](https://www.trustkeith.co/)

- Product 
    - [Privacy OS](https://www.trustkeith.co/product/privacy-os)
    - [Dedicated DPO](https://www.trustkeith.co/product/dedicated-dpo)
    - [Automated Data Discovery](https://www.trustkeith.co/product/automated-data-discovery)
    - [Intelligent Workflows](https://www.trustkeith.co/product/intelligent-workflows)
    - [Staff Training](https://www.trustkeith.co/product/staff-training)
    - [Global Risks & Controls](https://www.trustkeith.co/product/global-risks-controls)
    - [Proportional Policies](https://www.trustkeith.co/product/proportional-policies)
    - [Monitoring & Reporting](https://www.trustkeith.co/product/monitoring-reporting)
- Solutions 
    - [By Industry](https://www.trustkeith.co/solutions/industry)
    - [By Team](https://www.trustkeith.co/solutions/team)
    - [By Use Case](https://www.trustkeith.co/solutions/use-case)
    - [By Privacy Regulation](https://www.trustkeith.co/solutions/regulations)
- [How it works](https://www.trustkeith.co/how-it-works)
- [Customers](https://www.trustkeith.co/customers)
- [Pricing](https://www.trustkeith.co/pricing)
- [Resources](https://resources.trustkeith.co)
- [Company](https://www.trustkeith.co/company)

[![Talk to an expert](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/24879685/859c2149-73c5-4ae5-a465-6c639d24614f.png)](https://hubspot-cta-redirect-eu1-prod.s3.amazonaws.com/cta/redirect/24879685/859c2149-73c5-4ae5-a465-6c639d24614f)

[![Trust Keith](https://resources.trustkeith.co/hs-fs/hubfs/raw_assets/public/Trustkeith_March2023/images/trust_keith.png?width=500&name=trust_keith.png "Trust Keith")](https://www.trustkeith.co/)

- Product 
    - [Privacy OS](https://www.trustkeith.co/product/privacy-os)
    - [Dedicated DPO](https://www.trustkeith.co/product/dedicated-dpo)
    - [Automated Data Discovery](https://www.trustkeith.co/product/automated-data-discovery)
    - [Intelligent Workflows](https://www.trustkeith.co/product/intelligent-workflows)
    - [Staff Training](https://www.trustkeith.co/product/staff-training)
    - [Global Risks & Controls](https://www.trustkeith.co/product/global-risks-controls)
    - [Proportional Policies](https://www.trustkeith.co/product/proportional-policies)
    - [Monitoring & Reporting](https://www.trustkeith.co/product/monitoring-reporting)
- Solutions 
    - [By Industry](https://www.trustkeith.co/solutions/industry)
    - [By Team](https://www.trustkeith.co/solutions/team)
    - [By Use Case](https://www.trustkeith.co/solutions/use-case)
    - [By Privacy Regulation](https://www.trustkeith.co/solutions/regulations)
- [How it works](https://www.trustkeith.co/how-it-works)
- [Customers](https://www.trustkeith.co/customers)
- [Pricing](https://www.trustkeith.co/pricing)
- [Resources](https://resources.trustkeith.co)
- [Company](https://www.trustkeith.co/company)

[![Talk to an expert](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/24879685/859c2149-73c5-4ae5-a465-6c639d24614f.png)](https://hubspot-cta-redirect-eu1-prod.s3.amazonaws.com/cta/redirect/24879685/859c2149-73c5-4ae5-a465-6c639d24614f)

[![Talk to an expert](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/24879685/859c2149-73c5-4ae5-a465-6c639d24614f.png)](https://hubspot-cta-redirect-eu1-prod.s3.amazonaws.com/cta/redirect/24879685/859c2149-73c5-4ae5-a465-6c639d24614f)

![Menu Icon](https://resources.trustkeith.co/hubfs/raw_assets/public/Trustkeith_March2023/images/icon-menu.svg) ![Menu close](https://resources.trustkeith.co/hubfs/raw_assets/public/Trustkeith_March2023/images/icon-x.svg)

# Free Download Data Breach Report Form

Step one: write it down. Step two: contain the panic

![trust keith data breach reporting template](https://resources.trustkeith.co/hubfs/breach-hero-2a.png)

Someone's just told you something that might be a data breach, and you're not sure what to do with that information 😬

Sitting on it while you figure out if it's "serious enough" is how the 72-hour clock runs out before anyone's even looked at it properly.

So we've built the form that gets you moving straight away:

✅ A structured log for what happened, what data's affected and how  
📋 A severity check to gauge the likely harm  
🔍 A clear ICO reporting decision, with the reasoning behind it  
✍️ Sign-off fields so it's reviewed, not just filed

Overview

## What's in this report form?

Someone in your business has just spotted something that might be a data breach: an email to the wrong person, a lost laptop, an account that looks like it's been accessed by someone it shouldn't have been. Whoever finds it rarely knows straight away whether it's reportable, or even how to describe what happened.

Most scaleups don't have a form ready for this moment, so the first conversation happens over Slack, half the details get lost, and nobody's sure who's supposed to decide what happens next.

This form skips that. It's built to be started by whoever found the issue, then handed to your DPO or data protection lead to finish, ready to use today.

Short on time? Here's what's in this guide:

[**01**What's inside the report form*→*](https://resources.trustkeith.co/free-download-data-breach-report-form#whats-inside)[**02**Why the 72-hour rule matters*→*](https://resources.trustkeith.co/free-download-data-breach-report-form#why-now)[**03**Who this form is built for*→*](https://resources.trustkeith.co/free-download-data-breach-report-form#who-its-for)[**04**How to use it*→*](https://resources.trustkeith.co/free-download-data-breach-report-form#how-to-use)[**05**Where breach reporting goes wrong*→*](https://resources.trustkeith.co/free-download-data-breach-report-form#mistakes)[**06**Frequently asked questions*→*](https://resources.trustkeith.co/free-download-data-breach-report-form#faq)

## 📄 What's inside the report form

Eight sections, split between what whoever spotted the issue can fill in straight away, and what your DPO finishes off.

*01***Reporting details**Who found it, and when, so the clock starts from a real timestamp, not a guess

*02***What happened**A plain-terms description, how it was discovered, and whether it's still ongoing

*03***What data was involved**The type of personal data, whether special category data is involved, and roughly how many people are affected

*04***How it happened**Human error, a cyber-related incident, a third-party issue, or a lost device, ticked off fast

*05***What's already been done**The containment steps taken so far, before anyone forgets what they did

*06***Likely impact**A first-pass view on whether this could cause real harm to the people affected

*07***What happens next**Your DPO's call on whether this needs reporting to the ICO, and whether affected individuals need telling, with the reasoning recorded

*08***Review and sign-off**Who reviewed it, the outcome, and a signature so it's a closed, documented decision

Data Breach Report Form01

01. Reporting details

Who found it, and when, so the clock starts from a real timestamp, not a guess

{Company Name}

trustkeith.coPage 2

## Why the 72-hour rule matters

The clock starts the moment you become aware of it, not when you've decided how serious it is.

If a breach is likely to put people at risk, UK GDPR gives you 72 hours from becoming aware of it to report it to the ICO. Weekends count. There's no pause button for "we're not sure yet" or "let's see if it's actually a problem first."

The part that catches people out isn't the reporting itself, it's the 72 hours disappearing while a form gets written from scratch, or while everyone argues over Slack about how serious it is. A breach doesn't need to be confirmed as serious before it gets logged: it's far better to open this form, work through it, and rule it out than to sit on it while the clock runs.

Investors and enterprise customers also ask about incident response during [due diligence and procurement reviews](https://resources.trustkeith.co/5-privacy-questions-investors-ask-and-how-to-answer-them?hsLang=en). "We dealt with it, but we didn't really document it" isn't the answer anyone wants to give after the fact.

## Who this form is built for

This one's for scaleups, not enterprises. It's a good fit if your business:

- Has roughly 50 to 250 employees
- Doesn't have a documented process for what happens the moment a possible breach is spotted
- Processes personal data at scale, or handles special category data (health, biometric, financial)
- Needs a DPO or data protection lead to be looped in fast, with a clear record of what was decided and why

**Not sure if something counts as reportable?**  
Trust Keith runs [free monthly Office Hours](https://resources.trustkeith.co/office-hours?hsLang=en) where you can ask a privacy expert directly.

[Register now \>\>](https://resources.trustkeith.co/office-hours?hsLang=en)

## How to use this report form

1**Open it the moment something looks off.**

You don't need to be sure it's a breach. Logging it and ruling it out costs you ten minutes; sitting on it costs you the 72 hours.

2**Fill in sections 1 to 6 yourself.**

Whoever found the issue can complete the reporting details, what happened, what data's involved, and what's been done so far, without waiting for anyone else.

3**Loop in your DPO straight away.**

Don't wait until the form's finished to tell them. Ideally, work through section 6 onward together.

4**Let your DPO make the reporting call.**

Sections 7 and 8 are where the ICO reporting decision, individual notification, and sign-off happen, with the reasoning recorded alongside the decision.

5**Keep the record.**

A completed form is also your evidence that the right process was followed, whoever asks later. Trust Keith customers get [incident response built into their platform](https://www.trustkeith.co/product/manage-breaches-and-incidents) as standard, so nothing depends on someone remembering to open a document.

## Where breach reporting goes wrong

Avoid**Waiting to be sure before logging it.**

The form exists precisely for the "might be nothing" cases. Rule it out in writing, don't just decide quietly and move on.

Avoid**Assuming only cyber incidents count.**

An email sent to the wrong person or a lost phone is a personal data breach just as much as a hack is.

Avoid**Letting the DPO find out last.**

The sooner they're looped in, the more of the 72 hours is actually usable.

Avoid**Treating "contained" as "resolved."**

Recalling an email or disabling an account stops the bleeding; it doesn't answer whether the ICO or affected individuals need telling.

Avoid**Skipping the paper trail on a "no report needed" decision.**

If you decide it isn't reportable, that reasoning needs recording just as much as a decision to report.

Avoid**Leaving affected individuals out of the conversation.**

Notifying the ICO and notifying the people affected are two separate questions. Deciding one doesn't answer the other.

## Frequently asked questions

What is a personal data breach?

Any incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. That covers human error (an email to the wrong person, a lost device) just as much as hacking or malware.

How long do you have to report a data breach?

If it's likely to put people at risk, UK GDPR gives you 72 hours from becoming aware of it to report it to the ICO. That clock includes weekends and doesn't pause while you investigate.

Does every data breach need to be reported to the ICO?

No. Reporting is generally required if the breach is likely to risk people's rights and freedoms, not simply because data was involved. A DPO or data protection lead should make that call, and the reasoning should be recorded either way.

Do we have to tell the people affected, as well as the ICO?

Only if the breach is likely to result in a high risk to them. It's a separate decision from the ICO reporting question, not an automatic extra step.

Who decides whether something gets reported?

Usually your DPO or data protection lead, which is why this form is split: whoever found the issue can complete the first sections immediately, and the reporting decision sits with whoever is responsible for that call.

Is this form really free?

Yes. Trust Keith built this so businesses have something ready to use the moment something looks wrong, rather than writing a process from scratch under pressure. It's free and yours to edit, use and share internally.

Does this replace legal advice?

No. It's a strong starting point for logging and assessing an incident, but higher-risk or complex breaches should be reviewed by a privacy expert before a final reporting decision is made.

How often should we check this process still works?

Review it whenever your systems or suppliers change, and at least annually. Trust Keith customers review theirs as part of their regular risk cycle.

Disclaimer: This form is provided free of charge for general information purposes only. It does not constitute legal advice and should not be relied upon as such.

## Everything you need to run privacy *properly* in any jurisdiction

Trust Keith holds your hand to get you (and keep you!) as compliant as you need by giving you access to a dedicated human expert and an intelligent platform.

[Find out more →](https://www.trustkeith.co/how-it-works) ![Trust Keith Platform](https://resources.trustkeith.co/hubfs/raw_assets/public/Trustkeith_March2023/images/tk-platform.png)

[![Trust Keith](https://resources.trustkeith.co/hs-fs/hubfs/raw_assets/public/Trustkeith_March2023/images/trust_keith01.png?width=268&name=trust_keith01.png "Trust Keith")](https://www.trustkeith.co/)

[![Talk to an expert](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/24879685/859c2149-73c5-4ae5-a465-6c639d24614f.png)](https://hubspot-cta-redirect-eu1-prod.s3.amazonaws.com/cta/redirect/24879685/859c2149-73c5-4ae5-a465-6c639d24614f)

- Features 
    - [Comply with data regulations](https://www.trustkeith.co/product/comply-with-regulations)
    - [Discover your data risks](https://www.trustkeith.co/product/discover-data-risks)
    - [Expert Advice](https://www.trustkeith.co/product/expert-advice)
    - [Govern your data protection programme](https://www.trustkeith.co/product/govern-data-protection)
    - [Manage breaches and incidents](https://www.trustkeith.co/product/manage-breaches-and-incidents)
    - [Train your staff](https://www.trustkeith.co/product/train-your-staff)
- Product 
    - [How it works](https://www.trustkeith.co/how-it-works)
    - [Marketplace](https://www.trustkeith.co/marketplace)
    - [Pricing](https://www.trustkeith.co/pricing)
    - [Customers](https://www.trustkeith.co/customers)
- Trust Keith 
    - [Company](https://www.trustkeith.co/company)
    - [Talk to us](https://www.trustkeith.co/talk-to-us)
    - [LinkedIn](https://www.linkedin.com/company/trustkeith/)
    - [Privacy policy](https://trustkeith.trustkeith.co/)

© Trust Keith 2026. Trust Keith Ltd is a company registered in England and Wales number 12283797.

```json
{
  "@context" : "https://schema.org",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Any incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. That covers human error (an email to the wrong person, a lost device) just as much as hacking or malware."
    },
    "name" : "What is a personal data breach?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "If it's likely to put people at risk, UK GDPR gives you 72 hours from becoming aware of it to report it to the ICO. That clock includes weekends and doesn't pause while you investigate."
    },
    "name" : "How long do you have to report a data breach?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "No. Reporting is generally required if the breach is likely to risk people's rights and freedoms, not simply because data was involved. A DPO or data protection lead should make that call, and the reasoning should be recorded either way."
    },
    "name" : "Does every data breach need to be reported to the ICO?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Only if the breach is likely to result in a high risk to them. It's a separate decision from the ICO reporting question, not an automatic extra step."
    },
    "name" : "Do we have to tell the people affected, as well as the ICO?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Usually your DPO or data protection lead, which is why this form is split: whoever found the issue can complete the first sections immediately, and the reporting decision sits with whoever is responsible for that call."
    },
    "name" : "Who decides whether something gets reported?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Yes. Trust Keith built this so businesses have something ready to use the moment something looks wrong, rather than writing a process from scratch under pressure. It's free and yours to edit, use and share internally."
    },
    "name" : "Is this form really free?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "No. It's a strong starting point for logging and assessing an incident, but higher-risk or complex breaches should be reviewed by a privacy expert before a final reporting decision is made."
    },
    "name" : "Does this replace legal advice?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Review it whenever your systems or suppliers change, and at least annually. Trust Keith customers review theirs as part of their regular risk cycle."
    },
    "name" : "How often should we check this process still works?"
  } ]
}
```