Approval is the middle. Conditions are where files die.
A loan is approved, and then twelve conditions are chased across five parties who do not talk to each other. Most systems model the pipeline stage and none of them model the chase.
Thirty minutes · no predetermined package
What condition-chasing feels like from inside.
Conditions live in a PDF and a loan officer's memory, so what is outstanding depends on who you ask.
The borrower is emailed for the same document twice because nobody confirmed the first one arrived.
An appraisal or a credit report expires while the file waits on something unrelated.
Referral partners — agents, builders, planners — are never told where their client's file is.
Rate lock expiry and condition clearance are tracked in different places and reconciled by hand.
Loan officer performance is measured on volume, never on cycle time or fallout.
What you are probably running, and what constrains it.
The typical stack
What the rules require
Six questions before changing anything.
How a file actually closes.
Application
and the first pullCredit, income and asset documents, most of which have an expiry date from the moment they arrive.
Processing
and submissionThe file assembled and sent to underwriting, where the real work starts rather than ends.
Approval with conditions
the chase beginsTwelve conditions across five parties. This stage is where cycle time is won or lost.
Clear to close
and the clockEvery condition cleared before something else expires, which is a coordination problem rather than a credit one.
Closing and post-close
the referral loopFunded, and the referral partner told — which is the cheapest source of the next file.
What lenders and brokers ask.
What should a mortgage CRM do that an LOS does not?
Hold the relationship and the chase. The LOS holds the loan; the CRM should hold the borrower, the referral partner, the condition list and the clock on everything that expires.
How do you track loan conditions properly?
As records with a state, an owner and a party being waited on — not as a line in a PDF. Outstanding, received, rejected and expired are states, not notes.
Why do approved files fall out?
Usually coordination rather than credit. Something expires while the file waits on something unrelated, and nobody was warned before it did.
Can this integrate with Encompass?
Yes. The usual pattern is the LOS staying authoritative for the loan while the CRM holds the borrower, the partner and everything with a clock on it.
How should referral partners be managed?
With visibility into their own clients' file status, within what RESPA permits. Telling an agent where the file is costs nothing and retains the relationship.
What does TRID mean for the system?
Disclosure timing is triggered by events the system must detect rather than be told about, so those events have to be captured where they happen.
How does NMLS licensing affect assignment?
A loan officer may only originate where they are licensed, so routing has to check the record rather than rely on the manager knowing.
What is the most useful number a mortgage operation is not tracking?
Median days from approval to clear-to-close, split by which party was being waited on. It names the bottleneck rather than describing it.
Does this replace our LOS?
No, and it should not try. The LOS is regulated infrastructure. What sits around it is where most operations are losing time.