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 privacy suite documents the record of processing activities, technical and organisational measures and inquiries in a traceable, versioned way, and the vendor's own guidance on data protection management systems covers impact assessments with scoring plus processor contracts filed in the system — that reads as a real register, not a folder of Word files. I found no public information showing impact assessments are triggered from the record itself or that legal bases are linked into one connected data model, and the deeper DSMS descriptions sit on a knowledge page rather than product claims, so I land at solid but not connected. 2 2 4