How to organize a legal due diligence document index for Business Merger Transactions

An acquirer’s diligence document index should connect each source file to the target entity, diligence request, document family, and responsible reviewer. Preserve original file information, distinguish executed instruments from drafts, and record missing amendments or schedules without treating an upload as a complete response. The deliverable is a controlled inventory that lets counsel locate the evidence behind a merger diligence conclusion, identify incomplete production, and route follow-up requests. It supports—but does not replace—the findings tracker, approvals analysis, or closing checklist.

When to use this workflow

Use this workflow when the target opens its data room, supplemental production becomes difficult to reconcile, or the acquirer changes counsel or specialist reviewers. Corporate counsel should own the index structure; tax, employment, benefits, IP, and regulatory specialists should receive assigned records rather than maintain disconnected inventories.

The scope is source organization for a US business merger, with Delaware corporations as the corporate-law reference point. Confirm formation jurisdictions, entity types, merger constituents, and proposed survivor before choosing categories. Other jurisdictions, regulated operations, foreign investment, and contractual governing laws require separate analysis. The indexing controls below are practical recommendations, not statutory requirements.

What you need

Start with the current diligence request list, data-room inventory, access restrictions, and proposed transaction structure. Obtain an entity chart identifying legal names, formation jurisdictions, operating subsidiaries, merger constituents, and the expected survivor. Include the merger agreement and disclosure schedules, if available, in the indexed collection.

Collect materials that establish document relationships: capitalization records, equity plans and grants, charter documents, board and stockholder records, credit documents, security instruments, material contracts, IP assignments, permits, disputes, and intercompany arrangements. Request amendments, waivers, exhibits, incorporated terms, and signature pages—not just principal agreements.

Agree on reviewer assignments and status definitions before importing files. Decide who can amend metadata, approve completeness judgments, and reference restricted materials. Access rights may be qualified: the historical Dayforce/Dawn agreement’s §5.05 addresses legal restrictions, sensitive information, and potential privilege loss. That negotiated wording is not a privilege-preservation rule. See the SEC-filed agreement, Annex A, §5.05.

Use the template

Use the Business Merger Transactions — Diligence document index below. You can copy this table into your working document or spreadsheet. Keep one row per distinct source file or identifiable version, connecting related records through the family field.

Keep document IDs immutable. Source / upload preserves the original filename, data-room path, and upload date; distinguish the download date when the upload date is unavailable. Instrument / version records title, document date, version, and execution status. Do not infer execution from a filename.

Use Family / links for parent agreements, amendments, duplicates, and linked findings. Evidence / scope holds page, clause, or workbook-cell references and completeness limits. Status / access distinguishes receipt, family completeness, review progress, and access restrictions; one “complete” label is inadequate. Next action identifies the task and action owner when different from the reviewer.

For larger collections, split grouped fields into separate spreadsheet columns. Use clearly marked request records for missing expected documents, leaving the source-file ID and citation blank. A request reference identifies the gap without implying receipt.

Step by step

1. Define the transaction boundary and categories

Organize around the target group and proposed merger structure, not merely the seller’s folders. Establish categories for corporate authority, capitalization and awards, financing and liens, commercial contracts, IP, personnel, permits, disputes, tax, and regulatory materials. Add categories for business-specific exposures.

Delaware §259(a) provides for constituent corporations’ property and rights to vest in the survivor and their liabilities and duties to attach to it. Do not treat every target subsidiary as a constituent. Statutory succession also does not answer a contract’s consent, notice, or termination questions; review its wording and applicable law. See DGCL §259(a).

Record: request number, affected legal entity, category, and reviewer. Assign uncertain entity attribution for follow-up.

2. Establish a source inventory before renaming anything

Capture the data-room path and original filename before creating working copies. Assign a stable document ID independent of folder position. Preserve the source file and distinguish OCR copies, translations, extracted pages, and annotated versions through linked records.

For bundled PDFs, identify component documents and page ranges under the source ID. A board packet may contain minutes, a draft merger agreement, and unsigned resolutions; one filename does not establish their respective status. If downloading is prohibited, record the permitted retrieval location and limitation rather than circumventing access controls.

Record: source location, upload date or its absence, document ID, component ranges, and derivative-copy relationships.

3. Reconcile uploads against requests

Match every file to its originating request, allowing multiple request references where useful. Perform the reverse check: each request should point to responsive files, an outstanding request, or an affirmative seller response that no responsive document exists.

Do not equate “not uploaded,” “not maintained,” “not applicable,” and “none exists.” Record who supplied the response and where it is preserved. Broad requests such as “all equity documents” need subcategories for plans, individual grants, amendments, and award records before counsel can assess coverage. Reconcile the population as well as individual files.

Record: response status and the precise outstanding component. Preserve the response itself as a source where permitted.

4. Assemble document families and distinguish versions

Connect contracts to amendments, renewals, waivers, side letters, schedules, and incorporated terms. For debt, connect credit agreements with guarantees, security documents, and amendments. For capitalization, link plans and grants without assuming a summary spreadsheet substitutes for underlying instruments.

A later upload may be a duplicate, executed counterpart, or substantive revision. Compare enough content to classify it; do not overwrite the earlier record. Identify the apparent operative version and the reason for selecting it. If separately uploaded signature pages have not been matched to the agreement body, identify that uncertainty.

Record: family relationships, execution evidence, duplicate or superseded links, and missing components. “Latest uploaded” must not mean “operative.”

5. Route merger-specific evidence to the right reviewer

Index corporate approvals by constituent corporation and instrument. DGCL §251(b) requires board approval and a declaration of advisability; §251(c) generally requires adoption by a majority of outstanding stock entitled to vote, subject to exceptions. Counsel must consider the charter, voting classes, structure, and applicable exceptions—not merely whether a resolutions file exists. See DGCL §251(b)–(c).

Keep governmental review materials separate from corporate approvals and counterparty consents. The FTC explains that only certain transactions require HSR notification and that reportable transactions face applicable waiting restrictions. Operative thresholds, exemptions, and timing require separate verification. See the FTC merger-review overview.

Record: specialist assignment, evidence location, access limitations, and unresolved classification. Do not label an indexed filing as regulatory clearance.

6. Verify records against the underlying documents

Open each source supporting a material diligence conclusion. Check parties, dates, signatures, pagination, schedules, and referenced amendments. Verify extracted metadata rather than relying on filenames or automated classification. Distinguish PDF page numbers from printed page numbers when necessary for reliable retrieval.

For material-contract coverage, use the actual deal criteria. The Dayforce/Dawn agreement’s §3.18(a) uses a negotiated Material Contract definition and corresponding disclosure-letter list. It illustrates why reconciliation should follow the applicable agreement, not a universal materiality threshold. See the agreement example, Annex A, §3.18(a).

Record: supporting references, verification status, and links to separate findings. Keep legal interpretation out of inventory status labels.

7. Reconcile updates and issue a controlled snapshot

Compare supplemental production against existing IDs and open requests. Preserve superseded records, identify new substantive material, and notify assigned reviewers of changed evidence. Maintain a dated index snapshot at reporting milestones so the diligence report’s source base remains identifiable.

Before distribution, check unassigned items, inaccessible files, missing family members, and completeness labels unsupported by verification. Review sensitive descriptions as well as source permissions; an index entry may disclose information withheld from its intended recipients. Specify which production cutoff the snapshot covers.

Record: action owner, next action, review status, and snapshot reference. Keep substantive risk analysis in the findings tracker while retaining its source link.

Worked example

Fictional scenario: Alder Quay Holdings proposes to acquire Bracken Meterworks, Inc., a Delaware corporation. Alder’s wholly owned merger subsidiary will merge into Meterworks, which will survive. Meterworks’ operating subsidiary, Bracken Field Services LLC, holds customer contracts but is not a merger constituent. All parties, documents, dates, and provisions below are fictional.

On October 6, 2026, the seller uploads a customer agreement, purported merger approvals, and an equity workbook. The customer agreement references an unavailable amendment. Its consent clause addresses a merger of the contracting party, leaving its relevance to this structure uncertain. The approvals are drafts, and the workbook lacks links to award instruments.

The index changes three decisions. Commercial counsel should not assume a clause addressing the subsidiary’s own merger applies to its parent’s merger; the amendment and full wording remain necessary. Corporate counsel cannot treat draft resolutions as approval evidence. Benefits counsel can organize award populations but cannot verify underlying rights from the workbook alone. These are evidence gaps, not established breaches or failed closing conditions.

Common mistakes

• Using folder location as entity identification. Confirm the contracting party from the source; a subsidiary contract may sit in the parent’s folder.
• Marking a request complete after one upload. Reconcile the requested population and document families, identifying missing components separately.
• Replacing drafts without history. Preserve draft and executed records with their relationship so earlier conclusions can be revisited.
• Treating classification as legal review. A “consent” file may be a request, refusal, or draft. Verify its content and status.
• Combining inventory status with risk acceptance. Receipt is not sufficiency. Accepted commercial risk does not supply missing evidence; link the decision to a separate finding.

Final quality check

• Every indexed source has a stable ID, retrievable location, and preserved original filename.
• Each record identifies the entity and request, or assigns the uncertainty.
• Material families identify amendments, schedules, incorporated terms, and missing components.
• Draft, executed, duplicate, and superseded statuses have documentary support.
• Material conclusions link to verified page, clause, or workbook-cell references.
• Restricted sources and sensitive metadata receive appropriate access treatment.
• Open issues have owners and next actions; resolved gaps identify supporting evidence and reviewer approval.
• The snapshot reconciles to supplemental production and the diligence report’s source references.

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 diligence and prioritize human review. Tabular review supports work across multiple documents, and contract review can support examination of indexed agreements. Counsel remains responsible for verifying classifications, maintaining source relationships, and assessing evidence sufficiency. To discuss this acquirer-side indexing workflow, book a demo.

Frequently asked questions

Should the index follow the seller’s data-room folders?

Preserve paths for retrieval, but organize review by entity, request, and family. Folder changes should not alter IDs or break findings references. Record replacement locations without erasing provenance.

Should missing documents receive index rows?

Use clearly marked request records. Do not imply receipt or invent citations. Distinguish a missing amendment from an affirmative statement that no amendment exists, and preserve the statement.

How should disclosure schedules connect to the index?

Link schedule entries to supporting records. Record unavailable listed agreements as gaps. Route potentially relevant but unlisted contracts to counsel; an inventory discrepancy does not itself establish an inaccurate disclosure.

When is an indexed contract ready for substantive review?

Review can begin before production is complete if its limits remain visible. Identify the apparent operative instrument, execution evidence, amendments, and missing terms. Qualify affected conclusions and assign follow-up rather than delaying all review.

Sources

• Delaware Code, Title 8, §§251 and 259: corporate merger approvals and statutory succession.
• FTC, Premerger Notification and the Merger Review Process: federal HSR overview, not a transaction-specific reportability determination.
• SEC-filed Dayforce/Dawn merger agreement, Annex A: historical negotiated material-contract and access provisions, not market-standard evidence.

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.