March 8, 2026 · 5 min read
A loan sits in underwriting with three conditions outstanding: an updated bank statement, a letter explaining a large deposit, and a corrected pay stub. The borrower doesn't fully understand what's being asked for in underwriter language, sends the wrong version of the bank statement twice, and calls the loan officer three times in a week asking what's actually still needed. None of this is complicated work. All of it takes time that could have gone toward the next file.
A condition like "provide a letter of explanation for the $4,200 deposit dated March 12, sourced and documented" is precise from an underwriting standpoint and confusing from a borrower's. Loan officers end up translating the same handful of condition types over and over, on every file, because the borrower has no way to know what a satisfactory answer actually looks like without being told directly.
Once a condition is cleared, the next one usually needs a nudge, and that nudge depends on the loan officer or processor remembering which file needs which document on which day. On a pipeline of 25 or 30 active loans, that tracking lives in someone's head or a notes app, and the files that get followed up on promptly are the ones that happen to come to mind that day.
The agent who referred the borrower is checking their own phone for updates, and when they don't hear anything for a week, they assume the loan is stuck rather than simply waiting on a document. That assumption gets repeated to the next client the agent refers, and a routine underwriting delay quietly becomes a reputation problem.
Every day a condition sits unresolved is a day closer to a rate lock expiring or a closing date slipping, and neither of those costs falls on the underwriter. They fall on the borrower, the agent, and eventually the loan officer's referral pipeline, over what is usually just a document that needed to be requested more clearly the first time.