Simplify Supporting Document Submission

Four things, in order of how often they stop people: not knowing whether what they have counts, not having it in digital form, not knowing how many pages or which period you need, and losing the original request. None of these is solved by sending the request again.

The second one is the most underestimated. A client who has a paper payslip, a bank statement inside a banking app, and a passport in a drawer is dealing with three different capture problems, not one upload problem — and the slowest of the three sets the pace for the whole request.

Watch where requests stall rather than assuming. If one item consistently arrives last or arrives wrong, the instruction on that item is the defect, not the client.

Yes, and for most supporting documents a phone photo is the right answer rather than a fallback. Phone cameras out-resolve the average desktop webcam and most home scanners, and JPEG keeps a readable image at a size that uploads over a mobile connection without trouble.

The failure modes are predictable enough to prevent with one line of guidance: cut-off corners, glare from a window or overhead light, a finger over a number, and a photo taken at an angle so the text skews. Ask for the whole document flat, in daylight, with all four corners visible, and the rejection rate drops sharply.

Where a document genuinely must be an original PDF — many banks and payroll systems provide one — say so on the item itself, and say where it is downloaded from. Clients photograph screens when they do not know a PDF export exists.

One tap to open, one tap to attach, done. Every step you add between the message and the upload button loses a share of contributors, and account creation is the single most expensive step because it arrives before any value has been delivered.

A per-recipient magic link removes that step entirely: the link itself is the credential, it opens the client's own list of requests, and there is no password to reset six weeks later when you ask for one more document. Access can still expire and still be tied to one person.

Design for the phone first, since that is where the document is being photographed. If the list of requested items is readable and tappable on a small screen, it will be fine everywhere else.

Specific ones, attached to the item rather than the message. "Proof of address" produces a random assortment; "a utility or council bill in your name, dated within the last three months, showing the full address" produces the document you needed the first time.

Three elements do most of the work: what the document is, what period or version it must cover, and what must be visible on it. Add the accepted formats only if they genuinely matter, and keep the whole instruction to a sentence or two — an instruction nobody finishes is the same as no instruction.

If you collect the same set repeatedly, build it once as a reusable checklist. Our client document checklist covers the items most professional services end up asking for, and reusing a list is also what stops the incomplete file problem recurring case after case.

Reject the item, not the submission. When a document is unreadable or out of date, mark that single item as needing an update, write one sentence saying what is wrong, and leave everything else the client already sent untouched and accepted.

That sentence matters more than it looks. "Please resend" sends the client back to the beginning with no idea what changed; "the top of the page is cut off, we need the address line" is actionable in thirty seconds. Keep it concrete, and avoid repeating sensitive details in the note itself.

Give the correction its own visible state so nobody wonders whether the case is stalled or waiting. A client who can see one amber item and four green ones knows exactly what to do next — which is the same principle behind chasing only what is missing.