The test is risk to people, not the size of the company
A DPIA is required for processing likely to result in a high risk to individuals’ rights and freedoms. That is not the same as the risk of a fine or commercial embarrassment to the business. Think about consequences such as discrimination, exposure of sensitive circumstances, financial loss or interference with someone’s private life.
A small organisation can undertake high-risk processing, while a large organisation can make routine changes which do not automatically require a DPIA. Assess the nature, scale, context and purpose of the proposed activity. Company size alone is not a useful screening rule.
Screen the project before committing to its design
The ICO identifies types of processing requiring a DPIA and explains other indicators of high risk. Examples include certain systematic monitoring, large-scale sensitive-data processing and significant automated assessments. The circumstances matter; do not convert a list of indicators into an automatic exemption whenever one label appears absent.
Our practical recommendation is to add a short screening stage to procurement and project approval. Describe the people affected, data involved, sources, recipients, decisions and retention. Record why a DPIA is or is not needed. If a later feature changes those facts, reopen the screening rather than treating the original answer as permanent.
Describe a real information flow
A useful assessment explains what happens from collection to deletion. Identify the organisations and systems involved and distinguish information the project genuinely needs from information it would merely be convenient to have. Consider whether the objective can be achieved in a less intrusive way.
This is where operational colleagues matter. A supplier may describe the main platform accurately while overlooking the spreadsheet staff export each Friday. Bring the people designing, purchasing and using the service into the discussion. Test assumptions with a walkthrough of a typical record, including failures and exceptions rather than only the ideal journey.
Write risks that lead to decisions
“Data breach” is too broad to guide a project team. A more useful risk explains what could happen, to whom and with what consequences. For example, overly broad access to a sensitive case-management system could reveal information to colleagues who have no reason to see it.
Then connect the risk to a measure that can be implemented and tested. Restricted roles, less detailed records, shorter retention or a different workflow may be appropriate, depending on the case. Give each action an owner and completion condition. A table of safeguards without a delivery plan is unlikely to influence the finished service.
Get advice and assess the risk that remains
The ICO’s process includes consultation where appropriate, consideration of necessity and proportionality, assessment of risks and measures to address them. Where a DPO is appointed, their advice must be sought and recorded. Relevant views from affected individuals or their representatives may also improve the assessment.
If high risk remains which cannot be reduced, the organisation must consult the ICO before proceeding with the processing. Management acceptance does not replace that requirement. Nor does a supplier’s generic DPIA automatically settle your assessment: its document may be helpful evidence, but your configuration, purposes and population can produce different risks.
Keep the assessment connected to the project
Sign-off should identify the outcome, outstanding controls and responsibility for implementing them. Our recommendation is to make completion of essential safeguards a launch condition, rather than burying them in a document stored outside the project plan. Test the agreed design before introducing live information.
Revisit the assessment when the purpose, information, technology or risk changes. A DPIA can also reveal an opportunity to simplify the project: collecting fewer fields may reduce both privacy exposure and operational complexity. The value is not the length of the document. It is the evidence that the business recognised the implications for people and made defensible choices before the consequences became real. Assign somebody to check that the agreed controls still operate.
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.