How to organize a legal due diligence document index for Asset Purchase Transactions

A buyer’s asset-purchase diligence index should connect each document to the assets being acquired, the entity that owns or uses them, and the evidence needed to assess transfer and operational continuity. Start with the acquisition perimeter, assign stable document IDs, preserve versions, and link amendments and related instruments. Reconcile those records against diligence requests and purchase schedules. The deliverable is a controlled map of received and missing materials—not legal clearance—that lets reviewers retrieve evidence, identify gaps, and assign targeted follow-up.

When to use this workflow

Use this workflow when buyer’s counsel or an in-house legal team begins receiving asset-acquisition materials, inherits an unreliable data-room index, or must reconcile a changing acquisition perimeter before signing. It is particularly useful where contracts, systems, facilities, or employees support both purchased and retained operations.

The index organizes evidence. Findings trackers, consent analyses, and closing checklists should refer back to its stable IDs rather than duplicate its records.

This guide assumes US practice and provides workflow recommendations, not advice on a particular transaction. Governing law, asset location, seller organization, and industry determine the separate legal analysis. Do not treat an index category such as “excluded liabilities” as a conclusion about buyer exposure.

What you need

Collect the current draft asset purchase agreement (APA), purchase and exclusion schedules, diligence request list, seller entity chart, and buyer operating plan. The operating plan helps identify shared services or facility rights absent from the proposed asset list.

Obtain the data-room listing, source files, available upload history, seller responses, and custodian contacts. Include ownership records, leases, intellectual property instruments, customer and supplier contracts, permits, lien information, environmental materials, and shared-service arrangements. Identify applicable access restrictions before circulating employee or other sensitive records.

Check the actual access protocol before requesting information or contacting personnel. The Sensata–Cypress APA, §5.1, for example, limits required information creation and requires prior written seller consent for unilateral employee contact. These are negotiated provisions, not rights created by a diligence request list.

Use the template

Use the Asset Purchase Transactions — Diligence document index below. You can copy this table into your working document or spreadsheet. Keep one row per received file version or specifically identified missing document. Track broad unanswered questions against their request numbers rather than inventing document records.

Assign received-document IDs such as D-001 and gap IDs such as G-001. When a missing document arrives, assign a document ID and cross-reference the gap; preserve its resolution history.

“Request / APA link” identifies the request and relevant APA clause or schedule, including draft version. “Entity / asset” records the named owner, contracting party, or user and the asset category. Describe the entity’s role; do not infer ownership from a division name.

Record the document’s stated date separately from receipt metadata in a linked intake log. Execution status describes what is visible—such as signed blocks or missing signature pages—not enforceability. Use a controlled repository reference and page or clause citation. The last two columns hold document-family links, specific gaps, reviewer, status, and next action; keep extended legal analysis in a linked findings record.

Step by step

1. Define the acquisition perimeter before classifying files

Read purchased assets alongside excluded assets, assumed liabilities, and the buyer’s operating plan. Establish deal-specific categories, such as equipment, inventory, customer contracts, facility rights, intellectual property, permits, records, and shared services.

Do not rely solely on folder names. An “IT” contract may support both businesses, while a facility lease may name a retained affiliate. For equipment, connect records to serial numbers or asset-register references where available; descriptions alone may not distinguish similar machines.

Record the entity role, asset category, and current APA schedule reference. Mark “perimeter unresolved” where source documents and schedules conflict, and assign the question to buyer’s counsel.

2. Establish stable IDs and preserve the intake record

Give each received file version an immutable ID independent of its filename or folder position. Preserve the original file and record its source and receipt date. Keep renamed working copies traceable to that original.

For duplicate uploads, compare content, attachments, and signatures before designating a reference copy. Retain alternate locations. Distinguish a replacement from a duplicate, and never overwrite an earlier version used for review.

Complete the document title, stated date, location, version, and execution fields. Flag illegible scans, password-protected files, and inaccessible attachments. Record restricted access in the repository or linked intake log so retrieval problems are not mistaken for missing evidence.

3. Assemble document families and identify missing components

Link principal agreements to amendments, schedules, exhibits, side letters, assignments, guarantees, and termination notices. Give separately supplied files their own IDs. For an instrument embedded in a larger PDF, cite the parent ID and page range.

Use internal references to identify missing components. A reference to a pricing schedule does not establish its contents. Distinguish “referenced but not supplied,” “seller reports no document,” and “not yet reviewed.”

Record family relationships in “Links / evidence gap.” Create a gap row for each material missing instrument, cite the document that refers to it, and request confirmation of the complete document family—not merely another copy of the principal agreement.

4. Connect evidence to transfer and liability questions

For each material asset, identify what the source supports: ownership, permitted use, an obligation, or a transfer restriction. Cite the relevant text and distinguish a factual observation from counsel’s interpretation.

The Ellie Mae–AllRegs APA, §§1.3–1.4, illustrates why timing matters: it separates specified post-closing assigned-contract obligations from excluded earlier obligations and breaches, with separate treatment for later-transferred contracts. This is contractual allocation between those parties, not authority that third-party claims disappear.

Record available ownership, consent, notice, release, and transfer evidence. Link disputed interpretation to a findings record. Keep document receipt, review completion, and resolution of the transfer question separate.

5. Route special transfer evidence to the appropriate reviewer

Identify records requiring specialist input, including government contracts, permits, real property rights, and licensed intellectual property. Ask the responsible reviewer to specify the evidence needed rather than applying a generic private-contract consent checklist.

For federal contracts, FAR 42.1204(a), (e)–(g) addresses discretionary government recognition of a successor after specified asset transfers and supporting documentation. Recognition is not automatic. Have government-contracts counsel confirm applicable agency deviations and contract-specific requirements.

Record the specialist, underlying contract ID, and precise evidence request. A generic uploaded consent form should not resolve the issue. This step locates and routes evidence; the specialist makes the substantive assessment separately.

6. Reconcile requests, schedules, and seller responses

Compare the index in both directions. Check each material scheduled asset against available evidence, then examine indexed documents for assets or operating dependencies omitted from the schedules. Identify both unsupported schedule entries and documents outside the proposed perimeter.

Reconcile each request to received evidence, an identified gap, an attributable negative response, or an agreed withdrawal. Preserve the source and date of seller responses. “No responsive documents exist” differs from “documents cannot be located,” especially for ownership and amendment history.

Record discrepancies, owners, and next actions. Cross-reference a file answering several requests rather than duplicating its record. Escalate perimeter changes for legal and business confirmation.

7. Issue a controlled review snapshot

Test retrieval of material files and verify that citations match the recorded versions. Identify the APA and schedule versions used for reconciliation. State the intake cutoff and distinguish later uploads awaiting processing.

Give every open gap an owner and next action. Preserve resolved gaps with the responsive document ID and resolution basis. An internal follow-up date is a team instruction, not a contractual deadline unless supported by the operative language.

Circulate a dated index snapshot with a short summary of material evidence gaps. Preserve subsequent changes so reviewers can determine which evidence was available for an earlier decision.

Worked example

Fictional scenario: Alder Quay Components LLC proposes to acquire packaging equipment, selected customer contracts, and related operating assets from Briar Vale Manufacturing Inc. Briar Vale retains its distribution business. The buyer plans to use the existing production space and production-planning software.

APA v3 lists the software as purchased property, but the uploaded license names Briar Vale Systems LLC, a seller affiliate. All parties, documents, dates, and clause descriptions in this example are fictional. Transfer analysis remains open.

These entries change the review priorities. The equipment list becomes a starting point for title inquiries. The customer agreement requires its missing service schedule before counsel can assess the associated obligations. The software record raises a perimeter question: whether the buyer needs transferred rights, a new license, or another arrangement.

No source establishes the missing service scope or software permissions. Facility rights also remain a separate request; the software license cannot answer that question. The team sends targeted requests and links subsequent evidence to these records instead of marking whole folders complete.

Common mistakes

• Using filenames as identifiers. Renaming breaks references. Assign stable IDs and preserve source locations and versions.
• Treating schedules as ownership evidence. Listed assets may be leased, licensed, or affiliate-owned. Link supporting records and state uncertainty.
• Indexing only principal agreements. Missing schedules obscure rights and obligations. Build document families from internal references.
• Equating absence with a negative response. An empty folder establishes little. Obtain an attributable response and distinguish unavailable records from reported nonexistence.
• Marking receipt as clearance. An unsigned release or draft consent does not establish completion. Describe the file and link the separate substantive review.

Final quality check

• Each material purchased asset has evidence or an assigned gap.
• Entity roles distinguish seller, affiliate, owner, contracting party, and licensee.
• Source files are retrievable and citations match recorded versions.
• Amendments, schedules, and replacements link to preserved predecessors.
• Receipt, execution, and legal-review statuses remain distinct.
• Requests and current purchase schedules reconcile in both directions.
• Open issues have owners; resolved gaps identify evidence; the snapshot states its intake cutoff.

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 that support to build the evidence map while counsel verifies sources, entities, versions, and acquisition boundaries. The index remains your team’s work product. To discuss this buyer-side workflow, book a demo.

Frequently asked questions

Should excluded-asset documents appear in the index?

Yes, where they establish the acquisition boundary or a shared dependency. Label their relevance without classifying them as purchased assets.

How should we index one contract covering both businesses?

Keep one source record linked to both categories. Cite scope provisions and assign the separation question; do not assume the contract can be divided.

What if the seller replaces a file after review?

Create a new version record, link its predecessor, and flag dependent findings for reconsideration. Preserve both versions and their review history.

Can we call the index complete with missing documents?

Describe it as an intake snapshot through a stated cutoff, with gaps disclosed. Indexing completion does not establish diligence completion; material gaps need an assigned disposition.

Sources

• Sensata–Cypress Asset Purchase Agreement, §5.1: negotiated information-access restrictions.
• Ellie Mae–AllRegs Asset Purchase Agreement, §§1.3–1.4: contractual liability allocation and transfer timing.
• FAR 42.1204: federal successor recognition and supporting documentation.

Filed agreements illustrate specific drafting choices, not general law or market standards.

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.