GDPR Compliance Checklist (EU and UK): 12 Practical Steps

November 18, 2025

This GDPR compliance checklist covers the twelve things a supervisory authority will expect you to show under the EU General Data Protection Regulation (EU GDPR) and its UK equivalent (UK GDPR together with the Data Protection Act 2018). Each item names the article it comes from, what "done" looks like, and the evidence to keep. Use it as a self-assessment: work down the list, mark each item done, partly done or not started, and turn every gap into an action with an owner and a date.

The checklist is written for controllers (organisations that decide why and how personal data is processed). If you only process data on a client's instructions, you are a processor: items 5, 6, 9 and 11 still apply to you directly.

Who the GDPR Applies To

The EU GDPR applies to any organisation established in the EU that processes personal data, and to organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour (Article 3). The UK GDPR has the same reach for the UK. A firm based in Cyprus with UK clients, or a UK firm with EU customers, can fall under both, and a non-EU firm caught by Article 3 usually needs an EU representative (Article 27).

The stakes are real. The highest tier of fines is up to €20 million or 4% of worldwide annual turnover, whichever is higher (Article 83); the UK equivalent is £17.5 million or 4%. Most enforcement, though, starts with a complaint or a breach, and the first question the regulator asks is: show me your records.

The GDPR Compliance Checklist

1. Know what personal data you hold and why

Before anything else, build a data inventory: every system, spreadsheet and shared drive that holds personal data, what categories of data it holds (contact details, identity documents, health data, financial data), whose data it is (clients, employees, suppliers, website visitors) and why you hold it. Include data held by your service providers. This inventory is the raw material for every other item on the list.

Evidence: a data inventory with a named owner for each system, reviewed at least once a year.

2. Record a lawful basis for every processing activity (Article 6)

Each purpose needs one of the six lawful bases: consent, contract, legal obligation, vital interests, public task or legitimate interests. Choose it before you start processing and write it down; you cannot swap bases later because the first one turned out to be weak. If you rely on legitimate interests, complete and keep a legitimate interests assessment (purpose, necessity, balancing test). If you rely on consent, it must be freely given, specific, informed and as easy to withdraw as to give (Article 7), and you must be able to prove who consented, when and to what.

Special category data (health, biometrics, religion, trade union membership and others) also needs an Article 9 condition. Criminal offence data needs an Article 10 basis in national law.

Evidence: the lawful basis per purpose in your records of processing, plus legitimate interests assessments and consent records.

3. Keep records of processing activities (Article 30)

Your records of processing (often called a RoPA) must list, for each activity: the purpose, categories of data subjects and personal data, recipients, transfers outside the EU or UK and their safeguards, retention periods and a general description of security measures. Processors keep a shorter version for the processing they do for clients.

The exemption for organisations with fewer than 250 employees is narrower than it looks: it does not apply if the processing is more than occasional (payroll and client files are not occasional), likely to result in a risk, or involves special category or criminal offence data. In practice almost every business needs records.

Evidence: an up-to-date record, version-controlled, with the date of last review.

4. Tell people what you do with their data (Articles 12 to 14)

Privacy notices must say who you are, why you process the data, the lawful basis, who receives it, how long you keep it, any transfers, and what rights people have, in clear and plain language. Give them at the point of collection, or within one month when you obtain data from someone else. Check that the notice matches your records of processing; a notice that promises something your systems do not do is a finding in itself.

Evidence: current privacy notices (website, employees, clients) with version history.

5. Put contracts in place with every processor (Article 28)

Any supplier that processes personal data for you (cloud hosting, payroll, CRM, email marketing, IT support) must be bound by a written contract that covers the Article 28 terms: acting only on your documented instructions, confidentiality, security, use of sub-processors only with your authorisation, help with data subject requests and breaches, deletion or return at the end, and audit rights. Choose processors that give sufficient guarantees, and keep the due diligence that shows you checked.

Evidence: a processor list linked to signed data processing agreements and due diligence questionnaires.

6. Secure the data (Article 32)

Security must be appropriate to the risk: access control on a need-to-know basis, encryption where it matters, backups, patching, logging, and the ability to restore availability after an incident. Test the measures regularly; Article 32 asks for a process for regularly testing and evaluating them, not just a policy.

Evidence: a security policy, access reviews, backup and restore test results, penetration test or vulnerability scan results.

7. Run a DPIA for high-risk processing (Article 35)

A data protection impact assessment (DPIA) is mandatory before processing that is likely to result in a high risk to individuals: large-scale processing of special category data, systematic monitoring of public areas, profiling with significant effects, and the activities on your supervisory authority's published list. The DPIA describes the processing, assesses necessity and proportionality, identifies the risks to individuals and the measures that reduce them. If high risk remains after mitigation, you must consult the supervisory authority before you start (Article 36).

Evidence: completed DPIAs, the screening decisions for projects that did not need one, and the actions that came out of them.

8. Build privacy into new projects (Article 25)

Data protection by design and by default means privacy is considered when a system or process is designed, not bolted on after launch. By default, collect only what you need, keep it only as long as you need it, and make it visible only to people who need it. A simple screening question in your project or change process ("does this involve personal data?") triggers the DPIA check in item 7.

Evidence: retention schedule, project screening records, deletion logs.

9. Be ready to handle a breach within 72 hours (Articles 33 and 34)

A personal data breach must be reported to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to individuals. If the breach is likely to result in a high risk, you must also tell the people affected without undue delay. Processors must tell the controller without undue delay. Every breach, reported or not, goes in your internal breach log with the facts, effects and remedial action (Article 33(5)).

The 72 hours includes weekends. Have a written procedure, a named decision-maker, and a template notification ready before you need it.

Evidence: breach procedure, breach log, decision records for breaches you chose not to report.

10. Answer data subject requests on time (Articles 15 to 22)

People have the right of access, rectification, erasure, restriction, portability and objection, and rights related to automated decision-making. You must respond within one month, extendable by two further months for complex or numerous requests if you tell the person within the first month (Article 12(3)). Requests can arrive by any channel, so front-line staff need to recognise one.

Evidence: a request log showing date received, identity check, response date and outcome.

11. Control international transfers (Chapter V, Articles 44 to 49)

Transfers outside the EU (or the UK) need a mechanism: an adequacy decision, standard contractual clauses or binding corporate rules, or, in narrow cases, a derogation. For contractual clauses you should assess whether the law of the destination country undermines them (a transfer impact assessment). Remember that remote access from another country, for example a support team abroad, is a transfer.

Evidence: a transfer register showing destination, mechanism and assessment for each transfer.

12. Assign responsibility: DPO, training and review (Articles 37 to 39)

You must appoint a data protection officer (DPO) if you are a public authority, or if your core activities involve large-scale regular and systematic monitoring of individuals, or large-scale processing of special category or criminal offence data. Even when a DPO is not mandatory, someone must own data protection and report to senior management. Train all staff who handle personal data when they join and at least annually, and keep the attendance records. Finally, review the whole programme on a schedule: accountability (Article 5(2)) means being able to demonstrate compliance, not just achieving it.

Evidence: DPO appointment or documented decision not to appoint, training records, annual review report to the board.

UK GDPR and the Data Protection Act 2018: What Differs

The UK GDPR keeps the structure of the EU text, so the twelve items above apply in the UK as well. The differences that matter in practice:

TopicEU GDPRUK GDPR / DPA 2018
RegulatorNational supervisory authority (in Cyprus, the Commissioner for Personal Data Protection)Information Commissioner's Office (ICO)
Maximum fine€20m or 4% of worldwide turnover£17.5m or 4% of worldwide turnover
Transfer toolsEU standard contractual clausesInternational Data Transfer Agreement (IDTA) or the UK Addendum to the EU clauses
Children's consent online16 by default, member states may lower to 1313
Registration feeNot required by the GDPRMost controllers must pay the ICO data protection fee
RepresentativeEU representative for non-EU firmsUK representative for non-UK firms

The DPA 2018 adds the national detail the UK GDPR leaves open, including the conditions for special category and criminal offence data and a list of exemptions. The Data (Use and Access) Act 2025 amends the UK regime in stages, for example with "recognised legitimate interests" that do not need a balancing test and a duty to have a process for complaints, so check which provisions are in force when you review your UK checklist. Firms operating in both regimes usually keep one register and record which regime applies to each processing activity.

How to Run a GDPR Compliance Assessment

A checklist is only useful if it produces evidence and actions. A workable cycle:

  1. Scope. List the entities, systems and processing activities in scope.
  2. Assess. Go through the twelve items with each process owner; for each, record the status and the evidence that supports it.
  3. Rate the gaps. Score each gap by likelihood and impact on individuals, so you fix the processing that could cause harm first.
  4. Assign actions. Every gap becomes an action with an owner, a due date and a definition of done.
  5. Report. Give senior management a one-page summary: items complete, open gaps by rating, overdue actions.
  6. Repeat. Re-assess annually and whenever you launch a new system, supplier or market.

Keeping the Evidence in One Register

The work is rarely in knowing the rules; it is in keeping the evidence current. Policies live in one folder, processor contracts in another, the breach log in a spreadsheet, and nobody can say which DPIA actions are still open.

In ActiveERM, the pieces of this checklist sit in one place: privacy policies, records of processing and DPIAs in Documents with versioning; supplier due diligence sent through Questionnaires to external respondents; breaches logged as Incidents; every gap tracked as an Action with an owner and due date; and privacy risks scored in the risk register alongside the rest of the business. Findings from a GDPR review run through Audit Management. See also our guides on third-party risk management and policy management, or request a demo to see it in your own demo environment.

Frequently Asked Questions

What should a GDPR compliance checklist include?

At minimum: a data inventory, a lawful basis for each purpose, records of processing (Article 30), privacy notices, processor contracts (Article 28), security measures (Article 32), DPIAs for high-risk processing (Article 35), a breach procedure that meets the 72-hour deadline (Article 33), a process for data subject requests, controls on international transfers, a DPO decision, staff training, and evidence for each of these.

Is the UK GDPR checklist different from the EU GDPR checklist?

The core obligations are the same, so one checklist covers both. The UK differences are mainly the regulator (the ICO), the ICO data protection fee, UK transfer tools (the IDTA or UK Addendum), the age of consent for online services (13), and changes made by the Data (Use and Access) Act 2025.

How long do we have to report a personal data breach?

You must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the breach, unless it is unlikely to result in a risk to individuals. If you report later than 72 hours, you must give the reasons for the delay.

Do small businesses need records of processing activities?

Usually yes. The exemption for organisations under 250 employees does not apply when processing is more than occasional, likely to result in a risk, or involves special category or criminal offence data. Routine processing such as payroll or client files is not occasional.

How often should we carry out a GDPR compliance assessment?

Review the full checklist at least once a year and report the result to senior management. Also re-assess whenever you introduce a new system, supplier, type of data or country, because those changes are where new gaps appear.

Explore ActiveERM

See how ActiveERM helps you with governance, risk, compliance, and audit in one platform.