Loan program or terms change
How do we handle a change of program, amount or terms during origination so it is recorded, re-priced, re-disclosed if required and re-approved on the record?
Treat a terms change as an event with four consequences. When the borrower or the loan officer changes the program, the amount, the term or the rate structure before closing, Callvu records the change with its date and reason, re-prices it through the pricing engine and the lock, classifies whether it is a changed circumstance or a consumer-requested revision requiring a revised Loan Estimate, re-runs the automated underwriting and routes the re-approval in the Decision Desk, and writes the new terms, the disclosure and the approval to the LOS.
In scopeComplex: multi-party handoffsCallvu moves: classify, decide, write back
Last updated November 7, 2026.
The problem today
The borrower switched from a 30-year to a 15-year on a call, and three systems still show the 30-year.
A borrower changes their mind about the product, or the appraisal forces a lower loan amount, or the loan officer restructures to fit the ratios. The change is made in the LOS, or in the pricing engine, or in an email to the disclosure desk, but not in all three. The approval rests on the old terms; the Loan Estimate shows the old product; the lock is for the wrong one.
A terms change touches pricing (and the lock), disclosure (a consumer-requested revision or a changed circumstance under TRID, with the three-business-day clock), underwriting (the automated findings and the approval rest on the terms), and the closing package. Each has a rule, and all must follow from one recorded event.
Changes are normal. Unrecorded changes are the problem.
How it runs
From the requestto the system of record.
A change to the program, amount, term or rate structure is requested by the borrower (in any channel) or by the loan officer, or forced by a file event (the appraised value). Callvu records the change event.
- Borrower
- Requests or accepts the change and confirms the new terms on their screen.
- Loan officer
- Enters or relays the change through the process; sees every consequence.
- Underwriter
- Re-approves in the Decision Desk where the change requires it.
- Disclosure desk
- Issues the revised Loan Estimate where required.
- Callvu
- Records, re-prices, classifies the disclosure, re-runs, routes re-approval and writes.
Record and classify the change
The change is captured with its date, its source (borrower request, loan officer restructure, file event) and the old and new values; the classification sets what follows: a re-price and a lock change, a revised Loan Estimate (consumer-requested revision or changed circumstance), a re-run of automated underwriting, a re-approval, and a new closing timeline.
Re-price and confirm
The new terms are priced through the engine and the lock is amended or relocked through the lock process; the new rate, points and payment are confirmed by the borrower on their screen.
Re-disclose and re-run
Where the classification requires a revised Loan Estimate, it is issued within three business days of the change through the changed-circumstance process; the automated underwriting is re-run on the new terms through the findings process.
Decide and write back
The underwriter re-approves in the Decision Desk where the change requires it (a new amount, a new program), with the new findings and only the allowed outcomes; the new terms, the lock, the disclosure, the findings and the approval are written to the LOS so every system shows the same loan.
Where it ends: The change was recorded once and every consequence followed from it: the price, the disclosure, the findings and the approval all rest on the new terms in the LOS. The Decision Trace shows the classification and each consequence; the Audit Trace shows the request, the confirmation and the re-approval.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The borrower in any channel or the loan officer, through the process; the borrower confirms on their screen.
The back office
Secondary, the disclosure desk and underwriting each receive their consequence with the clock, from one event.
The Decision Desk
- The underwriter re-approves in the Decision Desk where the change requires it, with the new findings and only the allowed outcomes; a change after the Closing Disclosure that resets the period goes to the closing team.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
What happens when the borrower changes the product?
The change is recorded as an event, the loan is re-priced and the lock amended, a revised Loan Estimate is issued within three business days as a consumer-requested revision, the findings are re-run and the underwriter re-approves.
How do all the systems stay in sync?
Every consequence is written from the one recorded event to the LOS, the pricing and the disclosure records.
What if the change comes after the Closing Disclosure?
A product change then requires a new Closing Disclosure and a new three-business-day period, which the classification routes to the closing team.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.