Every practice has the same theory about why clients are slow to send documents. They are busy, they are disorganised, they do not read their email properly.
It is a comfortable explanation because it puts the problem on the other side of the desk. It is also mostly wrong, and it leads to the wrong fix, which is usually a firmer reminder.
The more useful explanation is that the request itself is too big to start.
Task paralysis, and why document requests trigger it
Most people know the paradox of choice, where too many options produce worse decisions rather than better ones. Task paralysis is its close relative. When someone perceives a task as large or complex enough that they cannot see where to begin, the common response is not to begin badly. It is not to begin at all.
A request for documents is almost perfectly designed to trigger it. It arrives as a list. The list is long. Several items are things the client has never had to find before, and one or two they are not certain they possess. There is no obvious first step, no sense of how long the whole thing will take, and no way to make a start without committing to the lot.
So it gets left until the weekend. Then the weekend after.
The client cannot see how close they are
The second problem compounds the first. When a request lives in an email thread, a client who has done half of it has no way of knowing that.
They cannot see six of eleven items complete. They see an inbox, a list they half remember, and a vague sense of being behind. Progress that is invisible is progress that does not motivate, so the half-finished task feels exactly as daunting as the untouched one.
This is why partial responses stall so reliably. The client has not given up. They have lost their place.
The mistake on the practice side
There is a matching problem at your end, and it is harder to see because it feels like good service.
Call it customisation bias: the belief that every client is different enough to need a different approach. Sometimes true, and flexibility genuinely matters. Applied to process, it is expensive. A bespoke set of touchpoints for every client means there is no standard to fall back on, so every follow-up is a fresh decision about what to chase and when.
That decision-making is the cognitive load nobody accounts for. It is also why reminders get missed. Not through carelessness, but because remembering to remind is a task in itself, and it competes with the “real work”.
What practices try first, and why it does not hold
Before changing the process, most people try to organise their way out of it. One broker we worked with had tried all of the following:
- A separate email folder and label for each client
- A spreadsheet tracking what had been received and what was outstanding
- Shared drive folders for clients to upload into
- A project management tool repurposed for document collection
- Driving out to meet clients and collect documents in person
Each of those is a reasonable idea. None of them addresses the thing that is happening, because all of them change how you keep track.
The client’s experience is unchanged. They still receive a long list with no starting point and no visible progress, and the person now maintaining a spreadsheet as well as an inbox is you.
The in-person visits are the most telling item on that list. Clients were choosing a two-hour round trip over sending documents by email, because at least the trip had a clear end.
What reduces the stalling
Four things, none of which involve chasing harder.
Break the request into discrete items. Eleven separate fields is a different psychological object from one email listing eleven things. Each field is small, obviously answerable, and can be done on its own. There is always a next step.
Make progress visible. A client who can see six of eleven complete will usually finish. The counter does more work than any reminder does, because it converts a vague obligation into a nearly-finished job.
Standardise, then vary at the edges. One template per situation, reused, with room to adjust individual questions. You keep the flexibility that mattered and lose the decision-making that did not.
Put the instruction next to the question. Most “wrong document” problems are unstated-requirement problems. The requirement belongs against the field it applies to, where the client reads it at the moment they need it.
How Gatheroo approaches this
Gatheroo is a secure client document collection portal built for professional services. A request is a set of guided fields rather than a list in an email, clients see exactly what is outstanding and how far through they are, automated reminders run at whatever frequency you set, and templates mean the same structure is reused rather than rebuilt.
The broker whose workarounds are listed above now runs his applications through it.
“I don’t know how we ever worked without Gatheroo, and my clients love the extra step I take to keep them safe, it’s a great way to differentiate how I work.”
John, Mortgage Broker
Frequently asked questions
Will clients use a portal instead of replying by email?
Most do, because it is less work than email. There is no account to create and nothing to install, and unlike an email thread it tells them exactly what is still outstanding.
Does breaking a request into fields make it feel longer?
It looks longer and completes faster. A visible eleven-item list with six ticked is more motivating than a short email that gives no sense of progress at all.
How often should reminders go out?
You set the frequency, daily, every second day, or weekly, depending on the deadline. The point is that it happens without anyone remembering to do it.
Can we keep different processes for different client types?
Yes, and that is the right use of flexibility. Build a template per situation and reuse it, rather than making a fresh set of decisions for every client.
* Name has been changed at the client’s request.