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 structured core is there: centralised data flow mapping feeding Article 30 report generation, Article 35 assessments documented with records, and processor and vendor management under Article 28 with contracts kept in one interface, on top of a knowledge-graph core that implies the connected model I want for reuse across a client book. We found no public information on TOMs assigned to processing activities, legal bases linked in the record, DPIA need derived from the record, or a multi-client set-up for an external data protection officer practice, which keeps it below the top of the scale. 1 3 7 8