Underwriting exception approval
How do we document a guideline exception with its compensating factors and route it to the right approval authority before the decision is recorded?
Make the exception a case with the authority table in it. When an underwriter wants to approve outside the guidelines, Callvu captures the exception (the guideline, the variance, the compensating factors from the file), classifies it against the lender's exception policy and authority table, routes it to the credit manager or the credit committee in the Decision Desk with the file and only the allowed outcomes, records the approval with its conditions and the approver, and writes it to the loan for the investor's review and the fair lending analysis.
In scopeComplex: multi-party handoffsCallvu moves: classify, decide, write back
Last updated November 7, 2026.
The problem today
The exception was approved in a hallway, and the fair lending review cannot find the pattern.
An underwriter wants to approve a loan with a debt-to-income ratio above the overlay, or reserves short of the requirement, because the file has strengths. They ask the credit manager, who says yes. The approval is a note in the file with 'strong comp factors'. At the investor's review, the exception is unexplained; at the fair lending review, the lender cannot show who got exceptions and who did not.
Exceptions are legitimate and governed: the lender's policy says which guidelines may be excepted, the compensating factors that support each, who may approve by the variance's size, and what must be documented. Regulators look at exception data for disparate treatment, and investors look for the approval.
The exception needs the same discipline as the decision it varies.
How it runs
From the requestto the system of record.
An underwriter requests an exception to a guideline in the LOS. Callvu opens the exception case with the loan, the guideline and the variance.
- Underwriter
- Requests the exception with the guideline, the variance and the compensating factors.
- Credit manager
- Approves exceptions within their authority in the Decision Desk.
- Loan officer
- Is told the outcome and any conditions; does not influence the approval.
- Callvu
- Captures, classifies, routes by authority, records and writes.
Capture and classify
The exception is captured in structured form: the guideline (agency or overlay), the required value and the loan's value, the variance, and the compensating factors selected from the policy's list with the evidence from the file (reserves, credit depth, residual income, payment history). The exception policy classifies whether the guideline may be excepted, the variance's tier and the authority required.
Decide
The exception goes to the approver whose authority covers the tier (the credit manager, the chief credit officer, the credit committee) in the Decision Desk with the file, the variance and the compensating factors, and only the allowed outcomes: approve, approve with conditions, or decline with a reason. A guideline the policy does not allow to be excepted is declined by rule.
Chase and verify conditions
Conditions attached to the approval become underwriting conditions in the condition process, requested from the right party and cleared with the record.
Write back
The exception, the factors, the approval with the approver and the conditions are written to the loan in the LOS as the exception record, flagged for the investor's delivery and included in the lender's exception data for the fair lending analysis.
Where it ends: The exception is documented with its guideline, variance and compensating factors, approved by the right authority with conditions, and recorded for the investor and the fair lending review. The Decision Trace shows the classification and the authority; the Audit Trace shows the request, the decision and the person.
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 underwriter's request in the LOS.
The back office
The approver decides from a structured case; compliance analyzes exceptions from data, not from notes.
The Decision Desk
- The exception goes to the approver whose authority covers the variance tier in the Decision Desk with the file, the variance and the factors, and only approve, approve with conditions, or decline with a reason.
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.
Who approves an exception?
The approver whose authority covers the variance's tier under the lender's exception policy, in the Decision Desk, with the file and the compensating factors in view.
What is recorded?
The guideline, the variance, the compensating factors with their evidence, the approver, the conditions and the reason, on the loan and in the exception data set.
Why does fair lending care?
Because discretionary exceptions are tested for disparate treatment; structured exception data is how the lender shows consistency.
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.