Inventory
Creating the RoPA: how the record becomes a steering instrument
A good record reflects real processing and links legal basis, data flows, recipients, deletion, risks and the people responsible.
9 minute read · Content as of 21.07.2026
Cut activities along stable purposes
Entries that are too coarse, such as “HR”, hide different purposes and legal bases. Entries that are too fine-grained, at the level of screens or tables, are barely maintainable. A workable cut describes a purpose the business understands, with stable data flows.
Upkeep comes from connections to your processes
The record stays current when new applications, service providers, projects and changes automatically trigger a data protection review. An annual round of calls alone often discovers relevant changes too late.
- business purpose and responsible role
- categories of data subjects and data
- recipients, third-country relevance and processors
- deletion logic, technical and organisational measures, risks and last review
Sources used
- General Data Protection Regulation (EU) 2016/679 · EU · check the consolidated version
- Short papers of the Datenschutzkonferenz · DSK
- Privacy management, RoPA, DPIA and incident templates · KaitoSec