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 processing register is documented as a dynamic system where changes to processes or assets update automatically, DPIAs run with in-system data-flow visualisation, processors are managed with contract tracking, TOMs are centrally documented with customisable authority reports, and third-country transfers are covered by transfer impact assessments. Multi-tenancy with inheritance including template tenants, rolled out from a master client to any number of sub-clients, is exactly the multi-mandate capability I need; I found no public information on DPIA need being derived from the register or on legal bases being modelled. 1 2 3 4