United Kingdom version. Written for UK organisations: UK GDPR and the Data Protection Act 2018, the ICO data protection fee, the 72-hour breach notification, the one-month subject access deadline and UK transfer rules. US version

Data Protection Readiness Checklist (UK)

Know your lawful basis, pay the ICO data protection fee, answer a subject access request within a month and report a notifiable breach in 72 hours.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Data Protection Readiness Checklist?

UK data protection law is UK GDPR plus the Data Protection Act 2018, supervised by the Information Commissioner’s Office. The practical starting point is not a policy document, it is knowing what personal data you hold, why you hold it, and which lawful basis you are relying on. Organisations that cannot answer those three questions cannot answer anything else that follows.

Two deadlines make this urgent rather than theoretical. A notifiable personal data breach must be reported to the ICO within 72 hours of becoming aware of it, and a subject access request must normally be answered within one month. Both clocks start without warning, usually on a day when the person who understands the systems is on leave.

Most UK organisations that process personal data also have to pay an annual data protection fee to the ICO unless exempt, which is a registration-style obligation people routinely miss because nothing chases them until it does.

  • Written to UK GDPR and the Data Protection Act 2018, not the EU-only position
  • Includes the ICO data protection fee most organisations owe
  • Built around the 72-hour breach and one-month SAR clocks
  • Covers UK transfer mechanisms and processor contract terms
  • Tick, reword and delete items, then export as a Google Form, PDF, CSV or Markdown
Read the guide: Why Checklists Work, and How to Use One Properly

Updated

How to use the Data Protection Readiness Checklist

  1. Map what personal data you hold, where it lives, why, and who it is shared with.
  2. Record a lawful basis per purpose, and a separate condition for any special category data.
  3. Check whether you owe the ICO data protection fee, and register if you do.
  4. Write the breach procedure against the 72-hour clock, and the SAR procedure against the one-month clock, then rehearse both.
  5. Put processor contracts and transfer mechanisms in place, and set retention periods with a deletion job that runs.

Worked examples

Marketing list built on consent

Input

Lawful basis items

Output

Basis reviewed; legitimate interests documented where it fits

Consent brings a right to withdraw and a management burden. Where another basis genuinely applies, choosing consent creates work without adding protection.

Laptop stolen on a Friday evening

Input

Breach items

Output

Assessed, logged, and reported inside 72 hours

The clock runs from becoming aware, not from confirming the detail, and weekends do not pause it. Every breach is recorded internally even when it is not reportable.

Ex-employee emails asking for "everything you hold on me"

Input

Subject access items

Output

Recognised as a SAR; one-month clock started

A request need not be written formally or use the right words, and can arrive anywhere in the organisation, which is why staff recognition is the control that actually matters.

Using a US analytics supplier

Input

Transfer items

Output

UK transfer mechanism in place and assessed

Transfers out of the UK need their own mechanism, and the UK makes its own adequacy decisions after Brexit, so an EU-only assessment does not cover you.

Background and insight

A lawful basis is required for every processing purpose, and consent is only one of six. Choosing consent where legitimate interests or contract actually applies creates an unnecessary right to withdraw and an unnecessary consent-management problem. Where you do rely on consent it must be freely given, specific, informed and as easy to withdraw as to give, which rules out pre-ticked boxes and cookie walls that only offer accept.

Special category data, including health, biometric and other sensitive categories, needs both a lawful basis and a separate Article 9 condition, and criminal offence data has its own regime under the DPA 2018. A staff wellbeing survey that collects health information is a different undertaking from a mailing list.

Breach handling has two tiers. A breach likely to result in a risk to people’s rights and freedoms goes to the ICO within 72 hours; a breach likely to result in a high risk must also be communicated to the affected people without undue delay. Every breach must be recorded internally whether or not it is reportable, and the ICO expects to see that record.

Subject access requests do not have to be in writing, do not have to use the words "subject access request", and can be made to any part of the organisation. The response is normally due within one month, extendable in limited circumstances, and a fee can only be charged in narrow cases. Staff who do not recognise one when it arrives are the usual cause of a missed deadline.

Processors and international transfers are the two contract items. Anyone processing personal data on your behalf needs a written contract with the required terms, and transfers out of the UK need a transfer mechanism such as the UK International Data Transfer Agreement or the UK Addendum, assessed for the destination. After Brexit the UK makes its own adequacy decisions, so EU-only analysis is no longer sufficient.

Finally, retention. Keeping personal data indefinitely because storage is cheap is a breach of the storage limitation principle and turns every future breach into a larger one. A schedule that names a period per category, and a deletion job that actually runs, is the control.

Common use cases

  • A small organisation starting out

    Data map, lawful basis and the ICO fee, in that order.

  • Before a breach happens

    The 72-hour procedure, rehearsed rather than written.

  • Handling a subject access request

    Recognising one and meeting the one-month deadline.

  • Using overseas suppliers

    UK transfer mechanisms and processor contracts.

Tips and limitations

  • Do the data map first. Every other obligation depends on knowing what you hold.
  • Do not default to consent. It is one of six bases and the most burdensome.
  • The 72 hours runs from awareness, including over a weekend.
  • Train reception and support to recognise a subject access request. That is where they arrive.
  • Log every breach internally, even the ones you decide not to report.

Sources and further reading

  1. Data protection, UK Government. UK GDPR, the DPA 2018 and individual rights
  2. Data protection and your business, UK Government. Organisational duties, the ICO fee and breach reporting
  3. Information Commissioner’s Office, UK Government. The UK supervisory authority, its fee and breach reporting
  4. Making a subject access request, UK Government. What a request is and the response deadline

Frequently asked questions

Which law applies to personal data in the UK?

UK GDPR together with the Data Protection Act 2018, supervised by the Information Commissioner’s Office. It is closely related to the EU regime but diverges in places, including on international transfers and adequacy, so EU-only guidance is no longer sufficient.

Do we have to pay a fee to the ICO?

Most UK organisations processing personal data owe an annual data protection fee unless they fall within an exemption, and the tier depends on size and turnover. Nothing chases you until it does, which is why it is one of the most commonly missed obligations.

How quickly must a breach be reported in the UK?

A notifiable breach goes to the ICO within 72 hours of becoming aware of it, and where there is a high risk to people they must also be told without undue delay. Every breach must be recorded internally whether or not it is reportable.

How long do we have to answer a subject access request?

Normally one month, extendable only in limited circumstances. The request does not have to be in writing, does not have to use the phrase, and can be made to any part of the organisation, so recognition by frontline staff is what protects the deadline.

Can we rely on consent for everything?

You can, but you usually should not. Consent is one of six lawful bases, must be freely given, specific, informed and as easy to withdraw as to give, and brings an ongoing management burden that contract or legitimate interests often avoids.

What do we need before sending data outside the UK?

A transfer mechanism such as the UK International Data Transfer Agreement or the UK Addendum to the EU clauses, plus an assessment of the destination, unless the UK has made an adequacy decision for that country. The UK decides adequacy independently of the EU.

Is there an in-depth guide to the Data Protection Readiness Checklist?

Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.