Request each document by name, send a secure upload link instead of asking for photos in a text, stop the reminders the moment the document arrives, and refresh documents before they go stale. GoHighLevel can track each item as an opportunity field and send only the reminders that match what is still missing. The bottom line: borrowers feel nagged when they get the same message about a document they already sent, and they send sensitive files to the wrong place when the request is vague.
Documents expire, so the chase has a clock
Consumer guides from lenders say pay stubs are generally considered current for about 30 days, bank statements for about 2 months, and a credit report for about 120 days. A lender guide cites Fannie Mae's Selling Guide, which allows credit documents no more than four months old on the note date. A document that was fine at application can be stale by closing, so the reminder system needs two jobs: request what is missing, and request a refresh of what has aged out.
Where the file goes matters more than how fast
Mortgage brokers are financial institutions under the FTC Safeguards Rule, according to the National Association of REALTORS and an FTC press release summarized by the National Law Review, which requires a written information security program with administrative, technical, and physical safeguards. Pay stubs, bank statements, and tax returns are exactly the customer information that program protects. A text that asks the borrower to send a photo of a paystub invites the file into a thread that is not an access controlled place. The better request is a link to your loan origination system's secure upload page, or to a portal your security program has approved.
| Document | Typical freshness | Refresh request |
|---|---|---|
| Pay stubs | About 30 days at underwriting | Ask for the latest stub when the file moves to underwriting |
| Bank statements | About 2 months | Ask for the next monthly statement when it is issued |
| Credit report | About 120 days; four months on the note date | Loan officer decision to re pull, not a borrower request |
| Tax returns and W 2s | By tax year | Ask once, with the year named |
Build it in HighLevel
- Add a checkbox or dropdown field for each document on the opportunity, with values Needed, Received, and Refresh needed.
- Create a workflow that starts when the stage changes to Documents requested and sends one text and one email naming each document that is still Needed, with the secure upload link.
- Add a Wait of 2 days, then an If/Else on any field still Needed. If none, end the workflow. If some, send one shorter reminder naming only those.
- Repeat once more at day 5, then create a task for the processor to call.
- When a processor marks a field Received, the Opportunity Changed trigger removes the loan from reminders for that item.
- Add a second workflow with a Custom Date Reminder set to 25 days after the pay stub date, to request a refresh when underwriting is near.
- Turn on Stop on Response so a borrower's reply goes to the processor.
Two messages, written out
Request: Hi Dana, this is Priya at [Brokerage]. To keep your loan moving, we still need: your last 2 bank statements and the signed letter of explanation. Please upload them here: [secure link]. Please do not send them by text or email. Reply STOP to stop messages. Reminder: Hi Dana, Priya again. Still needed: the signed letter of explanation. Here is the upload link: [secure link]. If a question is holding you up, call me at [number].
Worked example
A broker with 30 loans in processing and 4 open items per loan sends 120 requests at the start. If each loan averages 1.5 reminders instead of 4 because received items stop the chase, that is 45 reminder messages (30 loans times 1.5) instead of 120. The averages are assumptions to replace with your own.
Texting rules
Document requests are about the borrower's own application, so they are informational, but they still need consent and a registered number. Keep the text itself free of loan numbers, balances, and personal identifiers.
Why borrowers ignore a document request
Most borrowers who do not respond are not refusing. They do not know which document you mean, they cannot find it, or they are afraid of sending sensitive files to the wrong place. A request that names the document, says what it should show, and links to the upload page removes all three. For a bank statement, say all pages, both sides, and the last 2 months. For a letter of explanation, give a one line example of what it should say. A single clear request is followed more often than three vague reminders.
What a reminder should leave out
A reminder should not mention the borrower's balance, income, or the reason a document is needed beyond a short phrase such as for underwriting. It should not scold. It names what is still missing, repeats the link, and gives a phone number. If a borrower writes back that they cannot find a document, create a task for the processor to call, since a person can explain faster than a third text.
How this was handled before
A processor emailed a checklist and followed up by phone, and borrowers often replied with photos attached to a personal email. The checklist in the loan file stayed the source of truth, and the chase depended on the processor's day. Fields that drive the reminders keep the chase in step with the file.
What to measure
Track items requested, items received within 3 days, reminders per loan, and loans delayed by a stale document. A falling reminder count with a stable receipt rate means the system is working.
Questions people ask
How long are mortgage documents valid?
Lender guides say pay stubs are current for about 30 days, bank statements for about 2 months, and credit reports for about 120 days. Fannie Mae's Selling Guide allows credit documents up to four months old on the note date.
Should borrowers text photos of their documents?
No. Send a link to your secure upload page, since mortgage brokers are financial institutions under the FTC Safeguards Rule.
How many reminders is too many?
Send one request, one short reminder, and one more at day 5, then call. Stop the moment the item is received.
You can start a GoHighLevel account here and build the checklist fields, or see opportunities and workflows together in our capabilities demo.