The Monday after the board meeting
The board approved a shorter maximum term on used vehicles Thursday night. The lending manager updates the policy document on Friday, sends the revised PDF out Monday morning with a paragraph of explanation, and asks everyone to read it.
By Monday afternoon, three underwriters have read it. One is on vacation. One reads the email, remembers the old limit from ten years of habit, and approves a 60-month term on Tuesday. The dealer rate sheet shows the old term for another three weeks. Nobody did anything wrong. The policy changed in one place, and the places it has to reach are many.
Where the old rule lives on
A rule, once learned, is stored in more places than the policy document.
- In memory, which is where most rules are checked from on a busy day.
- On the cheat sheet taped to the monitor, and in the one a senior underwriter made for the new hires.
- In the dealer rate sheet, and in the indirect program guide the dealers were sent.
- In the decline template, which still names the old limit as the reason.
- In the training deck, until someone updates the training deck.
Each one is a place the old rule will be applied after the new one took effect.
Maximum term, used vehicles
- Was
- 60 months, rev. Sep 2026
- Now
- 54 months, rev. Oct 2026
- Files from Oct 1
- Checked against 54 months
- Files before Oct 1
- Stay decided under 60 months, the rule in force
- Changed by
- Lending manager, after board approval on Sep 25
What a change should look like
A policy change should be one thing, in one place, with a date: this rule, from this limit to that one, effective on this day, approved on that one. Every file after the effective date is checked against the new rule. Every file before it stays decided under the rule that was in force, which is the only fair way to read it later.
That gives the board a revision history it can read. It gives the examiner an answer to the question they always ask: which version of the policy was this file decided under? And it gives the underwriters one less thing to carry.
Why plain English matters here
If the rule is held as a sentence that reads like the policy, the person who changed the policy can change the rule the same day, and read it back to confirm it says what the board meant. If the rule is held as code or a vendor’s configuration, the change becomes a ticket, and the underwriters carry the new limit in their heads until it ships. The gap this page is about is exactly as long as that ticket.
Where Sidecar fits
Sidecar holds your lending policy as rules in plain English, owned by your team. When the policy changes, the rule changes, and every file that reaches an underwriter after that is checked against the new one, with the revision shown. The LOS does not need to change, and nobody has to remember an email.