Document collection · 6 min read

How to collect documents from clients without living in your inbox

Email is a fine way to ask for one document once. It is a terrible way to collect eight documents from forty people and know, at any moment, which ones you still do not have. Here is what works instead, whether or not you use software for it.

Why email fails at this specific job

An email request has no state. Once sent, it does not know what came back. Every "did you get my passport?" and "which ones were missing again?" exists because neither side can see the list with ticks against it. Add the fact that attachments get forwarded, that a passport scan in a mailbox is a passport scan in every mailbox it was copied to, and that the record of who checked the file lives in someone's memory, and the problem is structural rather than a matter of writing better emails.

1. Name every item, separately

"Please send your supporting documents" produces a ZIP file and a guess. "Proof of address, dated within the last three months" produces the right document or a specific question. List each item on its own, say whether it is required, and say what counts — a utility bill or bank statement, not a mobile phone contract. Where several files make up one item (twelve monthly statements), say so, and let the item accept several files rather than creating twelve items.

2. Separate answers from evidence

A date of birth is an answer. A passport is evidence for it. Keeping the two apart means you can accept the answers and reject one piece of evidence without reopening everything, and it means the client is not asked to retype what the document already says.

3. Give the client one place that shows what is missing

This is the step that removes most of the email. If the client can see their own checklist — five items, three done, two outstanding, one flagged with a note — they do not need to ask you where they stand, and you do not need to work it out to tell them. A shared folder does not do this; a folder shows what is present, not what is absent.

4. Assign each item to the person who has it

For a company, the registration certificate, the director's ID and the bank letter are held by three different people. Sending one list to one contact turns that contact into a coordinator. Send each person their own part, and let the person who started the process see how far the others have got.

5. Review per file, and say why

"Please update your documents" is a second round of guessing. "The bank statement covers one month; we need three" is a fix. Reject the one item, write the one sentence, and leave everything you have already accepted alone — both so the client only has to do the small thing, and so they cannot quietly change what you approved.

6. Chase automatically, within limits

The follow-up email is the most expensive part of the process because a person writes it, and it is written most in the week before a deadline. Automate it, but with rules: only while the client actually has something outstanding, only during working hours, and with a cap so a client who has gone quiet stops receiving mail rather than filtering you.

7. Keep the files out of the inbox

Identity documents belong in storage that is not publicly addressable, where every download is checked against who is asking. A link that anyone can open is not access control; it is a delay before the leak. The same goes for your own team: the record of who accepted a document, and when, should be part of the file rather than something reconstructed from sent items.

8. End somewhere useful

The point of collecting the documents is what happens next. A finished case should be exportable as one summary with its files attached, or pushed straight into the system where the work actually happens, so nobody re-downloads eight attachments into a folder named "final".

Doing this with Intaky

Intaky is built around exactly this list. You define named items in a form builder, send one link, and the client sees a checklist with their progress. Companies are modelled as an entity plus people, each invited separately. Reviewers accept or reject per item with a note, accepted items lock, and reminders go out on a schedule you set — working hours only, capped at six. Files live in private object storage, every decision carries a name and a time, and a finished case exports as a PDF or fires a webhook.

Contact us

Next: the client intake process checklist, or see how it works for accountants, law firms and recruiters.