top of page

"It was in the data room" is not a defence

Post-closing disputes in M&A often start the same way. Something surfaces, a claim is threatened, and the seller's first response is that the buyer had all of the information. It was in the data room.

A futuristic-looking virtual data room.

That may well be true. It is also frequently beside the point.

A data room is a diligence tool. It gives the buyer access to documents and information to investigate the business. Disclosure Schedules serve a different function. They are part of the purchase agreement. They provide contractual disclosure in the form of specific, organized exceptions that qualify the seller's representations and warranties.


The two are not interchangeable, and M&A documentation does not treat them as such.

Two Tools. Two Different Functions.


The reason this matters is structural. Representations and warranties in a share or asset purchase agreement are not drafted to incorporate the data room by reference. They are written as affirmative contractual statements, subject to what has been disclosed in the schedules.


When a buyer asserts that a representation was breached, the question is not whether a document somewhere in a virtual data room might have put them on notice. The question is whether the issue was properly disclosed, meaning disclosed: (i) in a way that qualifies the relevant representation, (ii) under the right heading, and (iii) with enough specificity that a reader can understand the nature and scope of the exception.

What proper disclosure actually requires


Here's what that looks like in practice:

  1. Placement matters. Disclosure under the wrong schedule heading, or in a general "catch-all" that the agreement does not support, may not effectively qualify the representation it is meant to address.

  2. Detail matters. A reference to a contract by name is a start. A disclosure that also identifies the key term at issue (e.g., a consent requirement, a termination right, an exclusivity provision, a rebate arrangement) is what actually protects the seller and informs the buyer.

  3. Clarity matters. Schedules that contain internal notes, ambiguous commentary, or references that require cross-referencing the data room to understand create interpretive problems. The disclosure should be readable and complete on its own.

Timing is not an afterthought


There is also a timing point that practitioners often underestimate. Well-prepared schedules, delivered early enough in the process, allow both sides to address issues before they become closing problems. A consent requirement identified in the schedules with time to spare becomes a workable closing condition. The same issue flagged in a schedule delivered the night before closing becomes a crisis.


The schedules are not just a risk-allocation tool — they are a project-management tool.

When a post-closing claim does arise, the schedules tend to become the centre of gravity for how it gets resolved. Private M&A disputes turn on what was represented, what was disclosed against those representations, and what the agreement says about reliance and remedies. A clear, disciplined disclosure record gives both sides something firm to work from and gives counsel a foundation for advising.


The data room tells the buyer what the business looks like. The Disclosure Schedules record what the parties agreed the business was. Those are not the same thing, and treating them as such is one of the more consequential mistakes a seller-side team can make.



Disclaimer


This article is for general informational purposes only and does not constitute legal advice. It does not create a solicitor-client relationship and should not be relied upon as a substitute for advice tailored to your specific transaction or circumstances.


If you’re navigating the complexities of M&A, remember that the details matter. For expert guidance, feel free to contact Outsiders Law.

Comments


© 2026 by Outsiders Law

Calgary: 587-333-3352 | Toronto: 647-692-2214

  • LinkedIn
  • Facebook
  • Instagram
  • Whatsapp
  • X
bottom of page