Every breach, block and override, with who owned it.
The Exception Log records every breach of a rule, every block and every override, with the owner. It is part of every Evidence Pack.
Controls are judged by what happens when they are tested, and exceptions are where that shows.
Exceptions are handled informally and forgotten, so patterns go unseen.
of employers have an AI policy at all
CIPD, 2026The benefits of Exception Log.
The people who feel the problem first.
Spot patterns early.
Own and close exceptions.
Evidence of how issues are handled.
Three ways teams use Exception Log.
Record who approved an exception and why.
See repeated breaches by team.
Give the auditor exceptions to review.
Works best alongside.
Register, data-flow map, control matrix and exception log, generated from the record.
See Evidence Packs Control MatrixWhich controls apply, where, and whether they are working.
See Control Matrix LogLog: the record of events.
See Log All of EvidenceA record of what AI saw, produced and who approved it, with reports against the regulations and your policies. Used with Guard.
See the Evidence modulePrices are indicative ranges, confirmed in writing before you commit. Estimates are replaced by your own figures once your health check runs.
See Exception Log working on your business.
First findings within 48 hours of the health check · Audit fee credited against year one