How to Track Disclosure Schedule Updates

How to track disclosure schedule updates is a signing-to-closing schedule ledger, not another sandbagging or knowledge-qualifier tab. For each signed deal, log whether the seller may or must update disclosure schedules between signing and closing, whether updates cover pre-signing and post-signing matters or post-signing only, what updates do to the buyer's indemnity and walk rights, an update log by date and schedule, any MAE or closing-condition interaction, and status. Raziel's sandbagging tracking page is known-breach indemnity after close. This page is whether schedules can change before close, and what that change does to walk-versus-claim elections.

This is not legal, tax, insurance, or investment advice. Raziel does not provide it. Copy the update election from the PDF. Do not invent a 2025-only percentage for allowed versus silent versus prohibited, and do not paste study snapshots onto a silent deal.

What this disclosure-schedule-update ledger is (and is not)

A disclosure-schedule update right (or duty) says the seller may, or must, refresh schedules between signing and closing for new or newly discovered matters. Goulston & Storrs, What's Market: Disclosure Schedule Updating, reports that allowing or requiring updates is permitted in only about one-quarter of reported deals (a minority). Deals that permit updates are more or less split on covering pre-signing and post-signing matters versus post-signing only. Limitations on the buyer's indemnification rights with respect to updated matters were at a 33% level in the current study, up from a low of 10% in 2021. Silent agreements typically mean the seller cannot unilaterally update. Label "current study" as Goulston's Bloomberg recap of the then-current ABA Private Target studies. The public recap does not isolate a 2025-only percentage for update permission. Do not invent one. Copy the PDF election. The ABA 2025 Study also newly tracks whether an existing fact or condition at signing can constitute an MAE (K&L Gates). That is the MAE-definition row, not this row. Pointer only. Those are study snapshots. Your update clause and closing conditions control.

This ledger is not sandbagging tracking (whether the buyer can still claim indemnity for a breach it knew about) and not knowledge-qualifier tracking (how "knowledge" is defined). Those rows matter after close or inside the reps. This row is the interim schedule path from signing to closing.

Seven columns on one disclosure-schedule-update row

Open one row per signed deal. Attach the update clause, the closing conditions, the MAE definition pointer, and each delivered update package.

• Allowed / required / prohibited / silent. Copy the election. Goulston: allowing or requiring updates is permitted in only about one-quarter of reported deals (minority). Silent typically means the seller cannot unilaterally update. Do not invent a 2025-only percentage for allowed versus silent versus prohibited.

• Pre-signing vs post-signing only. Deals that permit updates are more or less split on covering pre-signing and post-signing matters versus post-signing only (Goulston). Copy which window your paper allows.

• Effect on buyer's indemnity. Limited or not for updated matters. Goulston: limitations on the buyer's indemnification rights with respect to updated matters were at a 33% level in the current study, up from a low of 10% in 2021. Those are study snapshots. Copy your limitation sentence.

• Walk vs close-and-claim. Whether an update that would make a closing condition fail gives a walk right, a close-and-claim path, or both. Copy the closing-condition and indemnity interaction. Do not invent a default.

• Update log. Date, schedule number, matter summary, and who delivered. Keep each package as a child row if multiple updates arrive.

• MAE / closing-condition interaction. Pointer only to the MAE-definition row (including the 2025 Study's new existing-fact-at-signing data point summarized by K&L Gates). Do not rewrite the MAE definition here.

• Status. Copied, update delivered, accepted, rejected, closed, or terminated. When an update is accepted or a walk notice goes out, book the date.

Copy the clause, not the study percentage

Do not paste "about one-quarter" onto a deal that prohibits updates. Do not invent a 2025-only allowed/silent/prohibited split when Goulston's public recap does not isolate one. Do not paste the 33% indemnity-limitation print onto a paper with no limitation. Do not fold this row into sandbagging or knowledge-qualifier tracking. Sandbagging is known-breach indemnity after close. Knowledge is who knew what. Schedule updates are the interim refresh path. Keep them separate so a walk letter maps to the right cell.

When an update package arrives, log which schedules changed, whether the paper allowed that window, and whether closing conditions or indemnity rights shifted. That trail is what closing counsel will ask for before any accept, reject, or walk notice.

When the ledger holds

The row holds if the seven cells are copied from the PDFs (or marked missing). It fails when you invent an update right, ignore a silent agreement's no-unilateral-update reading, or treat the sandbagging tab as if it answered the interim schedule question. Raziel's alternative asset dashboard is where the update election, the update log, and any walk or claim election should sit together. Raziel does not decide your schedule fight. Copy the seven columns.