Loan pipeline management is the daily practice of tracking every open loan by stage, days in that stage, its current blocker and the next action with an owner. A small lending team keeps files moving by defining stages with exit tests, reading an aging report each morning and acting first on files that have stopped.
What does loan pipeline management track?
Loan pipeline management tracks five facts for every open file: its stage, the date it entered that stage, what it is waiting on, who owns the next action and the date that action is due. A pipeline that records only the stage tells you where a file is, not why it has not moved.
The minimum fields
- Borrower and loan number, so everyone means the same file.
- Product, because a bank statement loan and a conventional purchase move at different speeds.
- Stage, from a fixed list, never free text.
- Stage entry date, from which days in stage is calculated.
- Blocker, in a few words: "appraisal", "unsourced deposit", "title payoff".
- Next action and owner, a verb and a name.
- Hard dates, such as a contract closing date or a rate lock expiry.
Why the blocker field matters most
Stage and days tell you a file is late. The blocker tells you what to do about it. When a team reviews the pipeline and the blocker column is empty, the meeting turns into a hunt through emails. When it is filled in, the meeting takes minutes and ends with assignments.
Keep the pipeline in one shared place, whether that is a loan origination system report, a shared spreadsheet or a board. The tool matters less than the rule that the blocker and next action are updated the same day they change.
Defining loan pipeline stages with clear exit tests
Loan pipeline stages work only when each one has an exit test: a yes-or-no condition that must be true before the file moves on. Without exit tests, files drift forward on hope. "Submitted" should mean the underwriter has a complete file, not that something was uploaded.
A stage list with exit tests
The list below is an example for a lender or brokerage handling purchase and refinance files. Adjust the names to your process, but keep one test per stage.
- Application. Exit when the application is signed and the credit authorization is on file.
- Disclosed. Exit when initial disclosures are sent and intent to proceed is received.
- Processing. Exit when every document on the program checklist is in and reviewed, and third-party orders are placed.
- Submitted. Exit when the underwriter has issued a decision.
- Conditional approval. Exit when every prior-to-document condition is signed off.
- Clear to close. Exit when the closing date is set and the closer has the package.
- Closed. Exit when the loan funds.
- Suspended or withdrawn. Side stages with their own reasons recorded.
Who moves a file
One person moves a file between stages: whoever can confirm the exit test. The processor moves a file into "submitted" after checking the package against the broker loan submission checklist or the lender's own list. The underwriter's decision moves it out. If anyone can change a stage without the test, the pipeline stops being trusted.
Reading a loan pipeline aging report
A loan pipeline aging report lists every open file with the number of days it has spent in its current stage, sorted with the longest first. It shows where time is going. Each stage gets a target, and a file past its target is a file someone needs to act on today.
Example aging report
The table below is an example of a ten-file pipeline on one morning. The targets are illustrative; set your own from your closed files.
| Loan | Product | Stage | Days in stage | Target | Blocker | Next action |
|---|---|---|---|---|---|---|
| 1041 | Bank statement purchase | Conditional approval | 11 | 5 | Two deposits unsourced | Processor calls borrower today |
| 1038 | Conventional refi | Suspended | 9 | 3 | Missing 2 statement months | Loan officer requests by Friday |
| 1045 | Bank statement refi | Submitted | 7 | 4 | Underwriter question on expense factor | Underwriter replies to LO |
| 1047 | FHA purchase | Processing | 6 | 7 | Appraisal due day 8 | Processor checks date |
| 1049 | Conventional purchase | Processing | 4 | 7 | Written VOE out | None today |
| 1050 | Bank statement purchase | Processing | 3 | 7 | Statements under review | Processor finishes review |
| 1043 | Conventional purchase | Clear to close | 2 | 3 | Closing set | Closer confirms |
| 1051 | Small business term | Disclosed | 2 | 3 | Intent to proceed | Originator follows up |
| 1052 | Conventional refi | Application | 1 | 2 | Credit authorization | Originator sends form |
| 1053 | HELOC | Application | 0 | 2 | None | None |
What the example shows
Three files are past target, and all three are blocked by bank statement items: unsourced deposits, missing months and an expense factor question. That pattern is common and worth noticing. The fix for those three is not more processing hours in general; it is a statement review earlier in the file.
Set targets from your own history
Take your last twenty or thirty closed loans and note how many days each spent in each stage. The middle value per stage is a fair starting target. Revisit the targets each quarter as your process changes.
The daily loan pipeline review meeting
The daily loan pipeline review is a short standing meeting, usually 15 minutes, where the team walks the aging report from the oldest file down. Each file past target gets a named owner and a next action with a date. Files on track are skipped. The meeting ends when the over-target list is assigned.
Who attends
On a small team, the originators, processors and at least one underwriter. The underwriter matters because many blockers are questions that only the underwriter can answer, and a 30-second answer in the room beats a day of email.
A simple agenda
- Files with hard dates in the next five business days.
- Files past their stage target, oldest first.
- Suspended files and their reasons.
- New files entered since yesterday, checked for missing fields.
Rules that keep it short
- No problem-solving longer than two minutes per file. Take it offline with a named owner.
- Update the blocker and next action live, during the meeting.
- If the same file is discussed three days running without movement, escalate it to whoever can change the outcome.
How do you spot pipeline files stuck on bank statement conditions?
Pipeline files stuck on bank statement conditions show three signs: they sit in conditional approval or suspense well past target, their blocker names a deposit, a missing month or an income figure, and they cycle between processor and underwriter more than once. Bank statement files tend to stall in the same places.
Where statement files stall
- Unsourced deposits. The underwriter wants a document for a large deposit and the borrower sends a letter without proof.
- Missing months or pages. A statement arrives with a page missing, or a month is skipped between two statements.
- Income questions. The underwriter's calculation differs from the loan officer's, often because of which deposits were excluded or what expense factor the bank statement program applies.
- Undisclosed accounts. Transfers point to an account no one asked for.
Tag the blocker type
Add a short code to the blocker field, such as STMT for statement items, APPR for appraisal and TITLE for title. After a month, count the codes on files that went past target. If STMT leads, the answer is a fuller statement review during processing, before submission.
Suspended files need their own list
A file the underwriter has stopped reviewing until something arrives needs closer tracking than a conditioned one, because nothing moves until the missing item does. What triggers that status and how to get out of it is covered in what a loan in suspense means.
A statement review done in processing removes many of these stalls. TrueBankFlow lines up the months, totals deposits and flags out-of-pattern deposits and NSF events with the statement line, so the processor sees the likely conditions before the underwriter writes them.
Pipeline management mistakes that hide stalled loans
Pipeline management mistakes that hide stalled loans share one effect: the report looks healthy while files sit. The usual causes are resetting the stage date on any activity, vague blockers, missing owners and counting suspended files as active. Each one makes the aging report lie.
Resetting the clock on activity
Days in stage should count from when the file entered the stage, not from the last email. If any touch resets the counter, a file that has been in conditions for three weeks can show two days.
Blockers that say nothing
"Waiting on borrower" names no document. Write what is missing: "March checking statement, page 3". A specific blocker can be chased; a vague one cannot.
Files with no owner
A blocker without a name next to it belongs to no one. Every over-target file leaves the daily review with a person assigned.
Hiding suspended files
Some teams leave suspended files in "submitted" because the underwriter technically still has them. That makes the submitted stage look slow and hides the real reason. Put them in their own stage with the suspense reason.
Counting only volume
A pipeline report that shows how many files are open but not how long each has waited invites the wrong question. Ask about days in stage first and file count second.