The appointment test is about activities
A DPO is required for public authorities or bodies, subject to the relevant exception for courts, and for core activities requiring regular and systematic monitoring of individuals on a large scale, or large-scale processing of special-category or criminal-offence information. These tests can apply to controllers and processors.
Small headcount is not a complete answer. A small technology company might process information about a large population, while a larger ordinary business may handle staff records as a supporting function rather than its core activity. Assess the nature, scale, duration and purpose of the processing instead of relying on a simple employee threshold.
Document the decision either way
Start with a short description of the business model and the processing needed to deliver it. Identify whether monitoring or sensitive information is central to that activity, how many people are involved and how persistent the processing is. Where the answer is uncertain, obtain advice on the particular operation.
Our suggested decision record states the facts considered, conclusion, reviewer and triggers for reconsideration. A new service, acquisition or significant expansion can change the assessment. The record is more useful than a permanent checkbox saying DPO not required without an explanation.
A privacy lead is not automatically a DPO
Where a formal DPO is not required, an organisation still needs adequate capability to meet its obligations. It can assign operational privacy coordination to a suitable person and obtain external advice where needed. The title should accurately describe the role.
A practical privacy lead might maintain the action plan, coordinate supplier checks and make sure rights requests reach the correct people. That does not make the person an independent statutory DPO. Avoid using the title casually in contracts or public notices if the role has not actually been established on that basis.
Independence is a design requirement
A DPO needs appropriate expertise, resources, access and independence, including a route to senior management. The role can be internal or external, but outsourcing does not remove those requirements. A voluntary formal appointment also brings the position's requirements with it.
Conflicts deserve particular attention. Someone who decides the purposes and means of processing may be poorly placed to independently monitor those same decisions. Before appointing a marketing or technology leader, examine the actual authority of the role rather than assuming that familiarity with data makes them the obvious candidate.
Buy a functioning service, not a title
If considering an external appointment, ask who will actually perform the work, what expertise they bring and how much time is available. Find out how they will understand the systems, participate in project decisions and respond to urgent concerns. A generic mailbox with no agreed access or engagement may provide little practical value.
Our procurement recommendation is to specify meeting cadence, escalation routes, reporting, availability, project involvement and handover arrangements. Confirm how conflicts are managed and how advice is recorded. A cheap service that cannot engage with the business at the right time can be less useful than a clearly scoped advisory arrangement without a DPO title.
Check the practical access route
Test that employees and customers can reach the designated contact without navigating an unclear internal structure. Clear responsibility is valuable only if concerns actually arrive with someone who has the time and authority to address them.
Management keeps accountability
Appointing a DPO does not transfer the organisation's compliance responsibility to that individual. Management must make and support decisions, allocate resources and address findings. The DPO provides advice and monitoring; the business cannot treat the appointment as insurance against every mistake.
A sensible governance rhythm brings significant processing changes, unresolved risks and complaints to the appropriate decision-makers. Record why important advice is accepted or rejected and who owns the follow-up. Whether the organisation needs a formal DPO or a capable privacy lead, the objective is the same: decisions are informed, responsibilities are visible and privacy is considered before a project becomes difficult to change.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.