Why Borrowers Ignore Your Document Requests

The conventional read on document delays is that borrowers are disorganized, distracted or dragging their feet. Some delays are exactly that. Others start with a request that was too vague to act on without another call or email, and every ambiguity can add another call, another email or another delay.

Consider what this asks of somebody:

To act on that message a borrower has to work out which documents, for which period, in what format, from which of their accounts, and where to send them. That is five decisions, any one of which can stall. Most people respond to five open decisions by deciding to deal with it later.

Name the item, the period and the pages

“Bank statements” is at minimum two follow-ups. One to learn which account, another to learn which months, and usually a third when the borrower sends a screenshot of a balance instead of a statement.

“All pages of your [bank] checking statement for [month], including any pages that are blank or say ‘this page intentionally left blank’” is one message.

That last clause looks fussy written out. It heads off a common problem, which is an incomplete statement missing the last page.

Give them the channel, not just the ask

If you do not say where to send it, the borrower will use whatever is in front of them, which is often a reply to your email with a tax return attached. Sensitive documents have to travel through your lender’s approved secure method, and the way you prevent the wrong channel is to name the right one before they guess.

Name the secure portal. Link it if your process allows. If a borrower has never used it, the sentence “if you have not used the portal before, it will ask you to set a password the first time” answers the question they would otherwise call to ask.

That costs you one line, and it is the cheapest line in the message.

Do not interpret the request unless you have an approved explanation

To someone who has never been through underwriting, a request for more documents reads as bad news, and worried borrowers move slowly. The instinct is to reassure them.

Be careful here. You cannot tell every borrower that a request means nothing, because sometimes it does not mean nothing. A condition can come from a material underwriting issue, an eligibility question, an incomplete application or a review you are not going to describe in an email.

So do not characterize what the request means unless your lender has approved that explanation and it is accurate for this file. A neutral line your lender signs off on does the job without asserting anything you do not know, for example that the request does not by itself communicate a final credit decision and that you are happy to answer questions about the item or the submission process.

What you can always do is make the errand small: exact item, clear channel, real date.

Give a date, not an urgency word

“ASAP” is not a deadline. It is a feeling, and it competes with every other ASAP in that person’s week.

“By Thursday” is a deadline. If there is a real consequence attached, name it plainly, and only if you were given it. If there is not, a date still does more work than urgency language, because it gives the request somewhere to sit in their calendar instead of somewhere to sit in their conscience.

The four fixes, assembled

Under 150 words, and there is nothing left for the borrower to work out. The exact item, why a screenshot will not do, where it goes, what to expect when they get there, when it is needed, and what to do if they get stuck.

Notice what is absent. There is no explanation of why underwriting asked, and no reassurance about what the request means. If your lender has given you approved wording for that, add it. If not, the message is complete without it.

Where AI helps here

Document requests are high-volume, repetitive and formulaic, which makes them ideal for drafting assistance. The one rule is that the exact item comes from you.

The instruction not to interpret the condition is doing real work in that prompt. Ask a model why underwriting wants a document and it will tell you, confidently, and its answer will be a guess about a file it cannot see.

You are also not obligated to explain the reason at all. If you were given one, use it. If you were not, the message says what is needed and by when, and stays quiet about why.

One more thing, and it is not about speed

Apply your document-request process consistently. How much help a borrower gets, how much urgency they hear, and how often you follow up are worth deciding deliberately rather than leaving to whoever you happened to enjoy talking to that morning. Which differences matter, and what they attach to, is a fair-lending question with federal and state layers that vary by lender and by state. Your compliance team should define those obligations for your lender and your jurisdiction.

None of the four fixes above is clever. Name the exact item, give the channel, do not interpret the request, give a date. Together they can reduce unnecessary round trips per condition, and they give the borrower an officer who reads as being on top of the file rather than one who keeps asking for more.

The Claude Workflow System for Mortgage Loan Officers has 94 workflows covering document requests, status updates, rate-lock communication, closing day and the conversations nobody enjoys having.