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 four artefacts I audit against are all modelled — the register of processing activities records data, purposes and the systems involved, processor contracts are managed on the platform, TOMs are documented with periodic review, and DPIAs run on guided templates including AI-system assessment — and the central inventory propagates updates across the whole system, which is more than isolated modules. The captured pages do not show the legal basis wired into the record or DPIA need derived from it, so I stop short of calling the data model fully connected. 9 10 14