# Template: compliance calendar and change log

Two working sheets for staying compliant after go-live. Copy both.

## Sheet 1: the compliance calendar

One row per review cycle.

| Cycle | What is reviewed or re-tested | Depth | Owner | Output | Reported to |
| --- | --- | --- | --- | --- | --- |
| Quarterly | Register currency, open findings, vendor changes, request and grievance ageing, deletion run logs | 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, evidence model check | 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 + document updates | DPO office |
|  |  |  |  |  |  |

Column guide:

- **Cycle**: quarterly, annual, or on change. Add cycles your sector's regulators expect.
- **What is reviewed or re-tested**: name the registers, controls and vendors. A review that re-tests nothing confirms nothing.
- **Depth**: spot checks or deep dives, decided per cycle.
- **Owner**: the named role that runs it.
- **Output**: the artefact each cycle must leave behind.
- **Reported to**: where the output lands, ending at the board.

## Sheet 2: the change log

One row per legal or business change.

| Change | Noticed by | Date noticed | What it touches | What was updated | Owner | Closed on |
| --- | --- | --- | --- | --- | --- | --- |
| Example: new notification on a DPDP rule | Change-watch owner | | Consent notice set, timeline reference | Notice v3.3 published; register rows updated | DPO office | |
| Example: new lending product launch | Product team intake | | Register, record of processing, retention schedule | New register rows; retention class added | Product owner | |
|  |  |  |  |  |  |  |

The change log is the proof that the programme tracks the world. A change with no log entry is drift.
