How to organize a legal due diligence document index for Corporate Spin-Off Transactions

A parent-company spin-off diligence index should connect each source document to the separation perimeter, the parent’s potential retained exposure, and the evidence needed to assess completeness. Assign stable document IDs, distinguish versions and execution status, and link agreements to amendments, schedules, ancillary agreements, and implementing instruments. The resulting deliverable is a dated, traceable inventory showing what counsel has, what remains missing or restricted, which sources address allocation questions, and who must resolve each gap. It supports diligence review without substituting for legal conclusions.

When to use this workflow

Use this workflow when parent-company counsel begins collecting spin-off records, inherits a disorganized data room, or reconciles diligence materials with a revised restructuring plan. It is particularly useful where the parent and spin company share contracts, employees, technology, premises, or historical liabilities.

The scope is document organization and completeness, not a complete closing checklist or an opinion on the distribution. This guide uses a U.S. transactional orientation. Securities requirements, tax treatment, corporate distribution authority, creditor rights, and foreign transfer formalities require separate, transaction-specific analysis.

GE Vernova’s filed separation package illustrates the breadth of a collection: it lists separation, transition-services, tax, employee, trademark, real-estate, and investment agreements. Exhibit notes identify omitted schedules or exhibits and redacted portions. This is an inventory example, not a mandatory package or complete diligence record. GE Vernova Form 8-K, Items 1.01 and 9.01.

What you need

Begin with a dated description of the proposed separation perimeter. Identify transferring and retained entities, business lines, shared operations, discontinued businesses, and uncertain allocations. Obtain the restructuring step plan: an ownership chart alone does not explain how contracts, assets, or liabilities will move.

Collect these inputs:

• Entity and business lists, the proposed step plan, and the parent’s document request list.
• Separation and ancillary agreements, disclosure materials, schedules, and local implementing instruments.
• Underlying contracts and records for shared services, guarantees, intellectual property, employees, premises, permits, and historical claims.
• Repository references, supplying custodians, access restrictions, and existing version conventions.
• Parent-side workstream owners and the allocation question each request should answer.

Ask owners about records outside the central repository, including regional amendments and predecessor-business files. Define the collection cutoff and treatment of later additions so the reviewed population remains identifiable.

Use the template

Use the Corporate Spin-Off Transactions — Diligence document index as the master inventory. You can copy this table into your working document or spreadsheet. Maintain one row per identifiable source version and a linked gap row for an expected document that has not been supplied.

Keep each source ID permanent. Use a family identifier to group an underlying agreement, its versions, amendments, schedules, and implementation documents. A replacement draft receives a new source ID linked to the earlier draft; a renamed copy of the same source does not require a new substantive-version entry.

Include the exact document title and a usable repository locator. Distinguish document date, version, and execution status. Identify whether “jurisdiction” means governing law, entity jurisdiction, or asset location; these are different facts.

Use allocation values such as parent-retained, spin company, shared, or unresolved, followed by the business or asset concerned. Mark allocation as proposed until the relevant sources support it. Capture clause or page references beside linked IDs rather than relying on spreadsheet row numbers that may move.

The completeness field distinguishes absent attachments, redactions, incomplete signatures, and restricted access. The final field names an accountable owner, required evidence, and target date. These are user-maintained working fields, not a promised software module.

Step by step

1. Fix the perimeter and indexing rules

Agree which entities, businesses, assets, and historical operations the collection covers. Separate “outside the proposed perimeter” from “not yet assessed.” Keep the latter visible, particularly for parent guarantees and exposures associated with former businesses.

Choose ID conventions, family identifiers, and statuses before bulk collection. State how the team will identify source versions, exact duplicates, gap rows, and records received after the cutoff. Assign ownership by workstream rather than leaving all requests with deal counsel.

Record in the index: stable ID, subject, working allocation, and owner. Mark uncertain perimeter decisions explicitly; folder placement must not decide them.

2. Register sources without losing provenance

Capture each file’s title, location, supplying custodian, date, parties, and apparent status. Preserve the received record when creating a searchable or annotated copy. Distinguish signed documents, unsigned execution versions, negotiation drafts, and reference copies.

Compare candidate duplicates before consolidating them. Identical filenames may conceal different attachments or signatures; different filenames may contain identical content. Identify the working source without deleting evidence of its origin.

Record in the index: locator, source-version status, custodian, and unresolved duplicate questions. An incomplete scan remains incomplete even if its visible pages are signed.

3. Build document families and identify missing components

Read incorporation provisions, amendment histories, and attachment lists. Link side letters, schedules, statements of work, guarantees, and local instruments to the base agreement. Give separately supplied components their own IDs so reviewers can cite them precisely.

For an absent component, create a gap row identifying the source that establishes its expected existence. Distinguish a missing document from an unanswered request asking whether such a document exists. Do not infer an attachment’s contents from its title.

Record in the index: linked IDs, the originating clause or attachment reference, and a specific status such as “base agreement received; Schedule 4 absent.” Assign the request to the likely custodian.

4. Map which agreement addresses each subject

Group documents by legal function, not merely title. In the GE–GE Vernova agreement, Section 2.02 assigns specified tax, employee, intellectual-property, transition-service, and real-estate matters to ancillary agreements, subject to exceptions. These are contract-specific priority rules. Separation and Distribution Agreement, Section 2.02.

Read the actual hierarchy in the parent’s transaction. Connect the relevant definition, operative provision, allocation schedule, and local implementation instrument. Include transition-service schedules where they identify shared systems or premises, but keep service-exit analysis in the appropriate workstream.

Record in the index: subject references and related IDs. Assign uncertain priority or inconsistent allocations to counsel; do not select a controlling document solely because it is titled “separation agreement.”

5. Connect shared arrangements to the restructuring steps

Link each shared contract family to the proposed transfer, division, replacement, or continued-use arrangement. Identify sources for assignment, change of control, consent, termination, shared use, exclusivity, and parent guarantees. Put substantive findings in a linked issues record rather than crowding the index.

Section 2.04 of the GE–GE Vernova agreement illustrates shared-contract division or replication and interim arrangements, subject to exceptions and other provisions. It does not establish counterparty consent. Separation and Distribution Agreement, Section 2.04.

Record in the index: the step-plan reference, relevant contract clauses, consent evidence, and guarantee instrument. Separate planned allocation from received implementation evidence, and a proposed parent release from a documented release.

6. Separate completeness from access permission

Identify restricted records through a controlled locator and custodian without reproducing sensitive content in a broadly circulated index. Ask responsible counsel to determine access and permitted descriptions for privileged materials and sensitive employee or tax records.

The GE–GE Vernova Tax Matters Agreement contains information-cooperation provisions with relevance and privilege-related limitations. Those contractual protections do not establish that a particular disclosure preserves privilege under applicable law. Tax Matters Agreement, Sections 7.1–7.2.

Record in the index: whether the record exists, who controls access, and whether an authorized reviewer checked completeness. “Restricted” is neither “missing” nor “reviewed.” Avoid exposing sensitive conclusions through the index itself.

7. Reconcile gaps and issue a dated index

Reconcile entries against the request list, attachment lists, step plan, and workstream collections. Obtain owner confirmation of outstanding gaps and later additions. Test locators and citations against source files, including linked amendments and separately stored signature pages.

Where relevant, distinguish execution, delivery, and effectiveness of implementation documents. Distribution does not supply missing evidence for delayed transfers or guarantee releases. Carry those collection questions forward without converting the index into a full post-closing obligations tracker.

Record in the index: status, next action, accountable owner, and target date. Issue a dated version identifying unresolved gaps and its collection cutoff. Preserve earlier snapshots so reviewers can reconstruct the population supporting an earlier assessment.

Worked example

Fictional scenario: Alder Quay Holdings proposes to spin off its measurement-devices business as Bracken Instruments. Parent counsel receives a separation draft and a signed software agreement with some attachments. Procurement describes the software arrangement as ready to transfer. The separation draft refers shared-software allocation to Schedule C, which is absent. The software agreement contains a written-consent provision, but the team has not established whether the proposed steps trigger it.

All parties, documents, dates, identifiers, and provisions below are fictional.

The index changes the decision from “transfer ready” to “allocation and consent position unresolved.” Section 11.2 provides a review starting point, not a conclusion that consent is required. Counsel needs the complete amended contract and step S-07 to assess its application.

The absent schedule prevents confirmation that the draft assigns this platform to Bracken. Procurement’s statement remains an instruction to investigate, not documentary proof. Retain both gaps until sources arrive or counsel documents a supported alternative treatment. If Schedule C later arrives, give it a source ID and link it to GAP-001; preserve the gap’s resolution history.

Common mistakes

• Treating folders as the perimeter. Reconcile them against entities, shared operations, and former businesses; folder labels do not establish coverage.
• Equating signatures with completeness. Check attachments and amendments separately, even where the base agreement is signed.
• Assuming allocation proves release. Index allocation, guarantee, and counterparty-release evidence separately for counsel’s assessment.
• Overwriting earlier drafts. Preserve source-version IDs and relationships so prior findings remain traceable.
• Treating restricted records as collection gaps. Use controlled references and an authorized reviewer rather than unrestricted redistribution.

Final quality check

Before circulation, confirm:

• Every received source version has a stable ID and working locator.
• Dates, parties, status, and citations match the source files.
• Jurisdiction entries distinguish governing law from entity or asset location.
• Amendments, incorporated schedules, and local instruments are linked or specifically flagged absent.
• Shared arrangements and parent guarantees have explicit working allocations.
• Restricted records have an access owner and accurate review status.
• Open issues are resolved with evidence or assigned an owner, action, and target date.
• The dated index identifies its cutoff and separates document evidence from legal conclusions.

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 collections and prioritize human review. Tabular review supports work across multiple documents, while contract review can support examination of allocation and consent provisions. Counsel remains responsible for verifying sources, completeness, and interpretation. To assess the workflow for a parent-side spin-off collection, book a demo.

Frequently asked questions

Should the index include every document or only material agreements?

Register the collected population within the agreed scope, then prioritize review. Otherwise, “not indexed” may be mistaken for “not collected.” Document exclusions and preserve references where a record’s relevance remains uncertain.

How should we index an unavailable schedule?

Create a gap row with its own ID and cite the provision identifying the schedule. Leave unknown dates, parties, and contents unconfirmed. When received, create a source entry and link the resolved gap rather than erasing its history.

Can public filings establish the complete spin-off collection?

Use them to seed requests, not certify completeness. The GE Vernova exhibit notes identify omissions and redactions. Request complete executed documents, schedules, amendments, and implementation evidence from transaction custodians. Form 8-K, Item 9.01.

When can a document family be marked complete?

When identified components are received and checked, or an authorized reviewer records why a component is not required for the defined scope. Record access limitations separately. Family completeness does not establish legal sufficiency, effectiveness, or resolution of substantive issues.

Sources

These filed transaction documents illustrate wording and inventory structure, not generally applicable law or market standards. The guide does not assess subsequent amendments or transaction performance.

• GE Vernova Form 8-K, Items 1.01 and 9.01.
• GE–GE Vernova Separation and Distribution Agreement, Sections 2.02 and 2.04.
• GE–GE Vernova Tax Matters Agreement, Sections 7.1–7.2.

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.