Exception logs that actually close
An open item without an exit criterion is a wish, not a control. Write the done-state when you open the row.
Good exception logs answer four questions in one row: what broke, who owns the fix, how severe it is for sign-off, and what “closed” looks like. Miss any one and the item drifts into next month’s folklore.
Severity that controllers believe
Avoid five-color rainbows. Three levels suffice: blocks sign-off, needs disclosure in the packet, or monitoring only. Tie severity to workflow impact—failed approval path, missing timestamp integrity—not only to dollar amount.
Close criteria examples
“Journal posted” is weak. “Journal posted, approver confirmed in system ID X, and sampling frame updated with replacement note” is closeable. External auditors following a walkthrough can replay that path.
Carry-forward discipline
Anything still open at Day +2 must either escalate into the next owner map or convert into a tracked remediation with a date. Silent carry-forwards are how close theater returns.