Short answer: In mortgage operations, pull-through commonly describes the share of a defined commitment or pipeline cohort that reaches closing and funding. A loan officer should state the cohort, the start event, the end event, the time window, and excluded records before treating the number as a performance signal. It is not the same thing as a broad lead-to-close rate.
Different teams use the phrase at different points in a workflow. The Mortgage Bankers Association describes pull-through in relation to an interest-rate-lock commitment reaching closing and funding. Fannie Mae describes a closed-and-funded volume divided by committed volume. The OCC notes that the term is related to the inverse idea of fallout. Those sources make one thing clear: the definition has to travel with the number.
Define the rate before discussing the result
| Definition item | Write it down | Why it matters |
|---|---|---|
| Starting cohort | The exact event that places a record in the review: a lock, application, approved file, or another internally defined point. | A rate based on applications answers a different question from a rate based on committed loans. |
| Ending event | The specific status that counts as a completed result for this measure. | A funded record, a closed record, and a submitted record should not be used interchangeably. |
| Time window | The cohort date range and the point at which the review is considered mature. | Recent records can make a cohort look incomplete simply because they have not had time to move. |
| Exclusions | Which duplicates, withdrawn records, transfers, or incomplete records are excluded and why. | A number cannot be compared fairly when exclusions change without a record. |
| Review owner | The person or role responsible for definitions, exceptions, and the final interpretation. | A report is harder to use when no one can explain a record that does not fit the usual path. |
Separate pull-through from adjacent metrics
Lead conversion, application completion, lock fallout, closing, funding, and referral-source response are useful measurements, but they are not automatically interchangeable. Keep the labels separate. When a team needs to compare two sources or workflow changes, it should use the same start event, end event, and cohort window for both.
For lead-stage definitions and ownership before an application exists, use the mortgage lead-management workflow. For the daily view a loan officer needs while records move, use the mortgage CRM dashboard review.
Run a five-record pull-through review
- Completed record: confirm the start event, end event, and cohort date.
- Expected fallout: inspect the reason and make sure it is recorded under the team's definition.
- Still-in-process record: decide whether the record is immature for the review window rather than treating it as a final result.
- Duplicate or transferred record: apply the documented exclusion rule and record the rationale.
- Definition exception: identify who resolves a record that cannot be classified with the ordinary rules.
This review does not determine creditworthiness, underwriting, approval, or any lender decision. It is a record-definition exercise that helps a team interpret its own pipeline consistently.
Recorded workflow context
The public BNTouch Daily Dashboard walkthrough opens a daily operating view with task and status context. It is useful visual context for the record-review questions on this page.
Source: BNTouch: Daily Dashboard and Intelligence Walkthrough.
Scope of this recorded source: The walkthrough is a visual example. It does not establish current account behavior, field definitions, permissions, implementation steps, legal requirements, or outcomes for another organization. Confirm the current workflow in a live review.
Sources and further reading
- Mortgage Bankers Association glossary of origination terms
- Fannie Mae PE – Whole Loan glossary
- OCC Mortgage Banking Comptroller’s Handbook
- BNTouch: Mortgage Lead Management Workflow
Bring one current pipeline report and two records that are hard to classify. A BNTouch workflow review can help your team map source context, ownership, next actions, and exceptions around the definitions you use.
