Self-assessment
Score yourself
Answer each question honestly. Yes = 2, Partly = 1, No = 0. Keep a running total.
Your score
0/ 24
0 of 12 answered
Not scored yet
The register
0 / 601 Is there one register with a row for every processing activity in the enterprise?
02 Does each row record the purpose, the legal basis, the data categories, the retention period and the system of record?
03 Was the register built from discovery and mapping, not from what departments remembered in a workshop?
The upkeep
0 / 604 Does every row have a named owner?
05 Does every new project, product, vendor or report update the register at intake?
06 Is there a gate: no new processing goes live without a register entry?
07 Do owners confirm their entries on a cycle, with the confirmations recorded?
The assessment
0 / 608 Do you have a written trigger list: the events that force an impact assessment, such as high volume, sensitive data, new technology, profiling, children's data, or after an incident?
09 Does your method run in order: describe the processing, test necessity and proportionality, assess risks to people, set mitigations, state the residual risk?
10 Does every assessment end in a recorded decision, go, change or stop, with a named approver?
The proof
0 / 611 Could you start a periodic assessment and independent audit cycle quickly if you were notified as a Significant Data Fiduciary?
12 Pick a processing activity launched in the last six months: does it have a register entry, and an assessment if it triggered one?
| Score | Where you stand | What to do next |
|---|---|---|
| 0 to 8 | Exposed | There is no living register, so every downstream duty is guessing. Populate from the discovery and mapping groundwork. |
| 9 to 16 | Halfway | The register exists but drifts. The intake gate and owner confirmations are the fixes. |
| 17 to 21 | Strong base | Run the live test below on your newest processing, and complete assessments for your riskiest activities. |
| 22 to 24 | Leading | Align the assessment cycle with your audit cycle; you are ready for a Significant Data Fiduciary notification. |
Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.
What these two instruments are
The record of processing activities, the RoPA, is the register of every processing activity in the enterprise: its purpose, its legal basis, the categories of data it uses, how long the data is kept, and the system of record. The record of processing page introduces the register; this page is about running it as a living instrument. Notices, consent design, breach response, retention and audit evidence all read from it.
A Data Protection Impact Assessment, a DPIA, is a structured assessment of how a processing activity could harm people, and what reduces that risk. For Significant Data Fiduciaries it is a legal duty on a cycle. For everyone else it is good practice before launching anything high-volume, sensitive or new in kind.
The framework: four moves
Move 1: Populate from real groundwork. Build the register from discovery and mapping, not workshop memory. One row per processing activity: purpose, legal basis, data categories, retention period, system of record, owner. The discovery, classification and mapping page covers that work.
Move 2: Give every row an owner and a gate. A register with no owners is a snapshot, not a register. Keep it alive as a byproduct of change: every new project, product, vendor or report updates it at intake, and no new processing goes live without an entry. A yearly refresh is archaeology.
Move 3: Assess before the risky launches. Set the triggers in advance. When one fires, run the method in order: describe the processing; test necessity and proportionality; assess the risks to people, not to the enterprise; set the mitigations with owners; state the residual risk honestly.
Move 4: Decide, record, review. Every assessment ends in a decision, go, change or stop, with a named approver and the reasons recorded. Owners confirm their register entries on a cycle, and the DPO office reviews the whole register periodically.
Templates: the register row and the assessment sheet
The register, one row per processing activity:
| Activity | Owner | Purpose | Legal basis | Data categories | Whose data | Kept until | System of record | Who receives it | Reviewed on |
|---|---|---|---|---|---|---|---|---|---|
| Example: credit scoring | Head of lending | Assess loan applications | Consent | Identity, income, repayment history | Customers | Relationship + 3 years | Lending app | Credit bureau |
The assessment sheet, one per triggered activity:
| Step | Your entry |
|---|---|
| 1. The processing described | What data, whose, from where, for what |
| 2. Necessity and proportionality | Is the processing needed, and the data limited to what the purpose needs |
| 3. Risks to people | Possible harms, likelihood, severity |
| 4. Mitigations | What reduces each risk, and who owns each one |
| 5. Residual risk | What remains, stated honestly |
| 6. Decision | Go, change or stop; named approver; reasons |
Both are available as downloadable files.
What good looks like at the end
You should have: a populated register with owners and review dates, an assessment template in actual use, completed assessments for your riskiest processing, and a review cycle that keeps both current.
The live test: pick a processing activity that launched in the last six months. Find its register entry and, if it triggered one, its impact assessment. If neither exists, your intake gate is not working.
Where enterprises go wrong
- A register written once for a consultant's report and never touched again.
- Assessments done after launch, as paperwork for a decision already made.
- Risk findings with no decision attached. The assessment does not fix anything; acting on it is a separate, recorded decision.
- Tooling bought before the register's structure is settled. The tool should hold your register, not define it.
The decisions to make
- Document-based registers or tooling. Volume and change rate decide.
- Depth of risk scoring and tiering on top of the register.
- The review cadence and the intake gate design.
- Alignment of the assessment cycle with your audit cycle, essential if you are preparing for a possible Significant Data Fiduciary notification.
Next step
Preparing for a personal data breach, where the register becomes your fastest source of answers. If you need help with any of this, write to us and we will help.