Corporate Spin-Off Transactions

How to compare material contracts in a diligence table for Corporate Spin-Off Transactions

Compare material contracts for a corporate spin-off using a parent-side diligence table covering consent, shared use, guarantees, evidence, and decisions.

October 18, 2026  ·  10 min read
Book a Demo →

Compare material contracts against the parent company’s proposed separation steps, not simply against one another. Build a source-linked table distinguishing assignment, change of control, shared use, consent, termination, exclusivity, and continuing parent guarantees. Read each contract with its amendments and schedules, then reconcile the findings with the separation and ancillary agreements. The deliverable should identify contracts supporting the intended operating model, those requiring further evidence or counterparty action, and those leaving the parent exposed after distribution, with an accountable owner for each unresolved decision.

When to use this workflow

Use this workflow when parent-side corporate counsel, in-house teams, and diligence reviewers need to test the separation perimeter against customer, supplier, licensing, financing, and other material arrangements. Triggers include moving a contracting entity, transferring selected assets, dividing procurement, or temporarily retaining services with the parent.

This is contract comparison, not a complete closing checklist. Start while structural alternatives remain practical; refresh affected rows when the transfer sequence or operating model changes.

The guide uses a U.S. transactional orientation. Contract rights depend on the actual language, governing law, facts, and structure. The cited agreements illustrate one separation, not general law or market standards. Tax qualification, distribution authority, securities requirements, and foreign transfer formalities require separate analysis. The steps below are workflow recommendations, not prescribed legal requirements.

What you need

Obtain the entity and asset-transfer sequence, distribution structure, and allocation list showing what stays with the parent, moves to the separated company—SpinCo—or remains shared. Identify legal entities, not merely business names.

Collect:

  • Executed contracts, amendments, renewals, schedules, order forms, side letters, guarantees, and existing consents.
  • Parent-approved materiality criteria covering operational dependencies and financial exposure.
  • Business instructions identifying required users, locations, volumes, systems, and transitional services.
  • Draft separation terms, allocation schedules, transition-services provisions, and relevant ancillary agreements.
  • A document index recording stable IDs, versions, execution status, governing law, and custodians for missing records.

Do not treat a public filing as a complete diligence file. The GE Vernova Form 8-K exhibit index identifies distinct separation-related agreements and discloses omitted schedules, exhibits, and redactions. Request the complete documents needed to resolve your transaction’s questions.

Use the template

Use the Corporate Spin-Off Transactions — Material contracts comparison template below. You can copy this table into your working document or spreadsheet. Start with one row per contract; add rows for distinct transfer steps, business uses, or supporting instruments that require different decisions.

Source / step Assignment Change of control Shared use Consent Termination Exclusivity Parent guarantee Decision / owner

In Source / step, identify the document family, operative version, clause references, and restructuring step. Link the document index for metadata and completeness status.

Keep assignment and change of control separate. Identify the entities requiring continued access in Shared use. In Consent, distinguish the contractual requirement, request status, and approval evidence; also capture any notice requirement. Termination should identify relevant triggers and consequences, including commitments or charges.

In Parent guarantee, cite the supporting instrument and any release evidence. In Decision / owner, record parent exposure, preferred action, fallback, accountable owner, and decision milestone. Link a longer issue record when needed.

Use consistent labels: verified, open interpretation, and missing evidence. “Not located in supplied documents” is not equivalent to “no restriction.” Use “not applicable” only where the reviewed facts support it.

Step by step

1. Establish the contract population and operative record

Reconcile the inventory with procurement, sales, treasury, technology, and separation leads. Include shared contracts and instruments supporting another entity’s obligations, particularly parent guarantees. Ask whether an omitted low-spend contract could prevent a critical activity.

Group amendments and related instruments under a document-family ID. Distinguish executed documents from drafts and check whether renewals or order forms alter the relevant terms. Keep incomplete records in scope rather than excluding difficult reviews.

Record: the family ID, completeness status, and relevant entity or asset movement in Source / step. Assign missing-document requests in Decision / owner.

2. Translate the separation plan into contract-level facts

Describe what changes: contracting entity, ownership, performance assets, service recipients, licensed users, or payment support. Test intermediate transfers as well as distribution.

Ask business owners to confirm continued use. A parent-held contract may remain essential to SpinCo; a contract held by a departing subsidiary may still support retained operations. Resolve these dependencies before accepting a “parent” or “SpinCo” allocation label.

Record: the relevant step and intended users. Where the structure is unsettled, identify competing scenarios and assign the factual decision instead of giving unconditional clearance.

3. Test restrictions against each relevant step

Read definitions, exceptions, cross-references, and remedies alongside operative provisions. Compare assignment and change-of-control wording separately, then test shared use, consent or notice, termination, and exclusivity. Identify whether restrictions attach to an entity, affiliate group, location, product, or other defined perimeter.

Do not turn a keyword result into a conclusion. For an affiliate exception, test the definition and timing against the restructuring sequence, including the position after distribution. Distinguish uncertainty about wording from uncertainty about transaction facts.

Record: short findings and clause citations in the corresponding columns. Identify competing interpretations and assign counsel to resolve material questions.

4. Separate shared-contract allocation from counterparty permission

Identify the proposed solution: transfer, division, replication, replacement, or interim services. Test it against the underlying third-party contract rather than the internal allocation alone.

As an example, Section 2.04 of the GE–GE Vernova separation agreement provides reasonable-best-efforts mechanisms for dividing or replicating shared contracts and permissible interim arrangements, subject to disclosure-letter exceptions and Article III. Those provisions are not counterparty consent.

Record: the shared-use route, required counterparty action, evidence status, and fallback. If replication is proposed, identify who must obtain the replacement and whether retained parent operations also need coverage.

5. Reconcile findings with separation and ancillary terms

Check which transaction document controls the subject. Section 2.02 of the filed separation agreement, for example, assigns specified matters to ancillary agreements, subject to exceptions.

For a transition-services fallback, compare underlying use rights with proposed scope, duration, costs, and exit assumptions. The filed TSA’s Sections 9.01(f) and 9.02 illustrate agreed scope-change procedures and continuing payment obligations. A requested scope change does not automatically bind the provider; charge allocation depends on the applicable provisions and schedules.

Record: controlling-document references, inconsistent assumptions, and required revisions. Keep the analysis tied to the affected contract rather than expanding into general ancillary-agreement diligence.

6. Identify retained parent exposure and select an action

Compare economic allocation with the parent’s documented contractual position. Review guarantees, payment obligations, minimum commitments, termination charges, and relevant survival terms.

The separation agreement’s Sections 6.02–6.04 illustrate indemnities tied to defined liabilities and recovery adjustments. Internal indemnification does not establish an outside counterparty’s release.

Rank issues using deal-specific impact and uncertainty. Consider disruption to retained operations as well as SpinCo readiness. Select a preferred action and fallback: consent, amendment, replacement, temporary retention, or a structure decision. Temporary retention needs a defined operating arrangement, not merely an unresolved row.

Record: parent exposure, evidence, action owner, decision milestone, and approval required for the fallback. Distinguish a proposed mitigation from an approved residual exposure.

7. Verify resolutions and deliver the comparison

Have a second reviewer trace material findings to operative documents and confirm the transaction facts remain current. Ask business owners to validate operational assumptions; reserve legal interpretation for counsel.

A submitted request is not consent. Execution, delivery, and effectiveness may be separate questions. Check whether approval covers the relevant entities, steps, uses, and timing. Preserve supporting evidence and state what it resolves.

Record: the recommendation and evidence link, or an expressly assigned open issue. Deliver the table with a short summary of structure-sensitive contracts, unsupported shared arrangements, and retained parent exposure. Carry unresolved rows into the responsible follow-up record rather than marking them complete at distribution.

Worked example

Fictional scenario: Harbor Vale Holdings plans to separate its controls business into Beacon Controls through selected asset transfers and a subsidiary distribution. The initial allocation schedule labels three arrangements “Beacon.” All parties, documents, clauses, and facts below are fictional.

The software record is complete, but authorizes only parent use. The supplier file lacks a schedule defining restricted products and commitments. The lease stays with an existing subsidiary, while ownership changes; its parent guarantee is a separate instrument. These differences require distinct actions despite the common allocation label.

Source / step Assignment Change of control Shared use Consent Termination Exclusivity Parent guarantee Decision / owner
HV-01 executed software family, §§3, 12, 14; asset transfer §12 requires written transfer approval No separate provision located in complete family §3 authorizes parent only; Beacon access unsupported No approval supplied §14 permits termination for unremedied unauthorized use None located in complete family No supporting guarantee identified; treasury confirmation open IT counsel: obtain use amendment or replacement before access migration; TSA proposal does not resolve permission
HV-02 executed supply agreement, §§8, 16, 18; purchases divided §16 affiliate exception requires structure analysis No separate trigger located in supplied text Both businesses require supply No consent evidence supplied; requirement unresolved §18 refers to commitments in missing Schedule B §8 defines restricted products through missing Schedule B None identified in supplied record; completeness open Procurement counsel: obtain Schedule B and demand split before purchase allocation approval; restrictions and exit exposure remain unresolved
HV-03 executed lease §20; subsidiary distribution; G-03 §4 Tenant entity unchanged; no separate assignment identified §20 requires consent for proposed ownership change Beacon remains sole occupier Request sent; approval absent §20 permits termination following unapproved ownership change No restriction relevant to identified issue located G-03 §4 continues guarantee until written release; none supplied Real-estate counsel: obtain consent and separate release before distribution decision; treasury to assess fallback exposure

HV-01 changes the question from transfer alone to authorized access during and after separation. HV-02 cannot be cleared without the missing schedule; no conclusion about its contents is invented. HV-03 requires two independent outcomes: ownership-change consent and guarantee release. If the landlord offers consent without release, the parent must decide whether to accept continuing support, seek replacement security, or revisit the proposed structure.

Common mistakes

  • Reviewing only distribution. Test intermediate entity and asset movements separately.
  • Treating the base agreement as complete. Reconcile amendments, renewals, schedules, and supporting instruments first.
  • Equating allocation with approval. Distinguish separation terms from counterparty consent and release evidence.
  • Assuming a TSA solves access restrictions. Verify underlying third-party permissions and the proposed service’s scope and duration.
  • Closing guarantee exposure through indemnification alone. Record internal reimbursement protection separately from the parent’s continuing external obligation.

Final quality check

  • Every material contract is included or has a documented exclusion decision.
  • Each row identifies operative sources and the relevant restructuring step.
  • Material findings have verified clause citations, definitions, and exceptions.
  • Missing schedules, guarantees, and approvals remain visibly flagged.
  • Shared-use findings match confirmed operating requirements.
  • Internal allocations are distinguished from external consents and releases.
  • Each material issue has resolution evidence or an accountable owner and decision milestone.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional capabilities support tabular review across documents; due diligence capabilities include bulk document classification to organize records and prioritize human review. Use this table as your team’s work product, with parent-specific instructions. Counsel retains responsibility for source verification, interpretation, consent strategy, and residual-risk decisions. Book a demo to discuss reviewing a spin-off contract population.

Frequently asked questions

Should every contract have only one row?

No. Add rows where transfer steps, business uses, or supporting instruments require different conclusions. Retain the document-family ID and distinguish the step or instrument so related entries remain traceable.

How should we select material contracts?

Agree criteria with parent counsel and business leads. Include financial exposure, operational dependency, shared use, replacement difficulty, and continuing parent support. Document exclusions; spend alone may miss a critical license or service.

Can we clear a contract if no assignment restriction is found?

Not on that finding alone. Check completeness, change of control, authorized users, termination, exclusivity, and supporting guarantees against the structure. State the reviewed questions and remaining assumptions instead of using an unexplained “clear” label.

What if the consent strategy remains undecided?

Record the restriction, evidence, preferred approach, fallback, and authorized decision-maker. Separate interpretation uncertainty from the commercial choice to approach a counterparty. Tie the decision milestone to the first affected transfer or operational change.

Sources

Source scope as of October 13, 2026: the cited provisions concern the filed documents, not subsequent performance or amendments.

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo