How to prepare a due diligence request list for Corporate Spin-Off Transactions

Prepare a parent-side spin-off diligence request list by translating the proposed separation perimeter into specific evidence requests: what moves, what stays, what remains shared, and what could leave the parent exposed. Assign each request to a custodian, identify the allocation question it must answer, and require complete documents with schedules and amendments. The deliverable is a prioritized, source-linked request list that separates verified responses from missing evidence and directs unresolved questions to the lawyer or business owner authorized to decide them.

When to use this workflow

Use this workflow when parent-company counsel has a preliminary separation perimeter or restructuring plan and needs coordinated responses from legal, finance, tax, HR, IT, procurement, and operating teams. It also applies when an existing data room contains substantial material but does not explain which assets, liabilities, contracts, and dependencies belong to each business.

The task is preparing and maintaining the request list—not resolving every allocation issue or building the entire closing checklist. Requests should expose decisions affecting the separation agreement, ancillary agreements, local transfer documents, and continuing parent obligations.

This guide uses a US transactional orientation. Securities requirements, tax treatment, distribution authority, creditor issues, and foreign transfer formalities require transaction-specific analysis. Contract conclusions require the actual wording, governing law, facts, and restructuring steps. The cited agreements illustrate negotiated provisions, not general law or market standards.

What you need

Start with the current business perimeter, entity chart, restructuring steps, proposed distribution date, and drafting assumptions. Label preliminary materials so respondents do not mistake proposals for approved allocations.

Obtain these inputs:

• Ownership and operations: entity registers, business descriptions, locations, discontinued operations, and asset and liability inventories.
• Contract population: customer, supplier, financing, guarantee, license, lease, and shared-service records, including amendments and side letters.
• Separation documents: agreement drafts, allocation schedules, disclosure materials, and contemplated local instruments.
• Functional inventories: employees and benefits, permits, IP, data systems, real estate, claims, insurance, and tax records.
• Response governance: parent-side custodians, specialist counsel, access restrictions, and internal decision dates.

Maintain a supporting document index with stable IDs, parties, dates, execution status, versions, jurisdictions, and business allocations. Link amendments and schedules to their base documents.

Do not assume public filings supply complete precedent packages. GE Vernova’s April 2024 Form 8-K lists separate separation, transition-services, tax, employee, trademark, real-estate, and investment agreements; its exhibit notes identify omitted schedules and redacted material. Request complete source packages rather than treating that inventory as mandatory for every spin-off. Form 8-K, Items 1.01 and 9.01.

Use the template

Use the Corporate Spin-Off Transactions — Diligence request list below. Copy this table into your working document or spreadsheet and expand it by business, entity, jurisdiction, or contract population.

Keep request IDs stable when rows are reassigned. “Evidence requested” should specify the population, relevant period, document types, and completeness confirmation sought. “Parent question” explains the allocation or exposure decision—for example, whether a retained parent guarantee supports a transferring subsidiary’s obligations.

Use “Priority / due” for an internal response date tied to a decision dependency, not an assumed legal deadline. “Response citation” identifies the document ID and clause, schedule, page, or spreadsheet cell. The final field records the gap, next action, action owner, and status: absent, partial, under review, or closed.

For large populations, link supporting schedules rather than compressing dozens of contracts into one cell. Use linked response notes for access restrictions, review history, and disposition evidence. Distinguish “not applicable, confirmed by custodian” from “no response.”

Step by step

1. Convert the separation perimeter into request populations

Identify transferring entities, retained entities, shared operations, and uncertain allocations. Test the perimeter against operating arrangements: a business may use parent-owned IP, occupy a retained lease, or purchase under a group contract despite appearing self-contained in an entity chart.

Include former businesses and discontinued operations where they could affect allocation questions. Ask custodians to identify exclusions, records outside their systems, and the basis for any completeness confirmation.

Record: one request row per coherent population, its perimeter assumption, and the parent-side question. Mark disputed boundaries as open rather than assigning them by inference.

2. Map each topic to its controlling documents

Map the separation agreement, ancillary agreements, schedules, and local instruments. Request each complete package and ask which document is intended to control overlapping subjects. Include drafts where executed documents do not yet exist, but label their status.

Section 2.02 of the GE–GE Vernova separation agreement assigns specified tax, employee, IP, transition-service, and real-estate matters to ancillary agreements, subject to express exceptions. This illustrates why the request list should test document hierarchy rather than address the separation agreement alone. Separation and Distribution Agreement, Section 2.02.

Record: the expected governing document, related schedule, and missing component. Distinguish a missing schedule from an unresolved interpretation of an available clause.

3. Draft requests around evidence and decisions

Replace “provide all material contracts” with defined requests. For shared procurement, request the contract register, executed agreements, amendments, participating entities, spend allocation, and proposed post-separation user arrangements. Define any materiality threshold expressly rather than leaving respondents to apply inconsistent assumptions.

In a linked contract schedule, separate assignment, change of control, shared use, consent, termination, exclusivity, and parent guarantees. Request the facts needed to compare each provision against the proposed restructuring steps.

Section 2.04 of the GE–GE Vernova agreement illustrates mechanisms for dividing or replicating shared contracts and permissible interim arrangements. Disclosure-letter exceptions and Article III qualify those mechanisms; the provision does not establish counterparty consent. Separation and Distribution Agreement, Section 2.04.

Record: requested evidence, population boundaries, and the precise decision supported.

4. Prioritize residual parent exposure and operating dependencies

Prioritize requests whose answers could change the separation perimeter, undermine operational readiness, or reveal continuing parent exposure. Examples include unreleased guarantees, shared permits, incomplete IP ownership records, dependencies on parent systems, and historical claims with uncertain allocation.

Request both proposed liability allocations and underlying obligation records. Ask separately for defense arrangements, insurance, recovery rights, and third-party release evidence. Do not use an intercompany allocation schedule as a substitute for answering the release question.

Use qualitative priorities with a short reason. Avoid precise likelihood scores without supporting facts. An internal response date should precede the decision it supports and allow time for follow-up.

Record: priority reason, decision dependency, custodian, and response date. Identify what remains undecidable until evidence arrives.

5. Assign custodians and manage restricted responses

Assign a parent-side accountable custodian even when SpinCo personnel, advisers, or counterparties hold the records. Split requests where one owner cannot confirm completeness across jurisdictions or systems.

For tax, employee, claims, and sensitive commercial information, determine the response channel before circulation. Sections 7.1–7.2 of the GE–GE Vernova Tax Matters Agreement address information cooperation, relevant-information limits, and protection against disclosures reasonably expected to waive privilege. Those contractual terms are not a determination that a particular disclosure preserves privilege; refer disclosure decisions to counsel. Tax Matters Agreement, Sections 7.1–7.2.

Record: custodian and, in linked response notes, permitted response location, access restrictions, and responsible counsel. Avoid reproducing sensitive substance in the circulated list.

6. Validate responses and issue targeted follow-ups

Check each response against the request, not merely the presence of an uploaded file. Verify execution status, parties, amendments, schedules, and population coverage. Ask custodians to explain omissions rather than treating silence as confirmation.

Separate verified facts from custodian statements and legal conclusions. “Register lists 12 guarantees” does not establish that all guarantees were identified or released.

For transition services, request service descriptions, dependencies, charging inputs, exit assumptions, and proposed changes. Under Section 9.01(f) of the GE–GE Vernova TSA, agreed scope changes require schedule updates, and the provider need not agree to a requested change. Treat proposed reductions as unresolved until supported. Transition Services Agreement, Section 9.01(f).

Record: exact response citations, remaining gaps, and narrowly drafted follow-ups, retaining the original request ID.

7. Close requests only against an evidenced disposition

Close a row when the evidence has been checked and its question answered. If collection stops despite a limitation, record “closed with limitation” only after an authorized owner accepts the limitation and assigns the resulting issue elsewhere. Do not describe that response as complete.

Link drafting decisions to the deal issues list. Route delayed transfers or continuing obligations to the responsible workstream without expanding the request list into a complete post-closing tracker.

Record: disposition, supporting evidence, reviewer, and linked issue with its receiving owner and decision date. Preserve unresolved dependencies when issuing a revised list.

Worked example

Fictional scenario: Alder Quay Holdings plans to separate its industrial-controls business into Harbor Relay Systems. Parent counsel receives a preliminary entity chart, procurement register, draft transition-services schedule, and guarantees spreadsheet. Management describes the business as operationally independent, but the responses indicate continuing parent support.

All parties, documents, references, and terms below are fictional. “Before” dates are internal decision milestones, not legal deadlines.

These responses change the request strategy. Counsel should not accept operational independence without testing software access and payroll continuity. The license row requires the missing user schedule before a coverage conclusion. The guarantee row requires release evidence, not merely a revised intercompany allocation.

The payroll row reveals a planning gap, not an established early-exit right. Request readiness evidence and charging assumptions before proposing revised terms. No row supports closure merely because a relevant document exists.

Common mistakes

• Organizing only by entity. Shared contracts and systems cross entity boundaries. Add business-use and shared-dependency requests.
• Accepting registers as operative evidence. Use registers to define populations, then obtain underlying agreements and reconcile exceptions.
• Ignoring historical operations. Request former-business, claims, and insurance records to expose unexplained liabilities.
• Conflating assignment, consent, and release. Ask separate questions and require evidence for each.
• Closing at distribution by default. Transfer unresolved requests to named owners for guarantees, delayed transfers, services, or cooperation obligations.

Final quality check

• Every request maps to a perimeter assumption and concrete parent-side question.
• Contract populations cover amendments, schedules, side letters, and shared arrangements.
• Response citations resolve to the correct document version and clause or cell.
• Missing, redacted, unsigned, and superseded material is explicitly identified.
• Facts, custodian statements, and legal conclusions remain distinguishable.
• Restricted responses have an approved access route and responsible reviewer.
• Open issues have owners and decision dates; closed rows retain evidence or an expressly accepted limitation.

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 materials and prioritize human review. Tabular review supports work across multiple documents, while contract review can assist examination of the separation package. The request list remains your team’s work product; lawyers retain responsibility for completeness, allocation, and closure decisions. To discuss this parent-side workflow, book a demo.

Frequently asked questions

Should the parent use an acquisition diligence checklist?

Only as a starting inventory. Reframe requests around retained exposure, shared operations, separation implementation, and continuing relationships—not simply ownership and target-company condition.

How detailed should the first request list be?

Define populations precisely but stage collection where necessary. Start with registers and known critical documents, then request complete packages. Do not defer obvious parent guarantees or operational dependencies.

Can a business owner confirm that consent is unnecessary?

Ask the owner for facts and correspondence, and route the determination to counsel for assessment against the complete contract and transaction steps. Keep factual confirmation separate from legal analysis.

What if a requested schedule does not exist yet?

Record it as unprepared, identify its preparer, and request underlying records. Distinguish a future drafting deliverable from missing evidence that should already exist; neither should be marked complete.

Sources

• GE Vernova Form 8-K, April 2, 2024, Items 1.01 and 9.01
• GE–GE Vernova Separation and Distribution Agreement, Sections 2.02 and 2.04
• GE–GE Vernova Transition Services Agreement, Section 9.01(f)
• GE–GE Vernova Tax Matters Agreement, Sections 7.1–7.2

Source scope: the April 2024 executed documents illustrate their filed provisions; they do not establish 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.