Underwriting conditions

How do we clear underwriting conditions with each one requested from the right party, the returned document checked against the condition, and the underwriter's decision recorded?

Turn the approval's conditions into requests with owners. When the underwriter issues conditions, Callvu classifies each one (prior to docs, prior to funding, by party), sends each to the party that can satisfy it (the borrower, the employer, the title company, the insurance agent, the appraiser) through a link, reads what comes back and checks it against the condition's wording, presents the underwriter with the condition, the document and the check in the Decision Desk to clear or reject, and writes each clearance to the LOS.

In scopeComplex: multi-party handoffsCallvu moves: chase and verify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The conditions list is in the approval, the processor re-types it into an email, and the underwriter clears it from memory.

Today, without Callvu

The underwriter approves with fifteen conditions. The processor emails the borrower the ones they think are the borrower's and calls the title company about the rest. Documents arrive and are attached to the file; the underwriter, at the end of the queue, reads them and clears what they can, asks again for what they cannot, and the loan waits for a second round.

Each condition is a sentence with a party and an acceptance criterion: a document, a value, a correction. The investor's guidelines set what satisfies it. Clearing is a decision with a record; a condition cleared without the document is a quality control finding.

The conditions are already structured in the approval. The requests and the checks should be too.

How it runs

From the requestto the system of record.

The underwriter issues an approval with conditions in the LOS. Callvu reads the conditions and opens a request for each.

Underwriter: Issues conditions and clears or rejects each in the Decision Desk with the document and the check.
Processor: Sees every condition's status and handles only what the matching could not resolve.
Borrower: Provides the items that are theirs through a link.
Third parties: The employer, title company, insurance agent, appraiser or HOA provide theirs through links.
Callvu: Classifies, requests, reads and checks, routes the clearance and writes.

Classify each condition
Each condition is classified by stage (prior to docs, prior to funding, at closing), by the party that can satisfy it, and by what satisfies it (a document type, a corrected value, a verification), from the condition's wording and the program's guidelines.
Chase and verify
Each party receives a link to only their conditions with the acceptance criteria stated plainly; documents are read on arrival and checked against the condition (the right type, period, person, value); a document that does not satisfy the condition is sent back with the reason. The file shows every condition's status and age.
Decide
The underwriter sees each condition with the document and the check result in the Decision Desk and clears, rejects with a reason, or modifies the condition; conditions the policy allows to clear by rule on a passing check (a standard document that matched) clear automatically with the record.
Write back
Each clearance or rejection is written to the LOS against the condition, the stage gates (docs, funding) release when their conditions are cleared, and the condition history is kept for quality control.

Where it ends: Every condition went to the party that could satisfy it, every document was checked against the condition before the underwriter saw it, and every clearance is on the LOS with the document and the decision. The Decision Trace shows the classification and each check; the Audit Trace shows each request, response and clearance.

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.

Regulations

Investor and agency guidelines on conditions and documentation (Fannie Mae Selling Guide B3 and the quality control requirements; Freddie Mac Guide 5000 series; FHA Handbook 4000.1): An approval's conditions must be satisfied with documentation that meets the guidelines before the loan is closed or delivered; the lender's quality control reviews the conditions and the documents that cleared them; a condition cleared without supporting documentation is a defect that can lead to repurchase.
ECOA (Reg B, 12 CFR 1002.9): A conditional approval that is not met and is declined is adverse action with the notice rules; the condition record supports the reasons.
GLBA Safeguards (12 CFR part 364 appendix B): Third-party documents travel on authenticated links and are stored in the loan file.

Company policies

Every condition has a party, a stage and an acceptance criterion from its wording and the guidelines.
A document is checked against its condition before the underwriter sees it; the underwriter clears from the check, not from memory.
Conditions that may clear by rule are the lender's policy; everything else is the underwriter's decision in the Decision Desk.
The LOS holds the conditions, the documents and the clearances.

Controls

Condition classification by stage, party and criterion.
Per-party requests with plain criteria.
Document reading and condition matching.
Decision Desk clearance with the check in view.
Rule-based clearance where the policy allows.
Stage gates on docs and funding.

Clocks and deadlines

Prior-to-docs conditions: Cleared before the closing package is prepared; the gate holds it.
Prior-to-funding conditions: Cleared before funds release; the funding process checks them.
Party reminders: On the schedule, with aging visible.

Documents and checks

The conditions as issued and classified
Each request to each party
Each document received with its check against the condition
Each clearance or rejection with the underwriter and the reason
The condition history for quality control

In the Decision Trace

Each condition's classification.
Each document's check against the condition.
Each clearance decision and the person.

In the Audit Trace

Each request and response with time.
Each Decision Desk step.
The gate releases.

The handoff

Between the front doorand the back office.

The front door

Links to each party for their conditions, with the criteria stated plainly.

The back office

The underwriter clears from a checked document in the Decision Desk; the processor handles only unresolved matches; closing and funding see their gates.

The Decision Desk

The underwriter clears, rejects with a reason, or modifies each condition in the Decision Desk with the document and the check; a condition the parties cannot satisfy goes to the underwriter with the alternatives.

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.

Bank Leumi runs its home lending workflows on Callvu.

MTG-01

Community Bank of Mississippi runs TRID loans on Callvu.

MTG-02

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

Who is asked for each condition?

The party that can satisfy it, through a link to only their conditions with the acceptance criteria stated plainly.

What does the underwriter see?

The condition, the document and the check result, in the Decision Desk, to clear, reject or modify.

Can conditions clear automatically?

Where the lender's policy allows it for standard documents that matched; everything else is the underwriter's decision with the record.

Related processes

Borrower document collection Suspended file resolution Prior-to-funding conditions Underwriting exception approval Compared with the alternatives Try it in the sandbox All home lending 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.