Most firms do not have a document problem. They have a follow-up problem. The request goes out once, half of it comes back, and the rest takes three reminders, two phone calls and a search through an inbox. The fix is rarely a firmer email. It is a request that is easier to finish than to ignore.
The seven changes below come from one observation: clients are not avoiding you. They are busy, they are on a phone, and they are not sure what you meant. Remove each of those three obstacles and most of the chasing goes away.
Why clients go quiet
It helps to look at a stalled request from the client’s side. They opened your email on the bus. It listed nine things. Two of them they have, three they would need to find, and four they do not recognise. Replying with two attachments feels incomplete, so they decide to do it properly at the weekend. At the weekend they cannot find the email.
Nothing in that story is bad faith. Every step is a small cost you added: a list they had to interpret, a channel that shows no progress, and no easy way to send part of the answer now. The rest of this guide removes those costs one at a time.
1. Ask for documents, not “your paperwork”
A client who reads “please send your tax documents” has to work out what that means. A client who reads “T4 slips, one from every employer you had this year” does not. Name each document, say how many, and say which pages. Every item you leave vague comes back as a question or as the wrong file.
A useful test: could someone who has never worked with you find the right document from the item’s name alone? “Proof of address” fails that test. “A utility bill or bank statement from the last 3 months” passes.
2. Put instructions where the upload happens
Instructions in the body of an email are read once and lost. Instructions under the upload button are read at the moment they matter. One sentence is enough: where to download the notice of assessment, which pages of the passport, how recent the bank statement must be.
Write them the way you would say them on the phone. “Download it from CRA My Account, or send a photo of the paper copy” does more than a paragraph of formal wording, because it tells the client there are two acceptable ways to finish.
3. Separate required from optional
A list of fifteen items feels like fifteen chores. If nine of them only apply to some clients, mark them optional. Clients finish what is required, and “complete” means something you can act on.
This matters for your own tracking as much as for the client. If every item is required, a client with no childcare costs can never complete the request, and your list of outstanding work fills with requests that are in fact done.
4. Give every document one home
When clients can reply by email, by text and through a shared drive, they will use all three. Pick one place, give each document its own slot, and show the client what is still empty. A visible gap is a better reminder than any message you can write.
One home also solves the partial answer. A client who can upload two of five documents today, and see three empty slots waiting, has started. A client who is waiting until they have all five has not.
5. Make it work on a phone
Most clients will open your request on a phone, and many documents exist only on paper. If taking a photo and attaching it takes more than a few taps, the request waits for “when I’m at my computer”, which is often never.
Anything that needs an account and a password adds a step where people give up. A personal link and a one-time code sent to the same email address proves who they are without asking them to remember anything.
6. Return files with a reason
“This one doesn’t work” starts a conversation. “Page 2 is missing” ends one. When a file is not usable, say exactly why, next to the document, so the second upload is the right one.
Keep a short list of the reasons you use most: pages are missing, the image is too blurry to read, this is the wrong year, the document has expired. Picking from a list is faster than writing, and clients learn what each one means.
Batch your returns. Five separate emails about five files feel like five complaints. One message listing all five, with a link, feels like a to-do list.
7. Let reminders send themselves
A reminder that depends on someone remembering to send it will be late. Set a rhythm, for example every three days up to five times, and have each reminder list only what is still missing. Stop automatically when the last required document arrives, so nobody is chased for something they already sent.
Two details make automatic reminders feel helpful instead of nagging. First, a cap: after a set number, a person should take over. Second, specificity: “1 document still missing: notice of assessment” reads as help. “You have outstanding items” reads as a debt.
In Sealio, reminders are on from the moment a request is sent. See how automated reminders work.
A reminder message that works
If you write your own, a good reminder has four parts, in this order:
- What is still needed, by name. Not everything you asked for, only what is missing.
- When it is due, or that it is now overdue.
- The link to send it, in the message itself.
- Who to ask if they are stuck, in one line.
Leave out apologies for bothering them and explanations of why you need the documents. They already know.
What this looks like in practice
- Build a checklist once for each kind of work you do.
- Send it to the client with a due date.
- Let the system follow up while you do other work.
- Review each file as it arrives: accept it, or return it with a reason.
- Download the complete, named set when the request is done.
None of these steps needs your client to create an account or learn a tool. That is the test of a good request: the client only ever sees a list and an upload button.
How to tell it is working
You do not need a dashboard to see the difference. Watch three things over your next twenty requests: how many days pass between sending a request and the first upload, how many requests complete without a personal follow-up from you, and how many files you have to return. If the first number falls and the second rises, the request is doing the chasing.
Start from a checklist that already follows these rules. Browse the checklist templates.