Use this checklist to build the room structure
- Treat the checklist as the seller's plan, not the buyer's truth.
- Wait for the buyer's request list before assuming what they actually want next.
- Map every request-list row to a folder path so coverage is visible.
- Keep the checklist version-controlled across deals so it improves over time.
- Keep the request list inside the Q&A or process tracker, not inside the room itself.
- Use the checklist to populate the room; use the request list to drive the next priority.
- When the buyer asks for something the checklist missed, add it to the checklist template after the deal.
Data room checklist vs Buyer request list (IRL)
A row-by-row view of the decisions teams make when choosing between the two. Each row links to the relevant glossary term or guide.
Who writes it
Data room checklist. The seller or the seller's adviser, before buyers arrive.
Buyer request list (IRL). The buyer or the buyer's advisers, once engaged and under NDA.
Depends on the deal
When it is written
Data room checklist. During sell-side preparation, ahead of any buyer outreach.
Buyer request list (IRL). After the buyer reviews the teaser, signs the NDA and gains access to early materials.
Depends on the deal
Primary purpose
Data room checklist. Tell the seller what to assemble. Drives the collection plan and folder structure.
Buyer request list (IRL). Tell the seller what the buyer needs next. Drives the diligence response priority.
Depends on the deal
Organisation
Data room checklist. By workstream and document type. Categories are stable across deals.
Buyer request list (IRL). Numbered, row-by-row, often grouped by adviser team (FDD, legal, tax, HR).
Depends on the deal
Reusability across deals
Data room checklist. High. The checklist template ports to most deals of the same type with minor edits.
Buyer request list (IRL). Low. Each buyer's request list is specific to that diligence team and that deal.
Data room checklist wins
Where it lives
Data room checklist. In a template library, internal share or builder tool. Maps to the folder index.
Buyer request list (IRL). In the VDR Q&A module or an adviser tracker. Usually not inside the data room itself.
Depends on the deal
How it evolves during the deal
Data room checklist. Mostly static. Updated between deals, not during one.
Buyer request list (IRL). Updated continuously as new buyer questions arrive across diligence phases.
Depends on the deal
How they reconcile
Data room checklist. Use the checklist to assemble the room; gaps surfaced by the request list become collection priorities.
Buyer request list (IRL). Map every request-list row to a folder path; unanswered rows become the seller's next action list.
Use both
Verdict reflects the most common choice on each dimension in M&A, fundraising and sell-side workflows; the right call still depends on deal type, audience and timeline.
Why people conflate the two
Both documents are spreadsheets, both list documents and both sit alongside the data room. The difference is authorship and purpose. A data room checklist is the seller's pre-prepared master list of documents to assemble. A request list (often called an information request list or IRL) is the buyer's specific ask once they are engaged. Confusing the two leads to either over-collection (the seller assembles documents nobody asked for) or under-collection (the seller skips items the buyer cares about).
What a data room checklist contains
A checklist is structured by category and is largely deal-type generic. It comes from templates the seller, adviser or template library already has. The checklist drives what the seller assembles before any buyer arrives.
- Organised by workstream: corporate, financial, tax, legal, commercial, HR, operations.
- Reusable. The same checklist works across most deals of the same type with minor edits.
- Forward-looking. Designed to anticipate the questions a typical buyer will ask.
- Mapped to the folder structure one-to-one so every item has a home.
- Maintained by the seller or the seller's adviser, not the buyer.
- Improved between deals by adding items requested last time.
What a buyer request list contains
A request list is buyer-specific, numbered and tracked. It usually arrives after the NDA and initial process materials are signed, and is the operating document for the diligence phase. The seller's job is to respond, not to redraft.
- Numbered. Each row has a unique identifier the buyer references in Q&A.
- Specific. It names exact documents, periods, schedules and counterparties.
- Tracked. Status, owner, target folder path and response date are columns, not nice-to-haves.
- Continuous. New requests arrive as the buyer's diligence team reviews materials.
- Owned by the buyer. The seller can clarify but should not reinterpret.
- Often issued in waves: financial diligence first, then legal, tax, HR and commercial.
How they work together
In a clean process, the seller uses the checklist to assemble the room and a folder structure, then the buyer's request list is mapped row-by-row to those folders. Items the buyer requests that are missing from the checklist become collection priorities; items in the checklist the buyer never asks for stay parked in the room. After the deal, the seller updates the checklist template with anything the request list surfaced.
Where Data Room Builder fits
The checklist becomes the rows in your Excel or CSV index. Data Room Builder converts those rows into a previewable folder hierarchy and exports a ZIP skeleton, ready to upload into any VDR or cloud workspace. The request list lives inside the VDR's Q&A or in a separate adviser tracker; it does not need to be in the room itself.
Convert this guide into folders
Create the folder structure instead of building it by hand.
Paste the checklist into Excel or start from the sample file, then use Data Room Builder to generate the hierarchy and export a clean ZIP skeleton.
Matching downloadable template
Due Diligence Request List Template
A practical request-list structure for collecting documents before converting them into a buyer-facing data room. Use it as the spreadsheet starting point for the structure described in this guide.
FAQs
Is a data room checklist the same as a request list?
No. A data room checklist is the seller's pre-prepared list of documents to assemble before buyers arrive. A request list is the buyer's specific information ask issued during diligence. The checklist drives collection; the request list drives the next priority. Most deals use both.
Do I need a request list if I already have a comprehensive checklist?
Yes. The checklist anticipates what buyers usually want; the request list reflects what this specific buyer wants. Even a thorough checklist will miss buyer-specific asks like a contract amendment, a tax election or a working-capital schedule period.
Who writes the request list?
The buyer or the buyer's advisers write it. Financial due diligence teams usually issue the first wave, focused on quality of earnings and working capital. Legal, tax, commercial and HR advisers add their own waves as diligence progresses.
Should the request list be inside the data room?
Usually not. The request list is a tracking document, not a deliverable. It lives in the VDR's Q&A module, in a shared adviser tracker, or in a separate process spreadsheet. The data room holds the responses (the documents), not the questions.
How do sellers reduce request-list churn during diligence?
By preparing a comprehensive checklist first, mapping it to a clean folder structure, and answering buyer requests with file paths rather than re-uploaded duplicates. Repeated questions usually come from missing files, unclear naming or duplicate uploads — all problems the index step is designed to prevent.