How to Review a Disclosure Letter: a Clause-by-Clause Checklist

What a disclosure letter does, and why it decides the deal A disclosure letter is the document a seller delivers alongside a share or asset purchase agreement that sets out the facts which qualify, or cut down, the warranties the seller is giving. The logic is simple and important: the seller warrants that the company is in good shape, then uses the disclosure letter to say "except for these things". A matter that is properly disclosed cannot later be the basis of a warranty claim. That is why the disclosure letter, not the warranty schedule, often decides how much protection a buyer really has. Review it as the mirror image of the warranties. This article is general guidance, not legal advice. The law here varies by jurisdiction, so have a qualified professional review your specific deal before you rely on it. ## The clause-by-clause checklist ### 1. The disclosure standard

Find the clause that defines what counts as disclosed, and read it against the SPA definition. A buyer wants "fair disclosure": a matter is only disclosed if it is set out in enough detail for the buyer to understand its nature and effect. A seller wants a lower bar. Watch the exact words, because they decide every argument that follows. ### 2. General versus specific disclosures General disclosures are sweeping statements that everything in certain public registers, the data room, or searches is deemed disclosed against all warranties. Specific disclosures point at a named warranty and describe a particular exception. As a buyer, resist broad general disclosures, especially "all matters in the data room are disclosed", because that can neutralise the warranties wholesale. Push for disclosure to be specific and cross-referenced. ### 3. Deemed disclosure of public records Check which public filings are treated as disclosed (company registry, land registry, IP registries, court records). The wider this list, the more the buyer is taken to know, whether or not it actually looked. Narrow it to registers that were genuinely searched. ### 4. Data-room disclosure If the data room is disclosed, is it disclosed generally, or only where a specific document is cross-referenced to a warranty? A buyer should insist the index is attached and frozen (often on a USB or in a certified bundle) so there is no later dispute about what was in it. ### 5. The schedule of specific disclosures This is the heart of the letter. Go warranty by warranty. For each specific disclosure, ask: does it give enough detail to understand the risk, does it quantify the exposure where it can, and does it point to the document that proves it? A vague disclosure ("there may be disputes with suppliers") should be challenged or priced. ### 6. Consistency with due diligence Cross-check every red flag your due diligence found against the disclosures. A risk you discovered that is not disclosed may still support a warranty claim; a risk that is now disclosed has been shifted back to you unless you negotiate a specific indemnity for it. ### 7. The disclosure bundle Confirm the attached documents match the references, are complete, and are agreed by both sides as the definitive bundle. Missing or mislabelled documents cause the worst post-completion fights. ### 8. Timing and bring-down If warranties are repeated at completion, check whether a supplementary or bring-down disclosure letter is allowed for matters arising between signing and completion, and what rights the buyer has if a new disclosure reveals something serious (often a right to walk away or to claim). ## Red flags to stop on - A low disclosure standard, or a definition of "Disclosed" wider than the SPA expects.

• General disclosure of the entire data room against all warranties.
• Specific disclosures too vague to understand or quantify.
• A due-diligence risk that is now quietly disclosed, moving it back to the buyer with no indemnity.
• A disclosure bundle that is incomplete, unindexed or not agreed. ## How a disclosure letter differs from the warranties The warranties live in the purchase agreement and are the seller's positive statements. The disclosure letter is the seller's list of exceptions to them. Reviewing one without the other is pointless: a strong warranty undone by a broad disclosure gives the buyer nothing, and a weak warranty may not matter if nothing is disclosed against it. Always read them side by side. ## A note on jurisdiction The disclosure letter is a feature of English-style M&A practice and is used across the UK, Ireland, Singapore, Australia and, increasingly, India. Civil-law and US deals often handle the same job differently (for example, US deals rely more on disclosure schedules attached to the agreement and on concepts like sandbagging and anti-sandbagging). The effect of disclosure on a warranty claim, and whether a buyer can still claim for something it knew about, varies by jurisdiction and by the exact wording, so confirm the local position with counsel. ## Where one contract workspace helps A disclosure letter only works if every disclosure is matched to the right warranty and backed by the right document in the bundle. Done by hand across a long schedule and a large data room, that cross-referencing is where mistakes slip in and post-completion disputes begin. Drafting, reviewing, tracking and governing a disclosure letter and its bundle can live in one AI workspace tuned to how your deal team works, instead of being scattered across a data room and email. Adira is one tool designed for exactly that.