How to Track a Sandbagging Provision

How to track a sandbagging provision is a knowledge-and-recourse ledger from signing through indemnity claims, not a vibe that “buyers can sue anyway.” For each signed deal, log whether the agreement is pro-sandbagging, anti-sandbagging, or silent, the governing law, how knowledge is defined, how the disclosure schedules interact, how RWI changes the fight, a known-breach log at closing, and status of any claim that turns on what the buyer knew. Raziel's indemnity cap tracking page is the dollar ceiling. This page is whether a known breach still counts against that ceiling.

This is not legal, tax, or investment advice. Raziel does not provide it. Copy the sandbagging clause (or the silence) and the governing-law section. Do not invent a Delaware default onto a California deal.

What this sandbagging ledger is (and is not)

Sandbagging, in private M&A, is the buyer closing while knowing of a representation breach, then seeking indemnity after closing. A pro-sandbagging clause lets the buyer recover even with that knowledge. An anti-sandbagging clause bars recovery for breaches the buyer knew about. Silence leaves the result to applicable law. Goulston & Storrs, summarizing the ABA’s 2025 Private Target M&A Deal Points Study (139 agreements from 2024 and Q1 2025), reports that 69% of deals remained silent, 28% included pro-sandbagging language, and 4% included anti-sandbagging language. Wagner Hicks, summarizing the same study, puts silence at 68% (down from 76% in the prior study) and notes that Delaware law generally treats silence as pro-sandbagging, while California law generally treats silence as anti-sandbagging. Goulston also reports that RWI-referencing deals made up most of the silent set. Those are study snapshots. Your agreement and its chosen law control.

Seven columns on one sandbagging row

Open one row per signed deal. Attach the indemnification article, any “knowledge of the buyer” definition, the disclosure schedules, and the RWI binder if any.

• Stance copied. Pro-sandbagging, anti-sandbagging, or silent. Goulston: 69% silent, 28% pro, 4% anti in the 2025 Study. Copy the clause text (or “silent”) rather than a nickname.

• Governing law. Wagner Hicks: Delaware silence generally favors the buyer; California silence generally favors the seller. Store the stated law. Do not paste “Delaware” because the buyer is a Delaware LLC if the purchase agreement picks another state.

• Knowledge definition. Actual knowledge, constructive knowledge, named knowledge parties, and as-of date (signing versus closing). A closing-bring-down that the buyer already knew about is a different fact than a signing-date unknown. Copy the definition. Do not infer “they must have known.”

• Disclosure-schedule interaction. Whether a scheduled item is deemed disclosed for all representations, only the tagged representation, or not at all. A sandbagging fight often starts as a “was this disclosed?” fight. Keep the schedule on the same row.

• RWI overlay. Whether a policy exists, whether the insurer can assert the buyer’s knowledge as a defense, and whether seller indemnity is sole, excess, or gone. Goulston: most silent deals in the 2025 Study were RWI deals. A silent clause plus a knowledge-excluded policy is not “pro-sandbagging in practice.”

• Known-breach log at closing. Issues the buyer flagged in diligence, management Q&A, or a quality-of-earnings report, with a yes/no on whether each was scheduled. This is your contemporaneous record. It is not a finding that the legal standard was met.

• Status. No claim, claim noticed, knowledge dispute live, settled, or closed. When a claim is paid or waived, book the cash or the waiver date on the deal ledger.

Copy the clause (or the silence), not a forum’s default

Do not paste “Delaware is pro-sandbagging” onto a silent California deal. Do not treat a 4% anti-sandbagging frequency as “this never comes up.” Do not fold knowledge disputes into the indemnity-basket row. The basket is whether a claim counts toward a threshold. This row is whether knowledge blocks the claim at all.

When the ledger holds

The row holds if the seven cells are copied from the PDFs (or marked missing). It fails when you invent a stance, assume Delaware law, or skip the known-breach log. Raziel's alternative asset dashboard is where the agreement, the schedules, and later claim notices should sit together. Raziel does not decide whether a buyer “knew.” Copy the seven columns.