The Funding File The documents, and what each one is being read for.

The Funding File

DILIGENCE

How to Build a Funding Data Room That Shortens Diligence

By Baruch Mackliff · · 6 min read

How to build and name a funding data room so that diligence runs on fewer round trips and the reviewer's next answer is already sitting inside it.

The question underneath how do I build a data room is almost always a different question: why is this taking so long? You sent everything they asked for. Three weeks later you are still answering email.

The delay is rarely the underwriter being slow. It is round trips. A file moves forward when the person holding it can answer the next item on their checklist without writing to you, and it stops the moment they cannot. A data room is a container built so the answer is already inside it. That is the entire idea. Every design decision below exists to remove one round trip.

What diligence actually looks like from the other side

An analyst opens your file with a list. Some of the list is program policy, some of it is what the credit memo needs, and some of it is whatever a senior reviewer flagged at the last committee. They work down it. When an item is satisfied, they check it and continue. When it is not, they write a request, and your file goes back in the stack until you answer.

Here is the part owners never see. That stack is not first in, first out. It is sorted by what can be finished today. A file with two open items and a file with eleven open items are not competing evenly, even if the eleven are all small.

So the number that matters is not how much you sent. It is how many separate times somebody has to ask you for something.

The structure

Mirror the request list. If they sent you a checklist with eight categories, build eight top-level folders and number them in the order the checklist gives them. Not the order that makes sense to you. Somebody who reads the checklist should be able to look at your folder tree and see the same shape.

Inside each folder, one document per file, named so the name alone is enough:

Entity, document, period. That is the convention. It sorts correctly, it survives being downloaded into somebody's Downloads folder alongside four other borrowers, and it never produces the email that says which month is this?

What breaks: scan_004.pdf. Statements.pdf holding fourteen months in one file. Anything ending in final_v2_USE-THIS.

Formats, and the difference between sent and usable

A PDF that is a photograph of a document cannot be searched, and an analyst checking a 26-page statement for one debit is going to read every page by eye or ask you to resend. Export from the source system whenever the source system can export. Download statements from the bank as PDFs rather than scanning the paper copies. If you must scan, scan flat, at a readable resolution, with optical character recognition turned on.

Give financial statements in whatever format the reader will work in. A P&L delivered only as a locked PDF gets retyped into a spreadsheet, and retyping introduces errors that become your problem. Post both where you can: the PDF as the record, the spreadsheet as the working copy.

Keep individual files small enough to open on a phone, because part of the review happens on a phone.

The index file

Put one document at the root that lists what is in the room and where. Folder by folder, file by file, with the as-of date beside each one.

Then do the part almost nobody does. Add a short section at the bottom for items that are deliberately absent, with the reason. No receivable aging: all sales settle by card at the point of sale. 2024 return on extension, filed 2025-09-12, copy in folder 03. Lease not included; the shop is owned by the operating entity, deed in folder 05.

An absence with a reason is closed. An absence without one is a request.

Version control that does not create versions

Pick one rule and hold it. When a document is replaced, the old file leaves the folder and goes into an archive folder that the reader is told to ignore. There is exactly one balance sheet in folder 04 at any moment, and its filename carries the date it is as of.

The failure mode here is expensive and quiet. Two P&Ls in the same folder with different numbers, and the analyst does not know which one you meant. Now they have to ask, and worse, they have to wonder. A file that makes the reader wonder gets read more slowly from that point forward.

Refreshing on a clock

Financial documents age out. Interim statements go stale at some interval the program defines, bank statements always need the most recent closed month, and a long diligence period will roll past a month-end more than once.

So close your books on a schedule during an application, and when the month closes, drop the new statement and the new financials into the room without being asked. Then send one line saying August is posted. You have just prevented the request that was coming next week.

Take a request that runs eleven weeks from first submission to funding. That file crosses three month-ends. An owner who waits to be asked each time adds three round trips, and a round trip in a busy shop is rarely same-day. Call it four business days each, and you have handed away better than two weeks of calendar with no bad news in it anywhere.

The memos

For anything in your numbers that would make a careful reader stop, write a short note and put it in the folder beside the document it explains. Half a page. What happened, when, what the number would have been otherwise, and what it looks like now.

The revenue dip across two quarters when your largest customer changed purchasing systems. The month with four payroll runs instead of two. The owner contribution that landed in a revenue account before the bookkeeper caught it. None of these are disqualifying. All of them are questions, and a question you answer in advance costs you nothing while a question you answer in week four costs you a cycle and some confidence.

Write the memo in the same voice you would use to explain it out loud to somebody who knows accounting. No selling. Just the sequence of what happened.

What to leave out

A data room is not an archive of your business. Extra documents are not free, because every document in the room is a document somebody may read, and a document nobody asked for can raise a question nobody had.

Leave out marketing material. Leave out internal forecasts that contradict the numbers you submitted. Leave out employee records, customer contact lists, and anything carrying personal information about people who are not part of this transaction. If a document has a good reason to be there and also carries data that does not belong in a lender file, redact it before it goes in, and say in the index that it was redacted and why.

Access

One link, shared with the named contact, with permission to forward inside their institution. Not a 40-megabyte attachment. Not a link that expires in seven days when diligence runs for eight weeks. Not a fresh link every time something changes, because the reader will open the oldest one they can find in their inbox.

If the platform you use shows you access activity, look at it. A folder nobody has opened after ten days tells you something about where the file actually is.

Somebody has to decide whether a business they have never visited will pay money back over several years. Almost everything they can learn about how you operate reaches them as files. A room where every document is named and dated, where the current version is the only version in the folder, and where anything strange already has its note sitting beside it, makes a fairly strong argument before anybody reads a number in it.

Common questions

what is a data room for a business loan

It is an organized set of folders holding every document a lender has asked for, shared by link instead of by attachment. The structure mirrors the lender's own request list, each file is named with the entity, document type and period, and an index at the root says what is inside and what is deliberately missing. The goal is that the reviewer can answer their next checklist item without writing to you.

how long does lender diligence take

It depends on the program, the size of the request and how many open items your file carries at any moment. The part you control is the number of separate times somebody has to ask you for something, because a file with two open items moves faster than a file with eleven small ones. Sending complete, current, correctly named documents up front is the main lever you actually hold.

should I send loan documents by email or a shared folder

Use one shared link to a folder the reviewer can forward inside their own institution, and keep that link alive for the whole diligence period. Large email attachments get stripped, split across threads, and reopened in the wrong version. If you do email something, treat it as a copy and keep the folder as the record.

More on this