How to map separation agreements and dependencies for Corporate Spin-Off Transactions

Map a spin-off by connecting each material allocation, condition, and continuing obligation to its controlling agreement, implementation document, and supporting evidence. From the parent’s perspective, the question is whether the package implements the intended separation while identifying residual exposure. The resulting dependency matrix shows what must happen first, which provision controls, who must act, and what proves completion. It distinguishes missing information from unresolved legal decisions and carries delayed transfers, guarantees, and service-exit obligations beyond distribution when necessary.

When to use this workflow

Use this workflow when parent-company counsel has a proposed separation perimeter and draft agreements sufficient to test how the package fits together. Repeat the affected portions when revised schedules, restructuring steps, or service arrangements change an allocation or implementation assumption.

The scope is agreement dependency mapping, not a complete closing checklist or an opinion on the distribution. This U.S.-focused guide does not determine corporate distribution authority, securities requirements, tax-free qualification, creditor rights, or foreign transfer formalities. Assign those questions to appropriate counsel and connect their conclusions to affected rows.

The cited GE–GE Vernova documents illustrate one separation, not a mandatory agreement package or market standards. The source scope is the identified transaction documents, not subsequent amendments or performance.

What you need

Assemble the entity and asset perimeter, restructuring steps, distribution timetable, and parent’s allocation instructions. Include discontinued businesses and retained exposures, not merely assets intended to move.

Collect the separation agreement and relevant tax, employee, transition-services, intellectual-property, and real-estate agreements, with schedules, disclosure letters, amendments, and local implementation instruments. Request underlying shared contracts, parent guarantees, consent correspondence, liability inventories, and approval or release evidence relevant to identified dependencies.

Public filings may identify the package without supplying the complete record. GE Vernova’s exhibit index lists multiple separation-related agreements and identifies omitted schedules, exhibits, and redacted material (Form 8-K, Item 9.01). Obtain complete transaction documents before treating the record as sufficient. (sec.gov)

Assign each request a parent-side custodian and an allocation question. Requesting the license, amendments, and consent evidence needed to assess a transition service is more useful than requesting “all IT documents.”

Use the template

Corporate Spin-Off Transactions — Spin-off dependency matrix

Copy this table into your working document or spreadsheet. Use one row per dependency or decision, not one row per agreement.

Maintain a document index with stable IDs, parties, date, version, execution status, jurisdiction, and linked schedules. Matrix citations should identify the document ID, reviewed version, and clause, schedule item, or page.

“Control source” identifies the governing provision; “linked source” identifies an implementing or affected document. Use dependent row IDs under “trigger / predecessor” to make sequencing traceable.

Separate verified facts from missing evidence and legal conclusions. Describe exposure specifically: an unreleased guarantee, uncertain service capacity, or conflicting liability allocations. Name an accountable owner and decision date. Completion requires a reference to evidence; “done” alone is insufficient. Add supporting detail in a linked issue note rather than overloading cells.

Step by step

1. Establish the perimeter and document baseline

Reconcile the business perimeter against entity ownership, asset lists, retained businesses, and restructuring steps. Identify shared premises, licenses, employees, records, and guarantees that entity ownership alone does not explain.

Index amendments and schedules before substantive comparison, distinguishing executed documents from drafts. Do not infer an unavailable schedule’s contents from general allocation language.

Record: Create rows for material perimeter mismatches and missing documents. Identify the affected business, custodian, and question blocking analysis. Record the baseline version date so later changes can be assessed against a known package.

2. Determine which agreement controls each subject

Read priority provisions and subject-specific exceptions before comparing obligations. Section 2.02 of the GE–GE Vernova separation agreement directs specified subjects to ancillary agreements, with express exceptions (Separation and Distribution Agreement, §2.02). (sec.gov)

Build a subject-by-subject control map. For an employee-related tax liability, compare the tax and employee agreements, relevant definitions, and any separation-agreement exception. Do not assume that the document with the most specific title necessarily controls.

Record: Enter the control clause and linked provisions. For unresolved overlaps, state the competing readings, parent’s preferred outcome, and lawyer responsible for resolving the hierarchy. Distinguish a drafting conflict from a missing business allocation instruction.

3. Connect allocation to implementation and external consent

For each material allocated asset or obligation, identify the intended implementation instrument or action. Compare the complete underlying contract against the actual restructuring steps, checking assignment, change of control, shared use, consent, termination, exclusivity, and guarantees separately.

Section 2.04 of the filed separation agreement addresses shared-contract division or replication and permissible interim arrangements, subject to disclosure-letter exceptions and Article III (Separation and Distribution Agreement, §2.04). That internal mechanism is not evidence of counterparty consent. (sec.gov)

Record: Link allocation language to the implementation instrument and external evidence. Keep economic allocation, transfer effectiveness, and parent release distinct. For proposed interim performance, identify the required approvals, operating owner, and unresolved permissions instead of marking the transfer complete.

4. Map conditions and execution dependencies

Trace backward from each relevant distribution condition. Identify the required instrument, preparer, signatories, approval dependency, delivery recipient, and effectiveness trigger. Execution, delivery, and effectiveness need separate verification.

Section 4.02 of the filed separation agreement includes board approval and ancillary-agreement execution among conditions subject to satisfaction or parent waiver (Separation and Distribution Agreement, §4.02). Do not treat that contractual waiver mechanism as authority to dispense with independently applicable legal requirements. (sec.gov)

Record: Give each relevant condition its own row, exact clause reference, predecessor IDs, and satisfaction evidence. Identify the authorized waiver decision-maker and separately assign any question about corporate, regulatory, or local-law approval.

5. Test continuing obligations and parent exposure

Trace delayed transfers, guarantee releases, service payments, tax cooperation, indemnity administration, and information access beyond distribution. Reconcile historical-liability schedules against claims inventories and former businesses, including identified environmental exposures.

The filed agreement’s indemnities depend on defined liabilities and address specified insurance and third-party recoveries (Separation and Distribution Agreement, §§6.02–6.04). Treat those provisions as allocation terms, not proof of external release. (sec.gov)

Record: Identify each surviving trigger, operating owner, notice recipient, calculation method, and required completion evidence. Flag defense-control questions, overlapping recovery provisions, and unmapped liabilities for parent-counsel review. Do not resolve them through a broad “transferred liabilities” label.

6. Test changes across the package

When a definition, employee population, service date, or allocation schedule changes, identify every linked document now describing a different transaction. Test operational assumptions as well as drafting consistency.

Under the GE–GE Vernova TSA, scope-change requests do not compel provider agreement. Specified payments survive termination, and termination and decommissioning charges have a negotiated 180-day invoicing deadline. Schedule terms and the termination route matter (Transition Services Agreement, §§9.01(f), 9.02). (sec.gov)

Record: Link the initiating change to affected rows. Classify each consequence as confirmed, unresolved drafting, or missing business instruction. Assign reconciliation before package approval; do not assume an earlier migration automatically reduces charges.

7. Resolve, escalate, or carry forward each dependency

Review unresolved rows with parent legal, tax, treasury, HR, and operating owners as appropriate. Prioritize by impact, likelihood, decision timing, and whether the transaction can proceed without resolution.

Separate factual confirmation from legal judgment. An operating owner can confirm staffing availability; counsel assesses its significance under the service arrangement. Where a trade-off remains, record the parent’s preferred outcome, fallback, and authorized decision-maker.

Record: Close rows against identified evidence. Otherwise classify them as awaiting evidence, requiring a decision, or continuing after distribution. Preserve the rationale and next action. Risk acceptance may resolve a decision, but it does not supply missing consent or release evidence.

Worked example

The following parties, documents, clauses, and facts are entirely fictional.

Alder Harbor Holdings plans to distribute Beacon Process Systems. Its package includes separation agreement SA-01, TSA-02, employee agreement EMA-03, and software license LIC-04. TSA-02 requires Alder Harbor to provide payroll services for four months, using the licensed software and an identified administrator.

Revised EMA-03 transfers that administrator to Beacon at distribution. LIC-04 §8 requires vendor consent for Beacon’s proposed separate use. An attached guarantee supports license payments; SA-01 Schedule 5 allocates the related economic burden to Beacon and calls for the parent’s release. The review set contains neither vendor consent nor release evidence.

The map prevents approval of the TSA schedule on unsupported licensing and staffing assumptions. D01 and D02 require coordinated operational and contractual decisions; D03 requires separate release evidence or an explicit continuing-exposure decision. The gaps do not establish that consent or release is impossible. They identify what remains unverified and who must act.

Common mistakes

• One row per agreement. Split material allocations, conditions, and continuing obligations into separate dependencies.
• Assuming the separation agreement always controls. Check ancillary priority provisions, definitions, and exceptions.
• Equating indemnity with release. Record reimbursement rights separately from evidence addressing external obligations.
• Assuming service exit eliminates charges. Check schedules, termination routes, and surviving payments.
• Closing gaps through inference. Keep missing schedules and unanswered consent requests visible; record risk acceptance without relabeling it as proof.

Final quality check

• Each material allocation has a control source and implementation path.
• Citations match indexed versions, amendments, schedules, and exceptions.
• Missing or redacted material remains visible.
• Consent, execution, delivery, effectiveness, and release are distinguished.
• Changed definitions, personnel, and service dates have been tested across linked rows.
• Proposed waivers identify authority and separately assigned legal questions.
• Every open issue has an owner, next action, and decision date; closed rows retain supporting evidence.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include bulk document classification to organize the package and prioritize human review; tabular review supports work across documents. In contract review, lawyers can select the represented party, provide deal-specific instructions, and assess findings that quote and locate clauses or identify missing language. The matrix remains the team’s work product, with counsel responsible for hierarchy, effectiveness, and residual-exposure judgments. Book a demo to discuss this parent-side workflow.

Frequently asked questions

Is the matrix a closing checklist?

No. It explains relationships and evidence requirements. A closing checklist can draw deliverables from it, while services, delayed transfers, and unreleased guarantees remain tracked afterward.

How should we handle unavailable schedules?

Identify the missing schedule, custodian, and affected conclusion. Review available language, but qualify conclusions dependent on missing allocations or exceptions.

What if two agreements appear inconsistent?

Check priority language, definitions, exceptions, and versions. Present competing readings and affected documents as a discrete decision rather than silently choosing one.

When is a dependency ready to close?

When evidence supports the stated completion criterion. If management accepts residual risk, record that decision and carry forward any remaining obligation; do not describe acceptance as consent or release.

Sources

• GE Vernova Form 8-K, April 2, 2024, Items 1.01 and 9.01
• GE–GE Vernova Separation and Distribution Agreement, April 1, 2024
• GE–GE Vernova Transition Services Agreement, April 1, 2024

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.