The Disclosure Schedules: The Sell-Side Workstream Advisors Hand Off Too Late
A commercial landscaping and grounds maintenance business, 31 million dollars of revenue, was nine days from signing when the seller's counsel circulated the first full draft of the disclosure schedules. Schedule 3.14, material contracts, listed 62 agreements. Not listed was a verbal arrangement with the company's second largest municipal account, worth 2.1 million dollars a year, which had been operating on an expired written contract for nineteen months while a renewal sat unsigned. Everyone in the company knew this. Nobody had thought of it as a document, because there was no document. The buyer's counsel found it in the data room in an operations memo three days later, the representation about material contracts being in full force and effect became unsupportable, and the parties spent the next eleven days negotiating a 900 thousand dollar special indemnity with a separate escrow and a three-year survival period. The contract was renewed six weeks after closing on the same terms it had always run on. The exposure was never really about the municipality. It was about the fact that the seller learned what he was representing nine days before he signed it.
Disclosure schedules are the exhibit set attached to the purchase agreement that lists the exceptions to the seller's representations and warranties. The representation says every material contract is valid and in effect, except as set forth on Schedule 3.14. Whatever is on that schedule is disclosed, and a properly disclosed item is not a breach. Whatever is not on it, the seller has affirmatively represented does not exist. That is the entire economic mechanism, and it is startlingly simple: the line between disclosed and undisclosed is the line between a fact the buyer has priced and a fact the buyer can make an indemnity claim about. Practitioners across the middle market describe the schedules as the place where the seller's most consequential drafting happens, and they also describe, consistently, the same pathology. The schedules get treated as a legal formality, assembled in the final days before signing, by the most junior people with access to the files.
Sell-side advisors tend to leave this alone on the theory that it is counsel's workstream. That is half right. Counsel drafts the schedules and should. But counsel does not know which of the company's 400 customer agreements are material, which employees have side letters, which of the founder's handshake arrangements are load bearing, or which entity actually owns the truck fleet. The operating knowledge sits with the founder and three or four people around him, and the person whose job it is to get operating knowledge out of a founder and into a document on a schedule is the advisor. When an advisor says the schedules are legal work, what usually happens is that a second-year associate emails the controller a list of 41 requests two weeks before signing and the controller answers them in the evenings between her actual job.
The timing fix is the largest single improvement available, and it costs nothing. The schedule build should start when the sell-side quality of earnings starts, not when the purchase agreement is turned. In practice that means a skeleton set of schedules, keyed to a standard representation package, exists before the process launches. It will be wrong in places and incomplete in others. That is fine, because the purpose at that stage is not accuracy, it is discovery. A skeleton schedule asks the questions that surface the expired lease, the contractor who wrote the scheduling software and never signed an assignment of inventions, the two employees classified as independent contractors, the state where the company has had sales personnel and no registration, and the loan the founder made to the company in 2019 that was never documented. Each of those items is cheap to fix in month two of a preparation year and expensive to disclose in week two of exclusivity.
That is the same argument I have made about staging diligence readiness across twelve months and in the pre-mandate checklist, and the schedules are the sharpest version of it, because they are the only diligence artifact that converts directly into legal exposure. A finding in a quality of earnings report costs the seller price. A finding that shows up late on a disclosure schedule costs the seller price, plus indemnity, plus escrow, plus time, plus the buyer's confidence that the seller knows his own business.
Once the drafting is actually underway, the first recurring error is overbreadth. A seller who is anxious about non-disclosure will disclose everything, and the schedules balloon into a reformatted data room index with 1,900 line items across nineteen schedules. This feels safe and is not. Buyers read it as an inability to distinguish what matters, which invites more diligence rather than less. Sophisticated buyers will also argue that an item buried in an undifferentiated dump was not fairly disclosed with respect to the representation it was supposed to qualify. And, importantly, an insurer will read it too. The goal is specificity, not volume: each exception described in enough detail that a reader can tell what the item is, which representation it qualifies, and what its magnitude is.
The second recurring error is misunderstanding cross-references. Sellers want a general disclosure paragraph at the front of the schedules saying that any matter disclosed in one section is deemed disclosed for every other section to which its relevance is reasonably apparent on its face. Buyers push back and try to narrow that to items expressly cross-referenced. This single sentence is worth real money, and most founders never learn it exists. If the buyer's version prevails, an item correctly listed on the litigation schedule provides no protection at all against a claim under the compliance representation unless someone remembered to also list it there. Advisors do not need to draft the clause. They need to know which version is in the draft, tell the client what it means in plain language, and make sure that if the narrow version survives, counsel has the time and budget to cross-reference exhaustively, which is slow manual work.
The third error is the most common belief I encounter and it is simply wrong: that anything already produced in diligence is disclosed. It is not. Uploading a document to the data room does not qualify a representation unless the agreement says it does, and most do not. The schedules are the final written record of what was disclosed, which is why a document the buyer has read, indexed, and asked two questions about can still support a claim if it never made it onto a schedule. Some agreements do include a deemed-disclosure provision for data room contents. If one is on the table, it is worth having, but it is not a substitute for scheduling, and buyers frequently strip it back to documents posted by a cutoff date and fairly identified.
Fourth, understand how the schedules interact with the sandbagging position, because the two terms are read together. A pro-sandbagging clause preserves the buyer's right to claim on a breach it knew about before closing. An anti-sandbagging clause bars it. Delaware's default treatment is relatively settled and other jurisdictions are less so, which is why competent counsel takes an express position rather than leaving it out. The practical point for an advisor is directional: under a pro-sandbagging or silent agreement, thorough scheduling is the seller's only real protection, because the buyer's knowledge is not a defense. Under an anti-sandbagging clause, buyer knowledge does defensive work, but relying on that instead of scheduling means betting the escrow on a litigated question about what the buyer knew.
Fifth, deal with the gap between signing and closing before anyone gets there. Where signing and closing are not simultaneous, the seller's representations are typically brought down at closing, and the agreement will say whether the seller may update the schedules for events occurring in between. The difference is not cosmetic. In some agreements an update cures the breach, in others it only gives the buyer a walk right without curing indemnity exposure, and in others no updates are permitted at all. Whatever the answer, someone has to be responsible for refreshing the schedules at closing. Stale schedules that were built for signing and never revisited are one of the most reliably recurring traps in middle market deals, and they are entirely avoidable with a calendar entry and an owner.
Sixth, if a representations and warranties policy is contemplated, the schedules stop being a legal workstream and become a financing workstream, and the timeline compresses hard. Underwriters require a substantially complete acquisition agreement and disclosure schedules to begin binding diligence, and the centerpiece of that process is an underwriting call, commonly about an hour, in which the insurer works through the representations with the buyer's deal team and counsel to identify anything the buyer already knows to be a problem and any area where diligence was thin. Matters disclosed on the schedules are generally excluded from coverage as known matters, as are risks specifically flagged on that call. So the schedules do two opposing jobs at once: everything on them is protected from indemnity claims and excluded from insurance. A thin, late schedule set produces a slower policy, a more suspicious underwriter, and broader exclusions. I have written separately about how reps and warranties insurance changes the advisor's job, and this is the part of it advisors are least prepared for, because the insurer's diligence lands on the seller's document set weeks after the seller believed diligence was finished.
The operational build itself is not complicated and it benefits enormously from having a named owner other than the founder. I ask clients to assign one internal person, usually the controller or an operations lead, with explicit authority to interrupt people, and then run the work in six streams: contracts and customer or supplier concentration; employment, including classification, side letters, severance commitments, and any unwritten bonus practice; intellectual property, with particular attention to work created by contractors and to domains, code, and marks held personally by the founder; litigation, claims, demands, and anything that has been threatened in writing; permits, licenses, insurance, and state registrations; and related-party items, which in founder-owned companies are almost always understated because the founder does not experience his own arrangements as transactions. Nearly every founder I have worked with is surprised by the related-party schedule and by the employment schedule. Those two streams produce the most items and the most late items.
The advisor's own position on this should be written down rather than assumed. Most sell-side engagement letters say nothing about schedule support, which means the founder discovers the scope boundary at the worst possible moment, exactly as he does with the post-closing adjustment. It is reasonable for a firm to scope out and say that schedule preparation belongs to counsel. It is not reasonable to be silent and let the client assume coverage. One sentence about whether the engagement includes coordinating the disclosure schedule build prevents a bad conversation in week eleven, and it belongs with the other terms a seller should ask about before signing any engagement letter. The same logic runs through the terms that decide what a founder actually keeps, which is why I put the schedules in the same category as the post-closing true-up: economically live, negotiated late, and owned by nobody by default.
It is worth being precise about what the data supports here. The Cordis Institute Preparation Gap dataset (DOI 10.2139/ssrn.6515478) covers 89 transactions and finds that 68 percent saw a post-LOI price adjustment, with a 9.8 percent median compression between the letter of intent and closing. That study measures price movement, not schedule quality, and I will not claim it isolates disclosure work as a cause. What it does establish is that the post-LOI window is where value leaks, and the schedule build is one of the few workstreams in that window that a seller can substantially complete before the window opens. The pattern I see in practice is consistent with the same discipline that produces an add-back schedule buyers actually believe and a management team that holds up under what buyers are really testing in the management presentation. A seller who can produce a clean, specific, self-aware exception list is telling a buyer something about how the company is run, and buyers price that. The reverse is also true, which is why two offers at the same number are not the same offer once you know how each buyer intends to treat late-surfacing items, a distinction worth carrying into scoring competing letters of intent.
The landscaping founder did not have a problem with a municipality. He had a problem with sequence. The item was disclosable, defensible, and ultimately harmless, and it cost him 900 thousand dollars of escrow and three weeks of goodwill because it arrived as a surprise inside exclusivity instead of as a line item in month three of a preparation year. Schedules are not a document you produce at the end of a deal. They are an inventory of everything true about a company that a buyer will eventually be entitled to know, and a founder either builds that inventory on his own schedule or has it built for him on the buyer's. Doing that work early, while it is still cheap and while the facts can still be fixed rather than merely disclosed, is a large part of what we do for founders at Cordis Group.