Fair disclosure is a contractual standard, not a data-room event
Information can be available in a data room without being fairly disclosed for the purpose of a warranty claim. This note sets out how the disclosure standard, the disclosure letter and the transaction record should work together.
The contract defines fair disclosure
Dutch law does not prescribe a fair-disclosure standard for a share purchase agreement. The parties create it in the warranty limitations, disclosure letter and definitions. That is why a statement that all documents in a virtual data room are deemed disclosed often produces less certainty than it appears to offer.
The background law remains relevant. The rules on conformity and on mistake, with the balance between the seller's duty to provide information and the buyer's duty to investigate, still play a role. Neither doctrine supplies a universal rule that an uploaded document defeats a warranty claim. The contractual allocation of risk normally carries the analysis.
A general disclosure model treats the entire indexed data room as disclosed. A specific disclosure model limits qualification of a warranty to matters identified in the disclosure letter against that warranty. A hybrid model is common: the data room is generally disclosed, but only information fairly disclosed with sufficient detail to allow a reasonable buyer to assess the nature and scope of the matter qualifies the warranties.
Availability is not enough
The phrase "fairly disclosed with sufficient detail to enable a reasonable buyer to assess" has practical content. The relevant issue should be identifiable, intelligible and connected to the warranty it qualifies. A buried reference, an incomplete document or a label that does not reveal the material point creates room for dispute.
In warranty disputes, the knowledge of a professional buyer and whether information was fairly disclosed are recurring themes. The outcome still turns on the negotiated text and the record of what was provided.
A disclosure letter is the bridge between the warranty schedule and the underlying documents. Its front section normally contains general matters, such as corporate records and statutory filings. Its specific section should identify each exception by warranty number, explain the fact and cross-refer to the supporting document, preferably by stable document identifier rather than folder description alone.
A record that can be proved
A data room needs an index that records document name, identifier, upload date, version and location. Folder hygiene matters because the index is often the only reliable reconstruction of the disclosure exercise years later. The Q&A log should be preserved in the same record, as a question and response may disclose a point more clearly than the underlying document.
The statutory duty on parties to present relevant facts fully and truthfully in litigation does not cure an uncertain data-room history. Evidentiary burden makes the process record central. Access logs can show that a buyer's team opened a document, while the index and disclosure letter show the seller's position on what the document disclosed.
At signing, the parties can freeze the data room by exporting the index and documents, generating a hash for the export, and retaining provider certification and access logs. Notarial certification is another route where the transaction warrants the additional formality. The practical objective is a record that can be produced without relying on memory or a live platform years after completion.
Signing and completion require separate disclosure decisions
A warranty is often given at signing and repeated at completion. The SPA should say whether new matters may be disclosed between those dates, whether the buyer may terminate, whether a price adjustment applies, and whether the seller has liability for the new matter. A bring-down mechanism that merely says warranties are repeated can leave those consequences unresolved.
A short bring-down certificate can identify the date, confirm the repeated warranties, list each newly disclosed matter, attach the supplement to the disclosure letter and state the agreed consequence. The buyer's response should be recorded before completion. This structure can reduce the risk of a completion disclosure becoming an unpriced waiver by conduct.
Sandbagging also belongs in the negotiated framework. An anti-sandbagging clause prevents a claim for matters actually known by the buyer or fairly disclosed under the agreed standard. A pro-sandbagging clause preserves a claim notwithstanding buyer knowledge, subject to expressly agreed disclosure exceptions. Dutch law does not impose either result as a universal statutory rule.
Claims mechanics and drafting discipline
The claims provisions should use the same disclosure vocabulary as the warranties. A claim notice can require the buyer to identify the warranty, the disclosed information said to qualify it and the reason the buyer says the matter was not fairly disclosed. That structure focuses the dispute on the agreed standard rather than on a general argument about document availability.
The transaction record should also identify the persons authorised to supplement the disclosure letter and the cut-off time for uploads. A document added after the agreed freeze should not acquire an uncertain status merely because it became available on the platform. The SPA can provide a concise process for agreed supplements and preserve the buyer's response rights.
Knowledge qualifications need defined people and dates
A knowledge qualifier should identify the individuals whose actual knowledge counts, whether constructive knowledge is included and the date at which knowledge is tested. A general reference to the seller's knowledge can invite an unnecessary dispute about the relevant organisation and internal reporting. The disclosure regime should also state whether knowledge within the buyer's advisor team is relevant.
These qualifications perform a different function from disclosure. A knowledge-qualified warranty narrows the promise made by the seller, whereas a disclosure exception qualifies an otherwise unqualified promise by reference to information supplied during the process. The agreement should not use the two devices interchangeably.
Points that decide the outcome
- Fair disclosure is defined by the SPA and is not a statutory safe harbour.
- A disclosure letter is strongest when each exception is linked to a warranty and a stable document identifier.
- General data-room disclosure and specific warranty disclosure allocate risk differently.
- The data-room index, Q&A log, export hash and access logs form the evidentiary record.
- A bring-down certificate should state the consequence of every new matter disclosed before completion.
- Sandbagging treatment requires an express clause rather than an assumption about buyer knowledge.
Related advice