Start before the software is chosen
A common project sequence is to buy a platform, import the customer database and then ask someone to update the privacy notice. That leaves important decisions embedded in contracts and configurations before anyone has assessed them. Our recommended sequence reverses that order: define the task, identify the minimum information required, assess the risks and only then decide how the service should operate.
Article 25 requires appropriate measures to implement data protection principles and protect people’s rights throughout processing. The assessment takes account of context and risk, alongside factors such as available technology and implementation cost. It is not a demand that every small business buy the most expensive system, but neither does a limited budget excuse ignoring an obvious and avoidable exposure.
Treat defaults as business decisions
The default configuration determines what happens when nobody changes a setting. Consider whether new staff can see every customer record, whether a profile is automatically public, how much information a form demands and whether old files are retained indefinitely. These are operational choices with privacy consequences, even when they originate in a supplier’s standard product.
A practical project checklist should identify who approves each consequential default. Test the ordinary user journey rather than only the administrator view. Ask what a person would reasonably expect and whether the same service could work with fewer fields, narrower access or a shorter retention period. If children are likely users, assess the specific higher-protection requirements rather than assuming an adult-oriented design will be sufficient.
Understand the limited small-business exception
The exemption for organisations with fewer than 250 employees is not a general exemption from recording processing. The ICO explains that relevant activities still need documentation where they are not occasional, could risk people’s rights and freedoms, or involve special-category or criminal-conviction and offence information. These are alternative triggers, not a requirement that all three must apply together.
Regular payroll, customer administration and employee records are unlikely to become occasional simply because a business is small. Controllers and processors also have different record requirements. A business should assess the activities it actually performs and its role, rather than write “under 250 employees” in a policy and assume the question has been resolved.
Build a record colleagues can use
For a controller, the required record includes matters such as purposes, categories of people and information, recipients, relevant overseas transfers, envisaged erasure periods where possible, and a general description of security measures where possible. It must be available to the regulator on request. The legal requirement is more than a list of software subscriptions.
Our practical recommendation is to connect that record to the working documents that explain decisions. Link to the lawful-basis assessment, supplier contract, retention schedule and relevant privacy notice rather than copying each into multiple spreadsheets. Add a business owner and a review trigger. Those extra management fields make it easier to keep the record useful without confusing them with a prescribed statutory template.
Use risk assessment to change the design
A routine privacy review and a formal data protection impact assessment are not interchangeable labels. A DPIA is required where processing is likely to result in a high risk to individuals. Screening a project early helps identify that threshold, but the purpose is to influence the project, not simply to obtain a completed form.
For example, a proposed customer-scoring system may raise questions about accuracy, explainability and exclusion that an ordinary contact form does not. Record alternatives considered and why the chosen approach is necessary and proportionate. Where risks remain, assign concrete mitigation work and an owner. An unresolved risk should remain visible to the person deciding whether the project can proceed.
Make change control part of the process
A record can become inaccurate without any formal redesign. A marketing team connects a new integration; a supplier introduces overseas support; a form acquires an extra field; a department starts reusing information for a new purpose. The practical solution is to build privacy questions into the change process people already use.
Ask project owners to flag changes in purpose, recipients, information categories and access. Keep a short decision log and a record of completed checks. Set a proportionate review rhythm, but do not rely on the calendar alone: material changes deserve attention when they happen. A named owner should be able to explain what changed and why the documentation still matches the operation.
Measure decisions, not the size of the policy folder
A useful management review asks whether risky defaults were corrected, obsolete access was removed and unexplained data flows were resolved. Counting policies or completed questionnaires says much less about whether people’s information is protected.
Start with one important process and make its record accurate, usable and maintained. Then extend the method to the rest of the business. This is our suggested implementation approach, not a regulator-prescribed project plan. The objective is a defensible connection between what the business says, what its systems do and the evidence supporting its choices.
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.