How to build a closing deliverables checklist for Business Merger Transactions

Build an acquirer-side merger closing checklist by translating the executed merger agreement, applicable approval requirements, and closing-related diligence findings into evidence-backed tasks. Separate document preparation, signatures, funding, filing release, and confirmation of legal effectiveness. For each item, identify its source, owner, dependency, completion evidence, and release authority. The resulting checklist should distinguish what is prepared from what is authorized for release—and explain whether each closing condition is satisfied, remains open, or requires a documented waiver decision.

When to use this workflow

Acquirer counsel should establish the checklist before signing when execution deliverables or immediate preparations require coordination, then reconcile it to the executed agreement. In-house legal teams can use the same record to assign business decisions and funding responsibilities without taking over counsel’s substantive verification.

The scope is closing readiness, not complete diligence or integration planning. The baseline is a US acquisition involving Delaware corporate constituents, with federal HSR review where applicable. Other entity types, formation jurisdictions, regulated activities, foreign investment rules, and securities requirements need separate analysis. Distinguish signing, contractual closing, and legal effectiveness throughout; their sequence depends on the transaction documents and filing arrangements.

What you need

Start with the executed merger agreement, amendments, disclosure schedules, exhibits, and ancillary forms. Collect organizational and approval records for the buyer, merger subsidiary, and target as relevant to their respective roles.

The working set should include:

• A structure chart identifying the constituent corporations and proposed survivor.
• Resolutions, voting records, and counsel’s approval analysis.
• Regulatory counsel’s assessment and submission or waiting-period evidence.
• Diligence findings requiring consents, notices, releases, or closing cures.
• Financing documents, funds flow, payoff letters, lien-release arrangements, and payment-agent instructions.
• Capitalization and award records supporting consideration calculations.
• Filing drafts, signature arrangements, escrow instructions, and release contacts.

Assign stable document IDs and retain version and execution status. A draft and its signed counterpart represent different evidence states. Record unavailable evidence as unavailable, not as confirmation that no obligation exists.

Use the template

Use the Business Merger Transactions — Closing deliverables checklist as the central record. You can copy this table into your working document or spreadsheet. Create one row per independently verifiable deliverable or release decision.

Distinguish documents, signatures, funds, filings, and evidence in the type field. Source / standard should cite the agreement section or legal source and define completion. For a condition-linked row, identify the beneficiary and cross-reference any fuller conditions analysis.

Use Timing / dependency for the contractual deadline or triggering event and prerequisites—not simply “at closing.” Cite document IDs and clauses or pages under Evidence / gap. Distinguish draft, signed and held, verified, released, and confirmed complete. Release authority identifies the authorized decision-maker, who may differ from the preparer. In a spreadsheet, use stable row IDs for cross-references so sorting does not break dependencies.

Step by step

1. Fix the structure and milestone sequence

Confirm each constituent corporation, the survivor, acquisition vehicle, and filing route. Map signing, escrow delivery, closing authorization, funding, filing, and effectiveness separately. Validate their sequence against the agreement and release instructions rather than assuming funds always move before filing.

Identify the checklist owner and the decision-maker for unresolved conditions. Include buyer-side obligations as well as target deliverables: the acquirer needs to know whether its own performance is ready.

Record: entity-specific deliverables, stable row IDs, milestone dependencies, and responsibility for sequencing questions.

2. Extract obligations beyond the closing article

Read definitions, consideration mechanics, covenants, conditions, termination provisions, and exhibits together. Capture schedule exceptions and amendments. An officer’s certificate may appear in the conditions article while payment-agent funding sits elsewhere.

For example, §6.02(d) of the Dayforce/Dawn agreement requires a Company certificate, executed by an authorized executive officer, confirming satisfaction of specified conditions benefiting Parent and Merger Sub. It is not a certificate from the buyer or a universal statutory requirement. See the SEC-filed agreement, Exhibit 2.1, §6.02(d). (sec.gov)

Record: the exact source, required signer and recipient, satisfaction standard, and evidence needed. Link related rows instead of grouping everything under “closing documents.”

3. Separate corporate approvals from filing readiness

Under Delaware’s §251(b), each constituent corporation’s board generally approves the merger agreement and declares its advisability; §251(c) generally requires adoption by a majority of outstanding stock entitled to vote. Check statutory exceptions, charter provisions, voting classes, and structure before assigning approval tasks. The parent’s approvals should be assessed separately from those of the corporate constituents. See DGCL §251(b)–(c). (delcode.delaware.gov)

Section 251(c) permits filing a certificate of merger instead of the agreement and specifies its contents. Filing readiness does not establish satisfaction of every contractual condition. Separate approval evidence, certificate preparation, execution, release, and filing confirmation. See DGCL §251(c). (delcode.delaware.gov)

Record: the affected entity, approval basis, supporting records, filing reference, and any unresolved question assigned to counsel.

4. Turn regulatory and consent issues into evidence requirements

Ask regulatory counsel to identify the actual closing restriction and acceptable evidence. HSR applies only to certain transactions; thresholds change annually and exemptions exist. Where applicable, parties must observe the waiting restriction, including extensions following a Second Request. A filing receipt is not proof that the restriction has ended. Nor does HSR expiration establish satisfaction of every other regulatory requirement. See the FTC merger-review overview. (ftc.gov)

For commercial contracts, distinguish consent, notice, and express closing-condition status. Delaware statutory succession transfers rights and liabilities to the survivor while preserving creditor rights; that does not itself resolve contractual consent or termination triggers. Review the actual wording and applicable law. See DGCL §259(a). (delcode.delaware.gov)

Record: the source, required evidence, specialist reviewer, and whether the issue blocks closing or requires a separate risk decision.

5. Reconcile funds and execution packages

Tie the funds flow to consideration provisions, financing documents, payoff materials, and payment arrangements. Separate consideration, debt repayment, expenses, and award payments where recipients or timing differ. For lien releases, check the payoff letter’s conditions and identify evidence of the agreed release mechanism.

Reconcile capitalization and individual award records against the agreement’s treatment provisions. Assign an independent calculation check and payment-instruction verification through the team’s approved process. Keep sensitive bank details outside the broadly circulated checklist.

For documents, verify the signing entity, authority, final version, and delivery restrictions. Do not treat funding readiness as a contractual financing condition without an agreement basis, or assume an internal release hold excuses late performance.

Record: funds-flow version, reconciliation evidence, differences, signature status, and release dependencies.

6. Test conditions against evidence and waiver authority

Review each acquirer-benefit condition with its subject-matter lawyer and coordinate reciprocal deliverables with seller’s counsel. Compare evidence against the actual standard, including materiality qualifiers and the relevant measurement time. Check the substance and attachments of a bring-down certificate, not merely its title.

For an unsatisfied condition, identify the agreement’s waiver mechanism and authorized decision-maker. Do not treat a statutory or regulatory prohibition as waivable merely because it also appears in a contractual condition. Distinguish satisfaction, contractual waiver, and acceptance of commercial exposure.

Record: the reviewer’s conclusion, evidence citation, remaining qualification, or documented waiver. Preserve the written decision rather than changing only the status cell.

7. Run the release review and retain completion evidence

Review open rows with funding, filing, and document-release owners. Confirm what is signed and held, each release dependency, and who communicates authorization and completion. Check readiness against the contractual closing timetable; escalate a missed dependency rather than silently postponing performance.

After release, replace predictions with delivered documents, funding confirmations, and filing or effectiveness evidence. Where effectiveness is delayed, keep it separate from filing acceptance. Transfer genuine post-closing obligations to a linked handoff record without deleting their source.

Record: authorization, material release times, completion evidence, and an owner and next action for every remaining item.

Worked example

Fictional scenario: Alder Quay Holdings will acquire Birch Lantern Systems through Alder Quay Merger Sub, a Delaware corporation merging into Birch Lantern, the survivor. All parties, documents, amounts, and provisions below are fictional. Consideration is $72 million.

The executed agreement, MA-01, requires a target officer’s certificate under §7.2(c). Section 7.2(e) makes a specified hosting-provider consent a buyer closing condition. Section 2.1 requires designated counsel’s filing authorization under an agreed funding-and-release sequence; this sequencing instruction does not create a financing condition.

At release review, the officer’s certificate is signed but attaches language from superseded draft MA-00. The hosting provider has acknowledged the request without consenting. The merger certificate is signed and held, but funding readiness remains unconfirmed. Each gap requires a different response.

C-01 changes from “signature collected” to “delivery unverified” because the executed content is defective. C-02 lacks evidence of satisfaction; buyer counsel must separately assess whether a contractual waiver is available and what exposure would remain under the hosting contract.

C-03 remains held under the agreed instructions, but counsel must also assess the approaching contractual closing time. The missing confirmation proves neither that financing failed nor that delay is permitted. No row becomes complete merely because the closing call has started.

Common mistakes

• Copying an asset-purchase checklist. Rebuild around constituents, survivor, merger filing, consideration mechanics, and negotiated conditions; retain separate transfer documents only where required.
• Treating “signed” as “complete.” Verify final text, authority, delivery restrictions, and release evidence.
• Treating every consent as a closing condition. Separate the underlying contract obligation from the merger agreement condition and commercial decision.
• Using one funding row. Separate recipients and dependencies enough to expose unreconciled amounts, payoff conditions, or missing confirmations.
• Erasing waived requirements. Retain the original source, waiver authority, written decision, and any remaining exposure.

Final quality check

• Every deliverable has a source, affected entity, owner, and completion standard.
• Citations match the executed agreement, amendments, and applicable schedules.
• Approval and regulatory conclusions have evidence and an identified reviewer.
• Funding amounts reconcile to the approved funds flow and deal mechanics.
• Signed-and-held, released, and completed states remain distinct.
• Conditions are supported, properly documented as waived, or explicitly open.
• Release dependencies and authority match the agreement and agreed instructions.
• Remaining issues have owners and next actions; completion evidence and post-closing handoffs are retained.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its contract review capabilities to support review of merger obligations, tabular review to work across documents, and due diligence classification to organize materials for human review. In Word, counsel can select the represented party and provide deal-specific instructions; findings quote and locate clauses, rank severity, and identify missing language as not present. The checklist remains the team’s work product, and lawyers retain satisfaction, waiver, funding, and release decisions. Book a demo to discuss this workflow.

Frequently asked questions

Should preparation begin before signing?

Yes, when structure and drafts permit useful preparation. Mark draft-derived requirements provisional, then reconcile sources, signers, and deadlines to the executed agreement before relying on the checklist for release.

Is a conditions checklist enough?

No. It addresses the conditions to a party’s obligation to close. The deliverables checklist also captures execution, funding, filing instructions, and evidence retention. Link the records rather than maintaining inconsistent copies of the same requirement.

Does every diligence issue belong here?

No. Include issues producing a required consent, document, cure, funding adjustment, or closing decision. Keep other findings in diligence or integration records with a clear handoff and cross-reference where useful.

Who can mark an item complete?

The checklist owner can update status, but the designated reviewer should verify substantive completion. Regulatory evidence, funding, and filing release may require different reviewers. Checklist editing authority alone does not confer waiver or release authority.

Sources

• Delaware Code, Title 8, §251: constituent approvals and merger filing provisions.
• Delaware Code, Title 8, §259: statutory succession and creditor protections.
• FTC, Premerger Notification and the Merger Review Process: HSR overview and waiting restrictions.
• SEC-filed Dayforce/Dawn agreement, Exhibit 2.1, §6.02(d): negotiated officer-certificate example, not a market standard.

Scope: general professional workflow guidance, not advice for a particular transaction; conclusions depend on the actual documents, applicable law, and facts.

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.