AI is only as good as the context around each file. See why folder-based data rooms leave it guessing, and how request-first structure gives it something to work with.
Every deal team is being told that AI will speed up due diligence. Point a model at the data room, ask it whether revenue ties to the bank statements, and get an answer in seconds. Then someone tries it on a real data room and the answer comes back vague, wrong, or confidently built on last year's P&L.
The model usually isn't the problem. Modern AI reads a 60-page lease or a year of bank statements without trouble. What it can't do is work out what each file is supposed to be. And a folder-based data room, which is what most AI data room features are bolted onto, throws that information away at the moment a document is uploaded.
Reading a document and doing diligence on it are different jobs. To answer "does 2025 revenue tie to the bank deposits?", an AI has to know several things before it reads a single number. It needs to know which file is the 2025 P&L, and that it's the version the seller stands behind rather than a draft. It needs to know which files are bank statements, which months each one covers, and which account they belong to if the business banks in more than one place. And it needs to know whether all twelve months are actually there, or whether three are still outstanding.
None of that lives inside the documents. It lives in the diligence request list: "Monthly P&L, January through December 2025", "Bank statements, all operating accounts, last 24 months". That's the context that makes a file mean something. The question is whether the system holding the files still has it.
An AI reads each file, then gets asked to reconcile revenue. On the left the files sit in folders; on the right each one arrived against the request it answers.
| File | What a folder tells the AI | What the request tells the AI |
|---|---|---|
| Financials_FINAL_v3.pdf | Looks like a P&L. Which year? Is v3 the final one? | 1.2 Monthly P&L, Jan–Dec 2025 |
| scan0042.pdf | A scanned tax form. No year in the name. | 1.1 Tax returns, last 3 years |
| Q3_bank_stmt_revised.pdf | A bank statement for part of a year. Revised from what? | 1.3 Bank statements, Jan–Dec 2025 |
| From Bob - email attachments.zip | An archive with no description. Could be anything. | 1.3 Bank statements, Jan–Dec 2025 |
| IMG_2231.jpg | A phone photo of a table of names and amounts. | 1.4 AR aging, current |
A traditional virtual data room is a file system with permissions. Somebody on the sell side builds a folder tree (01 Financials, 02 Legal, 03 HR), documents get dropped into it, and a separate spreadsheet tracks what was asked for and what has arrived. That works for people, because people carry the context in their heads and in their inbox. An AI reading the data room sees only what's on disk, and what's on disk was never designed to explain itself. Four gaps show up in almost every folder-based room:
Adding AI to a folder-based room can help with search and summaries of single documents. But cross-document work, the part of diligence that takes the hours, depends on knowing how the files relate to each other and to the questions the buyer asked. That information was never captured.
The text is the same either way. Everything around it comes from how the file was collected.
The alternative is to stop treating the request list and the data room as two things. In a request-first data room the request list is the structure. The seller doesn't file documents into folders; they answer requests. Whatever they upload is attached to the request it answers.
That single change gives every document context a folder can't. A phone photo called IMG_2231.jpg is now known to be the current AR aging, because that's the request it was uploaded against. The period it should cover is written into the request itself. It belongs to a section and a workstream. And the request carries a status (open, submitted or complete) and an owner, so the system knows not just what has arrived but what hasn't.
Once files are tagged that way, extracting their text produces something closer to a structured knowledge base than a pile of PDFs. The system knows that these twelve files are the 2025 bank statements and this one is the P&L, so it can line them up. It also knows which requests are still open, which means an AI can say "September's statement hasn't arrived" instead of silently reconciling eleven months.
This is also why request-first collection is easier for the other side of the table. A first-time seller doesn't need to learn a folder taxonomy. They see a list of plain-English requests and answer them one at a time. The same structure that helps the counterparty is the structure that makes the AI useful.
With that structure in place, the useful work isn't summarizing one document. Single-document summaries save a few minutes of reading. The hours in diligence go into checking documents against each other, the way an analyst would, and that's where knowing which file is which pays off:
The same structure makes it practical to pull data out of documents into a workbook: resumes into a key-employee table, leases into a rent schedule, twelve statements into one month-by-month deposit summary.
Monthly revenue from the 2025 P&L next to deposits from the twelve monthly bank statements.
| Month | P&L revenue | Bank deposits | Difference |
|---|---|---|---|
| Jan | $360K | $355K | −$5K |
| Feb | $372K | $372K | $0K |
| Mar | $401K | $401K | $0K |
| Apr | $418K | $418K | $0K |
| May | $430K | $430K | $0K |
| Jun | $425K | $420K | −$5K |
| Jul | $410K | $410K | $0K |
| Aug | $415K | $415K | $0K |
| Sep | $404K | $214K | −$190K |
| Oct | $398K | $398K | $0K |
| Nov | $390K | $380K | −$10K |
| Dec | $397K | $397K | $0K |
| Total | $4.82M | $4.61M | −$210K |
Notice what the reconciliation above doesn't do: it doesn't decide what the September gap means. A customer may have paid late, a deposit may have gone to a second account, or revenue may have been booked that never arrived. AI is good at finding the question and pointing to the two files that raise it. A person still has to ask the seller.
Structure fixes the context problem. It doesn't make AI output trustworthy by default, and nobody signs a purchase agreement on the strength of a chat answer. The teams that get real value from AI in due diligence treat it like a fast, tireless junior analyst: useful for finding things and assembling them, never the last word. Three habits follow from that:
Vetting Vault is built request-first, so every file is attached to the request it answers and its text is extracted and searchable. That's the structure the rest of this article argues for, and it's what the AI works from. There are two ways to put it to work:
Nearly every data room vendor now advertises AI, and the demos all look alike: a document goes in and a tidy summary comes out. The difference shows up on a real deal, with a hundred files and a request list that's two-thirds done. Whatever platform you use, these questions separate AI that can do diligence from AI that can only read:
If the answer to the first two is no, the AI is working without the context a junior analyst would get on day one. For more on how the two models differ, see What is a Data Room?
No. AI can pull figures together, reconcile them across documents and flag gaps much faster than a person can, which shortens the work. Deciding whether an adjustment is legitimate, and putting a name behind the conclusion, is still the job of the accountant or deal team.
Only as well as the text that can be read from them. Scans and phone photos have to be converted to text first, and the quality varies. That's one more reason an AI should cite the file it used: a person can open the source and check the number.
One where the diligence request list is the structure. Each document is uploaded against the request it answers, so the system knows what every file is supposed to be, which period it should cover, and which requests are still open.
Ask the vendor where documents are processed, who can see AI output, and whether AI can be turned off for a deal. An AI that works inside the deal's own permissions shows each person only what they could already open.
Sign up free and open the sample deal: a request list with real-looking documents already attached. Ask Deal AI to reconcile revenue, check what's missing, and see which file every answer comes from.
Try the Sample DealLearn the fundamentals of virtual data rooms, their purpose in M&A transactions, and how they streamline the due diligence process.
Read articleMaster the art of due diligence with proven methodologies, common pitfalls to avoid, and expert tips from seasoned professionals.
Read articleNavigate legal due diligence effectively, from contract reviews to regulatory compliance and liability assessment.
Read article