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 Lead Auditor
The record of processing activities is maintained with templates, guided fields, ownership and versioning, includes an export for supervisory authorities, and is linked to asset and vendor data; DPIAs run as a structured module with a risk matrix, and TOMs and Art. 28 processor agreements sit centrally on the same platform with a 4,000+ vendor database. I found no public information showing DPIA need derived from the record, legal bases modelled into it, or multi-client reuse, so this is a well-connected module set rather than one data model driving everything. 12 13 3 9 13