When does UK GDPR make a data protection officer compulsory?
UK GDPR makes a data protection officer (DPO) compulsory if you meet one of three tests. You are a public body. Your main work is tracking people regularly and systematically on a large scale. Or your main work is handling sensitive or criminal offence data on a large scale.
Suppliers that handle data for others face the same tests. Main work means UK GDPR's core activities, and sensitive data means special category data, such as health information.
UK GDPR does not define large scale. The ICO points to five factors from EU regulators' guidance, which it calls useful but not binding in the UK: how many people, how much data, how many kinds of data, how wide an area, and how long it lasts.
| Test | Caught | Not caught on its own |
|---|---|---|
| You are a public body | Public bodies as the Data Protection Act 2018 (UK) defines them, when they carry out public tasks | Courts and tribunals acting in their judicial capacity |
| Your main work is tracking people regularly and systematically on a large scale | A large retail website that tracks searches and purchases to make recommendations | Tracking that is not part of your main work |
| Your main work is handling sensitive data or criminal offence data on a large scale | A health insurer that holds health information on a large number of people | HR work on staff data, which the ICO calls a secondary function for most organisations |
What does a data protection officer have to do?
A data protection officer advises your organisation and its staff on their data protection duties, and checks that the organisation follows the rules. In return, UK GDPR says you must give the officer the resources and the independence to do the job.
The officer's job, and yours
What the officer does
- Advises you and your staff on your duties
- Checks that you follow the rules, including staff training and audits
- Works with the ICO and is its contact point
What you must do
- Involve the officer in every data protection issue, properly and on time
- Give the officer the resources needed
- Make sure nobody tells the officer how to do the tasks
- Do not dismiss or penalise the officer for doing them
- Let the officer report directly to your most senior management
Can someone already on the team do it?
Yes, someone on your team can be your data protection officer, unless their other work creates a conflict of interest, such as deciding why and how you use personal data. The ICO's example is a head of marketing who decides which customers to target.
What happens if you appoint one when you do not have to?
A data protection officer you appoint by choice has the same position and tasks under UK GDPR as a compulsory one. Do not call other data protection specialists your DPO, because the title belongs to a role with particular requirements.
The DPO must be independent, an expert in data protection, adequately resourced, and report to the highest management level.
Can the role be outsourced, and to whom?
Yes, under UK GDPR a data protection officer can be on your staff or work under a service contract, with an individual or an organisation. UK GDPR asks for expert knowledge of data protection law and practice, but does not name a qualification the officer must hold.
Ask an outside provider what the fee covers, including help with a data breach. See providers that publish a price and how DPO services are priced.
What should you write down, and what must you tell the ICO?
If you appoint a data protection officer, you must publish the officer's contact details and give them to the ICO, which became the Information Commission on 30 September 2026. If you decide not to appoint, the ICO says it is a good idea to record that decision, because it helps show that you meet UK GDPR's accountability principle.
If your provider is your officer and you switch, give the ICO the new officer's details through its online service. The service asks for your registration reference and security number.
Read what to check before a first appointment or what to check when you switch.
After deciding whether you need a DPO
- Record your decision If you decide not to appoint, write down why.
- If you appoint An appointed DPO needs knowledge, resources and independence.
- Publish the contact If you appoint, give the DPO’s contact details to the ICO as well.
Did the UK's Data (Use and Access) Act 2025 change the rules?
The Data (Use and Access) Act 2025 (UK) kept UK GDPR's three tests for a data protection officer, except that it added tribunals to the court exception, from 20 August 2025. The officer's position and tasks are unchanged, apart from the regulator's name, the Information Commission, since 30 September 2026.
What to do
- Answer the ICO's online DPO questions, then write down the result and your reasons.
- Check that your candidate does not decide why and how you use personal data.
- Ask any outside provider, in writing, who the officer will be and how many other clients that officer serves. Ask what the fee covers and what indemnity cover the firm holds.
- Use the title DPO only for the person who holds the legal role.
Common questions
Can a small business need a data protection officer?
Sometimes. UK GDPR sets no minimum size for this duty, so a small firm is caught by the same three tests as any other organisation.
Is the data protection officer personally liable if you get it wrong?
No. The officer is not personally liable for data protection compliance, and your organisation remains responsible.
Can one data protection officer serve several organisations?
Yes. A group of companies may share one officer if every part of the group can reach the officer easily.
Do you have to publish the officer's name?
No. You can publish the contact details without the name. When you report a personal data breach to the ICO, the report must give the name and contact details of your officer or of another contact point.
Where next
Sources
- UK GDPR Article 39, legislation.gov.uk, checked 29 September 2026
- UK GDPR Article 38, legislation.gov.uk, checked 29 September 2026
- The ICO, guidance on data protection officers, checked 29 September 2026
- ICO service to add or change your DPO, checked 29 September 2026
- UK GDPR Article 33, legislation.gov.uk, checked 29 September 2026
- UK GDPR Article 37, legislation.gov.uk, checked 29 September 2026
- UK GDPR Article 37 from 30 September 2026, legislation.gov.uk, checked 2 October 2026
- UK GDPR Article 39 from 30 September 2026, legislation.gov.uk, checked 2 October 2026
- Data Protection Act 2018 (UK), section 7, checked 29 September 2026
- Data (Use and Access) Act 2025 (UK), Schedule 11, checked 29 September 2026
- UK commencement regulations, S.I. 2026/1015, checked 2 October 2026
- ICO questions on whether you need a DPO, checked 29 September 2026
- Freedom of Information Act 2000 (UK), Schedule 1, checked 29 September 2026
- The ICO: ICO welcomes transition to new Information Commission, 30 September 2026, checked 2 October 2026
This is an independent editorial guide, not legal advice.