Key takeaways
- A DPO is mandatory only for public bodies, large-scale monitoring, or core activities involving large-scale special category or criminal offence data[1].
- Most firms are small: 78% of legal activities enterprises employ four people or fewer[2], and few will meet the large-scale test.
- A DPO must be independent, report to the top and avoid conflicts, which rules out most managing partners and IT heads[3].
- If you are not obliged to appoint one, a named data protection lead with a written remit is usually the better choice.
- Record the decision either way, with your reasons, and revisit it when the firm grows or changes practice mix.
The short answer
Article 37(1) of UK GDPR requires a Data Protection Officer in three situations: the processing is carried out by a public authority; the core activities of the controller require regular and systematic monitoring of individuals on a large scale; or the core activities consist of large-scale processing of special category data or criminal offence data[1]. A private law firm is not a public authority and rarely monitors people systematically, so the third limb is the only one that usually matters.
For most firms the answer is no. The sector is dominated by very small businesses: 78% of legal activities enterprises (26,745 of 34,255) employed four people or fewer in 2026[2], and another 5,310 employed between five and 19[4]. At the other end, only 485 employed 50 to 249 people and just 200 employed 250 or more[5]. Size is not the legal test, but the large-scale threshold is much easier to meet with hundreds of staff and tens of thousands of files.
Core activities and large scale, in law firm terms
Core activities are the processing operations you cannot deliver your service without. For a crime practice, handling offence data is the service itself. For a personal injury firm, medical evidence is inseparable from the claim. For a commercial property firm, sensitive data turns up occasionally but is not central. That is why practice mix matters more than headcount.
Large scale has no fixed number. Weigh the number of people whose data you hold, the volume of data per person, how long you keep it and how widely you operate. A firm running thousands of clinical negligence claims at once, or a multi-office criminal legal aid practice taking police station calls around the clock, is far more likely to cross the line than a two-partner high street firm doing a handful of family matters a month.
| Firm profile (Example) | Likely mandatory? | Why |
|---|---|---|
| Sole practitioner, wills and conveyancing | No | Sensitive data is incidental and volumes are small |
| Twelve-person family and crime firm, one office | Borderline | Sensitive data is core, but scale is modest; document the reasoning |
| Volume personal injury firm, 150 staff | Likely yes | Health data is core and processed at large scale |
| Criminal legal aid firm, five offices, duty rota | Likely yes | Offence data is the core activity, at scale and over long periods |
| Commercial firm, 60 staff, corporate and property | No, usually | Special category data is not a core activity |
Who can do the job
The DPO must be chosen for professional qualities, in particular expert knowledge of data protection law and practice and the ability to carry out the Article 39 tasks[1]. Article 38 then protects the role: the DPO must not receive instructions about how to do those tasks, must not be dismissed or penalised for doing them, and reports directly to the highest management level. Any other duties must not create a conflict of interests[3].
The conflict rule is where firms go wrong. A DPO's job is to advise on and monitor decisions about why and how data is processed. People who make those decisions cannot independently police them. In a law firm that usually rules out:
- The managing partner or senior partner, who sets the firm's purposes.
- The head of IT, who chooses the systems and security measures the DPO should be scrutinising.
- The head of HR, where staff data is a major processing activity.
- The head of marketing, who decides how contact data is used.
- A COLP who also holds one of the roles above.
Workable options include a senior associate or risk and compliance manager with time ring-fenced for the role, or an external DPO service under a written contract. Whoever it is, their contact details must be published and communicated to the regulator[1], which since 30 September 2026 has been the Information Commission rather than the Information Commissioner's Office[6].
If you are not obliged to appoint one
You can appoint a DPO voluntarily, but if you use the title the Article 38 protections apply in full. Many smaller firms choose a data protection lead instead: the same practical work, without the statutory independence. That is legitimate, provided you do not call the person a DPO and you give them enough authority to be effective.
Write a one-page remit
List the tasks the lead owns, the decisions they can make alone and when they must escalate to the partners.
Give them time and budget
Agree hours per month and a training allowance. Data protection squeezed into a fee earner's spare time tends to happen only after something goes wrong.
Set a reporting line
A short quarterly report to the partners on requests, incidents, supplier reviews and training keeps the work visible.
Name a deputy
Subject access deadlines and breach decisions do not pause for annual leave.
Publish a contact route
Use a role mailbox, such as a dataprotection address, rather than a personal inbox, and put it in your privacy notice.
What the role covers day to day
- Logging and answering subject access and other rights requests within the statutory deadlines.
- Assessing incidents and recommending whether to notify the regulator and the people affected.
- Running data protection impact assessments for new systems, including case management, telephony and AI tools.
- Reviewing processor contracts with IT suppliers, cloud providers, outsourced typing and answering services.
- Handling data protection complaints. Since the Data (Use and Access) Act 2025, controllers must make it easy to complain to them directly, for example with an electronic complaint form, and tell the complainant the outcome[7].
- Keeping the record of processing activities and the retention schedule current.
- Training staff at induction and at least annually, with records of who attended.
Example: a fictional 14-person firm in Leeds does family, crime and private client work. The partners assess the test, conclude that crime is core but not large scale, and record that decision. They appoint their practice manager as data protection lead with four hours a week, an external adviser on call for breach decisions, and a partner as escalation point. They will revisit the decision if they join the duty solicitor rota in a second court area.
Signs you are moving into mandatory territory
Firms rarely cross the large-scale line in one step. They drift towards it through growth and new work. Treat any of these as a trigger to repeat the assessment, rather than waiting for the annual review:
- You win a panel appointment or bulk contract that brings hundreds of new injury, clinical negligence or housing disrepair claims a year.
- You join a further duty solicitor scheme, open a second criminal office or start taking prison law work.
- You acquire a firm whose archive is mainly family, crime or Court of Protection files.
- You introduce technology that profiles callers or clients, such as automated scoring of enquiries, which moves closer to systematic monitoring.
- Your number of staff passes the point where the partners no longer know who has access to which files.
Working with the COLP also matters. Data protection failures are often regulatory events too: a serious breach can be both notifiable to the data protection regulator and reportable to the SRA. Agree in writing who decides on each notification, who drafts it and who signs it off, so the two roles reinforce each other rather than waiting for each other.
Record the decision
Whatever you decide, write down the analysis: which Article 37 limb you considered, your volumes, your practice mix, the conclusion and the date. Review it annually and whenever you open a new office, take on a bulk claims contract or merge.
For the wider framework this role sits within, see our UK GDPR essentials for solicitors, and for the data most likely to trigger the test, our guide to special category and criminal offence data.
Frequently asked questions
Is a law firm a public authority for DPO purposes?
No. Private practices are not public authorities, even when they hold legal aid contracts. The question is whether the third limb of Article 37(1) applies because sensitive data processing is a core activity carried out at large scale.
Can our COLP also be our DPO?
Only if the COLP has no role that sets the purposes and means of processing, such as managing partner or head of IT, and has the expertise and independence Article 38 requires. In many small firms that combination is hard to achieve.
Can we outsource the DPO role?
Yes. An external DPO under a service contract is common. Make sure the contract gives them access to the information they need, a direct line to the partners and enough hours to do the work.
What happens if we do not need a DPO but appoint one anyway?
The statutory protections and tasks apply as if the appointment were mandatory. If you want flexibility, use a different title such as data protection lead.
References
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 37: Designation of the data protection officer (opens in a new tab) ↑
Office for National Statistics (2026). UK business: activity, size and location, 2026 (legal activities, by employment size) (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 38: Position of the data protection officer (opens in a new tab) ↑
Office for National Statistics (2026). UK business: activity, size and location, 2026 (legal activities with 5 to 19 employees) (opens in a new tab) ↑
Office for National Statistics (2026). UK business: activity, size and location, 2026 (large legal activities enterprises) (opens in a new tab) ↑
GOV.UK (DSIT) (2026). Data (Use and Access) Act 2025: plans for commencement (opens in a new tab) ↑
GOV.UK (DSIT) (2025). Data (Use and Access) Act 2025: data protection and privacy changes (opens in a new tab) ↑