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 External DPO
The RoPA is genuinely driven by the estate: a live data map feeds systems, data categories, purposes and vendors into dynamic Article 30 records, DPIAs and PIAs arrive pre-populated with real system and vendor data, and an audit-ready register exports as CSV or PDF — that is a connected model close to what I bill for. What I cannot credit from the captured pages is the rest of the legal toolkit: we found no public information on a TOM module, legal bases linked to records, or DPA management beyond a vendor inventory, and multi-brand support is documented for one company's brands rather than an external officer's client book. 2 3 4