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
This is the connected model I bill hours out of: the record of processing activities synchronises automatically with the impact assessment, the measures and the vendor register, impact-assessment need is derived by automated threshold analysis, and the deletion concept is generated from the record itself. Processor records under Article 30(2) sit beside controller records, more than 200 legally reviewed processing-activity templates and 150 vendor templates carry across companies and locations with configurable approval per company, and everything from the processor agreements to the record goes to the supervisory authority at a click. Only a continuously maintained, standing audit-ready state keeps it from the top mark. 7 8 9 7