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
The Article 30 register is a structured module fed by templates, questionnaires or an AI wizard, DPIAs, LIAs and TIAs run through the same questionnaire engine with validatable, exportable reports, and processors with their DPAs are handled through contracts with AI analytics — plus an external-DPO role to steer all clients as if there were only one, which is precisely my practice. We found no public information showing DPIA need derived from the register itself or legal bases modelled inside that connected record, so it stops just short of the register driving the rest. 1 2 6 10