How to build a closing deliverables checklist for Private Company Acquisitions

Build a buyer-side closing deliverables checklist by translating the acquisition agreement, closing conditions, ancillary documents, and relevant diligence findings into separately verifiable items. Identify each item’s source, preparer, signatories, recipient, required form, dependencies, and release authority. Track drafting, agreement, signature, delivery, and effectiveness separately. The result is a source-linked working checklist that tells buyer’s counsel what remains outstanding, what evidence supports completion, and who may authorize release—not merely which documents have been signed.

When to use this workflow

Use this workflow once the acquisition structure and closing mechanics are sufficiently settled to allocate responsibility, then update it through signing and closing. It serves buyer’s deal counsel, in-house legal teams, and professionals coordinating seller, lender, escrow agent, and third-party deliverables.

The scope is a US private-company equity purchase, asset purchase, or merger. Structure matters: an equity-transfer instrument, asset conveyance, and merger filing are not interchangeable. Entity type, governing law, regulatory exposure, and negotiated terms determine the requirements. The Delaware merger provisions discussed below do not supply universal acquisition requirements.

For simultaneous signing and closing, compress the timetable without combining the evidence checks. For deferred closing, distinguish documents that can be completed early from conditions requiring confirmation at closing.

What you need

Collect a controlled document set:

• The acquisition agreement, disclosure schedules, exhibits, amendments, and ancillary forms, each with a stable document ID and version.
• Entity and ownership records, the acquisition perimeter, and counsel’s approval analysis.
• Closing conditions, delivery obligations, estimated consideration calculations, funds-flow mechanics, and release instructions.
• Executed contracts and amendments relevant to required consents or notices.
• Financing, payoff, lien-release, escrow, insurance, tax, and transition documents required by the deal.
• Open diligence findings and the buyer’s decision whether each requires a deliverable, investigation, or risk acceptance.

Obtain the working closing date, time and time zone, intended sequence, contacts, authorized decision-makers, and recipients. Identify requirements for equity certificates, transfer instruments, or ownership-register updates from the actual structure and documents. Mark assumptions rather than presenting anticipated requests as agreed obligations.

Use the template

Copy the Private Company Acquisitions — Closing deliverables checklist into your working document or spreadsheet. Use one row per independently verifiable obligation; split packages when components have different recipients, dependencies, or completion tests.

In Source / form, record the document ID, controlling version, clause or page, and agreed-form reference. Label internal buyer requirements separately from contractual obligations.

In State / evidence, distinguish draft, agreed, signed, delivered, and effective, with dates and evidence locations. Explain inapplicable states. “Signed” must not conceal an outstanding delivery or effectiveness requirement.

Use Dependencies / timing for linked row IDs and sequence restrictions. Open point / action identifies the gap, action owner, and escalation time. Release authority identifies who may release documents or funds; it does not confer condition-waiver authority.

For conditions, link a note identifying the beneficiary, satisfaction test, waiver authority, and evidence. Keep detailed analysis outside the table but accessible from the relevant row.

Step by step

1. Fix the transaction structure and controlling documents

Identify the entities, equity interests or assets acquired, exclusions, and pre-closing restructuring. Reconcile the agreement body, schedules, exhibits, and amendments before extracting obligations. Preserve superseded versions without allowing them to drive current requirements.

Document hierarchy comes from the actual agreement. Section 13.11 of the Molina–Bright Health stock purchase agreement incorporates related materials but gives the agreement body precedence over inconsistencies, subject to specified disclosure exceptions. This is a drafting example, not a universal hierarchy.

Record: controlling source IDs and versions; assign inconsistencies for resolution before marking a form agreed.

2. Extract obligations beyond the delivery section

Read delivery provisions alongside conditions, covenants, purchase-price mechanics, and incorporated forms. Identify certificates, transfer instruments, resignations, escrow documents, releases, consents, approval evidence, and any required tax documentation. Include buyer funding and signatures, not just seller obligations.

Define observable completion evidence. Delivery of an executed escrow agreement and funding the escrow are separate events. Likewise, distinguish approval of the closing statement from authorization of the resulting payments.

Do not convert every diligence concern into a seller obligation. Classify it as contractually required, internally requested, or still negotiated.

Record: one sourced row per obligation, required form, and completion evidence; link related funding or transfer rows.

3. Separate documents from conditions and legal restrictions

Link certificates to the conditions they support without assuming certificates alone establish satisfaction. Identify beneficiaries and waiver holders. Article X of the Molina–Bright Health agreement distinguishes mutual, buyer, and seller conditions and restricts reliance on specified self-caused failures. Those allocations are agreement-specific.

Keep legal restrictions separate. For Delaware domestic-corporation mergers, DGCL § 251(b)–(c) addresses board approval and advisability, stockholder adoption, and filing, subject to statutory exceptions and alternative procedures. Counsel must identify the applicable approval route rather than importing those requirements into every equity or asset purchase.

For reportable acquisitions, the FTC’s merger-review guidance describes premerger notification and waiting-period requirements, including the effect of a second request. Have antitrust counsel determine reportability, applicable exemptions, and closing readiness; deal value alone is insufficient.

Record: distinct condition and restriction rows, supporting evidence, and responsible counsel. Never label a statutory restriction “buyer-waivable.”

4. Assign preparation, signatures, and receipt

Identify the preparer, required signatories and capacities, and recipient for each document. Distinguish the execution coordinator from the authorized signer.

Check required forms, certificate dates, attachments, and delivery methods. Where signatures are held pending closing, identify the holder and release instructions. Signed pages held by counsel are not necessarily delivered documents.

Allocate responsibility across organizational boundaries. If seller’s counsel coordinates a payoff package but the lender must confirm payment and authorize release steps, identify both owners. For buyer funding, identify treasury’s verification and payment-approval responsibilities without reproducing sensitive banking details in a broadly circulated checklist.

Record: owners, signatories, recipients, signature holder, form reference, and unresolved authority questions.

5. Build dependencies and release sequencing

Map when documents, funds, and filings may be released. For payoff materials, check the payment amount’s validity period, any contractual daily accrual, payment instructions, and the promised release steps. Receipt of a payoff letter is not evidence that those steps occurred.

For consents, examine underlying executed contracts and amendments. Separate notice, assignment, and direct or indirect control-change provisions. Section 2.4 of the Granite Southeast–Roberts Family equity purchase agreement separately requires specified contract consents in full force and an executed insurance change-of-control letter. These negotiated requirements illustrate distinct completion tests; they establish no consent requirement for another transaction.

Record: prerequisite row IDs, timing restrictions, release authority, and circular dependencies requiring an agreed sequence. Link funding to the approved funds flow and independently verified payment instructions.

6. Verify evidence instead of accepting status labels

Inspect the document behind each status. Check parties, execution capacities, dates, attachments, and deviations from the agreed form. Confirm required receipt and any express effectiveness conditions.

Treat “sent for signature,” “seller reports complete,” and “signed copy received” as different facts. Preserve uncertainty where evidence is missing. For a certificate speaking as of closing, check its stated date and coverage, any permitted advance execution arrangement, and the required closing-time confirmation. Do not assume an earlier signature necessarily invalidates an otherwise compliant certificate.

Escalate material deviations. Distinguish corrections, proposed waivers, and accepted risks rather than recording all three as “cleared.”

Record: evidence location, reviewer, remaining gap, and the decision or proof needed.

7. Prepare the release decision and limited handoff

Before the release call, extract unresolved rows into an exception list: blockers, closing-time confirmations, authorized departures, and genuinely post-closing tasks. Seek decisions from the appropriate authority; silence is not a release instruction.

Do not mark a promised later document complete. Record the authorized treatment and owner, including whether an amendment, waiver, or other documented arrangement is needed. Transfer only authorized follow-up work, preserving its source and triggering event.

After release, reconcile actual delivery, funding, and filing evidence against the checklist rather than treating authorization as proof of completion.

Record: release instructions, final states, decision evidence, and linked handoffs. Retain the version used for the closing decision.

Worked example

Fictional scenario: Harbor Vale Holdings is acquiring all shares of Cedar Quay Components for $38 million. Their fictional SPA-01 requires a customer consent effective at closing, a lender payoff package valid for the payment date, and a seller officer’s certificate dated as of closing. Signing occurred two weeks earlier; closing and funds release are planned for Friday.

Seller’s counsel reports all three items signed. Buyer’s counsel checks the documents. All parties, amounts, clauses, and document IDs below are fictional.

Three signed documents do not establish three completed obligations. The missing consent attachment prevents scope verification; counsel cannot assume it identifies the acquired company or relevant contract. The payoff letter supplies neither a valid Friday amount nor a formula permitting calculation. The certificate’s stated date—not simply when it was signed—creates the documented mismatch.

Buyer’s counsel places all three items on the exception list and requests evidence. No missing consent terms or payoff figures are invented. Any proposed departure requires separate analysis of the relevant condition, authorized decision-maker, and permissible treatment before release.

Common mistakes

• Copying a merger checklist into a stock purchase. Rebuild approvals and transfer mechanics around the actual entities and structure.
• Using “complete” as the only status. Separate agreement, signature, delivery, and effectiveness, with evidence.
• Burying buyer obligations. Give funding, payment verification, signatures, and buyer certificates owners and dependencies.
• Treating all consents alike. Examine the underlying wording and distinguish closing conditions from separate contractual exposures.
• Moving unfinished items to post-closing without authorization. Record the decision and necessary contractual treatment before handoff.

Final quality check

• Each obligation cites the controlling document and exact clause or page.
• Execution copies match agreed forms, including attachments.
• Preparers, signatories, recipients, and release authorities are identified.
• Delivery and effectiveness have evidence separate from signatures.
• Condition beneficiaries and waiver authorities match the agreement.
• Applicable legal restrictions have responsible counsel and supporting confirmation.
• Funding dependencies and closing-time tests are verified; open issues are resolved or expressly assigned for decision.
• Authorized post-closing tasks preserve their source, owner, and triggering event.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities can support review of obligations across acquisition and ancillary documents; due diligence classification can organize supporting materials and prioritize human review. The checklist remains the legal team’s work product. Counsel retains satisfaction, waiver, and release decisions. To assess support for this workflow, book a demo.

Frequently asked questions

Should signing and closing use separate checklists?

Use separate views when helpful, but preserve common IDs and expressly carry unresolved signing items forward. Avoid duplicate records with conflicting owners or statuses.

Does every diligence finding belong on the closing checklist?

No. Include findings producing a deliverable, condition, or closing decision. Keep broader investigations and accepted commercial risks in linked records.

Can a signed consent be marked complete?

Only after checking the applicable test: consenting party, covered transaction, attachments, delivery, and effectiveness. Missing pages remain an evidence gap.

Who should authorize closing with an outstanding item?

Identify the contractual beneficiary and authorized decision-maker. Distinguish condition waiver, risk acceptance, and release authority. Buyer approval does not replace responsible counsel’s determination concerning a legal restriction.

Sources

• Delaware General Corporation Law, § 251: Delaware corporate-merger approval and filing provisions.
• FTC, Premerger Notification and the Merger Review Process: notification and waiting-period framework.
• Molina–Bright Health stock purchase agreement: § 13.11 and Article X drafting examples.
• Granite Southeast–Roberts Family equity purchase agreement: § 2.4 consent and insurance-letter examples.

Scope: General professional workflow guidance, not advice for a particular transaction. Filed agreements illustrate negotiated wording, not market standards. Requirements depend on actual language, governing law, facts, and deal context.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.