Approval feels like the end. For the borrower it usually is, emotionally. They hear "approved" and start planning a move.
Operationally it is the beginning of the part that most often goes wrong.
Conditional approval is a list, not a decision
Most approvals are conditional. The underwriter has assessed the file and said yes, provided a set of things turn out to be true. Those conditions can be trivial or substantial, and the borrower rarely understands the difference.
A letter of explanation is not the same as a re-verification of employment. Both appear as "conditions" and both must clear. One takes ten minutes, the other depends on a third party responding.
The gap between approved and closed is where that list gets worked, and the list is where files stall.
What runs in this window
Conditions clearing
Each condition needs evidence, review, and a record that it was satisfied. In a manual process the evidence often arrives by email and the record of clearing lives in someone's notes. Reconstructing that later, under audit, is where compliant files fail reviews.
Re-verification
Employment and assets age. A verification obtained at application may not support the file at consummation. Re-verifying close to closing is standard practice and it introduces a dependency on someone outside your organisation responding in time.
Disclosure timing
The Closing Disclosure carries a waiting period, and a qualifying change during this window can trigger a revised disclosure with its own clock. A fee change discovered late does not just cost a day. It can reset the timeline.
Third parties
Title, appraisal, insurance, the settlement agent. Each has its own schedule and none of them are in your system. This window is where a file's progress depends most heavily on people you do not control.
Why "almost done" is the dangerous phrase
Files in this window get less attention, not more. They have been approved, so they read as solved. Processors move to files that look like they need help.
Meanwhile the file is accumulating dependencies, any one of which can reset the timeline. A condition that arrives incomplete on Wednesday and is noticed on Friday costs the weekend. A verification that expires unnoticed costs whatever it takes to redo it.
This is also the window where borrowers are least tolerant of delay, because they have already been told yes and have made plans accordingly.
What good handling looks like
Three things separate operations that close on time from operations that do not.
Conditions are tracked as items with owners and ages, not as a list in a document. If nobody can answer "which conditions are older than three days" without reading something, they are not being tracked.
Verification expiry is anticipated rather than discovered. The system should know which files will need a re-verification before closing, not surface it when a check fails.
Material changes are recognised as they happen. If a fee moves, the disclosure implication should be raised immediately rather than at final review, because the difference is whether you have time to absorb it.
The record matters as much as the work
Everything in this window is examinable. Whether a condition was cleared correctly, whether the disclosure went out in time, whether the re-verification was current at consummation.
A file can be handled perfectly and still fail a review if the evidence is spread across email threads and personal notes. Being compliant and being able to demonstrate compliance are separate problems, and only the second one is solved by keeping records where they can be found.
How CliQloan handles it
The CliQloan Disclosure Hub tracks the events that create disclosure obligations and generates from them, with a delivery record attached to the loan. Conditions, verification status and their ages stay on the file rather than in a thread.
Approval is not the finish line. It is the point at which a file stops being a question and starts being a countdown.