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 records model is genuinely connected: a central data inventory carrying the full register of processing activities whose updates propagate system-wide, guided DPIAs with a growing template set including AI-system evaluation, processor contracts managed on the platform, and TOMs such as access controls, encryption and backups documented and reviewed. What I cannot see is legal bases woven into that model, and the multi-entity support speaks of departments, locations and subsidiaries — intra-group, not thirty separate client mandates, which is the distinction that decides my tooling. 9 10 14