There is a version of the document problem that has nothing to do with speed.
The client responds quickly. They are helpful, they are trying, and what arrives is still not usable.
- Three months of statements when the lender wants six.
- A figure with no explanation attached.
- Forty pages of something, because they were not sure which part mattered and decided you could work it out.
None of that is a difficult client. It is a predictable outcome of how the request was made.
Wrong period, wrong version, wrong account
The most common failure is the narrowest. You asked for bank statements. They sent bank statements.
- They are the wrong three months, or:
- They are from the offset account rather than the transaction account, or;
- They are a screenshot of a balance rather than a statement.
The client did what you asked.
The problem is that what you asked contained an assumption you did not spell out, because to you it is obvious.
Six months, all accounts, PDF from the bank rather than a photo of the screen. To someone who arranges a mortgage once every seven years, none of that is obvious.
Not enough explanation
The second failure is the opposite of too much.
A client enters a number where the lender needs the number plus the reason for it. An unusual deposit, a gap in employment, a liability that has been paid out but still shows.
Left unexplained, that becomes a question from the assessor, which becomes a question from you, which becomes another day.
The information was there. The context was not, because nothing in the request told the client that context was expected.
Too much of everything
The third failure looks like generosity. Clients who are anxious about being approved often send everything they can find, on the reasonable theory that more must be safer.
What arrives is a folder you now have to read. Somebody has to work out which of the forty pages is the one the lender asked for, and that somebody is you. Worse, the client has probably sent you personal information you did not request and would rather not be holding.
Filtering that noise is real work, and it is work that appears nowhere in anyone’s estimate of how long an application takes.
The pattern underneath all three
Each of these is a gap between what you meant and what you said.
An email that reads “can you send through your bank statements and payslips” is a perfectly clear sentence that carries at least six unstated requirements. Which accounts. What period. What format. Whether a screenshot counts. Whether to explain anything unusual. Whether to include the joint account.
The client cannot see any of that. They answer the question they were asked, and it comes back wrong, and everybody experiences it as the client being difficult.
Changing the asking, not the client
The fix is not a firmer follow-up email. It is putting the requirement next to the question instead of leaving it in your head.
Ask for one thing per field. “Bank statements” becomes a request for a named account, over a stated period, in a stated format. There is nothing left to interpret.
Attach the instruction to the question. Notes, examples, even a short screen recording can sit against the specific field it relates to, so the client reads it at the moment they need it rather than scrolling back through an email.
Let the request adapt. Conditional logic means a self-employed applicant is asked for returns and financials, and a PAYG applicant never sees those questions at all. Clients stop guessing which parts apply to them, and you stop receiving answers to questions you did not ask.
Keep the clarification in context. When a client does have a question, a comment against that field keeps the answer attached to the thing it is about, rather than in a separate thread nobody can find in three weeks.
Ask only for what you need. A structured request is also a boundary. It quietly prevents the forty-page problem, because there is nowhere to put the extra forty pages.
What this changes in practice
The measure is not client satisfaction, though that improves. It is how many times a single document has to be requested.
Gatheroo is a secure client document collection portal built for professional services. Guided fields, instructions attached to the question, and conditional logic mean the request explains itself, so what comes back is usable the first time.
You can see how it works for mortgage brokers, or read what document chasing costs a brokerage if speed is the more pressing problem.
Frequently asked questions
Does asking for more detail make the request harder for clients?
The opposite, generally. Clients find a specific request easier than a vague one, because a vague request asks them to guess. Guessing is the part they find stressful.
Can I stop clients uploading things I did not ask for?
A structured request gives each document its own field, so there is no general inbox to send extra material to. Clients can still add a note if something needs explaining.
Can the same request work for PAYG and self-employed applicants?
Yes. Conditional logic changes which questions appear based on the client’s answers, so one request handles both without either applicant seeing questions that do not apply.
What if a client still sends something by email or message?
Send them the request link and ask them to upload it there. The point is that the file ends up in one place with a record attached, rather than spread across an inbox and a phone.