Records & DPIA depth
How this is scored
The DSMS core: records of processing activities (RoPA/VVT, Art. 30 DSGVO), data protection impact assessments (DSFA, Art. 35), processor and DPA management (AVV), and technical and organisational measures (TOMs) — how deeply the legal artefacts are modelled and connected.
0 — Not a privacy management tool; at most a set of document templates with no structured records.
3 — A structured record of processing activities with templates, and a DPIA questionnaire or checklist.
5 — Records of processing and DPIAs as modules with templates, processors and their DPAs recorded, and TOMs documented and assigned to processing activities.
8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA need derived from the record, reusable templates across companies, and outputs (Art. 30 register, DPIA report) ready for a supervisory authority.
10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client capability for external data protection officers, and the documentation is audit-ready without manual assembly.
The External DPO
This is the right shape for a thirty-mandate practice: a record of processing activities built on industry-specific templates with Excel/CSV import, data protection impact assessments, explicit multi-client capability (Mandantenfähigkeit), and the record of processing activities generated as a report at a click on one shared data basis with ISMS and emergency planning. Protection needs, risk assessment and ISO 27001 measures assigned from imported assets point to a connected model rather than isolated forms. I hold it below the top because we found no public information on processors with their data processing agreements modelled against processing activities, on legal bases, or on the DPIA need being derived from the record itself. 2 2 8