Broker loan package completion

How do we check a broker's loan package against a declared complete file and request only the missing items before submission to underwriting?

Let the broker declare the package and let the process read it. When a broker submits, Callvu checks the declared package against the program's required documents by type, reads each document for the right borrower, property and period, checks the broker's disclosures and their timing under TRID, lists only what is missing or wrong, sends that list to the broker, and submits the file to underwriting when the package passes.

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

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The account executive emails the broker a needs list on day three, and the broker sends the same package again.

Today, without Callvu

A broker submits a package through the wholesale portal. An account executive or a processor opens it and builds a needs list by hand. The broker, who declared the file complete, resends the same documents with different names. Meanwhile the broker's Loan Estimate timing, which the lender inherits responsibility for, is checked by nobody.

In a wholesale channel the lender relies on the broker for the application, the disclosures and the first document set, and is responsible for the loan's compliance. The package has a required list by program; the disclosures have TRID timing; the broker's compensation has its own rules. The lender needs a check that reads, not a reviewer who scrolls.

Brokers send loans to the lenders that tell them exactly what is missing, once.

How it runs

From the requestto the system of record.

A broker submits a package through the wholesale portal and declares it complete. Callvu picks up the package with the program and opens the check.

Broker: Submits the package, declares completeness, and provides only the items listed as missing.
Account executive: Sees the package's status and the broker's open items; no longer builds needs lists.
Processor: Receives packages that passed and reviews only flagged documents.
Callvu: Checks by type, reads, checks disclosure timing, lists the gaps, and submits on a pass.

Classify the required package
The program, the purpose and the occupancy derive the required documents by type (the application, the credit authorization, the credit report, income and asset documents, the purchase contract, the identification, the broker's disclosures) and the broker's own items (the broker agreement, the compensation disclosure, the anti-steering disclosure where applicable).
Chase and verify by reading
Each document in the package is read and matched to a required type for the right borrower, property and period; a document filed under the wrong type or for the wrong year does not count. The broker's Loan Estimate and other disclosures are checked for their dates against the application date and the three-business-day rule, and the broker compensation against the agreement.
List and request
The gaps and the problems are listed precisely (the missing type, the wrong year, the late disclosure) and sent to the broker through the portal with a link to upload only those items. Reminders run and the account executive sees the status.
Submit on a pass and write back
When the package passes, the file is submitted to underwriting with the check results written to the LOS; a package that cannot pass (a late Loan Estimate the lender cannot cure) goes to the account executive or compliance in the Decision Desk with the finding.

Where it ends: The broker's package reached underwriting complete, read and with the disclosure timing checked, and the broker was asked once for exactly what was missing. The Decision Trace shows the required list and each check; the Audit Trace shows the submission, the requests and the pass.

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

TRID in the wholesale channel (Reg Z 12 CFR 1026.19(e)(1)(ii)): A mortgage broker may provide the Loan Estimate on the creditor's behalf, but the creditor remains responsible for compliance; the Loan Estimate must be provided within three business days of the broker's receipt of the application, and the creditor must ensure the timing and content before relying on it.
Loan originator compensation and anti-steering (Reg Z 12 CFR 1026.36(d) and (e)): Broker compensation may not be based on the loan's terms, must be from either the consumer or the creditor but not both, and the anti-steering safe harbor requires presenting loan options; the broker's compensation disclosure and agreement are checked.
Investor and agency guidelines on third-party originations: The lender's quality control plan covers loans from brokers with specific review requirements; the package check and the record are part of it.

Company policies

The required package per program is derived by rule and checked by document type, not by the broker's declaration alone.
The broker's disclosure timing is checked on every package; a late Loan Estimate is a finding, not a note.
The broker receives one precise list of what is missing.
The LOS holds the check results with the file.

Controls

Required package derivation by program.
Document reading and type matching.
TRID disclosure timing check.
Compensation check against the agreement.
Precise gap list through the portal.
Submission on a pass; Decision Desk for incurable findings.

Clocks and deadlines

Loan Estimate (TRID): Three business days from the broker's receipt of the application, checked on the package.
Broker response: Reminders on the schedule; the account executive sees aging.

Documents and checks

The broker's package as submitted and read
The required list and the check results by type
The disclosure timing check
The gap list sent and the broker's responses
The submission record

In the Decision Trace

The required list and why.
Each document's check.
The disclosure timing result.
The pass or the finding.

In the Audit Trace

The submission and each request.
Each upload.
The submission to underwriting.

The handoff

Between the front doorand the back office.

The front door

The wholesale portal; the broker meets the process in the gap list and the upload link.

The back office

Underwriting receives packages that passed; the account executive stops writing needs lists.

The Decision Desk

A finding the broker cannot cure (a late Loan Estimate, a compensation issue) goes to the account executive or compliance in the Decision Desk with the finding and only the allowed outcomes.

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.

What does the broker get back?

One precise list of what is missing or wrong, by document type, with a link to upload only those items.

Is the broker's Loan Estimate checked?

Yes, for timing against the application date and for content, on every package, because the lender is responsible for it.

When does the file reach underwriting?

When the package passes the check, with the results written to the LOS.

Related processes

Completeness check before Processing Broker and correspondent onboarding Application intake (URLA / 1003)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.