# Template: rights request and grievance log

One row per request or grievance, from intake to closure. The log is both the workflow and the evidence. Copy it and fill it in.

| ID | Type | Channel | Received | Verified | Decision and reasons | Responded | Closed | Days taken |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Example: R-104 | Access summary | App | | | Granted in full | | | 6 |
| Example: R-105 | Erasure | Branch | | | Partially granted; statutory records retained, reason recorded | | | 9 |
| Example: G-21 | Grievance, marketing after withdrawal | Email | | | Upheld; suppression list fixed, apology sent | | | 3 |
|  |  |  |  |  |  |  |  |  |

Column guide:

- **ID**: sequential, so nothing goes missing silently.
- **Type**: access summary, correction, erasure, nomination, grievance.
- **Channel**: where it arrived. Volumes by channel tell you where to automate.
- **Received**: the date the clock starts.
- **Verified**: how identity was confirmed, and that the check was proportionate.
- **Decision and reasons**: granted, partially granted, or refused, with the reasons in one line. A reasoned refusal belongs here as much as a grant.
- **Responded**: when the person got the answer, against your published period.
- **Closed**: when execution finished, including erasure reaching archives, backups and processors.
- **Days taken**: feeds the ageing report to the DPO office.

What each closure must be able to show: what was requested, what was verified, what was found, what was decided, what was done, and when. Without that record, a handled request looks exactly like an ignored one.
