How to prepare a deal issues list from transaction documents for Corporate Spin-Off Transactions

Prepare a parent-side spin-off deal issues list by reviewing the separation agreement alongside its schedules, ancillary agreements, and implementation documents, then converting conflicts and gaps into decisions. Each issue should identify its source, parent exposure, preferred outcome, fallback, decision-maker, and resolution evidence. The deliverable is a prioritized decision table—not a clause summary—that explains what must change, who must decide, and which related documents must remain aligned before the parent approves the relevant transaction step.

When to use this workflow

Use this workflow when parent-company counsel has a substantive separation package and needs instructions for negotiations, an internal approval meeting, or a distribution-readiness review. It is particularly useful when specialists have reviewed individual agreements but their conclusions have not been reconciled across the package.

The scope is issue identification and disposition, not a complete diligence investigation or closing checklist. Include an implementation item when it presents an unresolved allocation, drafting, evidence, or approval decision. Otherwise, retain it in the supporting execution tracker.

This guide uses a US transactional orientation. Rights depend on actual language, governing law, facts, and separation structure. Securities requirements, tax qualification, corporate distribution authority, creditor rights, and foreign transfer formalities require transaction-specific analysis. The filed agreements cited below illustrate negotiated wording, not generally applicable law or market standards.

What you need

Start with the current separation and distribution agreement, definitions, disclosure letter, and schedules, together with relevant tax, employee, transition-services, IP, real-estate, and other ancillary agreements. Obtain local transfer instruments and underlying third-party contracts where they affect an allocation or implementation decision.

Also collect:

• The restructuring steps plan, entity chart, and proposed business perimeter, including discontinued businesses.
• Asset and liability schedules, claims inventories, shared-contract lists, and parent guarantees.
• Specialist comments, business instructions, and unresolved diligence requests.
• Proposed distribution conditions, approval materials, and delegated decision authority.
• A document index recording stable IDs, dates, versions, execution status, and missing attachments.

The GE Vernova Form 8-K, Items 1.01 and 9.01 identifies a multi-agreement separation package and discloses omitted schedules and exhibits and redacted portions. It is an inventory example, not a mandatory package or complete diligence record. Obtain missing materials before relying on provisions whose application depends on them.

Use the template

Use Corporate Spin-Off Transactions — Deal issues list as your working template. You can copy this table into your working document or spreadsheet.

Give each issue a stable ID. In Source / dependency, cite the document ID, reviewed version, clause or page, and schedule cell where available. Identify linked agreements rather than citing only the provision that revealed the issue.

In Decision / evidence, separate what the documents establish from missing facts and unresolved legal analysis. Describe parent exposure concretely: retained third-party liability, stranded service costs, loss of access, or an approval request without supporting evidence.

Explain priority rather than assigning only a color. Pair the preferred position with an authorized fallback—or state that fallback instructions are needed. Distinguish the working owner from the person authorized to approve the position. The Decision gate is the event before which instructions are necessary, not automatically a contractual deadline. Preserve resolution evidence in the final column.

Step by step

1. Fix the review baseline and identify decision-blocking gaps

Identify the versions used for review and their relationship to the steps plan. Distinguish executed agreements from drafts and incomplete schedules. If two teams are reviewing different liability definitions, reconcile the baseline before comparing conclusions.

Open an issue for missing material when its absence prevents a decision. For example, an unavailable service schedule may prevent evaluation of exit costs; “schedule outstanding” alone does not explain the required instruction. Keep routine collection requests outside the decision list unless they become consequential.

Record: reviewed versions, missing evidence, its decision consequence, the responsible custodian, and the next decision gate.

2. Map which agreement controls each disputed subject

Trace the subject through the separation agreement, ancillary agreements, schedules, and local implementation documents. Check priority provisions and exceptions before proposing amendments. Distinguish the document allocating an obligation from the instrument intended to implement the transfer.

In the filed GE–GE Vernova separation agreement, Section 2.02, specified tax, employee, IP, transition-service, and real-estate matters are assigned to ancillary agreements, subject to express exceptions. That contractual hierarchy illustrates why revising the separation agreement alone may not resolve an issue.

Record: the controlling provision, related documents requiring conforming review, and any unresolved priority conflict. Assign specialist confirmation where necessary.

3. Turn findings into discrete parent decisions

Replace descriptive comments with questions that require instructions. “Guarantee remains” becomes: “Will the parent accept continuing exposure, and if so, with what protection and release plan?” Identify the relevant obligor, beneficiary, business, and proposed allocation.

Separate economic allocation, defense control, and third-party release. Do not record an intercompany allocation as evidence of an outside creditor’s release. The filed separation agreement’s Sections 6.02–6.04 illustrate indemnities linked to defined liabilities, specified recovery reductions, and ancillary-agreement dependencies—not a determination of liability to outsiders.

Record: verified facts, remaining uncertainty, preferred instruction, fallback, and required approver. Split a row when the decisions require different approvals.

4. Test implementation assumptions against supporting documents

For shared contracts, compare the actual restructuring steps with assignment, change-of-control, shared-use, consent, termination, exclusivity, and guarantee provisions in the complete amended contract. Do not assume a spin-off triggers every restriction, or that an intercompany arrangement establishes permitted use.

The filed separation agreement’s Section 2.04 addresses efforts to divide or replicate shared contracts and permissible interim arrangements, subject to disclosure-letter exceptions and Article III. It is not counterparty-consent evidence.

For service exits, test operational assumptions against notice, pricing, and change-control provisions. Under the filed transition services agreement, Section 9.01(f), agreed scope changes require schedule updates; the provider need not agree to a requested change. A reduction may generate termination charges.

Record: the assumption, supporting or missing evidence, available alternative, and documents needing amendment.

5. Prioritize by consequence and decision dependency

Rank issues according to parent exposure, uncertainty, and the next decision they constrain. Keep impact and likelihood distinct: an unquantified historical claim may be significant even when likelihood cannot yet be assessed. Identify whether a decision depends on another row.

Escalate business-perimeter conflicts, retained guarantees, service-continuity risks, and unresolved distribution conditions. Keep routine drafting cleanups out of approval-meeting materials unless they affect those decisions.

The filed separation agreement’s Section 4.02 includes parent-board approval and execution of Master Ancillary Agreements among its distribution conditions. Do not treat contractual waiver language as establishing that independent legal requirements are waivable; obtain transaction-specific advice.

Record: priority rationale, affected decision gate, dependencies, and authorized approver.

6. Obtain instructions and reconcile the package

Circulate a focused request stating the source, exposure, proposed position, fallback, and instruction needed. Route tax, benefits, treasury, operational, and local-law questions to specialists while retaining responsibility for reconciling their answers.

After instructions arrive, check every affected definition, schedule, operative clause, and implementation document. If a service exit date changes, revisit payment provisions and dependent migration arrangements. The filed transition services agreement, Section 9.02 preserves specified payment obligations and imposes a negotiated 180-day invoicing limit for termination and decommissioning charges. Continuing charges depend on the applicable schedules and termination route; this is not a statutory deadline.

Record: instruction, approver, conforming changes, and remaining commercial dependencies. Do not present an unapproved fallback as an agreed position.

7. Verify disposition and preserve remaining exposure

Use precise statuses: awaiting evidence, awaiting instruction, drafting agreed, implemented, or accepted residual risk. Agreement on a negotiating position is not incorporation into the documents. Where implementation matters, distinguish execution, delivery, and legal effectiveness.

Verify revised text against approved instructions and inspect related schedules. For accepted risk, identify the approver, acceptance conditions, and continuing owner. A delayed transfer or guarantee release may move to a post-distribution tracker, but retain the handoff reference and unresolved exposure in the issues list.

Record: resolution evidence, remaining conditions, and handoff owner. Keep unresolved items visible at the next decision gate.

Worked example

Fictional scenario: Alder Harbor Holdings plans to distribute its equipment-services subsidiary, Bracken Field Services. All parties, documents, clauses, and amounts below are fictional. Parent counsel is preparing instructions before authorizing the final package.

The separation draft allocates Bracken’s operating liabilities to Bracken. However, only the base shared-software license is available; amendments and consent evidence are missing. The transition-services draft permits exit after six months while its pricing schedule assumes twelve months. A historical-site schedule assigns claims to Bracken, but a discontinued-operations exclusion appears to retain them at the parent.

The review baseline is SDA-03 draft v4, TSA-05 draft v2, and C-14’s signed base license. The missing amendments are not assumed to contain—or eliminate—restrictions.

The list replaces a general approval request with three targeted decisions. SO-01 requires contract and access verification, not merely stronger intercompany allocation wording. SO-02 requires costing before the fallback can be approved. SO-03 requires reconciliation of competing allocation provisions and specialist assessment; the reserve does not fill the missing claims inventory. None is ready to close merely because counsel has proposed language.

Common mistakes

• Summarizing clauses instead of requesting decisions. State the parent’s choice, proposed position, and instruction needed.
• Reviewing the separation agreement in isolation. Trace controlling ancillary provisions, exceptions, and affected schedules.
• Treating allocation as a third-party release. Identify the separate release or consent evidence needed.
• Calling every uncertainty a drafting defect. Distinguish missing business instructions, missing evidence, and text requiring revision.
• Closing rows when redlines circulate. Verify approved wording, implementation dependencies, and resolution evidence.

Final quality check

• Every issue cites the reviewed version and exact source location; references have been checked against the source.
• Verified facts are separated from assumptions and unresolved legal conclusions.
• Missing schedules, amendments, and consent evidence remain explicit.
• Parent exposure and priority have issue-specific reasons.
• Preferred positions and fallbacks reflect actual instructions or clearly assigned approval requests.
• Related agreements and implementation documents have been reconciled.
• Every open issue has an owner and decision gate; every disposed issue has resolution evidence or documented risk acceptance and any continuing handoff.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. For this workflow, contract review supports review in Word: choose the represented party or neither and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name and dismiss findings with reasons. Tabular review supports cross-document work; due diligence classification can organize the package and prioritize human review. The issues table remains counsel’s work product, with legal judgment and approvals retained by the team. Book a demo to discuss your separation-document review workflow.

Frequently asked questions

Should every diligence finding appear on the issues list?

No. Include findings requiring a parent decision, evidence that blocks one, or coordinated document changes. Keep routine requests and accepted drafting cleanups in supporting records, linked where useful.

How should we handle missing schedules?

Identify the allocation or approval question the missing schedule prevents you from answering. Assign a custodian and decision gate. Do not infer that an unavailable schedule contains no exceptions or that public filings provide the complete record.

Can one issue cover several agreements?

Yes, when one instruction resolves the underlying question. Cite every affected document and verify conforming changes. Split the issue when different approvers, evidence requirements, or implementation decisions would otherwise become obscured.

When can the parent accept an unresolved issue?

Document acceptance after the authorized decision-maker receives the exposure, uncertainty, alternatives, and necessary specialist advice. Record conditions and a continuing owner. Risk acceptance does not verify missing facts or replace separately required approvals.

Sources

These sources concern the filed transaction documents, not subsequent performance or amendments.

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

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.