How to ask a borrower for documents without spending your credibility

Diligence is an unusual kind of relationship. You are asking a company for its most sensitive material, at a moment when it wants something from you, and the asking is done mostly by people who will never meet.

That combination makes requests feel free. They are not. Each one is a small withdrawal, and there is a specific transaction that empties the account faster than anything else.

The expensive mistake

Asking for something they already sent.

It costs more than the ten minutes it wastes, because of what a borrower infers from it. Not "they made a mistake" — "nobody over there is reading what I send."

That inference changes their behaviour for the rest of the deal. They stop volunteering context. They answer literally rather than helpfully, because helpfulness appears to go unread. They start copying more people in, which slows everything down. And when the deal is done, it is the anecdote they tell about you.

The uncomfortable part is that it is almost never carelessness. It is structural: the person drafting the request cannot cheaply find out what has already arrived, so asking is faster than checking. Every process that makes checking expensive will produce this failure, no matter how conscientious the people in it are.

Check before you ask

The discipline is one sentence: before any request goes out, establish what you already have.

In practice that means looking in four places, in this order, because they get progressively more expensive:

1. The file. Everything already received on this deal — documents, extracted answers, previous replies, connector data.
2. Earlier deals. The same counterparty, or near enough. A question answered eighteen months ago on the last facility is answered, with a date attached so you can judge whether it is stale.
3. The public record. Filing history, directorships, charges, sanctions lists. Anything you can establish yourself without troubling them, you should.
4. Them. Only now.

Three outcomes fall out of that order.

Already answered. Do not ask. Surface it to the reviewer instead, with a citation, and let them accept or reject it.

Partially answered. Ask the narrow question. "We have the FY23 accounts — the FY24s are still outstanding" is a materially different message from "please send your statutory accounts", and it does two things at once: it gets you the missing half, and it demonstrates that you read the first half.

Genuinely not there. Ask, and say what you checked. Not at length — one line. It is the difference between a request that reads as diligent and one that reads as a form letter.

Batch by person, never by item

The second discipline is shorter and almost as valuable.

A finance director with five outstanding items should receive one message, not five. Five analysts each raising a question on Tuesday should produce one message on Wednesday.

This is not about the recipient's reading time. It is that a scatter of individual requests is itself a signal about how you are organised, and the signal is unflattering. One considered message a week reads as a firm running a process. Five messages in a day reads as five people who are not talking to each other.

Say who it is with

A small thing that buys a surprising amount of goodwill: when a borrower asks where things stand, be able to answer precisely, including the parts that are your fault.

"Two items are with you, one has been with our Legal team since Tuesday" is a better answer than "we're just working through it", and it is better specifically because of the second clause. A counterparty who can see that you are honest about your own delays will extend more patience on theirs.

What not to do

Do not automate the sending. Draft automatically if you like — the value is in the drafting and the checking, not the pressing of the button. Something goes out from your domain, in your name, to someone you want to do business with. A person should decide that it goes.

Do not confuse a chase with a deadline. A request with an implied threat in it changes the relationship permanently, and pre-close is exactly the wrong moment. The tone that works is the tone of someone keeping a shared list tidy, because that is what is actually happening.

Do not send a checklist as an attachment. A spreadsheet emailed on Monday is wrong by Wednesday, and now the borrower is working from a stale copy while you work from a fresher one. A standing page that always shows the current state is strictly better, and removes an entire category of confused reply.

The test

Before a request goes out, one question: if they have already sent this, what in our process would have caught it?

If the honest answer is "somebody would have had to remember", the process is going to spend your credibility sooner or later — and it will do it on the deal you most wanted to close.