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 In-House Counsel
The register of processing activities is the backbone: an automated Schwellwertanalyse derives DPIA need from the record, vendors link automatically to the register, and TOMs — including process-specific measures — are connectable to the SDM guarantee goals, with legal bases under Art. 6 and 9 pre-built and legally reviewed. Registers for Art. 30(2) processors run in the same workflow across companies and locations with configurable approval, and at a button press the whole file from processor agreements to the register goes to the supervisory authority. That is a connected data model I can defend to an authority. 7 8 9 7