Records & DPIA depth
How this is scored
The DSMS core: records of processing (RoPA/VVT), data protection impact assessments, processor/DPA management and TOMs — how deeply the legal artifacts are modeled and connected.
0 — Document templates in a folder tree; the "register" is a Word file with version numbers in the filename.
3 — A structured RoPA with basic fields and a DPIA questionnaire, but processors, TOMs and legal bases live outside the system.
5 — RoPA and DPIA as linked modules with templates; processor management and TOM assignment exist but are shallow, and group reuse is copy-paste.
8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA triggers derived from the record, reusable group templates, and outputs a supervisory authority accepts.
10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client/mandate capability included, and the documentation is audit-ready without manual assembly.
The IT Integrator
RoPA, DSFA with risk management, AVV and TOM modules all exist, and the RoPA layer is unusually deep — industry template packs of 65-77 activities, group templates, delegation to responsible users, and export as an official register — plus real multi-tenancy from 2 to 46 Mandanten. What's missing is evidence of the connected data model: no statement that activities drive DPIA triggers, TOM coverage or legal bases from one record, so it sits between rubric level 5 and 8. 4 2 3