How to chase documents without chasing your clients

Ask any broker what actually fills their day and 'chasing documents' will come up before 'structuring deals' most of the time. Bank statements that arrive as photos of a screen. A director's guarantee sent to the wrong email thread. A set of accounts that turns out to be last year's. None of it is difficult work. All of it takes time, and none of that time is billable.

The instinct is usually to chase harder: another email, another call, a slightly firmer tone. That treats the symptom. The loop exists because the request wasn't clear enough the first time, there's nowhere obvious for the client to put things, and nobody can see at a glance what's still missing. Fix those three and the chasing mostly disappears on its own.

Why the loop happens in the first place

A typical document request goes out as a paragraph in an email, often bundled with other information about the deal. The client reads it once, sends what they can find easily, and forgets the rest. Three weeks later the broker notices the file is short a P60 and a lease, and asks again. The client, who thought they'd finished, is mildly annoyed. The broker, who has now asked twice, is more annoyed. Neither side is wrong. The process just never told either of them clearly what 'done' looked like.

• Requests sent as prose rather than an itemised list, so items get missed by accident
• No single place for documents to land, so they scatter across email, WhatsApp and the odd printed copy
• No visible checklist showing what's arrived and what's outstanding
• Version confusion when a corrected document is sent and nobody's sure which one is current
• Reminders that go out manually, so they happen late or not at all

Ask for everything, once, in writing

The single biggest improvement is also the cheapest: send one itemised request at the start of the case rather than a trickle of follow-up asks as the broker thinks of them. A client who receives a clear list of eight named documents on day one will usually return most of them within a few days, because the task feels finite. A client who receives four separate emails over three weeks assumes there's always one more coming and paces themselves accordingly.

Building that list from the product, not from memory, matters too. A bridging case and an asset finance case need different supporting documents, and a generic checklist copied across every deal either asks for things that aren't relevant or misses something a particular lender will want. Our piece on what lenders actually want in an application pack is a useful starting point for building product-specific lists rather than one catch-all template.

Give clients somewhere to put things

Email is a poor filing system. Attachments get buried under later replies, forwarded threads lose context, and nobody can tell at a glance whether a document has actually been received versus just sent. A client portal solves this by giving each client one link where they can see exactly what's requested, upload against each named item, and see it marked as received. It removes the guesswork on both sides.

This matters more than it sounds for a fairly unglamorous reason: clients are busy, and most document collection failures aren't refusal, they're friction. A portal that takes thirty seconds to use gets used. An email thread that requires finding the original request, checking what's already been sent and composing a considered reply gets left for later, and later slips.

What a portal needs to do well

• Show the full checklist for that specific deal, not a generic list
• Mark items received the moment they land, visible to the client as well as the broker
• Accept photos and scans without complaint, since that's how most clients will actually submit things
• Timestamp and version each upload so a replacement document doesn't overwrite history quietly
• Work on a phone, since a meaningful share of documents get sent from one

Automate the reminder, not the relationship

Reminders are where a lot of broker time leaks away, because they rely on someone noticing a file is stale and deciding to chase. That works fine when a broker has six live files. It works badly at sixty. An automated reminder, sent a fixed number of days after a request with no response, does the noticing for free and does it consistently.

The trick is keeping the automated part invisible to the tone of the relationship. A system-generated nudge that lists exactly what's outstanding, sent from the broker's own address or portal, reads as helpful. A vague 'just checking in' reads as nagging, whether a person or a system sent it. Specificity does the work either way.

Clients don't mind being asked for documents. They mind being asked for the same one twice, or asked vaguely for something they've already sent.

Version control matters more than people think

A document collected once is rarely the final version. Accounts get restated, a lease gets amended, a bank statement is re-sent because the first copy cut off a page. Without clear version control, brokers end up unsure which copy is current, and that uncertainty travels straight into the lender pack if nobody catches it. It's a compliance issue as much as a tidiness one: an AML or KYC file built on a superseded document is a weak file, whatever else is right about it.

• Keep every version rather than overwriting, with a clear marker for which is current
• Record who supplied the replacement and why, briefly, at the point it happens
• Flag documents nearing expiry, such as ID or bank statements that lenders treat as time-limited
• Make sure the pack that goes to the lender always pulls the current version automatically

Knowing what's outstanding without asking

The chasing loop is at its worst when the broker themselves doesn't know what's missing without opening the file and checking manually. That's a workflow problem, not a client problem. If outstanding items for every live deal are visible on one screen rather than buried inside individual folders, a broker can batch their follow-ups for ten minutes on a Tuesday rather than reacting file by file all week. This is the same logic behind moving deal tracking out of a spreadsheet and into a proper system: the value isn't the software, it's being able to see the whole book at once.

Setting expectations at onboarding

Much of this loop is easier to avoid than to fix once a case is underway. A client onboarding process that explains upfront how documents will be requested, where they should go, and roughly how quickly they're needed sets the tone before the first ask even goes out. Clients who understand the shape of what's coming tend to respond faster and complain less, because nothing feels like a surprise or an extra hoop.

It's also worth being upfront that some documents will need to be current at completion rather than at application, particularly proof of ID and bank statements. Flagging that early avoids a last-minute scramble that looks, from the client's side, like the broker forgot to ask sooner.

The bottom line

Chasing documents will never disappear entirely. Clients are busy, paperwork is dull, and something will always need a nudge. But most of the chasing that fills a broker's week is generated by the process itself rather than by difficult clients: vague requests, no clear place to send things, and no visibility over what's missing. Fix those three and the job becomes what it should be, checking a short list of genuinely outstanding items, rather than reconstructing the whole picture from scratch every time.