How to build a closing deliverables checklist for Corporate Spin-Off Transactions

Build the parent company’s closing deliverables checklist by translating the separation agreement, ancillary agreements, restructuring sequence, and distribution conditions into evidence-backed tasks. Give each instrument a preparer, signatories, approval dependency, recipient, and effectiveness trigger. Track execution, delivery, and effectiveness separately, and distinguish condition satisfaction from an authorized waiver. The resulting checklist should tell parent counsel what can be released, what blocks distribution, and what requires a continuing owner after closing, with links to final documents and unresolved decisions.

When to use this workflow

Use this workflow when parent counsel starts coordinating the execution package for a corporate spin-off and the separation perimeter and proposed distribution sequence are sufficiently settled to identify instruments and conditions. It suits in-house teams and outside counsel coordinating corporate, tax, employment, financing, operational, and local-law workstreams.

The scope is closing readiness, not a complete diligence review or post-closing obligations register. Include historical issues where they require an instrument, approval, release, or express decision before distribution.

This guide uses a US transactional orientation. Applicable corporate law, securities requirements, tax treatment, creditor rights, and foreign transfer formalities require transaction-specific analysis. The filed agreements cited below illustrate negotiated arrangements, not generally applicable requirements or market standards. The checklist recommendations are coordination practices, not independent legal requirements.

What you need

Start with the current closing set:

• The separation and distribution agreement, amendments, disclosure letters, complete schedules, and condition list.
• Ancillary agreements addressing transition services, tax, employees, intellectual property, real estate, and other allocated subjects.
• The restructuring sequence, entity chart, separation perimeter, and local transfer instruments.
• Approval materials, signing-authority evidence, consents, guarantee-release requests, and distribution-agent instructions where applicable.
• A document index with stable IDs, versions, custodians, and links to final evidence.

The inventory must reflect this transaction. GE Vernova’s Form 8-K lists multiple separation-related agreements, while its exhibit notes identify omitted schedules and exhibits and redacted portions. The public package therefore does not establish documentary completeness. Request the complete closing set from responsible custodians. See Items 1.01 and 9.01 and the exhibit notes.

Use the template

The companion template is Corporate Spin-Off Transactions — Closing deliverables checklist. You can copy this table into your working document or spreadsheet. Use one row per independently verifiable deliverable or condition; link related rows through dependency references.

Use stable row IDs such as CD-014 and document citations such as SDA-01 §4.2(b). Identify the controlling version, not merely a title. For internal coordination tasks, cite the closing instruction rather than implying a contractual requirement.

“Type” distinguishes instruments, conditions, approvals, and coordination tasks. The preparer produces the item; signers are the parties or authorized persons whose signatures are required. Identify specific roles or names rather than “legal.”

The dependency field identifies predecessor rows and the event making the instrument operative. Use separate status labels: “Execution: signed; Delivery: held; Effect: pending distribution.” For a condition, mark those instrument statuses inapplicable and record “satisfied,” “unsatisfied,” “not verified,” or “waived” with supporting evidence.

The final field captures the next decision, accountable owner, and target date or milestone. Targets are management deadlines unless a contractual or legal basis is identified. For complex entries, link supporting instructions rather than compressing several independent decisions into one cell.

Step by step

1. Establish the closing perimeter and source hierarchy

Reconcile the restructuring sequence against the entities, assets, liabilities, and businesses moving to SpinCo. Identify retained parent interests and intentionally deferred transfers. Ask each specialist to identify the instrument implementing their portion of the separation.

Do not assume the separation agreement controls every subject. In the GE–GE Vernova agreement, §2.02 assigns specified tax, employee, intellectual-property, transition-services, and real-estate matters to ancillary agreements, subject to exceptions. Read the controlling ancillary document rather than merely collecting its signature page. See the separation agreement, §2.02.

Record: controlling source IDs, scope boundaries, and missing schedules. Assign a custodian to each gap affecting readiness.

2. Translate conditions into evidence requests

Create one row for each distribution condition and link the documents demonstrating satisfaction. Break an “ancillary agreements executed” condition into linked instrument rows so each required agreement remains visible.

The GE–GE Vernova agreement conditions distribution on satisfaction or parent waiver of listed conditions, including parent-board approval and execution of each Master Ancillary Agreement. Its waiver language is contractual; it does not establish that independently applicable legal requirements are waivable. See §4.02.

Ask counsel to classify proposed waivers and identify the authorized decision-maker. Distinguish missing evidence from an unsatisfied condition. Route transaction-specific securities, tax, and corporate-authority determinations to the responsible specialists rather than inferring them from the document inventory.

Record: exact condition citation, evidence required, linked deliverables, satisfaction status, and any authorized waiver with its approval record.

3. Define each instrument’s production and signing path

For every transfer agreement, ancillary agreement, certificate, or distribution instruction, identify the preparer, reviewer, signers, and recipient. Confirm legal entities against the restructuring sequence; similar names are not interchangeable.

Separate agreed text from execution-ready text. Check attached schedules, signature blocks, and the approved version. Ask the responsible specialist to confirm applicable authority and execution formalities, including any local requirements, rather than assuming one signing approach works everywhere.

Include the distribution-agent instruction as a separate coordination item if the transaction uses one. Identify who approves its final terms and authorizes release.

Record: preparer, signers, recipient, version, and authority or approval dependencies. Leave unresolved signatory questions open.

4. Map sequencing and effectiveness

Work backward from distribution through preceding restructuring steps. Identify instruments that can be signed early, documents held pending release instructions, and items dependent on another transfer or approval.

Read each instrument’s operative language before assigning an effectiveness status. Resolve uncertainty about whether execution, delivery, a specified time, or another event controls. Where filings or registrations form part of an implementing step, ask local counsel what evidence establishes completion.

Use predecessor row IDs to expose circular dependencies. A transfer intended to precede distribution should not depend on a service schedule assuming that transfer has already occurred without an agreed sequencing solution.

Record: predecessor IDs, release-instruction owner, effectiveness trigger, and evidence needed to confirm the trigger occurred.

5. Test shared contracts and retained parent exposure

Review closing-sensitive shared contracts, guarantees, and delayed transfers against the actual restructuring steps. Keep counterparty consent, internal benefit allocation, and parent release as separate evidence questions.

The GE–GE Vernova agreement provides reasonable-best-efforts mechanisms for dividing or replicating shared contracts and, if that is not achieved before distribution, reasonable permissible arrangements allocating benefits and obligations. These provisions are subject to disclosure-letter exceptions and Article III; they do not prove counterparty consent. See §2.04.

For checklist purposes, do not mark an external release complete based solely on an internal allocation or indemnity. Identify the evidence needed and escalate whether unresolved exposure affects a condition or requires an approved exception.

Record: consent or release evidence, counterparty position, proposed fallback, and decision-maker for remaining parent exposure.

6. Reconcile the package before release

Check entity names, business definitions, schedules, service commencement dates, employee allocations, and transferred assets across the package. Prioritize mismatches affecting what becomes operative at closing.

For transition services, reconcile the execution version with intended day-one service scope. The GE–GE Vernova TSA requires schedule updates for agreed scope changes and does not oblige the provider to accept a requested change. A request alone does not establish an agreed revision under that document. See TSA §9.01(f).

Check that final amendments have propagated into related instruments and instructions. Do not cure inconsistent schedules through an undocumented assumption about operational intent.

Record: reconciliation evidence, affected row IDs, and whether each mismatch requires revised text, a factual instruction, or a decision.

7. Freeze the release record and hand off exceptions

Circulate a dated checklist snapshot showing blockers, approved exceptions, and readiness evidence. Obtain affirmative confirmation from accountable workstream owners; silence should not become a completion status. Distinguish the team’s readiness recommendation from the authorized release decision.

After release, preserve the final signed set, delivery evidence, and confirmation of effectiveness triggers. Hand delayed transfers and unresolved releases to the continuing obligations register, retaining original row IDs and source links.

Record: release-decision reference, final evidence location, and named recipient of each continuing item. Close the handoff task only when accepted; do not mark the underlying obligation performed merely because distribution occurred.

Worked example

Fictional scenario: Alder Quay Holdings plans to distribute Beacon Circuit Corporation, its industrial-controls subsidiary. All parties, documents, and provisions below are fictional. Parent counsel is checking the agreed separation agreement, SDA-01, against the execution repository.

SDA-01 §5.3(b) makes execution of listed ancillary agreements a distribution condition. TSA-02 incorporates an operative Schedule C. Equipment transfer LT-07 requires approval recorded in checklist row CD-04 and release before distribution. A procurement contract remains with the parent pending counterparty action; SDA-01 §2.8 permits an interim arrangement only after specified review. The repository contains signatures and correspondence, but incomplete readiness evidence.

CD-01 requires an evidence hold, not an immediate conclusion that execution failed. Counsel must locate the actual executed schedule or determine how to resolve the package defect. The checklist cannot reconstruct missing source material.

CD-02 presents a sequencing problem: the available record does not prove approval. The team requests evidence without assuming approval was denied and prevents premature release.

CD-03 prevents supplier acknowledgment from being treated as consent or parent release. Counsel must check the proposed fallback against §2.8 and the actual distribution conditions before recommending readiness.

Common mistakes

• One row for the separation package. Separate instruments and conditions so a missing employee or tax agreement cannot disappear behind “signed.”
• Signatures used as proof of effectiveness. Record delivery and the operative trigger separately, including held documents and pre-distribution steps.
• Internal allocation treated as parent release. Request external release evidence and assign residual exposure for decision.
• Public exhibit lists copied unchanged. Build from the actual perimeter and complete documents, including local instruments and schedules.
• Deferred items deleted at distribution. Preserve unresolved status and source links through an accepted, named handoff.

Final quality check

• Every condition has an exact source citation and satisfaction evidence or an authorized, documented waiver.
• Sources are controlling versions, with necessary schedules and amendments verified.
• Preparers, signers, recipients, and authority questions are identified.
• Execution, delivery, and effectiveness statuses have separate evidentiary support.
• Dependencies match the restructuring and distribution sequence without unexplained circular steps.
• Parent guarantees, shared contracts, and delayed transfers have evidence-backed treatment.
• Open issues are resolved or assigned, with their effect on release stated.
• Final documents, release instructions, and continuing-item handoffs are preserved under stable IDs.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its contract review capabilities for parent-side review with deal-specific instructions, and tabular review to examine multiple documents. Due diligence classification can help organize the package and prioritize human review. The checklist remains your work product; lawyers verify evidence and retain waiver and release decisions. To assess support for your closing package, book a demo.

Frequently asked questions

Should every diligence issue enter the closing checklist?

No. Include issues requiring a deliverable, condition determination, release decision, or explicit closing exception. Link background analysis rather than reproducing the diligence register.

Can a parent waiver close an unsatisfied condition?

Counsel must evaluate the actual condition, contractual waiver authority, and independently applicable restrictions. Record the authorized decision and supporting evidence; another transaction’s waiver clause is not authority for yours.

How should missing schedules be handled?

Identify the affected agreement and readiness consequence. Assign a custodian, request the executed schedule, and verify its version and incorporation. Distinguish an incomplete repository from a defective execution package until evidence resolves the question.

When should a delayed transfer leave this checklist?

After its closing treatment is decided and a continuing owner accepts the handoff. Preserve the unresolved transfer status, governing source, interim arrangement, and completion evidence still required.

Sources

These primary-source examples fall within the October 13, 2026 research cutoff; they do not establish subsequent amendments or performance.

• GE Vernova Form 8-K, April 2, 2024, Items 1.01 and 9.01.
• GE–GE Vernova Separation and Distribution Agreement, April 1, 2024, §§2.02, 2.04, and 4.02.
• GE–GE Vernova Transition Services Agreement, April 1, 2024, §9.01(f).

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.