How to organize a legal due diligence document index for Private Company Acquisitions

Organize a buyer-side diligence index around stable document IDs, the target’s legal entities, and the acquisition structure—not the seller’s folder names alone. Record each document’s source, version, execution status, and relationship to amendments, schedules, and outstanding requests. Verify those records against the files, then assign unresolved gaps and specialist review. The deliverable is a dated, traceable inventory that supports diligence findings and identifies missing evidence without treating document receipt, apparent execution, or seller assurances as legal clearance.

When to use this workflow

Use this workflow when buyer’s counsel or an in-house acquisition team receives an initial data-room population, inherits inconsistent diligence folders, or reconciles supplemental uploads before issuing a report. Keep the task focused on identifying, connecting, and routing evidence; substantive findings belong in a linked findings tracker.

The acquisition form should shape the index. For a stock purchase, emphasize ownership records, acquired subsidiaries, and contracts potentially affected by a control change. For an asset purchase, distinguish transferred assets and contracts from excluded items and shared arrangements. For a merger, separately identify organizational records, approval evidence, and merger documents.

This is a general US legal-workflow guide. Entity type, governing law, industry, transaction structure, and actual contract language determine the substantive review. The Delaware merger example below is not an approval checklist for stock purchases, asset purchases, or LLC transactions.

What you need

Start with the proposed acquisition perimeter: entities, subsidiaries, business lines, assets, and exclusions. Obtain the structure chart and current transaction draft or term sheet, noting unresolved structural assumptions.

Collect the seller’s request responses, data-room listing, available files, and prior upload lists. Retain the buyer’s request list with request IDs, custodians, priorities, and requested periods. A response saying “uploaded” must be reconciled to an identifiable file.

Also assemble:

• Exact entity names, former names, and jurisdictions of organization.
• Available agreements, amendments, schedules, exhibits, side letters, and translations.
• Relevant ownership records, organizational documents, permits, and asset schedules.
• Named reviewers for corporate, commercial, employment, IP, tax, regulatory, and other applicable workstreams.
• Access restrictions and handling instructions for sensitive or potentially privileged material.
• A naming convention and one person responsible for index integrity.

Do not wait for complete production. Build the index from available evidence and label the gaps.

Use the template

Use the Private Company Acquisitions — Diligence document index below. You can copy this table into your working document or spreadsheet; no separate download is required.

Assign a stable document ID, such as D-001, independently of seller folder numbers. Include the associated request ID, such as R-014. Use a separate prefix, such as G-001, for requested documents not received. When evidence arrives, link the gap record to the new document record and retain the resolution history.

“Entity / scope” identifies the legal entity and whether the document concerns the acquired business, an exclusion, or a shared arrangement. “Document / dates” distinguishes the stated agreement date from an effective date when necessary. “Source / citation” holds the original filename, data-room path or other source, receipt date, and clause, page, or spreadsheet-cell reference. Retain the captured path if the room changes.

“Version / execution” distinguishes drafts, apparently signed copies, incomplete signature sets, and superseded copies. “Related IDs” connects document families and duplicate uploads. “Review / gaps” records coverage, completeness, review status, uncertainty, and linked findings—not a legal clearance conclusion. Give each open action a named owner and target date. Use consistent labels within these fields so the table remains sortable.

Step by step

1. Define the acquisition perimeter and index categories

Translate the transaction structure into categories before importing the room listing. Separate target entities from seller affiliates, transferred assets from excluded assets, and target contracts from shared services. Mark uncertain perimeter decisions rather than silently assigning them.

For a Delaware domestic-corporation merger, DGCL § 251(b) requires each constituent corporation’s board to approve the merger agreement and declare its advisability. Section 251(c) addresses stockholder adoption and filing the agreement or a certificate of merger, subject to statutory exceptions and alternative procedures. See DGCL § 251(b)–(c). This supports a distinct approval-evidence category for that structure, not every acquisition. (delcode.delaware.gov)

Record: entity, perimeter classification, document category, and the owner of unresolved structural questions.

2. Register source files without rewriting their history

Capture the original filename, source location, and receipt date before applying buyer-facing descriptions. Assign a stable ID to each distinct document record. Do not use spreadsheet row numbers: sorting should not break citations in the diligence report.

Retain the source copy under the team’s access and retention procedures. Compare apparently identical uploads before marking them as duplicates; similar filenames are insufficient. If one PDF contains several agreements, create separately citable records with page ranges linked to the same file. Identify unreadable or incomplete scans before routing them for substantive review.

Record: document and request IDs, original source path, receipt date, page range, and any file-quality limitation.

3. Confirm parties, dates, and execution evidence

Read the document itself to identify parties, title, stated date, and signatures. A “Target contracts” folder may contain a seller-affiliate agreement. Flag that mismatch for perimeter review rather than assuming the target owns the relationship.

Keep agreement dates, signature dates, and effective dates distinct where they differ. A signature page does not establish that all counterparts, schedules, or referenced attachments are present. Describe observable evidence: “apparently signed; one counterpart absent” is more useful than an unsupported “executed.” Do not infer effectiveness or enforceability from signatures alone.

For ownership records, distinguish a seller-created capitalization summary from the underlying ledger and supporting issuance or transfer documents requested by corporate counsel.

Record: exact parties, relevant dates, supported execution description, and missing components.

4. Build document families and preserve hierarchy

Connect each base agreement to amendments, schedules, exhibits, side letters, and translations. Make links reciprocal so reviewers can navigate from an amendment to its base agreement. Preserve superseded versions and identify the copy currently assigned for review. Do not assume that a translation is controlling or that an amendment replaces provisions it does not address.

Document precedence requires the actual wording. For example, § 13.11 of the Molina–Bright Health stock purchase agreement incorporates schedules and related agreements but gives the agreement body precedence over inconsistent provisions, except expressly stated disclosure exceptions. That is a drafting example, not a general rule for acquisitions. (sec.gov)

Record: related IDs, amendment sequence, relevant hierarchy clause, and absent family members.

5. Reconcile production against requests and responses

Compare each request with the evidence received, including its entities, periods, and requested attachments. A request for customer agreements and all amendments remains incomplete when only base agreements appear. A parent-company license does not answer a request for a target-held license without further assessment.

Use distinct statuses: not produced, seller says unavailable, seller confirms none exists, partial production, and buyer review pending. Preserve who supplied a response, when, and where it can be found. A seller confirmation establishes what the seller represented; it does not independently establish completeness.

Identify whether the next action seeks a missing file, an explanation, or confirmation of scope. Avoid repeatedly requesting an item without acknowledging the seller’s existing response.

Record: request coverage, gap description, response source, follow-up owner, and target date.

6. Route review while separating evidence from conclusions

Assign reviewers by subject, entity, and priority. First route records whose identity or completeness affects key acquisition assumptions: ownership evidence, principal revenue contracts, essential permits, or arrangements held outside the target group.

For commercial review, identify assignment and control-change language separately. Do not mark consent “required” because the seller used a consent folder. The reviewer must assess the underlying language, applicable law, and proposed structure.

Keep receipt, completeness verification, substantive review, and issue resolution distinct. Use a concise evidence note in the index and link substantive analysis to the findings tracker. Where access is restricted, identify the authorized reviewer without reproducing restricted content in a broadly shared table.

Record: named reviewer, priority, review status, uncertainty, and finding ID where applicable.

7. Reconcile updates and preserve a dated baseline

At an agreed review checkpoint, compare new uploads with the index. Classify each as new, supplemental, duplicate, or replacement. Do not overwrite a draft record with an apparently signed copy and leave its earlier description unchanged.

Ask reviewers to identify the version reviewed and whether later materials affect their findings. Preserve a dated index baseline showing its acquisition perimeter and unresolved gaps. Subsequent uploads should be distinguishable updates, with affected reviewers notified through the team’s agreed process.

Confirm that source links remain accessible to intended recipients. A baseline should explain what evidence supported the report, not imply that production is complete.

Record: version relationships, affected review assignments, outstanding actions, and baseline date.

Worked example

Fictional scenario: Valecrest Acquisition LLC proposes to buy all shares of Cedarline Instruments, Inc., which owns Cedarline Service LLC. At an October 8, 2026 review checkpoint, the seller has uploaded a customer agreement, an amendment, and an ownership spreadsheet. Counsel needs a reliable inventory before completing commercial and corporate review.

All parties, documents, dates, and clause descriptions below are fictional. These are three representative entries; referenced gap records sit elsewhere in the full index.

The family links change the review decision. Counsel cannot treat D-021 as a complete pricing record: Schedule B is absent, and D-022 purports to replace pricing without execution evidence. The appropriate next step is a focused request and assessment of operative status—not acceptance of the newest upload as controlling.

D-037 establishes that a holder list was produced, not that ownership has been verified. Corporate counsel receives a defined reconciliation task. The subsidiary remains within the overall diligence perimeter, but these three entries do not establish production of its records. No missing schedule, signature, ledger content, or subsidiary evidence is inferred.

Common mistakes

• Mirroring folders instead of checking entities. Read the named parties and flag seller-affiliate or shared arrangements separately.
• Treating the newest upload as operative. Compare dates, signatures, and amendment language; preserve earlier copies and explain the relationship.
• Closing a request when one file arrives. Check requested entities, periods, schedules, and amendments before marking coverage complete.
• Calling every unresolved item “missing.” Separate absent files, unavailable records, nonexistence confirmations, and pending review.
• Conflating signatures with clearance. Verify document-family completeness and route legal significance to counsel; apparent execution does not resolve the issue.

Final quality check

Before circulating the index, confirm that:

• Every received-document ID resolves to a source file or an explained access restriction.
• Entity names and perimeter classifications match inspected evidence.
• Dates and execution descriptions come from the documents, not filenames.
• Amendments, attachments, duplicates, and superseded copies have reciprocal links.
• Clause, page, and spreadsheet-cell references match the cited version.
• Request coverage distinguishes production gaps from pending legal review.
• Open actions are resolved with evidence or assigned to named owners with target dates.
• The baseline identifies its date, scope, and distinguishable later updates.

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, while contract review supports review of indexed agreements. The index remains the team’s work product; counsel verifies identity, relationships, completeness, and legal significance. To discuss these capabilities for buyer-side diligence, book a demo.

Frequently asked questions

Should unproduced documents appear in the index?

Yes, as clearly marked gap records linked to request IDs. Do not supply a file path or execution status as though evidence exists. When production arrives, link the new document record to the gap and preserve its resolution history.

Should every amendment have its own row?

Generally, give each distinct amendment an independently citable record. If it shares a PDF with the base agreement, use separate page ranges and reciprocal links. Keep the source file intact.

How should restricted documents appear?

Include only permitted identifying information, the custodian, access restriction, and authorized reviewer. Do not copy sensitive content into the general index. Record substantive review only when the assigned reviewer confirms its scope and status.

When is the index ready to support the diligence report?

When material source references are verified, document families are mapped, and unresolved gaps have explicit owners and report treatment. Complete production is not necessary to issue a qualified report, but the index’s scope and limitations must not contradict its conclusions.

Sources

• Delaware General Corporation Law, § 251(b)–(c) — Delaware domestic-corporation merger approval and filing provisions, subject to exceptions and alternative procedures.
• Molina–Bright Health stock purchase agreement, June 29, 2023, § 13.11 — a negotiated example of incorporation and precedence, not a market standard.

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.