Back office

How do we keep track of documents customers send us by email?

By Paul Meakin7 min read

A stack of paper clipped documents on a desk beside a keyboard and glasses
Photo: Kindel Media on Pexels

Why do documents go missing in the inbox?

Because an inbox is built to hold conversations, not records. A customer sends a signed form as a reply to a thread from last spring. Their accountant sends the bank statements from a different address. Someone forwards the lot to a colleague with "can you deal with this", and now there are two copies in two inboxes and nobody is sure which one was dealt with.

Then the customer rings to ask whether you got it. Someone searches. Someone else searches too. Eventually the answer is probably yes.

Nobody here is being careless. Email has no idea what a document is for, which customer it belongs to or whether anyone has checked it. It knows who sent it and when, and that is all. So the real record of what came in, from whom and what happened next lives in people's heads, and heads go on holiday.

When "did you get my email" becomes a regular call, the inbox has become the filing system.

What does the inbox actually know about a document?

Less than people assume. It knows the sender, the date and the subject line the customer happened to type. It does not know that the attachment called scan0042.pdf is a signed contract, that it replaces the one sent last week, or that it still needs a second signature.

Some documents do not even arrive as files. Google's help page on Gmail attachments says a personal Gmail account can send up to 25 MB in attachments, with Workspace limits set by your administrator, and that if the total is greater than the limit, Gmail automatically removes the attachment and adds it as a Google Drive link in the email. So the big documents, the scanned bundles and the photographed paperwork, often turn up as a link to a file that still sits in the sender's Drive, under the sender's control. Nobody saves it, because it looks like it has arrived. If the sender later moves or deletes the file, your copy goes with it.

Why does this matter beyond the irritation?

Because a good share of what customers send carries personal data. ID, bank details, payslips, medical letters, signed agreements. UK GDPR does not care that it arrived by email.

Two pieces of ICO guidance make the cost concrete.

The first is subject access. The ICO's step by step guide to handling a request for information tells small organisations they have one calendar month to get what they need together and send it to the person. It tells you to use the search functions on your computer, including archived files, and your email folders to find the information. If a customer's documents are spread across five inboxes and a download folder, that is five searches and a folder, done under a deadline. The same guide suggests setting reminders to complete a request within 28 days, and allows an extra two calendar months only for very complex requests or where someone has made a lot of requests, and only if you tell the requester before the first month is up.

The second is security. The ICO's guide to data security explains that personal data should be accessed, altered, disclosed or deleted only by those you have authorised to do so. It also says that if personal data is accidentally lost, altered or destroyed, you should be able to recover it. A passport scan forwarded around three inboxes, one of them belonging to someone who has since left, is hard to square with either.

Both ICO pages carry a note that they are under review following the Data (Use and Access) Act, so check the current versions before you set your process.

Where do people get this wrong?

The shared inbox. Everyone can now see everything, which feels like progress. It still has no idea which documents are complete, which are missing and who is dealing with them, and it widens the number of people who can open each one.

Saving attachments to a folder by hand. This works well until the person who does it is off for a fortnight, at which point the folder stops being the truth.

Asking customers to use the right subject line. Some will. Most will reply to whatever email of yours is nearest the top of their inbox.

And forwarding rules set up in a hurry. Gmail's page on filters notes that when you create a filter to forward messages, only new messages will be affected. A rule set up today does nothing for last month's backlog, which still has to be sorted by a person.

What can you set up this week without buying anything?

More than you might expect, if you use Google Workspace. The same filters page lists what a filter can do: send email to a label, or archive, delete, star or automatically forward it. That is enough for a basic routing rule. Mail from a known supplier lands under that supplier's label. Mail with an attachment from a customer domain gets starred for whoever handles intake.

Gmail's guide to search operators adds the finding part. It describes an operator to find emails that have attachments with a certain name or file type, and you can turn any search into a filter. A search for has:attachment from a customer's domain is a quick way to see everything they have ever sent you, in one list.

Then agree one naming rule and stick to it. Customer name, document type, date received. Saved in one place per customer, not in whoever's Downloads folder was open at the time.

Approach What it fixes What it leaves broken
Labels and filters Mail arrives sorted by sender No record of what is still missing
Shared inbox Nobody is the single point of failure Everyone can open everything, and nothing has a status
Saving to a named folder One home per customer Depends on someone remembering every time
A simple upload link Documents land in the right record with a date and a status Needs building once, and an owner afterwards

What does a simple client portal need, and what can it skip?

It needs very little. One link per customer, or per request. A short list of what you are waiting for, so the customer can see what is outstanding without ringing you. Uploads that go straight into that customer's record with the date they arrived. A status your team can see at a glance: requested, received, checked. A reminder that goes out on a schedule when something is still missing, so nobody has to remember to chase. And access limited to the people who need it, with a note of who opened what.

It can skip most of what portal software sells. Customers who send you three documents a year do not want another password. They do not need a chat window, a dashboard or an app. A secure link that works from a phone, camera included, is the part that matters.

If the documents come in at the start of a relationship, there is more on that in our piece on onboarding new clients without weeks of back and forth. We build this kind of collection flow as a web application, and the reminders and filing behind it as process automation.

When is this not the answer?

When documents arrive a few times a month and one person handles them all. Labels, one filter and a naming rule will do the job. Spend the money elsewhere.

When you already pay for software with a portal that nobody uses. The fix there is getting customers and staff onto the thing you own, not building another one.

When the question is how long you must keep something. Retention for accounts, regulated files or employment records is a question for your accountant, your professional body or a data protection adviser. We build the filing. We do not set your legal obligations.

And when the problem is that a document went to the wrong person. That is no longer housekeeping. Write down what happened and take proper advice on whether it needs reporting.

Where do you start?

Pick one ordinary week. Count every document that arrived by email, note where it ended up, and note how many times someone asked whether it had come in. That count tells you whether you need a filter, a folder rule or a proper upload link.

If the count is bigger than you expected, tell us what's stuck and we'll map the quickest fix. Time to talk yet?

Common questions

Is a shared inbox enough to keep track of customer documents?

It stops one person being the bottleneck, but it gives nobody a status for each document and it lets everyone open everything. For personal documents, the ICO's security guidance expects access to be limited to those you have authorised.

Do emailed documents count if a customer makes a subject access request?

Yes. The ICO's step by step guide tells small organisations to search their email folders and archived files, and to respond within one calendar month.

Will a Gmail filter sort the documents we already have?

No. Google's filters page says that when you create a filter to forward messages, only new messages will be affected. The backlog still needs sorting once by hand.

Do customers need an account to use an upload link?

Not usually. For customers who send a few documents a year, a secure link tied to their record is usually easier than asking them to create another password.

Sources

  1. How to deal with a request for information: a step by step guide, ICO
  2. A guide to data security, ICO
  3. Send attachments with your Gmail message, Gmail Help
  4. Create rules to filter your emails, Gmail Help
  5. Refine searches in Gmail, Gmail Help

Paul Meakin, Founder

Twenty years of fixing businesses from the inside, eighteen of them in recruitment from consultant to national operations, before building the automation, web applications and compliance systems Staxxd runs today.

More about Paul

Time to talk yet?

Tell us what's stuck and we'll map the quickest fix. Fifteen minutes, no obligation.

Time to talk yet?