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 views
0 / 601 Can the board see, on one screen, where you are compliant, where you are exposed, and what is being fixed?
02 Does each audience, senior management, IT, compliance, audit, have a view built from the questions it must answer?
03 Do the dashboards show risk indicators, not activity counts dressed as progress?
The evidence
0 / 604 Is there an evidence model: one row per obligation, naming the records that prove it?
05 Does every class of record have a named owner?
06 Are evidence retention periods set by decision, tied to your sector's audit and limitation realities, not by habit?
The retrieval
0 / 607 For any claim you make about compliance, can the records behind it be produced within one working day?
08 Have you tested that retrieval end to end, recently, with the clock running?
09 Are notice versions, consent artefacts, request closure records, deletion logs and drill reports all retrievable without digging through inboxes?
The response
0 / 610 Is there an inspection-response playbook: who receives an inspection, who gathers evidence, who approves responses, and how fast each class of record can be produced?
11 Is there a reporting calendar that actually runs: standing reports, their audiences, their cadence?
12 Are audit observations tracked to closure, with the closure records kept?
| Score | Where you stand | What to do next |
|---|---|---|
| 0 to 8 | Exposed | Compliance claims rest on memory. Build the evidence model first; the dashboards can wait a week. |
| 9 to 16 | Halfway | Records exist but retrieval is slow or views are decorative. Run the one-day test below. |
| 17 to 21 | Strong base | Rehearse the inspection playbook with a mock request. |
| 22 to 24 | Leading | Keep the evidence model in step with every new obligation the change-watch routes in. |
Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.
What this is
Two things working together. Reporting and dashboards: board, senior management, IT, compliance and audit each get a view of compliance status, risk indicators and remediation progress relevant to their role. And the evidence base: behind every claim of compliance, producible records. Notices shown, consents captured, requests handled, deletions executed.
The framework: four moves
Move 1: Design the views from the questions. What must the board be able to answer? What must IT see daily? What must compliance track weekly? Build each dashboard from those questions, not from the charts the tooling offers.
Move 2: Build the evidence model. For each obligation, name the records that prove it: notice versions for notice, artefacts for consent, closure records for requests, deletion logs for erasure, drill reports for breach readiness. One row per obligation, each with an owner.
Move 3: Set the reporting calendar. What is reported, to whom, how often: board reporting, DPO office reviews, regulator-facing reports where sectoral rules require them.
Move 4: Write the inspection playbook and test retrieval. Roles, routes and clocks for answering inspections and audits. Then test: pick a claim, produce the records, time it. Evidence kept too briefly fails an audit; kept forever it inflates risk, so tie retention to decision, not habit.
Template: the evidence model
One row per obligation. Copy this and fill it in.
| Obligation | The records that prove it | Where they live | Owner | Kept for | Last retrieval test |
|---|---|---|---|---|---|
| Example: notice before consent | Notice versions with dates, per channel and language | Notice store | DPO office | Life of use + required period | |
| Example: valid consent | Consent artefacts, exportable | Consent store | Digital | Relationship + required period | |
| Example: erasure on time | Deletion run logs, including processors | Deletion log store | Ops | Per sector limitation | |
The downloadable file adds the full obligation list and a column guide.
What good looks like at the end
You should have: dashboard designs per role built from real questions, a complete evidence model, an inspection playbook, and a reporting calendar that actually runs.
The live test: pick one compliance claim, say "consent is captured on all channels", and produce the records that prove it within one working day. Then do the same for "deletion happens on schedule". The claims that cannot be evidenced in a day are the gaps.
Where enterprises go wrong
- Dashboards as decoration: activity counts instead of risk indicators.
- Evidence assembled at audit time, from inboxes and memories.
- Confusing supporting an audit with conducting one. Independent audits are a separate assurance activity; this page is about being ready for them.
- Evidence retention set by habit rather than by decision.
The decisions to make
- Dashboard tooling: the privacy platform's views or your existing business intelligence stack.
- Which risk indicators matter at board level.
- Evidence retention periods per record class.
- How audit support is bounded, and how it is priced if external help provides it.
Next step
Staying compliant as everything changes, the discipline that keeps all of this true next year. If you need help with any of this, write to us and we will help.