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 Drafted Generalist
Data Mapping & Risk Manager keeps records with purpose, legal basis and retention, links system, vendor and process records, and automatically triggers a DPIA when high-risk processing is detected — that is exactly the software-knows-the-law-so-I-don't-have-to I need. Article 30 reports come out on demand, inherent and residual risk are scored, and a template repository pre-populates the most common systems and vendors so I am not building a register from a blank page. I found no public information on technical and organisational measures being modelled or on multi-client use for external data protection officers, which is why it stays where it is. 4 5 9