Ask most brokerage teams what slows a file down the most and the answer is rarely the lender — it is waiting on the client for documents that were requested once, vaguely, by email, and then chased individually for two weeks. The chase itself is expensive: every follow-up is a task someone has to remember to do, every partial document set is a delay at submission, and every unsecured attachment is a privacy exposure the brokerage owns.
None of that is a client-behaviour problem to solve with more patience. It is a system problem, and it has a system-shaped fix: request everything at once in a document a client can actually follow, collect it through a portal instead of an inbox, run reminders on a fixed schedule instead of an ad hoc one, and handle everything that comes in the way Canadian privacy law expects. This playbook builds that system in five steps.
Step 1. Diagnose why the chase happens before fixing it
Most document chases trace back to the same root cause: the initial request was incomplete, unclear, or scattered across more than one message, so the client sent back a partial answer to what they thought was being asked. The document-collection bottleneck is rarely about client responsiveness — it is almost always about request quality.
- →A request sent as a list of items works better than a request explained in paragraphs.
- →A request naming a specific format (a PDF, not a photo of a screen) avoids a second round of collection.
- →A request that says why a document is needed gets a faster response than one that just names it.
Step 2. Build one single, complete request instead of a trickle
The fix starts before the first message goes out: build the complete document list for that file type before requesting anything, so the client sees the whole list once instead of a new item arriving every few days. A ready-to-send starting point for this exists in Treadstone's document request email templates, which cover the initial ask, the nudge, and the escalation in one sequence.
- 01Confirm the deal type first (employed, self-employed, rental, new-to-Canada) so the list matches the file, not a generic template.
- 02List every document by name, not by category (“two most recent pay stubs,” not “proof of income”).
- 03Group the list by urgency if some items are needed immediately and others only if a condition triggers them.
- 04Send it once, in full, rather than adding items as they occur to whoever is working the file.
Step 3. Move collection into a portal, not an inbox
Email attachments scatter across threads, get lost in forwarded chains, and are the least secure way to move a client's income documents and identification. A shared document portal — whichever the brokerage's point-of-sale or CRM provides — keeps everything in one place, timestamps what arrived and when, and gives the client one link to return to instead of a growing email thread.
The habit that matters: every team member uses the portal for every file, every time — a system half the team bypasses for convenience is not a system.
Step 4. Run reminders on a fixed cadence, not from memory
| Day | Action |
|---|---|
| Day 0 | Send the complete request through the portal. |
| Day 3 | Automatic nudge if the list is not yet complete. |
| Day 7 | Personal follow-up call or message, not another automated email. |
| Day 10 | Escalate to the broker or team lead if the file is time-sensitive. |
A fixed cadence removes the guesswork of deciding when a follow-up is overdue, and it means no client goes silent for two weeks without anyone noticing.
Step 5. Handle everything the collection produces in a PIPEDA-safe way
Every document a client uploads is personal information under the Personal Information Protection and Electronic Documents Act (PIPEDA), and the collection system should reflect that from the first request onward, in line with the fuller picture in handling client documents under PIPEDA.
- →Collect only what the file actually needs — not a broader document set “just in case.”
- →Store documents in the portal or file system the brokerage has approved, not in personal inboxes or downloads folders.
- →Limit access to the people actually working the file.
- →Follow the brokerage's retention schedule for disposal once a document is no longer required.
Review the chase itself every quarter, not just the file
Track how many files needed more than two reminder rounds and why — a recurring reason (a confusing request line, a document type clients consistently misunderstand) is a fixable system problem, not twenty individual client problems.
This is the layer of a brokerage's operations that Treadstone's fulfillment services are built to run day to day — the request, the portal, the cadence, and the compliant handling, without it depending on any one person remembering to follow up.