How to organize a legal due diligence document index for Corporate Carve-Out Transactions

A buyer’s carve-out diligence index should show which documents support the acquired business, who holds the relevant rights, and what evidence remains missing. Start with the acquisition perimeter, assign stable document IDs, connect parent-level arrangements to business operations, and distinguish received files from complete, reviewed document families. The deliverable is a source-linked index that lets buyer’s counsel locate operative evidence, identify separation gaps, and route targeted requests without confusing data-room availability with legal or operational readiness.

When to use this workflow

Use this workflow when buyer’s counsel receives the initial data room, the acquisition perimeter changes, or diligence reveals shared arrangements. It is particularly useful where the business operates through several seller entities or depends on parent-owned software, personnel, facilities, IP, or procurement contracts.

The task is document organization and evidence completeness—not preparation of a complete contract risk matrix or closing checklist. The index should give those downstream work products dependable source references.

This is a US-focused workflow guide. Contract rights and transfer mechanics depend on actual language, governing law, transaction structure, and facts; cross-border assets require relevant local review. Keep current ownership, business use, and proposed transfer treatment separate rather than treating any one as proof of the others.

What you need

Collect these inputs before substantive indexing:

• Perimeter materials: transaction structure, entity chart, included and excluded assets, proposed liability allocations, and business locations.
• Source inventory: data-room listing, access dates, filenames, version information, and outstanding seller requests and responses.
• Dependency information: shared procurement, insurance, treasury, guarantees, applications, payroll, premises, and intercompany licenses.
• Transaction drafts: purchase agreement, disclosure schedules, separation documents, transition services agreement (TSA), and proposed supply, IP, lease, and employee arrangements.
• Review assignments: buyer legal and functional contacts, seller request coordinator, priority criteria, and applicable access restrictions.

If the perimeter remains under negotiation, record its version and date in an index cover note. Establish who may access sensitive records and how restricted materials will be referenced without reproducing their contents in a widely circulated index.

Use the template

Use the Corporate Carve-Out Transactions — Diligence document index below. Copy this table into your working document or spreadsheet. Maintain one row per substantive source document or separately tracked missing item; connect related records by family and request IDs.

ID / family combines a stable source ID with a family reference, such as D014 / F003. Use R IDs for requested items not received. A family connects the base agreement, amendments, schedules, orders, and side letters. Do not renumber records when folders move.

Holder / coverage distinguishes the named contracting party or apparent rights holder from the business using the arrangement. Mark uncertain coverage explicitly. Perimeter role records included, excluded, shared, transition-only, or unresolved, distinguishing current facts from proposed treatment.

Source / citation contains the data-room locator and relevant clause or page. For requests, cite the source establishing the gap or record the request and seller response dates. Evidence status separately records receipt, completeness, execution, and review—for example, “received; order missing; signed; review pending.”

Use Related IDs / gap for dependencies and linked requests. Put an accountable owner, priority, and next action in Owner / next action. Keep detailed legal analysis in a linked issue record.

Step by step

1. Translate the deal perimeter into indexing categories

Begin with entities, assets, liabilities, employees, IP, permits, data, and premises. For each category, ask who holds it now, which business uses it, and which proposed document explains the buyer’s future ownership or access.

Do not adopt the seller’s folder structure as the only taxonomy. A parent software agreement filed under corporate IT may support several acquired facilities. Conversely, a target-named document may concern an excluded operation.

Record: holder, coverage, and perimeter role, with the source supporting each classification. Use “unresolved” where evidence is insufficient, and identify the perimeter baseline in the cover note.

2. Register documents before assessing completeness

Capture stable IDs, exact filenames, locations, versions, and apparent execution status. Distinguish signed agreements from drafts, unsigned counterparts, and scans missing signature pages. Check similarly named files before deciding whether they are duplicates or different instruments.

Retain superseded versions where they support an existing diligence issue, but identify the current review version. If a replacement upload changes substantive text, preserve its relationship to the earlier source rather than overwriting the record.

Record: one row per substantive source, its family ID, and evidence status. For duplicate copies, preserve each location against the substantive record so request references remain traceable.

3. Reconstruct document families

Read incorporation language, amendment references, exhibit lists, and signature blocks. A master agreement without its site-specific order may leave the relevant coverage unresolved. Compare references within the documents against the room listing; do not rely only on adjacent filenames.

Create a request row for an expressly referenced but absent attachment. For a broader inquiry, use “requested; existence unconfirmed” rather than implying a document exists. Distinguish redacted material from missing pages and inaccessible files: the follow-up differs.

Record: a separate request ID, family ID, parent document citation, precise missing item, and owner. Close the request only after checking the response against the identified gap.

4. Map parent-level and shared arrangements

Look beyond target signatories. Connect shared services to their applications, vendors, personnel, premises, and data. Ask the buyer’s functional team to confirm operational use while counsel checks the documentary basis; record those as different evidence sources.

The filed Seres–Nestlé TSA illustrates dependency mapping: its service schedule connects HR administration to IT.03 and identifies vendor-contract conveyance among logistics dependencies. Redactions limit conclusions about commercial details. See the Schedule of Services.

Record: related service and contract IDs, evidence of current coverage, and unanswered questions about post-separation support. Where a dependency is known only from a business interview, identify the speaker, date, and requested documentary confirmation.

5. Connect allocation documents without resolving exposure

Link documents addressing the same asset or obligation across the purchase agreement, schedules, TSA, and separation instruments. Keep present ownership separate from proposed allocation, and flag inconsistent definitions or schedule references for counsel.

For example, Section 2.04—not Section 2.02—of the Emergent–BTG agreement addresses assumed and retained liabilities. Its contract-liability provisions address pre-closing breaches and delayed-transfer contracts, including a TSA cross-reference. See Section 2.04. Use this as an illustration of linked drafting, not a conclusion about another buyer’s exposure.

Record: the allocation clause, version, and underlying source IDs. If the documents conflict, assign reconciliation rather than choosing one draft’s treatment as definitive.

6. Prioritize gaps by the buyer decision they prevent

Rank requests according to the blocked decision: confirming coverage, assessing transfer language, evaluating transition support, or identifying replacement needs. Route technical questions to the relevant buyer function and legal interpretation to counsel.

Keep operational urgency separate from closing-condition status. Matthews–Duravant Section 5.5(e) generally excludes specified consent and separation failures from the closing-condition assessment, except to the extent of a breach of Section 3.4 or 5.5. Read those provisions with Article VIII. See Section 5.5(e).

Record: priority, accountable owner, precise request, and the decision awaiting evidence. Link any contractual closing-condition analysis separately; do not infer it from priority alone.

7. Reconcile and issue a controlled review version

Compare the index with the latest room listing, seller responses, and perimeter materials. Resolve orphan amendments, inconsistent statuses, and requests marked answered without supporting evidence. A replacement upload does not close a gap unless it answers the request.

Issue a dated version with a short cover note identifying the perimeter baseline, access limitations, and unresolved high-priority items. Assign maintenance responsibility and a practical update cadence during active diligence.

Record: updated evidence status, reviewer, and follow-up ownership. Preserve request and response references so another reviewer can understand why an item remains open or was closed.

Worked example

Fictional scenario: Alder Quay Holdings proposes to sell its industrial sensor business to Westhaven Instruments. The buyer will acquire a subsidiary and specified parent-held assets. Payroll and warehouse software currently depend on parent support. All parties, documents, identifiers, and clause descriptions below are fictional.

The room contains a signed warehouse software master agreement, a draft TSA schedule, and a draft purchase-agreement schedule. The master agreement references an absent order. The TSA describes payroll support but references an unavailable access schedule. The purchase-agreement schedule proposes excluding a parent procurement contract that the business team reports using.

Create separate R009–R011 request rows in the working index, linked to these sources. Do not fabricate the absent terms or treat business reports as verified contractual coverage.

The index changes the next decision. D021 requires the order before counsel can assess transfer language against the licensed scope. D034 identifies proposed payroll support but leaves its access dependency unverified. D041 calls for reconciliation, not a conclusion that supply will stop: exclusion remains proposed, and the underlying coverage is unknown. Three uploaded files therefore do not equal three completed diligence items.

Common mistakes

• Indexing only target signatories. Request parent-held and shared arrangements separately, recording both holder and business coverage.
• Treating folder placement as perimeter evidence. Cite the allocation document and distinguish its proposed treatment from established facts.
• Calling an upload a complete contract. Check amendments, incorporated orders, schedules, and signatures before changing completeness status.
• Recording every gap as “missing.” Separate referenced omissions, existence-unconfirmed requests, redactions, and access problems; give each the appropriate follow-up.
• Closing requests on receipt alone. Verify that the response addresses the cited gap and preserve the reason for closure.
• Embedding unsupported risk conclusions. Record evidence in the index and link clause-supported analysis to a named legal reviewer.

Final quality check

• Every substantive source and separately tracked request has a stable ID.
• Holder, business coverage, and current or proposed perimeter treatment are distinguishable.
• Families connect amendments, schedules, orders, and known omissions.
• Clause and page references match the identified source version.
• Receipt, execution, completeness, and review statuses remain separate.
• Shared-service records link known dependencies and identify unverified reports.
• Open issues are resolved with evidence or assigned an accountable owner and next action.
• The issued version identifies its perimeter baseline, access limitations, and maintenance owner.

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. Use these capabilities to support the buyer’s index while lawyers verify citations, document families, and perimeter judgments. The index remains the team’s work product. To discuss this carve-out diligence workflow, book a demo.

Frequently asked questions

Should the index have one row per contract or per file?

Use one row per substantive source, connected by a family ID. Keep amendments and separately supplied schedules traceable. Duplicate copies may share a substantive record if all relevant locations remain recorded.

How should we record documents the seller says do not exist?

Preserve the request and attribute the response to its source and date. Use “seller reports none,” not “absence verified.” Ask whether alternative evidence addresses the underlying ownership or coverage question.

Should excluded contracts remain in the index?

Retain them where they explain current operations, dependencies, or replacement needs. Mark the exclusion’s source and whether it is proposed or agreed. Link any replacement or transition document without assuming it resolves the gap.

When can the diligence team start using the index?

Once identifiers, source references, statuses, and ownership are reliable, issue a controlled version with explicit limitations. Open gaps need not prevent use, but they should remain visible and assigned rather than being relabeled complete.

Sources

These SEC-filed agreements are negotiated examples, not general law or evidence of market standards.

• Emergent–BTG Stock and Asset Purchase Agreement, Section 2.04: assumed and retained liabilities and related cross-references.
• Matthews–Duravant Equity Purchase Agreement, Section 5.5(e): qualified treatment of consent and separation failures.
• Seres–Nestlé Transition Services Agreement, Schedule of Services: service descriptions and dependencies.

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.