Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales)
UK GDPR Article 35 & Data Protection Act 2018
DATA PROTECTION IMPACT ASSESSMENT (DPIA)
Prepared pursuant to UK GDPR Article 35 and the Data Protection Act 2018
1. PROJECT DETAILS
Organisation: [Organisation Name]
Project or Processing Activity: [Project Name]
Project Owner: [Project Owner Name]
Data Protection Officer: [DPO Name]
Date of Assessment: [Assessment Date]
This Data Protection Impact Assessment (DPIA) has been conducted in accordance with Article 35 of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018. Recital 84 of the UK GDPR states that a DPIA should be used to assess the particular likelihood and severity of the high risk to the rights and freedoms of natural persons.
2. DESCRIPTION OF PROCESSING OPERATIONS
2.1 Project Description
[Project Description]
2.2 Nature of the Processing
[Nature of Processing]
2.3 Scope of the Processing
[Scope of Processing]
2.4 Context of the Processing
[Context of Processing]
2.5 Purpose of the Processing
[Purpose of Processing]
3. LAWFUL BASIS AND SPECIAL CATEGORY CONDITIONS
3.1 Lawful Basis (UK GDPR Article 6)
The processing is carried out on the following lawful basis: [Lawful Basis].
4. DATA SUBJECTS AND RETENTION
4.1 Categories of Data Subjects
[Data Subjects Categories]
4.2 Data Retention Period
[Data Retention Period]
Retention periods are set in accordance with UK GDPR Article 5(1)(e) (storage limitation principle) and the organisation's Records Retention Schedule. Personal data will not be kept for longer than is necessary for the purposes for which it is processed.
5. AUTOMATED DECISION-MAKING AND DATA SHARING
5.1 Automated Decision-Making and Profiling
Automated decision-making or profiling involved: [Automated Decision Making].
Where automated decisions are made that produce legal or similarly significant effects, the requirements of UK GDPR Article 22 apply, including the right to human review, the right to express a point of view, and the right to contest the decision.
5.2 Data Sharing with Third Parties
Personal data shared with third parties: [Data Sharing Third Parties].
5.3 International Data Transfers
International transfer of personal data outside the UK: [International Transfers].
6. NECESSITY AND PROPORTIONALITY ASSESSMENT
6.1 Necessity
[Necessity Assessment]
6.2 Proportionality
[Proportionality Assessment]
7. RISK IDENTIFICATION AND ASSESSMENT
The following risks to the rights and freedoms of data subjects have been identified in accordance with UK GDPR Article 35(7)(c) and ICO DPIA guidance. Risks are assessed by reference to their likelihood (probability of occurrence) and severity (magnitude of harm to individuals).
7.1 Identified Risks
[Risks to Individuals]
8. MITIGATION MEASURES AND RESIDUAL RISK
8.1 Risk Mitigation Measures
[Risk Mitigation Measures]
8.2 Residual Risk Level
After implementing the mitigation measures identified above, the residual risk level is assessed as: [Residual Risk Level].
Where the residual risk level is high, the controller is required by UK GDPR Article 36 to consult the ICO before commencing the processing. The ICO will provide written advice within 8 weeks of receiving a complete consultation request (extendable to 14 weeks in complex cases).
9. DPO CONSULTATION
In accordance with UK GDPR Article 35(2), the Data Protection Officer has been consulted in relation to this DPIA. The DPO was consulted on: [DPO Consultation Date].
DPO Advice:
[DPO Advice]
10. PRIOR ICO CONSULTATION (ARTICLE 36)
Prior ICO consultation required: [Ico Consultation Required].
Under UK GDPR Article 36(1), where the DPIA indicates that the processing would result in a high residual risk in the absence of measures taken by the controller to mitigate the risk, the controller must consult the ICO prior to processing. The ICO may issue written advice, impose conditions, or prohibit the processing where it does not comply with the UK GDPR.
11. DPIA OUTCOME AND APPROVAL DECISION
Having considered the nature, scope, context, and purposes of the processing, the identified risks, the mitigation measures implemented, and the residual risk level, the following decision is made regarding the processing activity described in this DPIA:
Decision: [Approval Decision]
This DPIA will be reviewed: (a) prior to any significant change in the processing operations described herein; (b) if a personal data breach occurs in connection with the processing; (c) if new risks are identified; or (d) in any event, at least every two years from the date of approval, in accordance with ICO DPIA guidance on ongoing review obligations.
12. AUTHORISATION
This Data Protection Impact Assessment is approved by:
Name: [Approver Name]
Organisation: [Organisation Name]
Date of Approval: [Approval Date]
Data Protection Officer
[DPO Name]
Signature
Date: ________________
Approving Authority
[Approver Name]
Signature
Date: ________________
What Is a Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales)?
A Data Protection Impact Assessment (DPIA) — UK GDPR in the United Kingdom sets the service levels, data-handling duties, fees, and liability terms under which the technology or platform is supplied, with its requirements set by UK General Data Protection Regulation (UK GDPR).
The ICO defines a DPIA as a process to help organisations identify and minimise the data protection risks of a project. This is both a risk management tool and a demonstration of accountability — one of the core principles of the UK GDPR under Article 5(2). Completing a DPIA before embarking on high-risk processing reduces the likelihood of a compliance failure and the associated reputational damage and regulatory consequences.
Recital 84 of the UK GDPR explains the purpose of the DPIA: to assess the particular likelihood and severity of the high risk to the rights and freedoms of natural persons, taking into account the nature, scope, context, and purposes of the processing. A DPIA is not a box-ticking exercise — it must be a genuine, evidence-based assessment that leads to informed decisions about how to design the processing activity to minimise privacy impact.
The ICO has published a mandatory list of processing types that always require a DPIA in the United Kingdom, in accordance with Article 35(4). This list includes: large-scale profiling; biometric data for unique identification; special category data matched or combined from multiple sources; personal data of vulnerable individuals processed on a large scale; innovative technology with significant privacy implications; and systematic monitoring of publicly accessible areas using CCTV or similar technology. Where a processing activity falls within any of these categories, a DPIA is legally required before the processing begins.
The legal framework governing the Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales) in United Kingdom draws on several key statutes and regulatory bodies. Under the Companies Act 2006, Companies House maintains the register of UK companies. Section 386 of the Companies Act 2006 sets accounting record obligations. The Competition and Markets Authority (CMA) enforces the Consumer Rights Act 2015. The Financial Conduct Authority (FCA) regulates financial services under the Financial Services and Markets Act 2000. The High Court of Justice has jurisdiction under the Senior Courts Act 1981. Parties executing a Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales) in United Kingdom should confirm the document reflects current law, including any amendments enacted since the original drafting date. The UK General Data Protection Regulation (UK GDPR) sets the foundational requirements.
When Do You Need a Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales)?
A DPIA is needed whenever your organisation plans to introduce a new processing activity or significantly change an existing one that is likely to result in a high risk to individuals. The ICO provides a screening checklist to help organisations determine whether a DPIA is required, but the following situations always require one under Article 35(3) UK GDPR or the ICO's mandatory list.
Biometric and genetic data processing requires a DPIA whenever you plan to use technology that processes facial recognition, fingerprints, iris scans, voice recognition, DNA, or other biometric identifiers to uniquely identify individuals. This applies to employee access control systems, customer authentication systems, and any other application that captures biometric data, even where the data is immediately converted into a mathematical template rather than stored as a raw image.
Large-scale profiling and automated decision-making requires a DPIA where you use automated systems — including machine learning, AI, or algorithmic scoring — to evaluate personal aspects of individuals (creditworthiness, health risks, job performance, behaviour patterns) and make or support decisions that produce legal or similarly significant effects. This includes credit scoring engines, insurance risk algorithms, recruitment screening tools, and fraud detection systems.
Employee monitoring projects require a DPIA where you plan to introduce new monitoring technologies such as email monitoring, internet usage tracking, keystroke logging, GPS vehicle tracking, productivity analytics, or any other systematic monitoring of employees' activities. The ICO and the Employment Practices Code both recognise that employees have a reasonable expectation of privacy even in the workplace, and systematic monitoring must be justified and proportionate.
Data sharing between organisations on a large scale, including creating centralised databases combining data from multiple organisations, requires a DPIA. This is particularly relevant for healthcare data sharing programmes, fraud prevention databases, and public-private data sharing initiatives.
New technologies and innovative applications of existing technologies require a DPIA where the privacy implications are not fully understood or where the technology could be used in ways that individuals would not reasonably anticipate. The ICO specifically identifies the Internet of Things (IoT), smart city infrastructure, wearable health devices, and AI-based decision support systems as examples of processing requiring a DPIA.
What to Include in Your Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales)
Systematic Processing Description — The foundation of any DPIA is a clear, accurate description of the processing operations. The description must address the four dimensions specified in Article 35(7)(a): nature (what operations are performed on the data), scope (the volume, frequency, and geographic spread), context (the environment and circumstances of the processing), and purpose (the specific objectives). A vague or incomplete description undermines the entire DPIA and may indicate that the controller does not have adequate understanding of its own processing.
Lawful Basis and Special Category Conditions — Every processing activity must rest on one of the six lawful bases in Article 6 UK GDPR. For special category data (health, biometric, genetic, racial, criminal, religious, sexual orientation, political), an additional condition under Article 9(2) must be identified. Where DPA 2018 Schedule 1 conditions are relevant (employment, research, substantial public interest), these must also be cited. The DPIA should confirm that the lawful basis has been documented in the controller's Records of Processing Activities (ROPA) under Article 30.
Data Subjects and Retention Assessment — The DPIA must identify the categories of data subjects with precision, noting any vulnerable groups (children, elderly individuals, people with disabilities, patients, job applicants) whose data warrants elevated protection. The data retention period must be specified for each category of personal data, with reference to the legal, regulatory, or operational basis for the chosen period. The UK GDPR Article 5(1)(e) storage limitation principle prohibits retaining personal data for longer than necessary.
Automated Decision-Making Evaluation — Where the processing involves automated decisions (including profiling) that produce legal or similarly significant effects, the DPIA must describe the logic involved and assess compliance with Article 22 UK GDPR. Data subjects have the right to human review of automated decisions, the right to express a point of view, and the right to contest the decision. The DPIA must address how these rights are supportd.
Necessity and Proportionality Test — Article 35(7)(b) requires a genuine assessment of whether the processing is necessary and proportionate to its stated purpose. The ICO expects this to include consideration of: whether a less privacy-intrusive approach could achieve the same objective; whether the same purpose could be achieved using anonymised or pseudonymised data; the minimum volume of personal data needed; and whether the data minimisation principle (Article 5(1)(c)) has been applied.
Risk Identification and Assessment Matrix — The core of the DPIA is a structured assessment of the risks to data subjects. The ICO identifies four categories of harm: physical (injury, safety risks), material (financial loss, identity theft, discrimination), non-material (distress, reputational damage, loss of opportunity), and loss of control (inability to manage one's own data). For each identified risk, the DPIA should assess the likelihood of occurrence and the severity of harm if the risk materialises, resulting in a risk rating (low, medium, high).
Risk Mitigation Measures — For each identified risk, the DPIA must describe specific technical and organisational measures to reduce the likelihood or severity of the harm. Technical measures include encryption, pseudonymisation, access controls, data minimisation, and security monitoring. Organisational measures include data retention policies, staff training, contractual obligations on processors, and audit procedures. After applying mitigation measures, the residual risk must be re-assessed.
DPO Consultation Record — Article 35(2) requires the controller to seek the DPO's advice, and Article 38(1) requires the DPO to be involved in a timely manner. The DPIA must record the DPO's specific recommendations and whether they were accepted. If the DPO disagrees with the controller's risk assessment or conclusions, this disagreement must be documented, with the DPO's reasoning and the controller's response. This record protects both the DPO (who has statutory independence under Article 38(3)) and the controller (who can demonstrate that proper governance was followed).
ICO Prior Consultation Decision — Where the residual risk after mitigation is assessed as high, Article 36(1) requires prior consultation with the ICO before processing begins. The DPIA must document this decision. Where ICO consultation is conducted, the controller must provide the ICO with the completed DPIA, the purposes and means of processing, the measures and safeguards, and the DPO's contact details. The ICO's written advice must be documented and implemented or formally disagreed with.
Formal Approval and Review Schedule — The DPIA must conclude with a formal approval decision by senior management. Where processing is approved with conditions, those conditions must be documented and tracked to completion. The review schedule must specify when the DPIA will be reassessed — at minimum before any material change to the processing, after any related breach, and at periodic intervals consistent with ICO guidance. The forms-legal.com Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales) template covers the mandatory elements under UK General Data Protection Regulation (UK GDPR).
Sources & Citations
Statutory citations link to official government sources.
- GDPR Article 5EU – GDPR
Cite this page
Reference this free template in an article, syllabus, or research note:
Forms Legal. (2026). Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales) (United Kingdom) [Legal document template]. Forms Legal. https://forms-legal.com/uk/business/policies/data-protection-impact-assessment-england-wales
"Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales) (United Kingdom)." Forms Legal, 2026, https://forms-legal.com/uk/business/policies/data-protection-impact-assessment-england-wales.
@misc{formslegal-data-protection-impact-assessment-england-wales,
author = {{Forms Legal}},
title = {Data Protection Impact Assessment (DPIA) — UK GDPR (England & Wales) (United Kingdom)},
year = {2026},
howpublished = {\url{https://forms-legal.com/uk/business/policies/data-protection-impact-assessment-england-wales}},
note = {Free legal document template. Based on UK General Data Protection Regulation (UK GDPR)}
}Frequently Asked Questions
Under Article 35(1) of the UK GDPR, a DPIA is required where a type of processing, in particular using new technologies, is likely to result in a high risk to the rights and freedoms of natural persons. Article 35(3) specifies three situations where a DPIA is always required: (a) systematic and extensive evaluation of personal aspects based on automated processing, including profiling, which produces legal or similarly significant effects; (b) processing on a large scale of special categories of data (under Article 9) or personal data relating to criminal convictions and offences; and (c) systematic large-scale monitoring of a publicly accessible area. The ICO has also published a list of processing types that require a DPIA, including: use of biometric or genetic data to uniquely identify individuals; matching or combining datasets from multiple sources; processing data of vulnerable individuals (children, employees, mental health patients); use of innovative technology; and processing that prevents individuals from accessing services or exercising rights. If a controller is uncertain whether a DPIA is required, the ICO recommends completing one as a matter of good practice, as the DPIA process itself demonstrates accountability under Article 5(2) UK GDPR.
Article 35(7) of the UK GDPR specifies that a DPIA must contain at a minimum: (a) a systematic description of the envisaged processing operations and the purposes of the processing, including, where applicable, the legitimate interest pursued by the controller; (b) an assessment of the necessity and proportionality of the processing operations in relation to the purposes; (c) an assessment of the risks to the rights and freedoms of data subjects as referred to in Article 35(1); and (d) the measures envisaged to address the risks, including safeguards, security measures, and mechanisms to confirm the protection of personal data and to demonstrate compliance with the UK GDPR. The ICO's DPIA guidance supplements these requirements with additional recommended elements: the name and role of the DPO consulted under Article 35(2); the lawful basis for processing under Article 6; for special category data, the applicable Article 9(2) condition; an assessment of necessity and proportionality including whether processing could be achieved by less privacy-intrusive means; and details of consultation with data subjects or their representatives where appropriate.
Under UK GDPR Article 36(1), if the results of the DPIA indicate that the processing would result in a high residual risk in the absence of measures taken by the controller to mitigate the risk, the controller must consult the Information Commissioner's Office (ICO) prior to processing. This is known as prior consultation. The ICO will provide written advice within 8 weeks of receiving the consultation request. This period may be extended by a further 6 weeks where the processing is particularly complex, for a maximum of 14 weeks. The ICO may, within this period: provide written advice to the controller or processor; exercise its investigative and corrective powers under UK GDPR Articles 58(1) and 58(2), including imposing a temporary or permanent ban on the processing; or take no further action where it is satisfied that the controller has adequately addressed the identified risks. Failure to consult the ICO when required may result in a fine of up to £8.7 million or 2% of global annual turnover under the lower tier of Article 83 UK GDPR.
Yes. Under Article 35(11) of the UK GDPR, the controller must carry out a review to assess if the processing is performed in accordance with the DPIA, at least when there is a change in the risk represented by processing operations. The ICO's DPIA guidance recommends reviewing and updating DPIAs: (1) before any significant change in the processing operations described in the original DPIA — for example, introducing new data sources, extending the processing to new categories of individuals, adding automated decision-making, or transferring data to new third parties or new countries; (2) if a personal data breach occurs in connection with the processing activity; (3) if new risks are identified during the processing; and (4) at periodic intervals (the ICO suggests at least every two to three years) even without any specific change, to confirm the DPIA remains current and accurate. The DPIA must be retained as a record of the controller's accountability under Article 5(2) and should be made available to the ICO on request. It is also a key document in due diligence exercises during business sales, mergers, or regulatory audits.
Under UK GDPR Article 35(2), where a Data Protection Officer has been appointed, the controller must seek the advice of the DPO when carrying out a DPIA. Under Article 38(1), the controller must confirm that the DPO is involved, properly and in a timely manner, in all issues which relate to the protection of personal data, including DPIAs. The DPO's role in the DPIA process includes: advising on the need to carry out a DPIA and the methodology to be used; assessing whether the DPIA has been correctly carried out; checking that the correct conclusions have been reached (particularly on the residual risk assessment and the need for ICO prior consultation); and verifying that the appropriate safeguards and risk mitigation measures are in place. Critically, the DPO's advice must be documented in the DPIA regardless of whether the controller follows it. Where the DPO disagrees with the controller's conclusions — for example, where the DPO believes prior ICO consultation is required but the controller does not — this disagreement must be formally recorded. Under Article 38(3), the DPO must not be penalised or dismissed for performing their duties, including for providing advice that the controller disagrees with.
The UK GDPR's requirement to carry out a DPIA applies primarily to new processing activities or significant changes to existing processing. However, the ICO expects controllers to conduct DPIAs for existing high-risk processing where no DPIA was previously completed — particularly for processing that was established before the UK GDPR came into force on 25 May 2018 and that would have required a DPIA had it been introduced after that date. The ICO's accountability framework strongly recommends retrospective DPIAs for legacy processing involving biometric data, systematic monitoring, large-scale special category data processing, or automated decision-making. Controllers that acquire another organisation's business and inherit its processing activities should conduct a DPIA review as part of their due diligence. Where processing has changed materially since a DPIA was last conducted (for example, the volume of data has increased significantly, new technologies have been adopted, or new data sharing arrangements have been established), the existing DPIA must be reviewed and updated. The obligation to maintain a record of all DPIAs is permanent and forms part of the controller's Records of Processing Activities (ROPA) under Article 30 UK GDPR.
This template is provided for informational purposes only and does not constitute legal advice. Laws vary by jurisdiction and change over time. Consult a qualified attorney for advice specific to your situation.Full disclaimer
Found an error? Let us knowRelated Documents
You may also find these documents useful:
Data Processing Agreement — UK GDPR (England & Wales)
Create a Data Processing Agreement (DPA) fully compliant with UK GDPR Article 28 and the Data Protection Act 2018 for England and Wales. This template covers all mandatory Article 28(3) processor obligations, ICO registration, sub-processor authorisation with prior notice, UK IDTA provisions for international transfers outside the UK, technical and organisational security measures under Article 32, personal data breach notification timelines, data subject rights assistance, DPIA support, audit rights with advance notice, and data deletion or return obligations. Includes controller ICO registration details, special category data provisions, and automatic termination with the principal services agreement. Governing law: England and Wales. Download as PDF or Word.
Privacy Policy (UK)
Create a detailed UK Privacy Policy compliant with the UK General Data Protection Regulation (UK GDPR) and Data Protection Act 2018. This template covers data controller identification, ICO registration, lawful bases for processing, data subject rights, cookies under PECR, international data transfers, data retention, and breach notification. Suitable for websites, apps, and online services operating in England and Wales. Fill in your organisation's details, preview in real time, and download as PDF or Word.
GDPR Data Breach Notification Form (England & Wales)
Create a detailed UK GDPR Data Breach Notification Form compliant with Articles 33 and 34 of the UK General Data Protection Regulation and Section 108 of the Data Protection Act 2018. This template covers mandatory ICO notification within the 72-hour window, data subject communication obligations, breach classification (confidentiality, integrity, availability), categories of personal data affected, scale assessment, risk evaluation, remediation measures, and cross-border supervisory authority notifications under the NIS Regulations 2018. Suitable for data controllers of all sizes operating in England and Wales. Download as PDF or Word.
Consent Form (UK)
Create a general Consent Form for use in England and Wales. This versatile template covers medical consent, activity consent, data processing consent, photography consent, and research participation consent. Compliant with common law informed consent principles, the Mental Capacity Act 2005, the Children Act 1989, and UK GDPR Article 7. Includes risk and benefit disclosures, right to withdraw, capacity confirmation, parental consent for minors, and emergency contact information. Fill in the details and download as PDF or Word.
Employment Contract (England & Wales)
Hiring someone in England or Wales? You are legally required to give them a written statement of employment particulars on or before their first day of work. Our UK Employment Contract template meets all requirements of the Employment Rights Act 1996 and covers working hours, salary, holiday entitlement, notice periods, pension auto-enrolment, confidentiality, and optional restrictive covenants. Download as PDF or Word in minutes.