How to organize a legal due diligence document index for Corporate Restructuring Transactions

Organize a company-side restructuring diligence index around legal entities and numbered transaction steps, not merely data-room folders. Give each record a stable identifier, connect amendments and schedules, distinguish executed evidence from drafts, and record missing material separately from confirmed nonexistence. The resulting deliverable is a traceable document map showing which records support each proposed merger, transfer, or separation, what evidence remains incomplete, and who must resolve each gap. Keep substantive legal conclusions in linked analyses rather than treating the index as proof that a step can proceed.

When to use this workflow

Use this workflow when the company has a proposed restructuring step plan and documents are arriving from subsidiaries, treasury, operations, HR, and advisers. Concrete triggers include a shared contract serving both retained and transferred businesses, intercompany obligations lacking supporting instruments, or an asset’s proposed destination differing from its recorded owner.

The audience is company legal teams and transaction counsel organizing diligence for out-of-court mergers, asset transfers, and corporate separations. The index supports review; it is not a consent determination, approval analysis, or closing checklist.

This guide uses US practice, with Delaware corporate-law illustrations and a federal procurement overlay. Other entity forms and jurisdictions require separate analysis. Tax, securities, antitrust, foreign-law, and bankruptcy requirements are outside this workflow’s scope. Contract consequences depend on actual wording, governing law, facts, and structure; federal discovery rules are not transactional indexing requirements.

What you need

Start with the current numbered step plan and before-and-after entity charts. Identify their versions: changing a stock transfer to an asset transfer can change the required evidence.

Collect these inputs:

• Entity records: exact legal names, incorporation jurisdictions, ownership ledgers, governing documents, approvals, and proposed survivor or recipient identities.
• Business and asset records: material contracts, title records, IP registrations and licenses, permits, employee arrangements, and shared-service agreements.
• Financial obligations: credit documents, security instruments, guarantees, intercompany notes, and any existing termination or release evidence.
• Document provenance: repository locations, available upload history, custodians, executed copies, amendments, schedules, and incorporated terms.
• Review parameters: transaction perimeter, materiality criteria, reviewer assignments, access restrictions, and questions requiring evidence for each step.

Request supporting records, not just summaries. A business spreadsheet naming a subsidiary as contract owner is a lead; it does not replace the agreement identifying the legal contracting party. Record exclusions expressly so “complete” has a defined scope.

Use the template

Use the Corporate Restructuring Transactions — Diligence document index below. You can copy this table into your working document or spreadsheet. Maintain one row per separately retrievable record and clearly labeled request rows for missing records.

Keep IDs stable when filenames or step numbers change. In Entity / step, distinguish the current holder from the proposed recipient and identify the step-plan version. Family / relationship links master agreements, amendments, schedules, guarantees, and releases through related-record IDs.

In Document / status, record title, document date, execution status, and version. Source / citation contains a retrievable location and relevant clause or page; cite the signature page when execution is the question. Identify both the access restriction and business custodian.

In Reviewer / gap, name the reviewer, record the review date, and use controlled terms: “unreviewed,” “reviewed—gap open,” or “reviewed—complete for scoped purpose.” Describe the missing evidence rather than merely saying “incomplete.” Owner / next action identifies the responsible person and the next verification task.

Use “requested—not received” rather than “none.” Confirmed nonexistence requires a named respondent, confirmation date, and stated search scope. Separate grouped fields into spreadsheet columns if filtering requires it.

Step by step

1. Fix the entity and transaction-step reference set

Assign each entity a short internal reference and each proposed step a number. Preserve exact legal names alongside abbreviations. Identify transferors, recipients, survivors, and affected businesses without inferring legal roles from branding.

Separate proposed sequencing from established facts. If a permit’s intended holder remains unresolved, index it under the existing holder and flag the destination question. A before-and-after chart expresses the proposed structure; supporting ownership records establish the present position.

Record in the template: entity references, affected step numbers, and the dated step-plan version. Map one record to multiple steps rather than creating competing copies.

2. Build the taxonomy around restructuring evidence

Within each step, classify documents into entity authority, ownership and title, financing and liens, commercial contracts, permits, employment, IP, and intercompany arrangements. Include shared-contract and transition-arrangement categories where the business perimeter requires them.

Approval records must match the proposed legal route. DGCL § 251(b) requires constituent boards to approve the merger agreement and declare its advisability; § 251(c) supplies the ordinary stockholder-adoption and filing route. Exceptions and alternative routes must be tested before assigning requirements. This supports requesting route-specific agreements, approvals, and filing evidence—not identical records for every merger. See Delaware Code § 251(b)–(c).

Record in the template: family, scoped review purpose, and any unresolved approval-route question. Request relevant evidence without treating its absence as a legal conclusion.

3. Register documents without losing provenance

Give each received record an ID before substantive review. Retain its original filename and source location. Link to the controlled repository rather than maintaining untracked reviewer copies.

Distinguish duplicate uploads from different versions. Similar filenames may conceal different signature pages, schedules, or handwritten changes. Compare the records before marking either redundant; identify the reviewed copy and preserve materially different versions.

Access restrictions should govern retrieval as well as indexing. Avoid exposing employee information or the substance of potentially privileged advice in a broadly circulated index. Use restricted references where appropriate.

Record in the template: title, date, execution status, source, custodian, access restriction, and version relationship. Mark uncertain dates explicitly; do not substitute upload dates for document dates.

4. Assemble complete document families

Read each principal document’s references to locate amendments, incorporated terms, exhibits, schedules, side letters, guarantees, and termination or release instruments. Give separately stored items their own IDs and connect them to the family.

Family relationships can cross departmental folders. A parent guarantee held by treasury may support a subsidiary’s procurement agreement. An intercompany note may depend on a separate amendment or debt-release instrument relevant to the same transfer.

A missing schedule is not an empty schedule. Request it and explain its purpose—for example, identifying covered facilities or transferred assets. Do not label the family complete merely because the principal agreement is signed.

Record in the template: related-record IDs, relevant references, and missing components. Distinguish partially signed documents from unsigned drafts and fully executed copies.

5. Map evidence to structure without deciding consequences prematurely

Confirm the named party or asset holder and covered operations, then connect the record to the proposed merger, transfer, or separation. Distinguish what the source establishes from what counsel must analyze.

DGCL § 259(a) vests property and rights in the survivor or resulting corporation and attaches constituent liabilities, while preserving creditor rights and liens. That statutory consequence alone does not resolve particular contractual consent or permit questions. Retain those questions for wording-specific and applicable-law analysis. See Delaware Code § 259(a).

For asset dispositions, § 271(a) addresses all-or-substantially-all-asset transactions. Section 271(c) generally dispenses with stockholder approval for transfers to qualifying wholly owned subsidiaries unless the charter provides otherwise. Index charter and ownership evidence; counsel must assess the threshold, subsidiary definition, and relevant exceptions, including § 272. See Delaware Code §§ 271–272.

Record in the template: verified holder, affected step, supporting citation, and a linked legal issue where necessary.

6. Route specialist gaps to accountable owners

Assign gaps to people who can supply evidence or determine scope—not simply to “legal.” Procurement can locate incorporated terms; treasury can identify guarantee records; entity counsel can verify ownership and approval evidence.

For federal contracts, FAR 42.1204(a) permits successor recognition after specified asset transfers when in the Government’s interest. Paragraph (b) makes novation unnecessary for a stock purchase when the contracting party remains legally unchanged, controls the assets, and performs the contract; other ownership-change issues may still require a formal agreement. Paragraphs (e)–(g) address submissions and permitted modifications. Use this framework only for the applicable federal workstream. See FAR 42.1204.

Record in the template: missing item, accountable owner, requested action, and dependency. An uploaded draft does not resolve a question requiring executed evidence or specialist analysis.

7. Reconcile and issue a review-ready snapshot

Reconcile the index against repository contents, custodian responses, and the current step plan. Check both directions: each indexed source must be retrievable, and each in-scope upload must have an entry or explained duplicate relationship.

Label the snapshot with its review cutoff and step-plan version. Summarize outstanding evidence by step and owner. Carry substantive findings into a separate issues tracker using the same source IDs; avoid converting the index into a negotiation memorandum.

Record in the template: scoped review status, reviewer and date, open-gap assignment, and next verification action. Preserve superseded snapshots so later reviewers can identify the evidence available at a decision point.

Worked example

Fictional scenario: Alder Reach Holdings, Inc. proposes transferring a components business from Alder Reach Operations, Inc. to Alder Reach Components, Inc. in Step 2. The step plan describes Components as Operations’ wholly owned subsidiary, but supporting ownership records have not arrived. Step 3 proposes merging another subsidiary into Operations.

Procurement supplies a signed shared supply agreement and amendment. Treasury supplies a signed Holdings guarantee covering Operations’ payment obligations under that agreement. Its fictional § 8 requires a written creditor release to terminate the guarantee. The company wants to assess whether Holdings can exit that exposure. Corporate records contain draft transfer resolutions. All parties, documents, clauses, dates, and repository references below are fictional.

These entries change the readiness assessment without inventing missing evidence. CR-021 does not establish full facility coverage; the assignment clause belongs in a separate consent analysis. CR-034 evidences guarantee exposure, not release, and does not establish that a release is available. CR-047 evidences proposed resolutions, not completed board action or eligibility for a subsidiary-transfer provision.

The team therefore does not mark Step 2’s document set complete. It requests defined evidence and assigns legal questions separately. Schedule B, if received, gets its own ID linked to SF-04 rather than silently replacing CR-021.

Common mistakes

• Using business names as legal parties. Verify party blocks and reconcile discrepancies against entity records.
• Assigning a shared contract entirely to one business. Identify covered operations and allocation schedules before mapping its destination.
• Calling a family complete because the master is signed. Check incorporated terms, amendments, schedules, guarantees, and relevant releases.
• Equating upload status with legal completion. Separate receipt, execution, review, and evidence of effectiveness.
• Deleting superseded records. Preserve version relationships and identify the current reviewed copy, especially after sequencing changes.

Final quality check

• Every in-scope record has a stable ID and working source location.
• Legal names and step references reconcile to the identified chart and plan versions.
• Document dates and execution status are verified from the records.
• Family links identify amendments, schedules, guarantees, and relevant releases.
• Missing records remain distinct from scoped confirmations of nonexistence.
• Source citations support recorded facts; legal conclusions are separately identified.
• Reviewer identities, review dates, and repository access restrictions are recorded.
• Every open issue is resolved with evidence or assigned to an accountable 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 records and prioritize human review; tabular review supports work across multiple documents. Use these capabilities to support the index while counsel verifies entity mappings, document families, and conclusions. The index remains the team’s work product. To discuss a company-side restructuring diligence workflow, book a demo.

Frequently asked questions

Should the index follow folders or transaction steps?

Use entities and steps as the organizing logic; preserve folder locations for retrieval. Map a shared agreement to each affected step without creating competing document copies.

Should missing documents receive IDs?

Yes, label them as request records, not received evidence. When documents arrive, give them document IDs and link them to the request history so the distinction remains visible.

Does the index need the full consent analysis?

No. Record relevant clause citations and link to the analysis. Keep notice, consent, novation, and release questions distinct; avoid an unsupported “transferable” designation.

What happens when the restructuring structure changes?

Retain source IDs, version the step plan, and revisit affected mappings and review scope. Evidence remains identifiable, but its relevance can change when an asset transfer becomes a merger or the recipient changes.

Sources

• Delaware Code, Title 8, §§ 251 and 259: merger approvals and statutory consequences.
• Delaware Code, Title 8, §§ 271–272: specified asset dispositions, subsidiary transfers, and relevant exceptions.
• FAR 42.1204: federal successor recognition and novation submissions.

Scope date: October 13, 2026. This is a general professional workflow guide; check applicable effective-date provisions before relying on live consolidated law for a particular transaction.

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.