Most brokers ask for documents the same way they'd ask a colleague for a favour — a quick, friendly, slightly vague message hoping the client fills in the blanks. Clients don't know what a “NOA” is, don't know why last year's isn't enough, and don't know that a blurry phone photo of a pay stub will bounce the file back. The result is a document chase that runs three or four rounds longer than it needs to, entirely because the first ask wasn't built to be understood and acted on in one read.
This guide is three ready-to-send templates — the initial complete-list ask, the day-3 nudge, and the day-7 escalation — plus the formatting rules and delivery choices that determine whether a client sends everything back correctly the first time. None of it requires new software; it requires writing the request the way a client actually reads it.
Why the first document request decides everything
A document request usually fails for one of three reasons: the client doesn't understand what's being asked for, doesn't understand why it's needed, or doesn't have an easy way to send it back. Fix those three things in the first email and most files come back complete on the first try; leave any one of them vague and every missing document becomes its own follow-up thread.
The fix isn't a longer email — it's a more specific one. Name every document exactly the way it appears on the client's own paperwork (not the internal shorthand a broker uses), explain briefly why each item matters, and give one clear channel to send it all back. The templates below are built around those three rules.
The real cost of a vague ask: every round of back-and-forth adds days to the file, and each round makes the client a little more anxious about a process that should feel routine.
Template 1. The complete-list, one-ask email
Send this once, at the start of the file, with every document the client will need listed in one place — not a partial list that grows over several emails. A client who sees the full scope up front plans for it; a client who gets a new request every few days starts to wonder what else is coming.
Subject line: Your mortgage document checklist — everything in one place
Hi [Client First Name], thanks again for choosing to work with me on your mortgage. Below is the complete list of documents I'll need to move your file forward. Sending everything together, in one reply or one upload, is the fastest path to an approval — partial batches usually mean extra rounds of back-and-forth later. [Insert the specific document list for this file's employment and deal type here.] If anything on this list doesn't apply to your situation, just let me know and I'll confirm what to use instead. Once I have everything, I'll confirm receipt and let you know the next step. Thanks, [Broker Name].
The bracketed document list should be the specific set for that client's employment type and deal type — not a generic list copied across every file. A salaried purchase and a self-employed refinance need different documents, and sending the wrong list is its own source of confusion.
Template 2 & 3. The day-3 nudge and the day-7 escalation
Silence after the first email almost never means the client is ignoring you — it usually means the request got buried, or the client is waiting on their employer or accountant for one item. A short, friendly nudge at day 3 catches most of these before they become a real delay.
Day-3 nudge subject line: Quick check-in on your mortgage documents
Hi [Client First Name], just following up on the document checklist I sent a few days ago — wanted to make sure it didn't get lost in your inbox. If you've already sent everything, no need to reply, I'll confirm once I've reviewed it. If you're waiting on anything from your employer, bank, or accountant, let me know which item and I can suggest a faster way to get it. Thanks, [Broker Name].
If the file is still incomplete by day 7, the tone shifts from a friendly check-in to a clear statement of what's at stake — without being alarmist. This is also the point to name a specific missing item rather than repeating the full list.
Day-7 escalation subject line: Time-sensitive: [X] still needed to keep your file on track
Hi [Client First Name], I want to flag that [specific missing document(s)] is still outstanding, and it's the piece holding up your file right now. To keep your timeline on track for [rate hold / closing date, if applicable], I'd need this by [specific date]. If there's a reason this is taking longer — waiting on someone else, a technical issue uploading, anything — let me know and we'll figure out a path together. Thanks, [Broker Name].
Formatting rules that cut back-and-forth in half
- →Name files the way you'll search for them later — ask clients to save documents as “LastName_DocumentType_Date” rather than accepting whatever the phone or scanner auto-names them.
- →Set a photo standard up front — whole document in frame, flat surface, good light, no shadows across the text; this alone eliminates a large share of re-request cycles caused by unreadable images.
- →Ask for PDF over photos where the client's device allows it — most phones can scan-to-PDF directly from the camera app, and a PDF rarely has the framing or glare problems a photo does.
- →Batch by document, not by message — one email or upload with everything attached is easier to track than five separate texts sent throughout the day.
None of this needs to sound like a set of rules to the client — folding the naming and photo guidance into the first template's bracketed instructions keeps it friendly while still doing the work of preventing unusable submissions.
Handling the client who says “I'll send it this weekend”
A vague commitment to a vague timeframe is the single most common way a document request quietly slips by a week or more. The fix isn't pressure — it's converting the vague promise into a specific one, in the same conversation, without making it feel like a demand.
A simple reply works: “Sounds good — would Saturday morning or Sunday evening work better for you? I'll check in right after whichever time works.” Naming two specific windows, rather than accepting “this weekend” as-is, gives the client an easy choice instead of an open-ended task, and gives the broker a concrete point to follow up against.
Why this matters: an open-ended commitment has no natural trigger to remind the client; a specific window does. The gap between “this weekend” and “Saturday morning” is often the gap between a two-day delay and a two-week one.
Secure delivery: portals vs. email, and the privacy line
Mortgage documents carry sensitive personal and financial information, and how that information is collected and stored is not just a convenience question — it's a privacy obligation. Under PIPEDA's Safeguards principle, personal information must be protected by security measures appropriate to its sensitivity — and a client's income documents, identification, and account statements sit toward the sensitive end of that scale.
A secure client portal is generally the stronger choice over plain email attachments, since it keeps documents off personal inboxes and gives the brokerage consistent control over access and retention. Where email is used because that's what a client is comfortable with, avoid asking clients to send sensitive documents to a personal address, and remove or archive attachments out of the inbox promptly rather than leaving them to accumulate indefinitely.
The practical rule: collect only what the file actually needs, store it somewhere access-controlled, and be able to explain to a client — in one sentence — how their documents are being protected.
For the fuller version of this conversation — what happens in the first 24 hours after a client says yes, before the document ask even goes out — see the Client Onboarding Welcome Sequence guide. And for the operational side of a bottleneck that keeps recurring across files, this article on fixing the document collection bottleneck goes deeper on root causes.