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 Drafted Generalist
The records register is a real database — a guided form with autosave, tracked changes, an automatic risk assessment with a color code, and a searchable filter view — and TOMs, processors and a DPIA assistant are all named modules of the same web-based product. But we found no public information showing a processing activity linked to its processors, TOMs and legal bases in one data model, or a DPIA triggered from the record itself, which is what separates tidy modules from a connected system. 1 2 3 6 11