A data protection impact assessment (DPIA) is a documented risk analysis required by Article 35 of the GDPR before processing that is likely to result in a high risk to individuals. It describes the processing, tests necessity and proportionality, assesses risks and sets measures, and ends with a management decision. In Morocco, Law 09-08 does not impose a DPIA, but one strengthens a CNDP authorisation request.
- Required by Article 35 for processing likely to cause high risk
- Two or more criteria from the European list usually trigger it
- Six steps from description to management decision
- Do it before launch, while changes are still cheap
- In Morocco it is good practice and supports CNDP authorisations
01In brief
An impact assessment is needed when treatment is likely to create a high risk to people's rights and freedoms.
The decision depends on the context, scale, data, surveillance and vulnerability of people. A tool or sensitive data does not automatically trigger the same conclusion in all cases.
02What to prepare
- Objective and scope of the processing or mission.
- Actors, tools, suppliers and flows concerned.
- Documents, contracts and decisions already available.
Talk to a DPO for 30 minutes, free of charge: they tell you what applies to your company and where to start.
03The criteria that trigger a DPIA
Article 35 of the GDPR requires a data protection impact assessment when processing is likely to result in a high risk. European guidelines list nine criteria; processing that meets at least two of them generally requires a DPIA:
- Evaluation or scoring of people, including profiling.
- Automated decisions with legal or similarly significant effects.
- Systematic monitoring, for example of employees or a public space.
- Sensitive or highly personal data.
- Large-scale processing.
- Matching or combining datasets.
- Vulnerable people: employees, patients, children.
- Innovative use or new technology.
- Processing that prevents people from exercising a right or using a service.
04What a DPIA contains
- Description of the processing: purposes, data, people, recipients, retention and tools.
- Necessity and proportionality: legal basis, minimisation, information and individuals’ rights.
- Risk analysis: unauthorised access, unwanted modification, loss of data, and their consequences for people.
- Measures: technical and organisational measures that bring the risk to an acceptable level, with owners.
If a high risk remains despite the measures, the supervisory authority must be consulted before the processing starts (GDPR Article 36).
05When should it be done?
A DPIA is carried out before the processing starts, ideally while the project is being designed, when a technical choice or a vendor can still be changed. It must then be reviewed when the processing changes significantly: new purpose, new data, new vendor or a change of scale.
06What about Morocco?
Morocco’s Law 09-08 has no mechanism identical to the GDPR DPIA. Some processing does require prior authorisation from the CNDP, particularly when it involves sensitive data. For a Moroccan company subject to the GDPR, for example because it works for European clients, the DPIA remains the reference method for documenting risk.
07A practical method in six steps
| Step | Question | Output |
|---|---|---|
| 1. Describe | What does the processing do, with which data and tools? | Description sheet |
| 2. Justify | Is each data item necessary and proportionate? | Reduced data list |
| 3. Identify risks | What could happen to individuals? | Risk list |
| 4. Evaluate | How severe and how likely? | Risk levels |
| 5. Reduce | Which measures lower each risk? | Measures plan |
| 6. Decide | Is the remaining risk acceptable? | Signed decision |
08Rating a risk simply
| Low likelihood | High likelihood | |
|---|---|---|
| Low severity | Low risk | Medium risk |
| High severity | Medium risk | High risk: measures required before launch |
A useful DPIA is often only a few pages. What matters is the decisions taken, not the weight of the document.
09Example: tracking delivery drivers (illustrative)
A logistics company wants real-time location tracking for its drivers. The DPIA finds two high risks: continuous monitoring of employees, including breaks, and over-broad access to trip histories. The measures chosen are tracking only during working hours, a pause button, short history retention, access limited to dispatchers and a clear written notice to drivers. The CNDP filing then builds on this analysis.
10Who takes part
- The business owner of the project, who knows the need
- IT, for tools, security and hosting
- The DPO or adviser, for method and opinion
- Management, which validates the decision
- Where possible, representatives of the people affected, such as employees
11Common measures that reduce risk
- Collect less data
- Limit who can access it
- Shorten retention
- Encrypt sensitive data
- Give clear notice and offer an alternative where possible
- Log access and review the logs
12DPIA and the CNDP in Morocco
Where Moroccan law requires prior authorisation, for example for biometrics, health data or certain transfers, the CNDP examines whether the processing is proportionate. A DPIA gives you the material that review looks for: why each data item is needed, which risks you identified and which measures reduce them. It makes the file stronger and reduces requests for additional information.
13Mistakes to avoid
- Doing the DPIA after launch
- Leaving it to IT alone
- Listing risks without choosing measures
- Forgetting to inform the people concerned
- Never revisiting it when the project evolves
14When a DPIA is not needed
Plenty of processing is ordinary and low risk: a standard customer database, routine payroll or a simple contact form. For these, the record of processing and standard security measures are usually enough. A DPIA becomes proportionate when the processing combines several risk factors, such as monitoring, sensitive data and scale.
If you are unsure, do a short screening: list the nine European criteria, tick those that apply, and write down your conclusion. A documented decision not to carry out a DPIA, with reasons, is better than silence.
| Situation | DPIA likely? | Why |
|---|---|---|
| Standard HR administration for 30 staff | No | Routine, no monitoring |
| Employee geolocation across a fleet | Yes | Systematic monitoring of employees |
| Biometric access to a data centre | Yes | Sensitive data, new technology |
| Newsletter to opted-in subscribers | No | Low risk |
| Health app for patients | Yes | Sensitive data, vulnerable people |
| Customer scoring for credit decisions | Yes | Evaluation with significant effects |
15What to write down
- The date and the people who took part
- The screening result and the criteria met
- The description of the processing and its purposes
- The risks identified and how they were rated
- The measures decided, with owners and dates
- The management decision and the date of the next review
Keep the DPIA with the record of processing. It will be one of the first documents a customer or authority asks for.
16Maintaining the DPIA over time
A DPIA is a living document. Revisit it when the processing changes, when a new tool is added, when a security incident shows a gap or at a fixed interval such as once a year for the most sensitive activities. Add the changes to the same file so the history is visible.
17More questions answered
Is a DPIA mandatory for all processing?
No. It is required when processing is likely to result in a high risk, typically when it meets at least two criteria from the European list.
Who should carry out the DPIA?
The controller, usually through the business owner with IT and the DPO. An adviser can guide the method.
How long does a DPIA take?
A few days to a few weeks depending on complexity. Start at design stage.
Does a DPIA need to be sent to an authority?
Not in general. If residual risk remains high, the GDPR provides for prior consultation of the supervisory authority.
Is it different from a TIA?
Yes. A DPIA assesses risks of a processing. A TIA assesses whether a transfer to a third country remains protective.
Can you help with a DPIA?
Yes. We run DPIAs as part of our GDPR compliance work, quoted after a free 30-minute call.
Do we need a DPIA if we are only a processor?
The obligation sits with the controller, but a processor must assist. Customers often ask suppliers for the information they need.
Can one DPIA cover several similar processing activities?
Yes, when they share nature, scope and risks. Document the common features and any differences.
18Frequently asked questions
Is a DPIA mandatory for all processing? +
No. It is mandatory for processing likely to result in a high risk. For other processing, a short documented review of the criteria is often enough to justify the decision.
Who should carry out the DPIA? +
The controller is responsible for it. The DPO, if there is one, must be consulted; business teams, IT and processors provide the information needed.
How long does a DPIA take? +
It depends on the complexity of the processing: from a few days for a simple tool to several weeks for a project involving sensitive data and several vendors.
19Boundaries
This content provides general information. It does not constitute legal advice tailored to any particular situation.
Keep reading
GDPR compliance
Audit, record of processing, policies and procedures: your Law 09-08 and GDPR compliance built on your real processing.
See the offer ↗ Free 30-min call ↗