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 documented with activities, legal bases, data categories and systems mapped in one place, processors and their data processing agreements tracked under Article 28, and impact assessments run per Article 35 with decisions captured and a maintained audit trail. Risks and mitigating controls connect to processing activities, systems and vendors, which reads as a connected data model rather than parallel folders. We found no public information on assessments being triggered from the record itself, on reusable templates across companies, or on multi-client use by external data protection officers, so it stops short of the system-of-record level. 3 3 3 2 1