
A DPIA template for a new IT system: the part IT has to supply
Every DPIA template asks the same questions, and about half of them can only be answered by IT: which data sits where, who can reach it, how long it is kept and what protects it. The DPIA itself belongs to the organisation that will use the system, not to the IT team or the supplier. This is the technical part, and the questions to ask early enough for the answers to matter.
A DPIA is required when processing is likely to result in a high risk to the people whose data you process, and it has to be done before the system goes live.
IT supplies the system description, data flows, storage locations, access rights, retention periods and technical measures. The judgement on necessity and risk belongs to the controller.
Ask the supplier your questions before the contract: where the data sits, which sub-processors there are, what is logged and how deletion works. After signature every answer comes more slowly.
When is a DPIA required?
Under the GDPR, and the UK GDPR, a data protection impact assessment is required when processing is likely to result in a high risk to the rights and freedoms of individuals (Article 35). That is not a question about technology but about what the system does to people. European regulators set out nine criteria; if processing meets two or more, a DPIA is generally needed:
- evaluating or scoring people, or making automated decisions about them with significant effects;
- systematic monitoring, such as cameras, location data or monitoring staff;
- special category or highly personal data: health, criminal records, financial data;
- processing on a large scale, or matching datasets that were collected separately;
- vulnerable individuals, such as children, patients or employees in relation to their employer;
- innovative technology, or processing that stops people exercising a right or using a service.
In the UK the ICO publishes a list of processing that always needs a DPIA, along with its own DPIA template; the Irish Data Protection Commission does the same. If in doubt, record why you are or are not doing one. That decision is part of accountability, even when the answer is no.
What a DPIA template contains, and who writes which part
The law names four elements, and they do not all come from the same person:
- A systematic description of the processing and its purposes. The purpose comes from the process owner; the description of the system, the data and the data flows comes from IT.
- Necessity and proportionality. Is this needed for the purpose, can it be done with less data, what is the lawful basis. That is the controller’s judgement, with advice from the data protection officer if there is one.
- The risks to individuals. Not the risks to the organisation, but to the people the data is about: what goes wrong for them in a breach, an error or misuse.
- The measures to address those risks. Many of them are technical, and that is where IT comes back in.
Any DPIA template helps with the order. None of them fixes the usual problem: the technical questions reach someone who can answer them far too late. Bring IT in while the system is still being chosen, not once the draft is finished.
The system description and data flows
This is where a DPIA usually stays too vague. “Data is stored securely in the cloud” describes nothing. What belongs here:
- Which data, by category. Not “customer data” but name, email, phone number, order history, and whether special category data turns up, including in free text fields.
- Where it is stored. Which data centre, which country, and where the backups and logs are kept. Those last two are often forgotten and sometimes sit elsewhere.
- How it flows. A diagram with the sources, the system, its integrations with other systems and the recipients. Every arrow is a point where data is in transit and needs a measure.
- Who can access it. Which roles, how many administrators, whether the supplier has access for support, and how that is recorded.
- For how long. The retention period per category, and how deletion actually works: is a record truly deleted or only hidden, and what happens in the backups.
A data flow diagram is the most useful thing IT can hand over. It shows what disappears in prose, and it is the document you will need if there is ever a data breach.
Technical measures tied to a risk
A list of measures with no link to the risks is an inventory, not a DPIA. Tie each measure to the risk it reduces, and be specific about what is actually in place:
- Access: multi-factor authentication, roles with the least privilege needed, and a fixed periodic review of who still has access.
- Encryption: in transit and at rest, and who holds the keys. With a cloud service that is the difference between “encrypted” and “encrypted with a key the supplier also has”.
- Logging: who viewed or changed which data, how long those logs are kept and who reviews them. Logs nobody reads are an archive, not a control.
- Backup and recovery: how often, where, for how long, and when a restore test last succeeded.
- Minimisation in the system itself: switching off fields you do not need, pseudonymising data in test and reporting environments, and deleting automatically at the end of the retention period.
What remains after the measures is the residual risk. If it stays high, the controller must consult the regulator before processing starts. IT does not make that call; IT makes sure the measures match what is really running.
What to ask the system’s supplier
With a new system from a third party, half the technical answers come from that supplier. As a processor it is required to help you with a DPIA, and that belongs in the data processing agreement too. Ask at least:
- in which countries the data, the backups and the support teams are, and whether data is transferred outside the UK or the EEA;
- which sub-processors there are and how you are told about a new one;
- which certifications it holds and which part of the service they cover, because an ISO/IEC 27001 certificate does not automatically cover the product you are buying;
- what is logged, whether you can see those logs yourself and how long they exist;
- how data is deleted at the end of the contract, and how you get it back in a usable format before that.
A supplier that answers with a standard annex is not suspicious in itself. A supplier with no answer after three weeks is telling you something about how things will go when something goes wrong.
When to start, and the usual mistakes
A DPIA has to be finished before the processing starts, and in practice that means before the contract. After that the main choices have been made and every measure becomes a change request. The order that works:
- During selection: screen whether a DPIA is needed and put the supplier questions in the tender.
- Before the contract: description, data flows and measures in draft, so the outcome can still influence the choice.
- Before go-live: the measures checked as configured, not as promised.
- Afterwards: review it when a change alters the risks: a new integration, a new supplier, new data.
Three mistakes keep coming back: writing the DPIA once the system is already running, so it becomes a report rather than a decision document; asking the IT questions at the very end, so they are filled in with assumptions; and never touching the document again while the system keeps growing.
Where our work stops
What we do. For systems we supply, configure or manage, we provide the technical part of the DPIA: the system description, the data flow diagram, storage locations, access rights, retention periods as technically configured and the security measures. We answer the questions of the controller and its data protection officer, and we adjust measures when the DPIA calls for it. We work under ISO/IEC 27001; that describes how we work, not a judgement on your processing.
What we do not do. We are not lawyers and not a data protection officer. The DPIA belongs to the controller: we do not sign it off, decide whether it is required, assess the lawful basis, necessity or proportionality, or consult the regulator. We do not sign a DPIA on a client’s behalf. That judgement belongs to your own organisation, your data protection officer or a privacy lawyer.
Questions we get about this
The five that come up most often.
What is a DPIA?
A data protection impact assessment is an assessment, made in advance, of the risks a processing operation poses to the people whose data is processed, and of the measures to reduce them. The GDPR and UK GDPR require one for processing that is likely to be high risk. It describes the processing, tests necessity and proportionality, and sets out the risks and the measures.
When is a DPIA required?
When processing is likely to result in a high risk to individuals’ rights and freedoms. If processing meets two or more of the nine European criteria, such as sensitive data, large scale, systematic monitoring or innovative technology, a DPIA is generally needed. The ICO also publishes a list of processing that always requires one.
Is there a DPIA template I can use?
Yes, the ICO publishes one, and many regulators and sector bodies offer their own. A template helps with structure and order, but the quality depends on the technical answers: the data per category, the data flows, storage locations, access and retention. Those have to come from IT and the supplier, and early enough to influence the choice of system.
Who is responsible for carrying out a DPIA?
The controller, meaning the organisation that decides why and how the data is processed. If there is a data protection officer, their advice must be sought. IT and the supplier provide the technical input, but the judgement and sign-off stay with the controller.
Can you write or approve our DPIA?
No. We are not lawyers and not a data protection officer, and the DPIA belongs to the controller. For systems we supply or manage, we provide the technical description, the data flows and the measures, and adjust measures when the DPIA calls for it. Whether a DPIA is required and whether the residual risk is acceptable is for your organisation and its privacy adviser to decide.
Further reading
What this assessment connects to.
A new system on the way? We supply the technical part
Tell us which system you are bringing in. We describe the data flows, storage and measures as they will really be configured, so your data protection officer can judge on facts rather than assumptions.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.