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 calendar
0 / 601 Is there a monitoring and review calendar: quarterly and annual reviews, each with a defined depth?
02 Does each review re-check registers, re-test controls and re-review vendors, rather than confirm that everything is fine?
03 Do you know what drifts fastest in your environment, systems, vendors, products or people, and does the calendar watch exactly that?
The change-watch
0 / 604 Does a named person own tracking new rules, notifications and sectoral directions?
05 Is each legal development routed to the register, policy or control it touches, with a change log?
06 When the last relevant notification arrived, can you trace who noticed it, what it changed, and where the change is recorded?
The loop
0 / 607 Are your registers, policies, notices and training current as of this quarter, not as of go-live?
08 Is tooling support and patching disciplined, with a log of what changed and why?
09 Do review findings become actions with owners and dates, tracked to closure, and reported upward?
The contract
0 / 610 If you buy ongoing support, are its obligations bounded: regulatory changes, audit support and drills priced or capped consciously, not discovered at invoice time?
11 Is there an answer to "when do we run alone", with capability transferred to internal owners?
12 Would the programme survive the support contract ending next quarter?
| Score | Where you stand | What to do next |
|---|---|---|
| 0 to 8 | Exposed | The programme ended at go-live and decay has started. Set the review calendar and name the change-watch owner. |
| 9 to 16 | Halfway | Reviews happen but the loop leaks: findings without closure, changes without routing. |
| 17 to 21 | Strong base | Run the trace test below on the most recent legal development. |
| 22 to 24 | Leading | Watch the contract: bounded obligations and a real run-alone date keep sustenance honest. |
Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.
What ongoing compliance is
Post-implementation monitoring, reporting and governance for sustained compliance: periodic reviews, support and patch management for the tooling, and a framework that refreshes itself as rules and notifications evolve. The Government has phased this law before; the verified dates live on the dates and timeline page, not in vendor marketing.
The framework: four moves
Move 1: Set the review calendar. Quarterly and annual reviews at minimum, each with a defined depth: what registers are re-checked, which controls are re-tested, which vendors are re-reviewed.
Move 2: Run the change-watch. Someone owns tracking new rules, notifications and sectoral directions, and routes each one to the register, policy or control it touches. Keep support and patching disciplined: post-go-live support for the tooling, patch management, and a log of what changed and why.
Move 3: Close the loop. Policies, notices, training and the record of processing all evolve; every legal or business change lands on a named document with a named owner. Review findings become actions with owners and dates, tracked to closure, and reported upward.
Move 4: Bound the contract and plan to run alone. If you buy ongoing support, read the open-ended clauses carefully. Some support arrangements in this market expect the provider to absorb all regulatory and statutory changes during the term at no extra cost, to support security audits and regulator audits and close out observations without extra charge, and to run periodic drills at no extra cost. These are real costs, whichever side of the contract you are on; price or bound them consciously. And set the date the enterprise runs alone, with the capability transferred.
Template: the compliance calendar
One row per review cycle. Copy this and fill it in.
| Cycle | What is reviewed or re-tested | Depth | Owner | Output | Reported to |
|---|---|---|---|---|---|
| Quarterly | Register currency, open findings, vendor changes, request and grievance ageing | Spot re-tests | DPO office | Review note + action list | DPO, then board report |
| Annual | Full re-assessment, control re-tests, training refresh, contract and support review | Deep | DPO with business owners | Updated registers + roadmap | Board |
| On change | Any new rule, notification, product, vendor or system | Targeted | Change-watch owner | Change log entry + updates | DPO office |
The downloadable file adds the change log columns.
What good looks like at the end
You should have: a running review calendar, a working change-watch with a change log, support with clear service levels and bounded obligations, and review reports showing findings closing.
The live test: take the most recent legal development relevant to you and trace its path. Who noticed it, what did it change, where is the change recorded? If the answer is "nothing yet", the change-watch is the first thing to fix.
Where enterprises go wrong
- Set-and-forget: the programme ends at go-live, and decay starts the next day.
- Reviews that confirm everything is fine without re-testing anything.
- Uncapped obligations in support contracts, discovered at invoice time.
- No answer to "when do we run alone", so support never ends and capability never transfers.
The decisions to make
- Support scope and service levels, and how regulatory change is absorbed and priced.
- Review depth per cycle.
- Audit support: what is included, what is extra.
- When sustenance ends and the enterprise runs alone.
Next step
Back to the gap assessment, because a programme that sustains itself re-assesses on a cycle. If you need help with any of this, write to us and we will help.