Document request email templates

A document request email needs five things: what you need, why you need it, when by, where to put it, and what happens if it is late. Most of them are ignored because they carry the first three and leave the fourth to "just reply with the attachments."

The wording matters less than people think and the structure matters more. Every request that lands does the same five things in the same order, and every request that gets ignored has dropped one of them:

1. 01The documents, named individually. "Your paperwork" is a research task for the recipient; "your last two pay stubs" is an instruction.
2. 02What they are for. One clause is enough — people move faster when they know which of their own deadlines this belongs to.
3. 03A date. Without one the request is an item on a list that has no top, and it will sit there.
4. 04Somewhere to put them. This is the step almost everyone skips, and the reason for most of the follow-ups.
5. 05What happens if it slips. Not a threat — the actual consequence, so the recipient can weigh it against everything else in their inbox.

The version to send when nothing has gone wrong yet. It is short on purpose: every additional sentence is a sentence someone decides to read later.

Send this one before the deadline rather than after it, and keep the accusation out of it. Most non-responses are not refusals — they are a person who opened the first email on a phone, could not act on it in that moment, and never came back to it.

The last line is the one that earns its place. A request that only repeats itself gives the recipient nothing new to do; asking which item is the blocker turns a silent non-response into a reply you can work with.

Firm without being unpleasant. The consequence is stated as a fact about the schedule, not as a warning about them.

It is almost never unwillingness. The request arrives while the person is somewhere they cannot act on it, and the effort of coming back to it later is higher than it looks: find the email again, find the documents, work out how to send four files that are too large to attach, hope they arrive.

Each of those is a place to lose them, and the last one is the worst — Gmail caps attachments at 25 MB, which a handful of phone photos of receipts will clear. The client who hits that limit does not usually ask what to do instead. They compress the files, or they put it off, and you find out days later. The longer version of that argument is in how to collect files from clients without making them sign up.

The single change that most reduces follow-ups is writing the list as items rather than as a description. Compare "please send your financial documents" with a list of four named things: the first asks the recipient to decide what counts, which is exactly the decision they are paying you to make. The second is a checklist they can work through.

• Name each document the way the recipient would recognise it, not the way your software files it.
• Say how many of a repeating thing you need — two pay stubs, three months of statements — so nobody sends one and waits.
• Say when a photo is acceptable and when it is not. Most re-requests are a scan asked for and a screen photo received.
• Keep the list to what you need now. A request for eleven things gets started later than a request for four.
• If the list is long enough to need sorting on arrival, that belongs to the intake rather than the email — document collection software covers the filing side.

The fourth item on the list at the top is the one this page exists for. An email that asks for six documents and offers no destination is asking for six attachments, which means the size limit, the missing context, and a thread you have to dig through later to work out what arrived and from whom.

A link fixes it in one step, and the link belongs in the first email rather than the third. Drive File Request creates one per request: your client opens a page, adds the files, and everything lands in a folder inside your own Google Drive — no account on their side, nothing installed, and no reply-all thread carrying 40 MB of receipts. You can ask for their name and the document type on the upload page too, so what arrives is labelled rather than named scan_003.pdf.