How to prepare a document collection checklist for Post-Acquisition Disputes

Prepare the checklist by mapping each disputed acquisition provision to the records, custodians, and systems needed to test it. Separate purchase-price adjustments from indemnity and other claims, then identify the executed deal record, accounting support, knowledge evidence, and notice history for each issue. Record preservation and access risks, retain source and version information, and assign every gap. The deliverable is a collection plan showing what counsel needs, why it matters, where it resides, what has been collected, and what remains unverified—not merely a file inventory.

When to use this workflow

Use this workflow when litigation counsel or an in-house team receives an adjustment objection, indemnity demand, escrow-release dispute, or allegation of inaccurate pre-closing disclosures. Start before integration retires accounting systems, changes email access, or separates records from their custodians.

The scope is collection planning and verification, not a merits determination or production protocol. Read the agreement’s dispute mechanism first: an accountant submission and litigation over representations may require different evidence sets.

This guide uses a US orientation. The cited federal discovery rules concern US district-court litigation, not automatically state litigation, arbitration, or contractual accountant proceedings. Confirm the forum, applicable orders, and agreement before setting boundaries (Federal Rules of Civil Procedure, Rules 1 and 26).

What you need

Assemble these inputs before requesting broad exports:

• Operative documents: executed purchase agreement, amendments, disclosure schedules, exhibits, ancillary agreements, closing certificates, and escrow arrangements.
• Dispute records: demands, objections, responses, notice-delivery evidence, pleadings or proposed allegations, and accountant engagement instructions.
• Financial support: estimated and proposed closing statements, adjustment workbooks, accounting-policy schedules, trial balances, ledger detail, journal entries, and invoices.
• Deal-process evidence: data-room indexes and snapshots, diligence questions and answers, management presentations, disclosure drafts, and relevant negotiations.
• Repository information: seller, target, buyer, and adviser custodians; system owners; retention settings; migration dates; backups; and access restrictions.

Obtain existing preservation instructions and collection histories. Ask whether prior exports converted files, omitted attachments, or lost spreadsheet formulas. Counsel’s working folders may be useful without constituting a complete source collection.

Use the template

The Post-Acquisition Disputes — Document collection checklist links each evidence need to an acquisition issue and a verifiable collection result. You can copy this table into your working document or spreadsheet. Use one row per record category and source; split rows when custodians, access restrictions, or collection methods differ.

“ID” identifies the collection task. Assign separate stable document IDs to received files. “Issue / clause” identifies the theory and agreement section; “Dates / versions” distinguishes business-event dates from file creation and export dates.

Use “Evidence / gap” for status, document IDs, pinpoint citations, and omissions. For spreadsheets, identify the version, sheet, and cells. Link to a collection manifest when source details exceed the available space. “Access / preservation” distinguishes secured records from requested records. The final column requires a responsible person and concrete action, not an unassigned “pending.”

Step by step

1. Define the issues and collection purpose

Separate adjustment, indemnity, direct-breach, and fraud allegations. Identify each disputed fact, relevant provision, potentially adverse evidence, and records needed to evaluate both sides. Do not let an untested theory expand every collection.

In federal litigation, discovery covers nonprivileged matter relevant to claims or defenses and proportional to the case’s needs; discoverability does not require admissibility. Apply that framework when evaluating a broad deal-team collection (Rule 26(b)(1)).

Record: issue-linked rows stating each category’s purpose, initial scope, and provisional assumptions. Identify shared evidence without merging distinct claims or calculations.

2. Establish the authoritative deal record

Collect the signed agreement with incorporated schedules, exhibits, amendments, and side agreements. Compare the closing index against received files. Verify that a schedule labeled “final” accompanied the executed agreement rather than a later compilation.

Read notice and dispute provisions before choosing supporting records. A filed transaction agreement separately addresses direct-claim notice content and representation-claim survival, illustrating why both notice evidence and the operative contractual provisions matter. Its deadlines and prejudice language are deal-specific, not default rules (Cohen–HCMC agreement, §11).

Record: operative clause citations, version provenance, missing attachments, and who can verify the executed set. Refer deadline interpretation to the responsible lawyer rather than deriving it from an example agreement.

3. Map repositories and preservation risks

Interview transaction counsel, the target controller, business leaders, and IT personnel. Ask where diligence answers originated, closing calculations were prepared, and accounting decisions were discussed. Distinguish original repositories from post-migration copies.

Identify seller, target, buyer, and adviser sources separately. Flag disputed access for legal assessment rather than assuming target ownership answers every access question. Coordinate preservation with the responsible legal team before deletion or retirement changes the available evidence. Prioritize threatened sources even while the broader checklist remains under development.

Record: custodian, system, access contact, retention concern, migration history, and whether preservation or collection has been confirmed. An inaccessible repository is not a source searched with no results.

4. Specify dates, versions, and collection instructions

Set issue-specific windows around signing, closing, accounting cutoff, discovery of the alleged problem, and notice delivery. A cutoff dispute may require later invoices; a disclosure dispute may require earlier business communications and intervening disclosure versions.

Request native spreadsheets with formulas and linked inputs when calculations matter. Include message attachments and document families, not favorable excerpts alone. Preserve earlier workbooks where changed assumptions are disputed.

For accountant proceedings, follow the actual submission provisions. One filed agreement calls for the post-closing statement, dispute notice, resolved items, and position statements—an example of why the collection must preserve the procedural record as well as accounting support (Moser–Atlas–Wyatt agreement, §2.06(e)).

Record: date boundaries, required formats and versions, exclusions, and reasons for limitations. Document search methods and unresolved source limitations in the linked manifest.

5. Collect with provenance and trace the figures

Record who supplied each collection, its source system, collection date, method, and known limitations. Keep original collected files separate from annotated working copies. Assign stable IDs before substantive analysis generates competing filenames.

For adjustments, trace estimated, proposed, and disputed figures to native workbooks and ledger entries. Collect the accounting-policy hierarchy, cutoff support, and relevant journal entries. Cross-reference amounts also asserted as indemnity losses without deciding recovery through the checklist.

Federal Evidence Rule 901 requires support that an item is what its proponent claims. Provenance assists foundation work but does not independently establish admissibility (Rule 901).

Record: document IDs, sheet and cell references, source details, reconciliation results, and missing inputs. Distinguish a verified calculation from a figure merely repeated in correspondence.

6. Route sensitive records and test completeness

Identify pre-closing counsel relationships, contractual privilege allocations, mixed legal/business communications, and restricted diligence material. Establish restricted review where access or privilege remains unresolved.

Federal Evidence Rule 501 addresses applicable privilege law, and Rule 502(d) permits federal nonwaiver orders; neither decides ownership of a target’s pre-closing privilege. That question requires transaction-specific analysis (Rules 501–502).

Compare collections with independent reference points: data-room indexes, closing checklists, workbook links, email attachments, and notice enclosures. Distinguish “not collected,” “not located after specified checks,” and “collected but restricted.”

Record: restricted-review routing, missing families, unexplained date gaps, and the reviewer assigned to access or privilege questions. Keep sensitive legal assessments outside broadly circulated collection lists.

7. Close tasks with an explicit completion basis

Review each row with the custodian or system owner. Confirm what was searched, excluded, and delivered, and whether another source could fill a gap. Reconcile promised exports against received material before closing a task.

If collection supports federal document requests, link checklist IDs to a separate response tracker. Rule 34 requires item-specific responses and specific objections, including whether responsive material is withheld on an objection; collection status does not replace that response (Rule 34(b)(2)).

Record: completion basis, limitations, escalation owner, and next review date where needed. Deliver a gap summary separating unavailable evidence, outstanding collections, and material awaiting review.

Worked example

Fictional scenario: Alder Basin Industries acquires Cedar Quay Components. The buyer challenges a $640,000 inventory amount in the closing working-capital statement and alleges that a customer cancellation was omitted from disclosures. The fictional agreement’s §2.7 governs adjustments, §4.12 addresses customer disclosures, and §9.3 addresses claim notices.

The target’s finance system is scheduled for retirement. Counsel has received a PDF closing statement, selected emails, and a standalone notice file, but no native adjustment workbook or complete data-room archive. All parties, provisions, amounts, and document IDs below are fictional; missing evidence remains unverified.

C01 makes preservation more urgent than further PDF analysis. C02 requires both business communications and transaction disclosures: neither alone establishes what was known and disclosed. C03 prevents a standalone notice file from becoming assumed proof of delivery. Counsel must still read §9.3 to determine which delivery facts matter; the table supplies no fictional notice deadline or conclusion on compliance.

Common mistakes

• Collecting only the closing binder. Add issue-linked diligence exchanges, business records, and post-closing calculations.
• Treating a PDF as sufficient accounting support. Seek native formulas, linked inputs, policies, and relevant versions; identify unavailable originals.
• Equating target ownership with unrestricted access. Assign seller, adviser, and pre-closing legal repositories for access and privilege assessment.
• Using one date window for every source. Tailor windows to cutoff, disclosure, knowledge, and notice questions.
• Marking receipt as completion. Reconcile attachments, versions, referenced files, and export limitations before closing the row.

Final quality check

• Every row states an issue and operative clause or factual purpose.
• Executed documents are distinguished from drafts and superseded versions.
• Seller, target, buyer, and adviser sources have separate coverage decisions.
• Accounting entries link to native support or identify missing inputs.
• Document IDs, page citations, and workbook references resolve to the actual source.
• Preservation, access, and privilege questions have responsible reviewers.
• Open gaps have owners and actions; closed rows state their completion basis.
• Legal references match the forum, and illustrative agreements have not supplied assumed terms.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Document review, privilege and confidentiality analysis, and bulk document classification can support organization and prioritization of collected acquisition records. Teams can connect due diligence review with chronology work using the chronology viewer. The checklist remains counsel’s work product, and counsel retains scope, access, privilege, and completeness decisions. To discuss this collection workflow, book a demo.

Frequently asked questions

Should adjustment and indemnity records use separate checklists?

Use distinct issue identifiers within one checklist unless access restrictions require separate files. Cross-reference shared records while preserving separate contractual provisions, calculations, and purposes.

How should we handle a missing data-room snapshot?

Record the gap and seek indexes, upload records, downloaded copies, diligence correspondence, and recipient-held versions. Explain what each substitute establishes; do not treat a current folder as proof of pre-signing availability.

Should we collect every pre-closing lawyer communication?

First identify relevance, sources, counsel relationships, access questions, and review restrictions. Assign privilege questions before broad circulation. Do not make indiscriminate collection or deletion decisions based solely on acquisition ownership.

When is the checklist complete?

When scoped sources are accounted for, received material is validated, and gaps have explicit dispositions. An assigned action alone does not mean collection is complete: unresolved rows should remain open or be closed with counsel’s documented acceptance of the limitation.

Sources

• Federal Rules of Civil Procedure, Rules 1, 26, and 34.
• Federal Rules of Evidence, Rules 501, 502, and 901; applicability is subject to Rule 1101.
• Cohen–HCMC Master Transaction Agreement, §11, illustrative notice and survival wording.
• Moser–Atlas–Wyatt Stock Purchase Agreement, §2.06(e), illustrative adjustment procedure.

Scope: general professional workflow guidance as of October 13, 2026. Transaction rights depend on the actual agreement, governing law, facts, and forum.

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.