Accountio / Templates / UK GDPR / Data breach log

Data breach log template for accountancy practices

Record every personal data breach in one place, from a misdirected email to a stolen laptop, with the ICO deadline worked out from the moment you found out. This data breach log template is one Excel workbook, with logs for subject access requests and complaints alongside.

UK practices
$15
In the pack
UK GDPR pack for practices
Files
10, Word and Excel
Buy the pack · $15
Global library · 101 packs

Get this pack and 100 more for $129

UK GDPR for practices · this packAML complianceCharity accountsEstate administrationMTD for Income TaxP11D and payrollingUK SRS readinessCarbon reduction planCIS+ 92 more
$129$1,42191% off

You save $1,292 on buying them one by one

Buy the global library · $129

What the log looks like

Data breach log template
What the log recordsColumn in the Breaches sheet
A reference for each breach
✓
ReferenceRoom for 50 breaches
When you found out
✓
Date and time we became awareThe point the 72 hours run from
What happened
✓
What happenedIn your own words
Whose data was involved
✓
Whose data and what dataClients, staff or others, and the type of information
How serious it is
✓
Likely risk to peopleUnlikely, Risk or High risk, picked from a list
The ICO deadline
✓
Report to ICO byWorked out as 72 hours after you became aware
Whether you reported it
✓
Reported to ICO?Yes, or No: unlikely risk. Turns red if the risk is Risk or High risk and the answer isn't Yes
Your ICO reference
✓
Date reported and ICO referenceFor any follow-up with the regulator
Telling the people affected
✓
People told? (needed if high risk)Yes, No or Not needed. Turns red for a high risk breach until it says Yes
What you did about it
✓
Action taken to contain and prevent itThe fix, and what stops it happening again
When the matter closed
✓
Closed onThe date the breach was dealt with
The deadlines explained
✓
How to useThe breach, subject access and complaint time limits in plain English

When you need it

The UK GDPR requires you to keep a record of every personal data breach, with the facts, its effects and the action you took, whether or not you report it to the ICO. Add a row as soon as you know about a breach, for example:

  • An email or letter goes to the wrong client
  • A laptop, phone or box of papers is lost or stolen
  • A staff email account is hacked
  • Someone opens client records they had no reason to see
  • A supplier tells you about a breach on their system that affects your data

How to use the data breach log template

  1. Start a row straight away. Enter the date and time you became aware. The grey Report to ICO by cell fills in.
  2. Describe the breach. What happened, whose data and what type of data.
  3. Judge the risk. Pick Unlikely, Risk or High risk. Red cells show what still needs doing.
  4. Record your decisions. Whether you reported it, your ICO reference, and whether you told the people affected.
  5. Close it. Write down the action you took and the date the matter closed.
  6. Keep it private. Store the workbook where only the people who handle breaches can open it.

Questions

What is a data breach log?

A record of every personal data breach your firm has had, with the facts, the effects and the action taken. Article 33(5) of the UK GDPR requires it, and the record must let the Information Commission check that you have complied.

Do you have to log breaches you don't report to the ICO?

Yes. The duty to record covers every breach. A breach that is unlikely to put anyone at risk does not have to be reported, but it still goes in the log, and the log shows the reason you didn't report it.

What should a data breach log include?

At least the facts of the breach, its effects and the action you took. This log also records when you became aware, whose data was involved, the risk to people, the ICO deadline, whether you reported it, whether you told the people affected and when the matter closed.

How long should you keep a data breach log?

The retention schedule in the same pack keeps data protection breach, subject access and complaints logs for six years from the date the matter closed, as evidence of compliance.

What would an empty data breach log indicate?

Either your firm has had no breaches, or staff are not reporting them. Emails sent to the wrong client and lost phones count as breaches, so make sure everyone knows to report every one, however small.

Also in the UK GDPR pack for practices

See the whole pack →

Who it's for

Accountancy practices that want one record of every breach and the deadlines that go with it.

Last checked

Checked against Articles 33 and 34 of the UK GDPR on legislation.gov.uk in November 2026.