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 model is genuinely connected: each processing activity carries its systems, safeguards and data processing agreements as a graphical relationship view, legal bases sit in the same structured form, and a threshold analysis derives the Article 35 need from the record itself, which an external data protection officer can run across hundreds of clients. Deletion classes hang off the processing activities, and status reports, procedure files and the Bavarian supervisory-authority questionnaire come out at a button push. That approaches a system of record; I hold a point back because the DPA-to-record linkage rests on name matching with a manual step for everything that does not match. 16 21 11 16