You open a file you haven’t touched in five days. You know an email went out asking for the information you need. You think most of it came back. You’re fairly sure something was still outstanding, but you can’t remember what.
So you go looking.
- Two emails from the client, one with attachments and one without.
- A reply you sent asking about a date range.
- A forwarded message from a colleague you’d half forgotten about.
- Half an hour later you know where things stand, and you still haven’t done a minute of the work you sat down to do.
Nobody counts that time. It doesn’t appear on a timesheet and it never makes it into a process review. But it happens every time you open a file, and if you have fifteen files open, it happens fifteen times.
Your client document collection process has a hidden cost
When people talk about the cost of collecting information from clients, they usually mean the chasing. The follow-up emails. The reminders that need reminders.
That’s the visible part, and it’s not the expensive part. The expensive part is reconstruction: the work of establishing, from scratch, what has arrived, what hasn’t, what was queried and what was resolved, before any real work can begin.
Chasing takes two minutes. Reconstruction can take half an hour on a file with any complexity to it, and it happens more often than we think it should.
It also happens at the worst possible moment.
You find out something is missing on the day you needed it, because that’s the day you finally looked closely enough to notice.
Why the state of the file lives in your head
With the best intentions, we create email folders to file emails by client, shared drive folder to save attachment, yet the problem lives on.
The issue is that f you ask for ten things in one email, the answers don’t come back as one email.
- They come back as several, over days, out of order, some with attachments and some without.
- One item arrives three times because the client wasn’t sure the first two went through.
- One item never arrives at all. Maybe it was too large to send. Maybe it was overlooked.
- One arrives but covers the wrong period, and you won’t discover that until you read it properly.
At no point does anything in that process record the current state.
Your inbox records events, not status.
Which means the only place the status exists is in your memory, and memory doesn’t survive a weekend, let alone annual leave.
Make the file tell you where it stands
The fix is to move the status out of your head and into your list or request itself.
A few things do that, and most of them cost nothing.
- Ask for everything in one numbered list rather than in a series of messages, and keep that list as the single reference point.
- When something arrives, mark it against the list immediately rather than filing it and moving on.
- If you query an item, record the query against that item, not in a reply buried in a thread.
There is a simple test: could a colleague open this file cold and know what’s outstanding without asking you? If not, the status is still in your head.
The same applies to decisions. “We agreed the older statements were fine” is worth nothing if it only exists in a sent-items folder.
Ask in a way that can only be answered one way
A lot of reconstruction work is caused at the point of asking.
“Please send through your recent bank statements” produces a different result every time. Three months for one client, twelve for another, a screenshot from a third.
Be specific about the period, the format, and how many. State it next to the item rather than in a paragraph at the top, because clients read requests as a list, not as prose.
If an item has caught people out before, say what good looks like.
One sentence of instruction attached to the question saves a round trip, and a round trip costs you two reconstructions, not one.
Let your client see the same list you do
Your client is doing exactly what you’re doing.
They’ve sent some things, they think they’ve sent others, and they have no clear view of what’s left.
When someone can’t tell how much is outstanding, they assume it’s a lot, and they stop.
Giving them a visible, updating list of what’s still outstanding removes that.
It also removes the most common cause of duplication: two people, often a couple or two colleagues, each assuming the other dealt with an item. If both parties are looking at the same list, that guesswork disappears.
What a better client document collection process gives you back
The point of all of this isn’t tidiness.
It’s that when you open a file, you should be able to start work in the first thirty seconds rather than the first half hour, and you should never learn on a deadline that something has been missing for a fortnight.
That’s a compounding return. It’s small on one file and substantial across everything you have open.
How Gatheroo approaches this
Gatheroo holds the status on the request rather than in an inbox.
The dashboard shows how every client is progressing, so you can see which files are complete, which are close, and which haven’t moved, without opening any of them.
Inside a request, each item is either outstanding, submitted, queried or accepted, so completeness is a state you can read rather than a conclusion you have to work out.
Clients see their own version of the same list, with instructions attached to each question, updating as they go.
Multiple people on one request share the same view, so nothing gets answered twice.
And because none of it lives in a single person’s inbox, a colleague picking up the file finds exactly what you would have found.
Frequently Asked Questions
What is a client document collection process?
It’s the sequence you follow to request, receive, check and store information and documents from a client. Most practices have one by default rather than by design, usually built around email, which is why the status of any given file is so often unclear.
Why does collecting client documents by email take so long?
Email records messages, not status. Ten requests come back as an unpredictable number of replies, out of order and sometimes duplicated, so the current position has to be reassembled manually every time the file is opened.
How do I stop finding out at the last minute that something is missing?
Track completeness continuously rather than reviewing everything at the end. Check and accept or query each item as it arrives, and keep that record against the item itself so the outstanding list is always current.
How can I make it easier for clients to give me everything first time?
Be specific at the point of asking, attach instructions to the individual item rather than the covering message, and give the client a visible list of what’s still outstanding so they can see their own progress.
What happens to an information request when a staff member is away?
If the status lives in that person’s inbox or memory, the file stalls until they return. If it lives on the request, anyone can pick it up and see the current position immediately.