- At least quarterly. No more than three months should pass between reviews. It is also sensible, though not required by the standard, to review when your AI use changes.
- Reviewed and updated. Reading the register is not reviewing it. If nothing changed, it helps to say why, although guardbook does not require a note for a risk marked No change.
- By the right people. Whoever actually decides how your firm uses AI, not whoever has a spare afternoon.
Running a review
1
Fix the dates in advance
guardbook works out when your next review is due: three months after the last signed review. It shows on your dashboard and in reminder emails. About two weeks before, guardbook prepares the review and flags what to look at. Still book the meeting with the people who make the decisions.
2
Work through every risk that is not Closed
That includes Mitigated and Accepted risks, and guardbook asks you to mark each one No change or Updated. For each one, ask whether the scores still hold, whether the controls are actually operating, and whether the status is still accurate. Open a risk from the register to see its full record.
3
Look at what has changed around the register
New tools on the Tool Register usually mean new risks. Rejected outputs in the Oversight Log often point at a risk that is scored too kindly. A near miss that never made it into the register is the most valuable input a review gets.
4
Update the register, do not just discuss it
Change the scores that moved. Move statuses that no longer hold. Add what is missing. Use Edit risk on the review screen first (it opens in a new tab), then mark the risk Updated with a short note of what changed.
5
Sign the review in guardbook
Choose who carried it out, set the date and write a short summary. If others attended, name them in the summary. guardbook does not check who you choose, so pick someone who makes decisions about your firm’s AI use.

