How to build a due diligence findings and risk tracker for Corporate Spin-Off Transactions

Build the tracker around the parent company’s separation perimeter, retained exposure, and unresolved dependencies—not merely the documents reviewed. Give each finding a stable ID, precise source references, an evidence classification, a parent-risk assessment, and an accountable owner. Test findings across the separation agreement, ancillary agreements, schedules, and underlying business records. The resulting deliverable should distinguish established facts from uncertainty, identify decisions needed before distribution, and preserve evidence of resolution or an expressly accepted continuing exposure.

When to use this workflow

Use this workflow when parent-company counsel needs a consolidated findings record before negotiating separation allocations, approving transition arrangements, or recommending distribution readiness. It suits in-house teams coordinating corporate, tax, employment, real estate, IP, finance, and operational specialists.

The task is findings management: identifying issues, assessing parent exposure, assigning decisions, and preserving resolution evidence. The tracker supports—but does not replace—the closing checklist, specialist analysis, or approval materials.

This is a U.S.-oriented workflow. Actual contract language, governing law, restructuring steps, and local transfer requirements determine the analysis. Securities requirements, tax qualification, corporate distribution authority, and creditor rights require separate, transaction-specific advice. The public agreements cited below illustrate negotiated provisions, not generally applicable rules or market standards.

What you need

Start with the separation perimeter and restructuring sequence. Identify which entities, assets, liabilities, and operating functions will remain with the parent, transfer to SpinCo, or serve both businesses.

Collect:

• Entity charts and step plans identifying transfer entities, jurisdictions, and effectiveness points.
• Separation and ancillary agreements, disclosure letters, schedules, amendments, and local implementing instruments, with execution status.
• Allocation schedules covering historical businesses, claims, guarantees, insurance, employees, and intercompany balances.
• Shared contracts, permits, property records, IP licenses, data arrangements, and relevant consent correspondence.
• Transition-service schedules, operational dependencies, and proposed releases or replacement arrangements.

Give every document a stable ID in a supporting index. Record its date, parties, version, jurisdiction, business allocation, and missing attachments. Assign a parent-side custodian to each missing record.

Do not equate public availability with completeness. The GE Vernova Form 8-K exhibit index identifies multiple transaction agreements and notes omitted or redacted material; request the complete applicable package for the matter under review.

Use the template

Use Corporate Spin-Off Transactions — Diligence findings tracker as the working template. You can copy this table into your working document or spreadsheet. Create one row per issue requiring a distinct decision, not one row per document.

“Perimeter” identifies the affected entity, business, asset, or liability. Classify each finding as a verified fact, document gap, or legal question. Split findings when different decisions or owners are needed.

Source references should include document ID, version, clause or page, and relevant schedule cell. Link evidence rather than reproducing sensitive material unnecessarily.

Describe the parent’s exposure separately from the proposed allocation. Treat an indemnity, a third-party release, and operational continuity as separate verification questions. Record likelihood and impact separately, with a short rationale and “unassessed” where evidence is insufficient.

Use distinct statuses: investigating, decision pending, implementation pending, accepted continuing exposure, and resolved. Record the authorized acceptance decision for continuing exposure; do not label it eliminated.

Step by step

1. Define the perimeter and parent decision criteria

Confirm the current restructuring version with the transaction lead. Identify retained entities, transferring businesses, shared resources, and discontinued operations that do not fit current business lines.

Agree internal escalation criteria: retained liability, operational interruption, uncertainty affecting a distribution decision, or an allocation needed by another workstream. These are review criteria, not legal thresholds.

Record each issue’s perimeter in the first column. Where the allocation cannot be established, open an “allocation unresolved” row and identify the factual instruction needed. Preserve the step-plan version so later changes can be tested against existing findings.

2. Establish controlling documents and evidence gaps

Map each subject to the agreement and implementing documents that address it. Check priority provisions before relying on general separation language. The filed GE–GE Vernova agreement’s Section 2.02 assigns specified matters to ancillary agreements, subject to exceptions. That provision illustrates why document hierarchy belongs in the review. (sec.gov)

For each finding, record the operative clause and related schedule or local instrument. Distinguish drafts from executed documents and link amendments.

If a schedule is missing, identify the specific conclusion it prevents—for example, whether a former facility’s liabilities are retained. Assign its production to a custodian. The output is a bounded evidence gap, not a conclusion that the missing document contains no obligation.

3. Test shared-contract and continuity assumptions

Compare the actual restructuring steps against complete amended contracts. Use a supporting comparison sheet for assignment, change of control, shared use, consent, termination, exclusivity, and parent guarantees. Transfer actionable exceptions into the findings tracker.

Ask whether SpinCo needs a separate contract, whether continued parent-provided access is supported, and what evidence establishes any interim arrangement. The filed agreement’s Section 2.04 addresses shared-contract separation and interim arrangements, subject to disclosure-letter exceptions and Article III; it does not establish counterparty consent. (sec.gov)

Record the affected operation, relevant contract restriction, available consent evidence, and requested decision. Keep “intercompany mechanism agreed” distinct from “external contractual position verified.”

4. Assess retained exposure and conflicting allocations

Reconcile allocation schedules with claims inventories, former businesses, guarantees, insurance records, and indemnity procedures. Investigate three questions separately: economic allocation between parent and SpinCo, control of claims or defense, and the parent’s position toward outsiders.

The filed agreement’s Sections 6.02–6.04 link indemnities to defined liabilities, account for specified recoveries, and recognize ancillary indemnification provisions. They illustrate allocation dependencies rather than resolving third-party liability. (sec.gov)

State likelihood, impact, and evidence confidence with reasons. Avoid unsupported amounts or probability scores. Record conflicting definitions as discrete decisions, with the parent’s preferred outcome, fallback, and affected documents in a linked decision note. Identify whose specialist judgment is needed.

5. Convert findings into accountable decisions

Write actions as concrete requests: obtain a missing release, confirm an affected entity, reconcile allocation schedules, or obtain advice on a defined legal question. Assign one accountable owner and identify the authorized decision-maker.

Tie the decision date to its dependency. A supplier arrangement needed for readiness testing may require resolution before the distribution recommendation.

Where an issue affects a distribution condition, cite that condition separately. The filed agreement’s Section 4.02 contains listed conditions and parent-waiver language. Treat that as contractual wording, not an answer about independently applicable legal requirements. Record a specialist determination or an open referral before presenting waiver as available. (sec.gov)

Output: a decision-ready row stating the requested outcome, evidence still needed, owner, approver, and decision trigger.

6. Verify mitigation and preserve continuing exposure

Test whether the proposed solution addresses the identified problem. Track execution, delivery, effectiveness, operational readiness, and external release separately where relevant. Agreed drafting may leave implementation unresolved.

For service findings, verify scope, pricing, termination route, and surviving charges against the applicable schedules. The filed transition services agreement’s Sections 9.01(f) and 9.02 address negotiated scope changes, surviving payments, and a 180-day invoicing period for termination and decommissioning charges. The provider need not agree to a requested scope change. These are contractual examples, not universal exit rules. (sec.gov)

Record mitigation evidence and remaining uncertainty. Carry delayed transfers, guarantee releases, service exits, and cooperation obligations into an assigned follow-up record, retaining the finding ID. Require the receiving owner’s acknowledgment before closing the handoff task; keep the underlying exposure visible until resolved or expressly accepted.

Worked example

Fictional example. Alder Quay Holdings plans to distribute its industrial-sensors business as Lumen Harbor Systems. All parties, documents, provisions, and facts below are invented.

The draft separation agreement allocates sensor-business costs to Lumen Harbor. Procurement assumes that allocation permits use of the parent’s supplier platform. Finance expects lower service fees when users leave. Treasury points to a draft indemnity as protection for a parent guarantee. The review team tests these assumptions rather than treating them as established outcomes.

F01 requires the annex before counsel can assess permitted users; the record does not establish a consent requirement or permission. F02 needs a commercial decision reflected in the service terms, not merely revised wording. F03 distinguishes the evidenced guarantee from the unknown likelihood of a call and the missing release evidence.

The parent decision therefore changes from “the draft allocates these items” to three specific requests. No missing consent, revised fee, or lender response is assumed to exist.

Common mistakes

• Treating allocation as release. Review the external instrument and release evidence separately from the intercompany allocation.
• Calling missing schedules immaterial. Identify which conclusion depends on each missing attachment and keep it provisional.
• Using unexplained risk scores. State likelihood, impact, and evidence confidence; distinguish uncertainty from established exposure.
• Closing rows when drafting is agreed. Require issue-specific implementation evidence and distinguish accepted exposure from resolution.
• Assigning several nominal owners. Name one accountable owner and identify other specialists as dependencies.

Final quality check

Before circulating the tracker, confirm:

• Each row identifies the affected entity, business, asset, or liability.
• Source references resolve to the correct version, clause, and attachments.
• Verified facts, document gaps, and legal questions remain distinguishable.
• Risk assessments state their basis and acknowledge insufficient evidence.
• Cross-agreement conflicts and external-release questions remain visible.
• Every open issue has an owner, decision trigger, and escalation route.
• Resolved rows retain evidence; accepted exposures retain approval and follow-up ownership.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its due diligence capabilities, including bulk document classification, to organize the separation record and prioritize human review. Tabular review supports work across multiple documents. For related contract review in Word, reviewers can select the represented party and supply deal-specific instructions; findings quote and locate clauses, rank severity, and identify missing language as not present. The tracker remains the team’s work product, and lawyers retain allocation analysis and decision responsibility. Book a demo to discuss this parent-side workflow.

Frequently asked questions

Should every reviewed contract receive a findings row?

No. Use the document index as the review inventory. Create findings rows for actionable exceptions, gaps, or decisions. Separate issues when remedies, decision-makers, or closure evidence differ, even if they arise from one contract.

How should tax-information issues be recorded?

Identify the requested records, custodian, purpose, access restrictions, and specialist decision needed. Verify applicable cooperation provisions and deadlines separately. Keep sensitive material in appropriately restricted source records; do not assume contractual confidentiality language answers the privilege question.

Can distribution close all remaining findings?

Do not use distribution alone as closure evidence. Retain delayed transfers, release requests, and service obligations until resolved or accepted with assigned follow-up responsibility. Distinguish completing the handoff from eliminating the exposure.

What belongs in the parent decision summary?

Highlight material unresolved exposure, consequential evidence gaps, requested approvals, and proposed residual-risk acceptance. Link every item to a tracker ID. State whether the requested decision concerns investigation, drafting, implementation, or acceptance so the summary does not obscure the remaining work.

Sources

These filed documents illustrate contractual wording, 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, Sections 2.02, 2.04, 4.02, and 6.02–6.04.
• GE–GE Vernova Transition Services Agreement, 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.