How to ask a borrower for a document re-upload
Most borrowers are genuinely trying to help. When they re-upload the wrong thing, or the same incomplete document a second time, it's almost always because the re-upload request was too vague.
"Please re-submit your bank statement" creates a coin-flip chance you'll get the same file back. "Please re-upload all pages of your Chase statement for January 2026, the upload we have is missing pages 4-6" gets the right document.
This post is about writing the second kind of request.
The 4 reasons documents need to be re-uploaded
Understanding why a document failed makes it much easier to write a clear request:
Missing pages. The most common problem by far. A borrower takes a photo of each page, or downloads only part of the statement, or the PDF cuts off before the last page. Underwriting counts pages against the expected statement length.
Wrong date range. The borrower uploads their most recent statement when underwriting needs a specific month, or uploads the wrong year of a tax return. They followed the instructions as they understood them, but the instructions weren't specific enough.
Illegible scan. Dark photo, cropped corners, low resolution. Usually happens with older documents or anything photographed with a phone at an angle.
Wrong document entirely. The borrower confuses account types, uploads a credit card statement instead of a checking account, or sends the wrong year's W-2. More common than you'd think, especially when a borrower has several accounts.
What makes re-upload requests fail
Before getting to scripts, it's worth naming what goes wrong:
Vague language. "Please re-send your bank statement" doesn't say which account, which month, or what was wrong. The borrower has to guess.
No acceptance criteria. Telling someone to re-upload doesn't tell them what "acceptable" means. Borrowers who uploaded a screenshot once will upload a screenshot again unless you tell them not to.
Multi-item requests. Sending three re-upload requests in one message creates confusion about which ones are urgent and which ones can wait. Separate requests for separate items.
Alarming framing. "Your document was rejected" sounds like something went wrong on the borrower's end. "Underwriting reviewed this and needs one small fix" is factually the same thing with much less drama.
No upload destination. If you ask for a re-upload but don't include the link, a borrower who already has your email address open will email it back to you. Now you have a second version in your inbox instead of in the checklist.
Scripts for each failure type
Use these as a starting point. Paste them into the checklist item's notes or re-upload reason field on the borrower portal, not a separate email.
Missing pages:
"Underwriting needs all pages of your [BankName] statement for [Month]. The upload we have appears to be missing pages. Please download the complete PDF from your bank's website and re-upload it using this link. Include all pages, even blank ones."
Wrong date range:
"Thanks for uploading. Underwriting needs your [BankName] statement specifically for [Month/Year]. Please upload that month's statement (all pages, PDF preferred) using this link."
Illegible or low quality:
"The [document name] upload is hard for underwriting to read clearly. Please download a fresh PDF copy from [bank/employer portal] and re-upload it using this link. A direct download from the website works much better than a photo."
Wrong document:
"It looks like we received [what was sent]. For this request, we need [specific document name and date range]. Please upload that one using this link and we'll get it reviewed."
One request per problem
If three documents need re-uploading, send three separate requests. This is worth the extra step.
When borrowers get a message that says "please fix items 1, 3, and 4," they often fix item 1, think they're done, and wait for the next message. Separate requests make it clear that each one is its own task, and it lets you track them individually in your conditions tracker.
If one item is more urgent than the others (say, it's the only thing blocking a resubmission), ask for that one first. Let the others follow once the blocker is resolved.
Closing the loop
When a re-upload comes in, review it before marking it as received. If it looks good, send a quick confirmation:
"Got it, looks good. No more action needed from you on this one."
That message might seem unnecessary but it stops another round of "did you get it?" texts. Borrowers who hear nothing after re-uploading assume something is still wrong.
Ready to get started?
Try using BorrowerDocs to send a borrower portal, collect secure uploads, and track document status in one place.
Start for Free