Key takeaways
- A written checklist for each engagement type stops you from asking for documents one email at a time.
- An instruction and an example under each item prevent most wrong or incomplete uploads.
- One link per client keeps every file in one place, unlike attachments spread across email threads.
- Checking files on arrival and sending reminders that list only the missing items shortens the chase.
Why collecting client documents by email breaks down
Most firms start by emailing a list and asking clients to reply with attachments. It works for one or two files. With ten items, the documents arrive across several threads, some as photos, some as forwarded PDFs, and a few not at all.
The real cost is the follow-up. Someone on your team has to open every attachment, compare it with the list, and write back about what is still missing or unreadable. Each round adds days, and the client loses track of what they already sent.
A better process fixes the causes rather than the symptoms. Clients send the wrong file when the request is vague, and they forget when nothing reminds them. The steps below deal with each of those points in order.
Step 1: Build a checklist for each type of engagement
Start with a written checklist for every service you offer: a personal tax return, a company year-end, a visa application, a new hire. Write it once, then reuse it for every client of that type. Your team stops rebuilding the list from memory, and clients get the same clear request every time.
Keep each item specific. "Bank statements" is too vague. "Bank statements for every business account, January to December 2026, all pages" tells the client exactly what to look for.
Mark which items are required and which only apply in some cases, such as rental income or a foreign pension. A short checklist that fits the client gets finished. A long generic one gets abandoned halfway.
- Proof of identity: passport or driver's license, not expired
- Proof of address dated within the last 3 months
- Bank statements for the full period, every page
- Income documents such as payslips or year-end tax forms
- Signed engagement letter
- Last year's tax return, for new clients
Step 2: Explain each item with an instruction and an example
Clients are not experts in your paperwork. A one-line instruction under each item answers the question they would otherwise email you about. For a bank statement, say which pages you need and that a screenshot of the banking app will not do.
An example removes even more doubt. Show a blurred sample of the document, or describe it the way the client will see it: "the PDF your bank calls Monthly statement, not the transaction export." For identity documents, say that all four corners must be visible and there should be no glare across the photo.
Write instructions in plain words and avoid internal jargon. A form code like P60 or K-1 means something to you, but add a short description so the client knows where to find it.
Step 3: Collect documents from clients through one link, not email attachments
Email attachments scatter files across inboxes, hit size limits and get lost in long threads. A single upload link per client gives them one place to send everything, and gives you one place to see what has arrived.
The link should work without an account or password, and it should open on a phone. Many clients will photograph documents with the phone camera, so the upload page needs to accept photos as well as PDFs. Let clients come back to the same link later, because they rarely have every document at hand in one sitting.
If you use a shared folder instead, create one per client and never reuse it between clients. A shared folder shows the client nothing about what is still missing, so you still end up chasing by email.
DocAsker is built around this step: each client gets one secure link with their checklist, needs no account, and can upload from a phone or computer and return later to finish.
Step 4: Check every file when it arrives
Check files as they come in, not the night before a deadline. When a problem surfaces weeks later, the client has moved on and the fix takes another round of emails.
Check the same things every time. Is the photo readable, or is it blurred, glared or cut off at the edges? Is it the document you asked for, or a utility bill sent in place of a bank statement? Does the date or period match, are the signature fields filled in, and did every page arrive?
When a file fails, tell the client exactly why and what to send instead. "The statement covers February only. Please upload January to March" gets a fix the same day. "Please resend" gets a confused reply.
DocAsker runs these checks with AI the moment a file is uploaded and shows the client the reason in plain words, so they can upload a better file straight away. Your team only sees files that passed, plus anything flagged for a person to review.
- Image quality: blur, glare, cropped edges
- Document type: the file matches the item requested
- Dates and periods: statement period, issue date, expiry date
- Signatures: every signature field is filled in
- Completeness: all pages of multi-page documents
Step 5: Set a reminder cadence before you send the request
Decide the reminder schedule when you send the request, not when you notice it is late. A simple cadence works for most firms: a friendly reminder after 3 days, a second one after a week, and a final one a few days before your deadline.
Each reminder should list only what is still missing or needs a retake. A client who has already sent eight of ten documents should see the two that remain, not the full list again. That makes the reminder quicker to act on and shows them they are nearly done.
Stop reminders as soon as the checklist is complete. Few things annoy a client more than a reminder for documents they sent yesterday. If you send reminders by hand, keep a simple tracker so nobody on the team sends a duplicate.
- Day 0: the request with the checklist and the link
- Day 3: a friendly reminder listing the missing items
- Day 7: a second reminder with the deadline
- 3 days before the deadline: a final reminder
- After that: a phone call
Step 6: Name and file documents the same way every time
Files named IMG_4021.jpg or scan(3).pdf cost time whenever someone opens the folder. Pick one naming pattern and apply it to every accepted file, for example 2026-03_Nova-Logistics_Bank-statement.pdf: period, client, document.
File documents to one agreed location per client, sorted by year or engagement. Whether that is your practice software, Google Drive, Dropbox or OneDrive matters less than everyone using the same structure.
Rename and file at the point of acceptance, not in a batch at the end. Once a file is checked and named, it is ready for work and nobody has to sort it again.
Security basics for collecting client documents
Client documents contain identity numbers, bank details and salaries, so treat them with care from the first request. Avoid email attachments for sensitive files where you can, since copies stay in several inboxes indefinitely.
Whatever tool you use, look for encryption in transit and at rest, links that expire or can be revoked, and a log of who uploaded and downloaded each file. Decide how long you keep documents, and delete them when that period ends.
Data-protection rules vary by country and by profession, so confirm your own obligations. Ask any software provider for a data processing agreement and keep it on file.
- Encrypted uploads instead of email attachments
- One link per client, never shared between clients
- Links that expire or can be revoked
- A log of every upload and download
- A written retention period, and deletion when it ends


