Doculane
To request documents from a client, send a short email that names each required item, identifies the relevant period, gives an agreed submission date and links to one upload destination. Tell the client how to report an unavailable item. Before following up, check what has already arrived and request only the outstanding documents.
Prepare your request
A useful request answers five questions: what to send, which period it covers, when to send it, where to upload it and who can help. The client should not need to reconstruct the task from several earlier messages.
| Part of the email | Include this | Avoid this |
|---|---|---|
| Subject | The work or period, plus the requested action | “Quick question” with no context |
| Checklist | Specific documents, accounts or file groups | “Send everything we need” |
| Instructions | The period and what a complete file contains | Unexplained internal terminology |
| Submission date | A date agreed for this request | An invented legal deadline or an unexplained threat |
| Destination | One clearly labeled submission link | Several competing folders and attachments |
| Exception route | A person to contact if an item is unavailable | Silence being interpreted as approval or completion |
The templates below are original examples for adaptation, not messages tested on customers. Replace bracketed fields, remove irrelevant items and verify the link before sending. Do not claim an upload is private or compliant unless you have confirmed the actual service and configuration.
Email templates
The first request
Use this version when the client is seeing the checklist for the first time. Include enough context to identify the work without repeating the whole engagement agreement.
Subject: Files for [project or period] — requested by [date]
Hi [first name],
We're preparing [specific next step] for [business or project].
Please send the following by [day, date]:
- [Document 1: source/account + period + expected contents]
- [Document 2: source/account + period + expected contents]
- [Document 3: source/account + period + expected contents]
Submit the files here: [upload link]
If an item doesn't apply or isn't available yet, reply with its name
and a short explanation. [Contact name] can help with questions.
Thank you,
[Name]
[Company]
Keep the client-specific checklist in the request itself if the email would otherwise become difficult to read. The email and the linked checklist should agree about the scope and date.
After a partial delivery
Acknowledge receipt, then name the missing items. Avoid sending the original full list as though the client had done nothing.
Subject: Remaining files for [project or period]
Hi [first name],
The files for [received items] have arrived. Thank you.
We still need these items for [specific next step]:
- [Outstanding item 1, including period]
- [Outstanding item 2, including period]
Please add them through [upload link] by [agreed date].
You don't need to resend the files already listed as received.
If one of the remaining items is unavailable, let [contact] know.
Thank you,
[Name]
“Received” describes delivery. Do not replace it with “approved” unless someone has actually reviewed and approved the document in your business process.
A corrected or complete document
Describe the mismatch precisely. “Wrong file” leaves the client guessing whether the problem is the document, the dates or the format.
Subject: Replacement needed: [document name] for [period]
Hi [first name],
We received [file or document description]. It appears to cover
[period received] / it does not include [specific missing detail].
For [work or request], we need [correct period or complete contents].
Please submit the replacement here: [upload link].
If you cannot obtain that version, reply to [contact] so we can
agree on the next step rather than asking you to resend the same file.
Thank you,
[Name]
Describe only the issue you checked. For example, discovering a missing page does not justify saying the rest of the document has passed review.
When missing files block the work
Explain the specific dependency and ask for a practical reply. Use this template only when the stated next step really is blocked.
Choose an upload method
Choose the destination according to the collection task, not just the tool your team already uses. Test it as an external recipient before putting the link in a template.
| Method | Client account requirement | Useful when | What the team still needs to establish |
|---|---|---|---|
| Email attachments | No new portal account; client uses email | An isolated exchange fits the team's approved process | How to track missing items and manage copies/access |
| Google Forms with a file-upload question | Google sign-in is required for the upload | Respondents can use Google accounts and a form suits the task | Appropriate form restrictions and follow-up process |
| Dropbox file request | A Dropbox account is not required to submit files | The team needs an external file-collection destination | How to track individual checklist requirements in its process |
| Doculane document request | No client Doculane account; email verification and sender access rules apply | The team needs a checklist, staged submissions and scheduled reminders | Suitable formats, allowances, access and retention arrangements |
The account requirements above come from Google Forms Help and Dropbox Help. This is a comparison of collection approaches, not a full feature audit or a security ranking. Product capabilities and policies can change.
An upload link that opens for your signed-in team may behave differently for a client. Check the recipient’s path, allowed formats and sender identity requirements before sending it.
Follow-up workflow
Maintain one current checklist and one follow-up owner. Before sending a reminder, check receipt, review notes and any explanation the client has provided.
Use this editorial sequence: check → acknowledge → specify → link → exception route. It is a writing aid, not a measured claim about response rates. A reminder should become more specific as the team learns what is missing, rather than simply becoming more forceful.
Doculane can hold the document checklist, track received items and schedule email reminders for the request. It supports saved templates and later submissions while a request remains active. It does not turn these four examples into a preconfigured email sequence, guarantee inbox delivery or automatically create a new request each month.
For a narrower starting list, use the monthly bookkeeping checklist or the web design client content checklist.
Frequently asked questions
How often should you remind a client?
Agree on a cadence that fits the work, document availability and the client relationship. There is no universal interval established by these templates. Stop routine chasing to clarify an exception when another identical reminder will not resolve it.
Can you request documents without creating a client account?
Yes. Some file-request tools support that flow. In Doculane, clients verify their email with a one-time code and must meet the workspace’s sender access rules; account-free does not mean anonymous or unrestricted.
Can these emails be used for sensitive documents?
The wording alone does not establish suitability. Confirm the destination, recipient access, retention, recovery and your organization’s requirements before collecting sensitive records. Do not put passwords or recovery codes in the template.
Is a reminder sent the same as a reminder delivered?
No. Submission to an email provider does not establish inbox placement or that the client read the message. Review delivery information separately from the document checklist.
Put the templates to work
Choose the email that matches the current situation, tailor the checklist and check the external submission path. Use the collection record to decide what to ask for next.