---
title: "DPIAs and Records of Processing | Pitch, European law firm"
description: "Your Article 30 record of processing set up and kept current, and data protection impact assessments under Article 35 carried out before a risky project starts."
url: https://pitch.law/solutions/dpia-and-records-of-processing
---

[pitch](https://pitch.law/) [Solutions](https://pitch.law/solutions) [Data Protection](https://pitch.law/solution-categories/privacy)

# DPIAs and Records of Processing

Your Article 30 record of processing set up and kept current, and data protection impact assessments under Article 35 carried out before a risky project starts.

- - By [Bart Lieben](https://pitch.law/team/bart-lieben), Attorney-at-Law
  - 19 November 2026

- Updated

  19-11-2026

## The question

You are about to launch something new: a camera system, an app that tracks drivers, a scoring tool for job applicants, a customer analytics platform. Someone asks whether you need a DPIA. And when you look for the processing in your record, it turns out the record was last updated two years ago.

Two GDPR documents carry most of the weight here. The record of processing activities under Article 30 is the inventory: for each processing activity, the purposes, the categories of data subjects and personal data, the recipients, transfers to third countries, the envisaged time limits for erasure and a general description of security measures. It has to be available to the supervisory authority on request.

The data protection impact assessment under Article 35 is the deeper check for one processing. It is required where processing is likely to result in a high risk to the rights and freedoms of individuals. Article 35(3) names three cases in particular: systematic and extensive evaluation of people based on automated processing, including profiling, with legal or similarly significant effects; large-scale processing of special categories of data or data on criminal convictions; and systematic monitoring of a publicly accessible area on a large scale. Supervisory authorities publish lists of processing that always needs a DPIA (Article 35(4)), and the Belgian Data Protection Authority has adopted such a list. Processing that is not on the list can still need one.

## Our approach

We start with the record, because a DPIA builds on it. If you have a spreadsheet, we import it into [our register](https://pitch.law/technologies/privacy-register), which shows per entry which required elements are missing. If you have nothing, we build the record from short interviews with the people who run each process. Your team completes and maintains the entries in the [client portal](https://pitch.law/technologies/client-portal), with an explanation next to each field that names the article behind it. The lawyer reviews and approves every entry, and each approved version is dated. [What a record of processing must contain](https://pitch.law/academy/gdpr-records-of-processing-activities-ropa-what-you-need-to-know) gives the background.

For a new or changed processing, we first screen. A short questionnaire records the data, the scale, profiling, monitoring, vulnerable individuals and new technology, and checks them against Article 35(3) and the Belgian list. The outcome, with the criteria that triggered it, is confirmed by the lawyer. If no DPIA is needed, the reasoning is stored, because that choice should be documented as well.

When a DPIA is needed, we carry it out with your project team in [our DPIA function](https://pitch.law/technologies/digital-data-protection-impact-assessment), as a working record. It follows the minimum content of Article 35(7): a description of the processing and its purposes, an assessment of necessity and proportionality, an assessment of the risks to individuals, and the measures to address them. The description starts from the register entry, so the same facts are not written twice. We focus on harm to people, such as discrimination, loss of control over data or exposure of sensitive information.

If a high risk remains after the measures, Article 36 requires you to consult the supervisory authority before the processing starts. We prepare that consultation and the file that goes with it.

We work on our own technology, with our own AI, and a lawyer reviews every entry and every assessment before it is final. Where an AI system is involved, the DPIA also feeds the work under the AI Act ([AI Act meets GDPR](https://pitch.law/academy/ai-act-meets-gdpr-where-frameworks-overlap)), and where the project is a website or app, we often start with a [website technology audit](https://pitch.law/academy/website-technology-audits-and-gdpr).

## What you get

- A record of processing activities, approved by a lawyer, exportable as HTML or PDF and ready to hand to the authority.
- A list of open points: entries without a retention period, transfers without a recorded safeguard, missing elements.
- A documented screening for each new or changed processing.
- A completed DPIA as a dated record, with risks, measures with owners and the residual risk.
- Where needed, a prior consultation file for the supervisory authority.
- Review dates, so register and DPIA are revisited when the processing changes.

Limits apply. A DPIA records how risks were assessed and reduced. It does not make the decision to go ahead for you, and it cannot remove a risk that the design of the project creates. If the honest conclusion is that a project needs to change, we will say so.

## Next step

Send us a short description of the project or processing you are planning, and your current record if you have one. We will tell you whether a DPIA is needed and what the record is missing.

[Schedule a meeting](https://pitch.law/schedule) or [contact us](https://pitch.law/contact-us).

## In short

- Record of processing with every element Article 30(1) lists
- Screening that shows whether a DPIA is needed, and why
- DPIAs with risks, measures and residual risk documented
- Prior consultation with the authority prepared where needed
- Register and assessments linked, so facts are written once
- Reviewed by a lawyer

## Our proprietary Legal Tech

- [Technology](https://pitch.law/technologies/privacy-register)
  ### [Records of Processing and Compliance Registers](https://pitch.law/technologies/privacy-register)
  [One register engine for the GDPR record of processing activities and for the AI Act, NIS2 and DORA registers, with article references, evidence and attorney or DPO approval.](https://pitch.law/technologies/privacy-register)
- [Technology](https://pitch.law/technologies/digital-data-protection-impact-assessment)
  ### [Data Protection Impact Assessment](https://pitch.law/technologies/digital-data-protection-impact-assessment)
  [Guided data protection impact assessments, kept as working records that you and your attorney complete together in the client portal.](https://pitch.law/technologies/digital-data-protection-impact-assessment)
- [Technology](https://pitch.law/technologies/client-portal)
  ### [Client Portal](https://pitch.law/technologies/client-portal)
  [A secure place where you follow your matters, instruct us on deadlines, work on registers with us and see your IP portfolio, in the same environment as our work.](https://pitch.law/technologies/client-portal)

## Background reading

- [Academy](https://pitch.law/academy/gdpr-records-of-processing-activities-ropa-what-you-need-to-know)
  ### [Records of Processing Activities (RoPA)](https://pitch.law/academy/gdpr-records-of-processing-activities-ropa-what-you-need-to-know)
  [What Article 30 GDPR requires you to record, who must keep a register, and how to keep it useful.](https://pitch.law/academy/gdpr-records-of-processing-activities-ropa-what-you-need-to-know)
- [Academy](https://pitch.law/academy/ai-act-meets-gdpr-where-frameworks-overlap)
  ### [AI Act Meets GDPR: Where the Two Frameworks Overlap](https://pitch.law/academy/ai-act-meets-gdpr-where-frameworks-overlap)
  [How the AI Act and the GDPR apply side by side to the same AI system: roles, impact assessments, automated decisions, transparency, data quality and special categories.](https://pitch.law/academy/ai-act-meets-gdpr-where-frameworks-overlap)
- [Academy](https://pitch.law/academy/website-technology-audits-and-gdpr)
  ### [Website Technology Audits and the GDPR](https://pitch.law/academy/website-technology-audits-and-gdpr)
  [What a website technology audit examines, why privacy notices and actual data flows drift apart, and which legal duties it checks.](https://pitch.law/academy/website-technology-audits-and-gdpr)

## More in Data Protection

- ### [GDPR Compliance Programme](https://pitch.law/solutions/gdpr-compliance-programme)
  [A GDPR programme built from what your organisation really does with personal data, from a gap audit and records of processing to policies, roles, training and follow-up.](https://pitch.law/solutions/gdpr-compliance-programme)
- ### [Data Processing Agreements](https://pitch.law/solutions/data-processing-agreements)
  [Article 28 GDPR agreements drafted, reviewed and negotiated for controllers and processors, including sub-processors and international transfers.](https://pitch.law/solutions/data-processing-agreements)
- ### [Transferring Personal Data Outside the EEA](https://pitch.law/solutions/international-data-transfers)
  [Transfers of personal data outside the EEA mapped and given a lawful basis under Chapter V GDPR, with adequacy checks, standard contractual clauses and transfer impact assessments.](https://pitch.law/solutions/international-data-transfers)
- ### [Cookies and Direct Marketing](https://pitch.law/solutions/cookies-and-direct-marketing)
  [Cookie banners, consent records and e-mail marketing set up under the ePrivacy rules, Belgian law and the GDPR, starting from what your website and mailing tools really do.](https://pitch.law/solutions/cookies-and-direct-marketing)
- ### [Handling Data Subject Requests](https://pitch.law/solutions/data-subject-requests)
  [Access, erasure, objection and other requests under Articles 12 to 22 GDPR handled within the deadline, with identity checks, exemptions weighed and a reviewed answer.](https://pitch.law/solutions/data-subject-requests)
- ### [Data Protection Officer as a Service](https://pitch.law/solutions/dpo-as-a-service)
  [An external Data Protection Officer who advises, monitors and documents your GDPR compliance, with a register, calendar and portal behind the advice.](https://pitch.law/solutions/dpo-as-a-service)

## Let’s talk

Tell us what you’re working on. We’ll get the right person on it and reply within one business day. The first chat is free.

[Schedule a meeting](https://pitch.law/schedule)
