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 In-House Counsel
The record of processing activities is deeply evidenced: generated at the push of a button, filled in by delegated department contacts, kept with an edit history, exported as an internal or authority register, and seeded with sector template packs of 65 to 77 activities; DPIAs with risk management, processor agreements with an automatically generated processor register, and TOMs with over 200 text modules are documented, alongside multi-client tiers for external data protection officers. The captured pages do not show a connected model deriving DPIA need from the record, which holds it just under the fully connected level. 2 4 4 3