A litigation representation qualified by an item on a different schedule entirely

The situation

A structural-engineering consultancy based in British Columbia, with a concentrated client base of municipal and institutional customers, was sold on a share basis for $4,600,000. The purchase agreement followed the usual architecture: broad representations in the body of the agreement, qualified by specific disclosure schedules attached at signing.

Where this agreement departed from the norm was in how the schedules were drafted to interact with one another. Rather than requiring each disclosed item to be cross-referenced to the specific representation it qualified, the schedules carried a general clause: “Any matter disclosed on any Schedule shall be deemed disclosed against, and shall qualify, each representation and warranty to which its relevance is reasonably apparent on its face, notwithstanding that such matter is set out in response to a different representation or Schedule.” The seller's counsel had proposed it; the buyer's counsel, seeing it as a fairly standard boilerplate efficiency, did not push back.

The problem

The material-contracts schedule listed, among the firm's significant engagements, a termination notice the firm had received two months before signing from its second-largest institutional client, ending a multi-year framework agreement effective six months after closing. The litigation schedule, filed separately and reviewed on its own by the buyer's diligence team, disclosed nothing — there was no pending or threatened litigation at the time of signing.

After closing, the terminated client relationship deteriorated further into a formal fee dispute, which the client pursued through a demand letter and, eventually, a small civil claim over disputed invoices from the engagement's final year. The buyer framed its indemnity claim as a breach of the general representation that there was no material undisclosed litigation risk affecting the business, arguing that nothing on the litigation schedule had put it on notice of a dispute with this specific client.

The rule that decided it

No statute governs how a Canadian purchase agreement's disclosure schedules interact with each other or with the representations they qualify; that architecture is a pure drafting choice, and the two competing choices produce opposite outcomes on the same underlying facts. Treadstone Law's own description of how disclosure schedules are conventionally built confirms which choice is the market default, and which one this agreement rejected: a disclosure schedule is where the seller “carves out the real-world exceptions to those broad statements, item by item, usually cross-referenced by section number to the specific representation it qualifies.” The same point is made from the buyer's side: “Each schedule usually corresponds to a specific representation and warranty in the body of the agreement.”

This agreement did the opposite on purpose. A general cross-application clause is the less common, and more seller-favourable, drafting choice precisely because it removes the buyer's ability to treat each schedule as self-contained — a fact disclosed anywhere in the document can qualify a representation anywhere else, provided the connection meets an objective standard: whether the relevance was “reasonably apparent on its face.” That phrase has no fixed legal content outside the agreement; it asks how a careful reader, cross-checking the schedules against the representations, would have read the disclosed fact — not whether the seller filed it under the label the buyer expected.

Applied here, a termination notice from the firm's second-largest client, named specifically enough to identify the relationship, sitting on the material-contracts schedule of a professional-services business whose value depends overwhelmingly on client concentration, made the risk to that specific relationship reasonably apparent to any buyer's counsel reading the schedules as a set rather than in isolation. The litigation schedule's silence did not control; the general clause meant it never had to.

The outcome

The buyer's indemnity claim failed. The arbitrator appointed under the agreement's dispute-resolution clause held that the termination notice, though filed under material contracts rather than litigation, satisfied the “reasonably apparent on its face” standard given the client's size and the firm's revenue concentration — a buyer that had cross-checked customer concentration data against the material-contracts schedule, which the buyer's own diligence memo showed it had reviewed, could not credibly say the risk to that relationship was hidden. The buyer bore the loss on the fee dispute itself.

What it would have cost otherwise

Had the schedules instead been drafted with the market-standard, section-specific cross-referencing Treadstone Law describes — each disclosure tied only to the representation it names — the litigation schedule's silence on this client would have controlled the litigation representation entirely, and the termination notice buried in a different schedule would have done nothing to qualify it. The buyer's claim would likely have succeeded on the facts alone; it failed because of the architecture the buyer's own counsel had agreed to without pushing back.

The tell

The tell was in the schedules' own drafting, readable before signing: a single sentence stating that disclosure on any schedule qualifies every representation to which it is “reasonably apparent,” rather than requiring each item to be cross-referenced to the specific representation it affects. Reading every schedule against every representation, not just the schedule that appears to match, is the only way to know what a general cross-application clause has actually put the buyer on notice of.

Takeaways

• • The market default is section-specific disclosure: each schedule item cross-referenced to the representation it qualifies, so a clean litigation schedule genuinely means no disclosed litigation risk.
• • A general cross-application clause is the opposite drafting choice. It lets a fact disclosed anywhere qualify a representation anywhere else, provided the connection is “reasonably apparent” — an objective standard with no fixed legal content outside the agreement.
• • Before accepting a general cross-application clause as boilerplate, read every schedule against every representation the deal actually cares about — not just the schedule that appears, by its label, to match.
• • No statute decides which drafting choice governs. The only law that reaches a disclosure schedule's effect is the ordinary law of contract interpretation, applied to whichever architecture the parties actually signed.

Sources

• • No statute governs how disclosure schedules interact with the representations they qualify, or with each other. It is a pure drafting choice, decided by the words of the agreement the parties signed.
• • Treadstone Law — disclosure schedules in an Ontario business sale agreement — source of the quoted description of the section-specific, market-standard cross-referencing convention this agreement departed from.
• • Treadstone Law — what’s actually in the schedules to a purchase agreement — source of the quoted confirmation that each schedule usually corresponds to one specific representation. Neither source addresses a general cross-application clause of the kind this file turns on.