Exceptions are judgment, not errors
No lending policy anticipates every member. A long-time member with a thin file. A used vehicle a few points over the LTV line, with a strong co-signer. A term a few months past the limit on a model that holds its value. The policy sets the line, and the underwriter’s job includes knowing when to step over it. A credit union with no exceptions has a policy nobody is reading.
The problem is not exceptions. It is exceptions nobody can count.
The exception that was never recorded
Here is how most exceptions are made. The underwriter checks the file, finds the LTV over the limit, decides the co-signer carries it, and approves. The note says strong co-signer, approved. It does not say which rule, by how much, or under what authority, because the underwriter knew all of that and was busy.
Six months later the board asks how many LTV exceptions were made this quarter, and how they are performing. The honest answer is that someone would have to read the files. The examiner asks the same question with less patience. And the second rule that file failed, the one the underwriter never reached because the review stopped at the first, was never an exception at all. It was simply missed.
Maximum loan-to-value, used vehicles
- Policy limit
- 90% of retail value
- In the file
- 96.4% · 6.4 points over
- Approved by
- Senior underwriter, under the authority the policy grants for exceptions up to ten points
- Reason
- Co-signer with twelve years of membership and a clean history. Vehicle under two years old.
- Also failing
- No other rule
- Policy revision
- Sep 2026
What a recorded exception holds
- The rule, by name, as it reads in the policy.
- The limit and the value, so the gap is a number, not an adjective.
- Who approved it, and under which level of authority the policy grants.
- The reason, in a sentence, with the compensating factors named.
- The policy revision the file was checked against, so an exception to last quarter’s limit is not confused with a breach of this quarter’s.
- Every other rule the file failed, so an exception on one rule does not hide a miss on another.
What counting makes possible
Once exceptions are records rather than notes, three conversations change.
The policy conversation. A rule excepted on most of the files it touches is not an underwriting problem. It is a limit set too tight for the members the credit union actually serves, and the count is the evidence the board needs to revisit it.
The coaching conversation. Exceptions by underwriter show who is stepping over the line on judgment and who has learned a workaround. Both are worth knowing, and neither is visible today.
The examiner’s conversation. The question becomes a list, not a search. Which files, which rules, who approved, why, and how they are performing.
Every rule checked makes every exception visible
Exceptions go unrecorded because rules go unchecked. When every rule is checked on every file before the underwriter looks, every approval outside a rule is already visible as one the moment it is made: the rule, the value, the gap. The underwriter adds the reason and the authority. And the write-up for a decline carries every failing rule, not the first one, which is what the adverse-action notice needs.
Where Sidecar fits
Sidecar checks every file that reaches an underwriter against the whole lending policy and shows its work, so an approval outside a rule is visible as one, with the rule, the value, and the gap. The underwriter adds the judgment. Every decision points back to its rule, for the board and for the examiner.