Why the room decides the timetable
Diligence rarely kills a transaction outright. Delay does, and disorganised data rooms are the most dependable source of delay.
Momentum is a real asset in a process. Bidders competing on a published timetable behave differently from bidders who have been waiting three days for a document. Every request that cannot be answered from what is already loaded costs time, and time gives everyone room to reconsider.
There is a second effect that sellers underrate. A buyer forms a view of how the business is run from how the room is assembled. A clean index and consistent naming suggest a management team with operational discipline. A folder called "Financials FINAL v3" suggests something else, and that impression colours how every subsequent answer is received.
Choosing a platform
The established providers are Intralinks, Datasite and Firmex, and for a transaction in this size range any of them is adequate. What matters is the feature set.
Per-document and per-folder permissions, so that sensitive material can be released to some counterparties and not others. Dynamic watermarking carrying the viewer's identity. Two-factor authentication. A full activity log showing who opened what and for how long, which is both a security control and useful intelligence about which bidders are actually working. A question and answer module, so that requests are tracked rather than arriving by email. And an interface your own team will use without complaint, because a room nobody maintains is worse than no room.
Avoid running a process from a general file-sharing service. It lacks the permissioning and the audit trail, and its use signals inexperience to every counterparty.
A structure that works
Nine top-level categories, numbered so that the order is stable.
Corporate, covering constitutional documents, share registers, board minutes and group structure. Financial, covering audited accounts, management accounts, budgets, forecasts and tax filings. Contracts, split between customer, supplier, partner and property. Intellectual property, including registrations, assignments and an open-source audit. Technology, covering architecture, security assessments and infrastructure. People, covering the employee census, compensation, benefits and any consultancy arrangements. Legal, covering litigation, regulatory filings and compliance certification. Insurance, covering policies and claims history. Operations, covering the metrics, cohort data and customer analytics.
For a carve-out, add a tenth for separation, holding the perimeter definition, the standalone cost model and the draft transition services schedule. Buyers ask for all three, and having them in one place answers a large part of the technical diligence before it starts.
Naming and indexing
One convention, applied without exception. Section number, document name, date. Nothing else.
Maintain a master index mapping every document to the diligence request item it answers. When a buyer's list arrives, most of it should be answerable by pointing at the index rather than by producing anything new. That is the measure of whether preparation was done.
Staging disclosure
Do not load everything at once, and do not open everything to everyone.
At the memorandum stage, corporate, high-level financial and market material. At the indication stage, detailed contracts, technology documentation and people data. After a letter of intent, the sensitive layer: customer-level revenue, unit pricing, strategic plans and anything a competitor would value independently of the transaction.
Where a bidder is a direct competitor, hold the third layer longer and consider releasing parts of it to their advisers only.
Running the questions
One named person coordinates every response. Multiple people answering independently produces inconsistency, and inconsistency in diligence is expensive out of proportion to its cause.
Track each question with an owner and a deadline. Answer consistently across bidders, both because inconsistency creates legal exposure and because bidders compare notes more often than sellers expect.
Where an answer is unfavourable, give it plainly. A buyer who receives a straight answer to a hard question treats the rest of the room as reliable. A buyer who receives evasion starts checking everything.
What to do before launch
Populate the room before the first non-disclosure agreement is signed, not after the first request list arrives.
Then have someone who has not built it try to use it. Give them a standard diligence request list and see how much they can answer without asking. Whatever they cannot find is what a buyer will ask for on day three, and finding it now costs a morning rather than a week of momentum.
Editorial Team · Published for orientation, not as advice on a specific transaction. Any figure cited is orientation, not a valuation. See market notes.