Exception logs work when they answer four questions: what was supposed to happen, what happened instead, who decided to continue or stop, and what compensating control was used. Vague apologies (“delay due to busy day”) age poorly because they explain nothing.
Link, don’t bury
Reference the exception ID inside the main Offline Wallet Compliance Note. Burying deviations in a separate chat thread is how reviewers lose trust in the primary document.
Close the loop
When the compensating control ends, write a closure line with a timestamp. Open-ended exceptions make the whole note look unfinished. For structured practice, see the Exception Log Craft add-on on the courses page.