A recruiter, a letting agent and an immigration adviser will all describe the same frustration in nearly identical words: clients send documents one at a time, half of them are wrong, and the pack is never complete on the first pass.
It is worth resisting the obvious conclusion. The behaviour is consistent across industries, client types and price points, which is unusual for something explained by clients not paying attention. Consistent behaviour usually points at a consistent cause in the process.
Nobody has shown the client what complete looks like
Completeness exists in your head, or in a checklist on your screen. The client has a message.
From where they sit, they have been asked for some documents and they are producing them as they find them. Sending each one as it turns up feels like progress and demonstrates good faith. There is no signal telling them that the submission is judged as a complete set, because nothing they can see shows the set.
This is why drip submission is so consistent. It is the rational response to a task with no visible end state. Give the client a list where items tick off and the behaviour changes without anyone being asked to change it — the incentive to finish comes from being able to see the finish.
The words mean something different to them
“Proof of address” is the clearest example. To a bank it means a utility bill or statement from a defined list. To a letting agent it may include a tenancy agreement. To the client it means anything with their address printed on it, which is why you receive an Amazon delivery confirmation.
“Recent” is worse, because it sounds precise and is not. A client reading “a recent bank statement” will supply the most recent one they have, which may be from four months ago if they bank in an app and never download anything.
Neither of these is a comprehension failure. They are reasonable readings of an ambiguous term. The fix is unglamorous: name the acceptable documents explicitly, state the age limit as a number, and say what is not acceptable if you get the same wrong answer repeatedly.
The phone is the scanner now
Most requests are still written as though the client will produce a PDF. Most clients will photograph the document on a phone, in a hallway, at an angle, with a lamp reflecting off the laminate.
You can be annoyed about this or you can write the request for what actually happens. Saying that a photograph is fine if all four corners are visible, the whole page is captured rather than the relevant part, and there is no glare across the text, produces usable files from people who would otherwise submit something you have to reject.
The rejection itself matters here too. “This is not acceptable, please resend” produces a second photograph taken exactly the same way. “The bottom edge is cut off — please retake it with the whole page in frame” produces a usable one. A rejection without a reason is a request for a repeat of the same mistake.
The submission the client does not control
This is the category that gets misdiagnosed most often, and it is worth separating from the rest.
A meaningful share of incomplete packs are missing an item the client cannot produce alone: an employer’s reference letter, an accountant’s confirmation of income, a guarantor’s payslip, a previous landlord’s reference. The client has done everything available to them and is now waiting on a third party who has no relationship with you and no deadline.
Chasing the client harder does nothing here, and it damages the relationship because they know they are being blamed for someone else’s delay. If your incomplete submissions cluster on these items — and in referencing, lending and immigration work they usually do — the answer is to request from the third party directly, with their own named item and their own reminder schedule. Routing it through the client turns them into an unpaid intermediary. The multi-party version of this is set out in tenant document collection for property teams.
What a second cycle actually costs
It is easy to treat a resubmission as a minor delay. In practice each additional cycle costs more than the last, for reasons that are not obvious from inside the process.
The first cost is elapsed time. A rejected document does not take another hour to obtain; it takes another three days, because the client has moved on to other things and has to be pulled back. Two rejections on the same case routinely add a week to something that was scheduled for a fortnight.
The second is that the client’s estimate of the task changes. Someone who believed they were finished and then learns they were not will approach the next request with less urgency, because the evidence now suggests that submitting things does not conclude anything.
The third is internal. Every rejection creates a review event, a message and a status change, all of which have to be recorded and none of which advance the case. In a workflow measured on throughput, resubmission cycles are the largest source of work that produces no progress.
This is why the economics favour spending time on the request. A minute spent making an item unambiguous is competing against days of elapsed time on the cases where it would otherwise be misread.
Diagnosing your own pattern
The three causes need different fixes, so it is worth knowing which one you actually have. The diagnosis takes an hour with twenty recent cases.
For each rejected or missing item, ask which category it falls into. Was the request ambiguous, so the client supplied something reasonable but wrong? Was the request clear but the artefact unusable, a legibility and format problem? Or did the client never control the document in the first place?
The distribution tends to surprise people. Teams who assume they have a client-diligence problem usually find they have a wording problem on two or three specific items, repeated across every case. Fixing those items is a morning’s work and removes a recurring cost.
What a complete-first-time process looks like
Four things do most of the work. Each item is named separately, so the client can see the shape of the task. Each item states its acceptable forms and its age limit in concrete terms. Rejections carry a reason specific enough to act on. And items that depend on a third party are requested from that third party directly.
None of this requires the client to behave differently. It requires the request to carry the information the client needs in order to get it right the first time — which is the same principle behind how to collect documents from clients securely.
CVOR issues requests as named items with their own status, so the recipient can see what a finished submission looks like, and reviewers can reject a single item with a reason rather than returning the whole pack.
The observation worth keeping is that “incomplete” describes the submission, not the submitter. Most clients supply exactly what they were asked for, read the way a reasonable person would read it. If that is consistently not what you needed, the sentence is the thing to change.
For what to do with the items that remain outstanding, see how to track which documents are still outstanding.
CVOR governs document workflows for compliance-sensitive organizations.
Explore the platform →Frequently asked questions
Why do clients send documents one at a time?
Because nothing shows them what a complete submission looks like. Without a visible list, sending each document as they find it is rational behaviour — it feels like progress. A visible checklist changes the behaviour without anyone being asked to change it.
Why do clients send the wrong documents?
Usually because the term you used means something different to them. "Proof of address" means one thing to a bank and another to a letting agent, and "recent" means whatever the client decides. Naming the acceptable documents explicitly removes most of these.
How do you stop clients sending unusable scans?
Assume a phone camera, because that is what most people use. Say what makes a photograph acceptable — all four corners visible, no glare, the whole page rather than the relevant part — and reject with a specific reason so the second attempt is better than the first.
Is an incomplete submission always the client's fault?
Often it is not. A large share of incomplete submissions involve a document the client does not control, such as an employer reference, an accountant's letter or a guarantor's payslip. Reminding the client harder does not speed up the third party who actually holds it.