How to organize a legal due diligence document index for Distressed Business Acquisitions

A buyer’s distressed-acquisition diligence index should connect each document to the entity, asset, contract, or asserted interest it concerns, while distinguishing execution, completeness, version, and review status. Start with stable document IDs, preserve amendment and version histories, and prioritize evidence affecting ownership, transferability, and operating continuity. Link missing records and unresolved inconsistencies to named reviewers and specific requests. The resulting deliverable is a traceable inventory that helps counsel retrieve supporting evidence without confusing seller assertions, proposed court relief, and verified facts.

When to use this workflow

Use this workflow when buyer’s counsel receives an incomplete or changing data room before a distressed-acquisition bid or diligence decision. It suits in-house teams coordinating outside counsel, finance, operations, and specialists who need common document references under compressed timelines.

The principal setting is a US federal bankruptcy asset sale. For an out-of-court acquisition, equity purchase, receivership, or state-law foreclosure, retain the indexing method but replace bankruptcy categories with the transaction’s actual transfer and authority records. The statutory sale and assignment mechanisms discussed below concern bankruptcy transactions, not distress generally. See 11 U.S.C. § 363 and 11 U.S.C. § 365. (uscode.house.gov)

The index locates and qualifies evidence; it does not replace a risk register, contract analysis, or closing checklist. Counsel must separately evaluate governing law, controlling decisions, local requirements, and transaction-specific orders.

What you need

Collect the available source population and identify priority requests:

• Data-room listings, access restrictions, available upload histories, and seller diligence responses.
• Draft purchase agreement, disclosure schedules, purchased and excluded asset lists, and assumed-liability definitions.
• Entity charts, ownership records, lien searches with search dates and jurisdictions, financing documents, and financing or cash-collateral orders.
• Critical contracts, amendments, incorporated schedules, default notices, cure schedules, permits, and supplier records.
• Liquidity forecasts and operational information identifying immediate interruption risks.
• For bankruptcy sales, relevant motions, exhibits, proposed and entered orders, objections, notices, and available service evidence.

Identify the buyer’s deal lead and specialist reviewers. Establish a review cutoff and secure repository. Register records received outside the data room, including management emails and attachments. Preserve the email when its assertions matter; an attachment alone may not identify who supplied a cure estimate or ownership explanation.

Use the template

Use the Distressed Business Acquisitions — Diligence document index below. You can copy this table into your working document or spreadsheet. Maintain one row per distinct document or version. Give separately reviewable attachments their own IDs and link them to their parent record.

Doc ID is permanent, not a spreadsheet row number. Reserve a separate prefix, such as REQ, for requested but unreceived documents. Entity / asset identifies the named entity and affected business component without assuming ownership merely from folder location.

Record / version captures the title, document date, version, and receipt date. Source / pinpoint provides a stable repository reference plus clause, page, docket, or paragraph citations. For an unreceived document, state “not received”; cite the record establishing why it is expected, if available.

Status / links should use separate labels within the cell: execution, completeness, version, and review. An executed contract may be missing exhibits; a reviewed order may still be only proposed. Link related document IDs and substantive issue references.

Priority / basis explains the decision or operational dependency. Gap / action states missing evidence and the next request. Owner / review names an accountable reviewer and review date or target. These grouped columns keep the table compact; split them into separate spreadsheet fields if sorting requires it.

Step by step

1. Define the acquisition perimeter and indexing rules

Begin with proposed purchased assets and seller entities, not data-room folder labels. A “Group Contracts” folder may contain an affiliate agreement outside the deal. Map entity names, facilities, business units, and critical assets to consistent tags, retaining original names in the source description.

Agree on ID conventions, status labels, and responsibility for uncertain ownership. Distinguish document, receipt, and review dates. Use “entity unconfirmed” where the source does not establish the relevant party.

Record in the template: permanent ID, entity and asset tags, and any perimeter question requiring reconciliation with the purchase agreement or schedules.

2. Register sources without overwriting history

Inventory the initial delivery and retain a dated folder listing. Assign IDs before substantive review. Compare apparent duplicates: identical filenames may conceal changed schedules, signatures, or attachments. If copies are identical, retain one review record and note the other locations.

Keep superseded versions under separate IDs and link replacements. Register missing records as request entries rather than documents received. When a requested record arrives, give it a document ID and cross-reference the request; do not erase the request history.

Record in the template: source location, version, receipt date, predecessor or duplicate IDs, and access problems. Distinguish corrupt files, inaccessible links, and missing pages from substantive legal uncertainties.

3. Classify records by the buyer’s immediate decisions

Classify by document type and decision relevance. Ownership records support the asset perimeter; financing records identify asserted collateral coverage; supplier contracts address continuity; cash forecasts help prioritize time-sensitive requests. A document may support several decisions.

Prioritize evidence whose absence prevents testing a bid assumption or assessing continued operations. Include permits needed for a facility’s expected use, but do not infer transferability from possession of a permit. Avoid marking the entire room urgent.

Record in the template: category within the record description, priority with factual basis, and assigned reviewer. “Urgent—sole identified storage facility; lease amendment missing” gives the reviewer a concrete task rather than an unexplained materiality label.

4. Connect ownership and encumbrance evidence

Link material assets to ownership evidence, lien searches, security documents, asserted claims, and requested treatment. Preserve differences in serial numbers, legal descriptions, debtor names, or collateral schedules. A search result and a security agreement answer different questions; neither should silently substitute for the other.

In bankruptcy, section 363(f) permits a free-and-clear sale only if at least one of five statutory alternatives applies. Whether an asserted claim qualifies as an interest and satisfies an alternative requires legal and factual analysis. Do not tag an asset “clean” merely because the proposed order requests that result. See 11 U.S.C. § 363(f). (uscode.house.gov)

Record in the template: related ownership and security-document IDs, conflicting descriptions, and required reconciliation evidence. Link counsel’s treatment analysis separately from intake facts.

5. Build complete contract and cure document chains

For critical contracts, connect the base agreement, amendments, schedules, guarantees, default notices, cure records, and assignment materials. Confirm the contracting entity and facility. Preserve seller summaries as separate sources, not replacements for contract text.

For executory contracts and unexpired leases, section 365(b)(1) generally conditions assumption after default on cure or adequate assurance of prompt cure, compensation or assurance of compensation for resulting actual pecuniary loss, and adequate assurance of future performance, subject to exceptions. See 11 U.S.C. § 365(b). (uscode.house.gov)

Section 365(f)(2) requires assumption and adequate assurance of the assignee’s future performance; section 365(c) restricts assumption or assignment in specified circumstances. Contract type, applicable law, consent, and controlling interpretation matter. See 11 U.S.C. § 365(c), (f). (uscode.house.gov)

Record in the template: amendment-chain IDs, assignment and default pinpoints, missing exhibits, and cure-figure provenance. Link the purchase agreement provision allocating cure responsibility; do not infer allocation from a seller estimate.

6. Separate requested court relief from entered relief

Create distinct entries for motions, proposed orders, entered orders, objections, and service records. Verify an order’s entry against the docket; link the operative order to its motion and exhibits. Capture case identification, docket number, entry date, and relevant paragraphs.

Rule 6004(c) requires a free-and-clear sale motion to comply with Rule 9014 and be served on lienholders or other interest holders; the notice must identify hearing and objection timing. Indexing service materials does not establish compliant service. See Federal Rules of Bankruptcy Procedure, Rule 6004(c). (uscourts.gov)

Rules 6004(h) and 6006(d) generally impose 14-day stays after entry for covered property-use, sale, or lease orders and section 365(f) assignment orders, unless the court orders otherwise. Rule 6004(h) excludes cash collateral. Check actual orders and separate appellate stays. See Rules 6004(h) and 6006(d). (uscourts.gov)

Record in the template: proposed or entered status, docket evidence, operative pinpoints, and assigned procedural questions. “Entered” is not closing clearance.

7. Reconcile gaps and issue a controlled handoff

Compare the index against purchase agreement schedules and priority requests in both directions. Each scheduled critical asset or contract needs supporting records or an explicit gap; each critical document needs a perimeter link or exclusion question.

Resolve orphaned amendments, inconsistent entity tags, and unsupported completion labels. Circulate a dated baseline with its review cutoff and open-item owners. Register later changes against that baseline and notify affected reviewers when new evidence changes a priority record.

Record in the template: review status, unresolved action, owner, target, and linked issue reference. State what was examined and what remains unavailable without implying that completing the inventory resolves substantive risk.

Worked example

Fictional scenario: Alder Basin Components LLC proposes to acquire selected manufacturing assets from Juniper Forge Inc. through a bankruptcy sale. Immediate furnace-line operation depends on equipment access and warehouse storage. The room contains an executed security agreement, an executed warehouse lease missing a referenced amendment, and a proposed sale order.

A management email asserts that the furnace lien will disappear and estimates lease cure at $48,000. The team registers that email as DBA-008. No entered order, lien search, missing amendment, or counterparty cure support has been supplied. All parties, records, amounts, and references below are fictional.

The index changes the buyer’s position from presumed readiness to defined evidence dependencies. The security agreement identifies asserted collateral but does not resolve ownership or current lien treatment. The missing amendment prevents a complete lease review, while the email establishes only the estimate’s provenance. The proposed order shows requested relief, not granted protection.

Counsel should flag these dependencies to the bid decision owner rather than declare the acquisition unworkable or ready. An entered order, if later received, gets a new ID linked to DBA-031; the proposed version remains retrievable.

Common mistakes

• Using folder location as ownership evidence. Check the named entity and asset description; flag affiliate records outside the perimeter.
• Treating the newest upload as controlling. Compare execution, amendments, dates, and provenance before assigning current status.
• Counting requests as received documents. Use separate request IDs and “not received” status; link the eventual document.
• Recording estimates as established cure amounts. Identify the speaker and supporting records; preserve disputed figures separately.
• Equating proposed relief with protection. Preserve proposals and entered orders separately; verify operative coverage and procedural dependencies.

Final quality check

• Stable IDs remain unchanged after sorting, and received-document links open for authorized reviewers.
• Entity and asset tags match the proposed perimeter or identify discrepancies.
• Execution, completeness, version, and review status are checked separately.
• Critical contract chains include amendments, exhibits, and explicit missing-record entries.
• Ownership and encumbrance evidence is connected without unsupported clearance conclusions.
• Court records distinguish proposed relief, entered relief, and procedural questions.
• Pinpoints have been verified against source documents, and material open issues are resolved or assigned with a next action and target.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its due diligence capabilities for bulk document classification to organize records and prioritize human review. Tabular review supports work across multiple documents, while contract review supports examination of indexed agreements. Keep the index as the team’s work product and retain lawyer verification of ownership, transferability, and court-order treatment. To discuss this workflow, book a demo.

Frequently asked questions

Should the index include documents not yet received?

Yes, as clearly labeled request entries with separate IDs. Identify the expected record, affected asset, request owner, and decision dependency. Do not assign a fictitious source location or imply review occurred.

Can one row cover an entire contract family?

Use a parent entry for navigation, but give independently reviewable amendments, guarantees, and notices separate IDs. Link them so reviewers can identify both the controlling text and missing components.

How should late uploads be handled before a bid?

Register receipt, compare prior versions, and flag affected priority entries. Ask the responsible reviewer whether the new evidence changes a bid assumption. Preserve the earlier baseline and record the change rather than silently replacing it.

Is the document index also a closing checklist?

No. It supplies evidence to that checklist. Link relevant records, but leave condition satisfaction, waiver authority, and closing decisions in the appropriate work product. Document receipt alone does not establish substantive readiness.

Sources

• 11 U.S.C. § 363 — conditional bankruptcy authority for sales free and clear of interests.
• 11 U.S.C. § 365 — assumption, cure, assignment, and statutory limitations.
• Federal Rules of Bankruptcy Procedure — Rules 6004 and 6006 governing relevant sale and assignment procedure.

Scope: General buyer-side workflow guidance, with an October 13, 2026 research cutoff; not advice 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.