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 IT Integrator
The record model is genuinely connected: each processing activity shows its systems, safeguards and data processing agreements in a graphical relationship view, contracts are matched to data recipients automatically, and a built-in screening analysis on the record drives the Art. 35 DPIA necessity assessment. Multi-client capability for external data protection officers is real — new tenants in under three minutes with strict separation — and status reports, procedure files and the BayLDA questionnaire come out at the push of a button. Where names do not match, missing contract links are still closed by hand, which keeps this just short of a fully self-driving system of record. 16 2 11 16 17 12