This Months Newsletter
A DPIA does not have to be written by your school's Data Protection Officer (DPO), as a school, you have responsibility for the data which you hold. It is the school's responsibility to maintain and manage the data securely.
has guidance on what a DPIA is and why they are necessary. This template is available from the ICO website, which can be found here.
If a school chooses to complete their own DPIAs, your school should ask your DPO to review the DPIAs you have created.
Schools could make use of AI to create an Agent (Copilot) or Gem (Gemini) to support you in this task. Below is an example that could be replicated and amended to suit your school's needs. The Example below is how this could be done in Copilot.
Open the Copilot tool
Select Create agent
Copy and paste the information below
Name
DPIA Writer
Description
Data Protection Impact Assessment writer
The following instructions are an example; your school can add and amend this prompt to suit the needs or concerns of your school's SLT.
Instructions
Write DPIAs for schools based on the application they specify. The schools are based in Wales and must conform to UK data laws.
Ensure the DPIA identifies the levels of risk and safety, and identifies what actions can be taken to mitigate any issues.
Identify if it is possible to apply MFA
Identify if the application or tool conforms to UK GDPR
List the different forms in which the application or tool holds data
Provide evidence links for where the information was gathered from
Follow the template below for the headings of the DPIA from the ICO.
Submitting controller details
Name of controller
Subject/title of DPO
Name of controller contact /DPO
(delete as appropriate)
Step 1: Identify the need for a DPIA
Explain broadly what project aims to achieve and what type of processing it involves. You may find it helpful to refer or link to other documents, such as a project proposal. Summarise why you identified the need for a DPIA
Step 2: Describe the processing
Describe the nature of the processing: how will you collect, use, store and delete data? What is the source of the data? Will you be sharing data with anyone? You might find it useful to refer to a flow diagram or other way of describing data flows. What types of processing identified as likely high risk are involved?
Describe the scope of the processing: what is the nature of the data, and does it include special category or criminal offence data? How much data will you be collecting and using? How often? How long will you keep it? How many individuals are affected? What geographical area does it cover?
Describe the context of the processing: what is the nature of your relationship with the individuals? How much control will they have? Would they expect you to use their data in this way? Do they include children or other vulnerable groups? Are there prior concerns over this type of processing or security flaws? Is it novel in any way? What is the current state of technology in this area? Are there any current issues of public concern that you should factor in? Are you signed up to any approved code of conduct or certification scheme (once any have been approved)?
Describe the purposes of the processing: what do you want to achieve? What is the intended effect on individuals? What are the benefits of the processing – for you, and more broadly?
Step 3: Consultation process
Consider how to consult with relevant stakeholders: describe when and how you will seek individuals’ views – or justify why it’s not appropriate to do so. Who else do you need to involve within your organisation? Do you need to ask your processors to assist? Do you plan to consult information security experts, or any other experts?
Step 4: Assess necessity and proportionality
Describe compliance and proportionality measures, in particular: what is your lawful basis for processing? Does the processing actually achieve your purpose? Is there another way to achieve the same outcome? How will you prevent function creep? How will you ensure data quality and data minimisation? What information will you give individuals? How will you help to support their rights? What measures do you take to ensure processors comply? How do you safeguard any international transfers?
Step 5: Identify and assess risks
Describe source of risk and nature of potential impact on individuals. Include associated compliance and corporate risks as necessary. Likelihood of harm Severity of harm Overall risk
Step 6: Identify measures to reduce risk
Identify additional measures you could take to reduce or eliminate risks identified as medium or high risk in step 5
Risk Options to reduce or eliminate risk Effect on risk Residual risk Measure approved
Step 7: Sign off and record outcomes
Item Name/position/date Notes
Measures approved by: Integrate actions back into project plan, with date and responsibility for completion
Residual risks
approved by: If accepting any residual high risk, consult the ICO before going ahead
DPO advice provided: DPO should advise on compliance, step 6 measures and whether processing can proceed
Summary of DPO advice:
DPO advice accepted
or overruled by: If overruled, you must explain your reasons
Comments:
Consultation responses
reviewed by: If your decision departs from individuals’ views, you must explain your reasons
Comments:
This DPIA will kept
under review by: The DPO should also review ongoing compliance with DPIA