Prepare a buyer’s diligence request list by translating the acquisition structure, investment thesis, and known information gaps into specific, answerable requests. Identify the entities, periods, documents, and explanations each request covers; assign priority and responsibility; and explain how the seller should respond. The deliverable is a controlled request register linking unanswered questions to evidence and buyer decisions. Maintain a buyer-only master and a seller-facing version, then refine requests as reviewers identify missing records, conflicting explanations, or changes to the acquisition perimeter.
Use this workflow when buyer’s counsel or an in-house legal team must issue an initial list, tailor an inherited checklist, or supplement requests after new disclosures. Concrete triggers include changing from an asset purchase to an equity purchase, adding a subsidiary, or discovering that a founder—not the target—may own an essential asset.
The scope is preparing, issuing, and refining requests, not completing all diligence or drafting the acquisition agreement. This guide uses a US private-company acquisition orientation as of October 13, 2026. Adapt requests to organizational jurisdictions, operating locations, regulated activities, and deal structure. Contract rights depend on the actual language, governing law, facts, and transaction context; the recommendations below are workflow choices, not universal legal requirements.
Assemble these inputs before drafting:
Ask the deal lead which unknowns could change the acquisition decision, valuation, or proposed terms. Use those answers to order requests rather than treating every category as equally urgent.
The companion template is Private Company Acquisitions — Diligence request list. Copy this table into your working document or spreadsheet. Maintain a buyer-only master; remove internal legal analysis and negotiating positions from the seller-facing version.
| ID | Scope | Request | Priority / need-by | Owners | Access | Response / evidence | Status / next action |
|---|---|---|---|---|---|---|---|
Scope identifies the entity, asset, period, and selection criteria. Request states the documents and any separate explanation sought. Owners names both the seller responder and buyer reviewer. Priority / need-by records a business target date or transaction milestone, not an assumed legal deadline.
Access identifies approved recipients or an unresolved sharing prerequisite. Response / evidence contains the seller’s explanation, document IDs, versions, and clause or page references. Use stable request IDs when referring to spreadsheet cells so sorting does not break the record.
Distinguish not received, partial, received but unreviewed, follow-up required, verified complete, and buyer-deferred. In Status / next action, record the next owner and target, or the decision-maker and reason for deferral. An upload alone is not an adequate response.
Write a scope statement identifying the proposed acquisition and the entities owning relevant assets. Reconcile the organizational chart with management’s account. Ask about founder-owned IP, affiliated property owners, intercompany balances, and shared services outside the perimeter.
For an equity acquisition, prioritize capitalization, equity rights, entity history, and target obligations. For an asset acquisition, identify acquired assets, proposed assumed obligations, transfer documentation, and operational dependencies. Treat historical exposure as a specialist question rather than assuming the structure answers it.
Template output: enter perimeter-confirmation requests, name entities or assets, and assign unresolved ownership boundaries for follow-up.
Create a category map, then tailor individual requests. These are drafting prompts, not instructions to demand every record indiscriminately.
| Category | Requests to consider | Buyer decision supported |
|---|---|---|
| Ownership and governance | Charter documents, equity ledger, grants, shareholder agreements, approvals | Identify sellers, rights, and capitalization |
| Financial, tax, and debt | Accounts, returns, examinations, debt instruments, security records | Direct specialist analysis and debt treatment |
| Commercial arrangements | Selected customer and supplier agreements, amendments, side letters, disputes | Assess revenue continuity and dependencies |
| People and benefits | Workforce census, incentives, benefit plans, employment and contractor terms | Assess retention and compensation questions |
| Technology and IP | Ownership instruments, development contracts, licenses, open-source inventory | Test rights supporting the business |
| Operations and compliance | Leases, permits, claims, insurance, incident records | Identify operational constraints and exposures |
For a private target, reconcile management summaries to underlying records rather than expecting a public-company disclosure package. Assign tax, benefits, environmental, privacy, and regulatory categories to specialists. Require additions and deletions to reflect the target’s business.
Template output: create category-specific rows with an acquisition-specific scope and named reviewer.
Specify the document population, period, entities, and attachments. For selected customer agreements, request executed contracts, amendments, incorporated terms, statements of work, waivers, and material notices. Define selection using agreed revenue concentration or operational-dependence criteria rather than an unexplained monetary cutoff.
Vary the lookback by question. Current agreements may support continuity analysis; historical issuance records may be needed to reconcile ownership. Ask specialists to justify periods instead of imposing one blanket period.
For an IP-dependent target, request instruments supporting its claimed ownership and an explanation of that ownership basis. Under 17 U.S.C. § 204(a), copyright transfers other than by operation of law require a writing signed by the rights owner or authorized agent; the writing may be an instrument of conveyance or a note or memorandum. Accordingly, seek relevant signed development agreements as well as standalone assignments. Do not assume that only a document titled “assignment” can answer the request.
Template output: record bounded requests, separating documents sought from explanations needed.
Separate requests needed for the investment decision from those needed for signing analysis or later confirmation. Elevate essential-asset ownership, concentrated revenue, financing obligations, and business-critical permissions. Record the rationale in the buyer-only master.
Resolve restrictions before requesting sensitive records. For transactions involving competitors or potential competitors, FTC staff guidance recommends limiting competitively sensitive disclosures to the diligence need and transaction stage, using clean teams or other safeguards, and excluding personnel responsible for competitive planning, pricing, or strategy from clean teams. These are context-dependent safeguards, not permission for unrestricted disclosure.
Ask counsel to determine treatment of personal information and potentially privileged materials before production. Where appropriate, begin with a restricted or aggregated response rather than demanding unrestricted upload.
Template output: assign priority, response target, recipients, and any prerequisite access decision.
Review the room index before issuing the list. Map available materials to request IDs, inspect priority documents, and replace duplicates with precise gap questions. A file labelled “customer agreement” does not establish whether amendments or side letters exist.
Separate evidence from inference. “No executed ownership instrument located in the supplied folder” records a gap; “the target does not own the software” requires further analysis.
When records conflict, identify both sources and request reconciliation. For example, cite the equity ledger and management workbook showing different outstanding share counts, then request the underlying issuance or cancellation records.
Template output: add source citations and missing components; mark completion only after the reviewer confirms that the response satisfies the defined request.
Have the deal lead consolidate specialist requests, remove overlap, and approve the seller-facing version. Preserve stable IDs across revisions. State globally applicable entities and periods, retaining exceptions in individual rows.
Ask the seller to respond by ID with document references or an explanation. Distinguish “not applicable,” “no responsive document exists,” “not located,” and “withheld pending access arrangements.” Request the basis for nonproduction and an expected response date where available.
Identify a response coordinator and clarification channel. Keep a dated issuance record with the master so reviewers know which version the seller received; do not overwrite earlier responses silently.
Template output: record response targets and contacts in the rows, scope objections in next actions, and the issued version in the register’s header or version log.
Test whether each response answers the request. Trace references to omitted schedules, guarantees, amendments, assignments, and related entities. State the precise gap and what evidence would satisfy it.
Separate collection from substantive risk resolution. Complete production of a customer agreement can close the collection request while leaving a consent question unresolved in the buyer’s issues register. Cross-reference that issue instead of keeping the collection status ambiguous.
For unavailable evidence, assign a buyer decision: alternative verification, further inquiry, deferral, or escalation. When the perimeter changes, revise affected rows rather than merely adding an unexplained supplemental checklist.
Template output: record verified completion or a focused follow-up, its owner and target, and the buyer decision still blocked.
Fictional scenario: Alder Quay Holdings proposes a $38 million purchase of all shares in Beacon Loom Systems, a private software company. Every party, document, amount, and clause below is fictional.
The buyer values Beacon’s scheduling software and recurring customer relationships. Initial materials include capitalization workbook D-005, customer agreement D-021, developer invoices D-044, and seller email E-007. No signed developer agreement or ownership instrument has been supplied. E-007 asserts repayment of a founder loan, but supporting records are absent.
D-021, §14.2, requires consent for specified control changes; the supplied materials do not establish its complete amendment history or whether the proposed purchase falls within those specified events. Counsel converts three generic requests into targeted inquiries:
| ID | Scope | Request | Priority / need-by | Owners | Access | Response / evidence | Status / next action |
|---|---|---|---|---|---|---|---|
| COM-04 | Beacon; largest customer; current contract set | Supply amendments, waivers, and consent correspondence | High; before signing recommendation | Seller legal / buyer commercial counsel | Counsel | D-021, §14.2, p.18 addresses specified control changes; amendment history unconfirmed | Partial; commercial counsel to obtain full set and analyze applicability |
| IP-03 | Core code; outside developer’s contributions | Supply signed development terms and ownership instruments; explain ownership basis | High; before valuation confirmation | Seller CTO / buyer IP counsel | Restricted IP review | D-044, pp.1–3 contains invoices only; no signed ownership terms supplied | Follow-up; IP counsel to verify claimed rights before proposing remediation |
| FIN-06 | Founder loan and related security | Supply loan terms, repayment records, and applicable releases | High; before debt treatment agreed | Seller CFO / buyer finance counsel | Finance and counsel | E-007 asserts repayment; supporting records absent | Unverified; finance counsel to reconcile assertion with documents and accounts |
COM-04 seeks completeness rather than another copy of D-021. IP-03 allows signed development terms to answer the ownership question, instead of insisting on a standalone assignment. FIN-06 tests the repayment assertion without assuming that security existed or remains outstanding.
The missing evidence changes sequencing: counsel cannot finish the consent, ownership, or debt-treatment recommendation. It does not establish a required consent, defective ownership, or unpaid debt. Each row identifies the evidence needed before that decision.
Before issue or reissue, confirm:
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence workflow supports bulk document classification to organize materials and prioritize human review. For closer agreement analysis, contract review offers clause-quoted findings ranked by severity and linked to text locations, guided by the represented party and deal-specific instructions. Lawyers verify sources and decide which requests to issue; the register remains the team’s work product. Book a demo to discuss the document set and diligence questions.
No single period should govern every category. Seek historical ownership records when needed to reconcile capitalization, while tailoring operational and compliance periods to the question. State exceptions and obtain specialist input.
Request complete agreements and relevant waivers or correspondence. Give the reviewer the proposed structure and ownership changes. Seek evidence for clause analysis rather than accepting an unsupported seller assurance that no consent is required.
Record the seller’s explanation, search undertaken, and whether the record never existed or cannot be located. Consider alternative evidence and assign the unresolved decision. Absence alone is not satisfactory completion.
Issue when scope, priorities, owners, access rules, and instructions are coherent enough for action. Preserve uncertainties as specific requests. A discrete specialist supplement need not hold up unrelated, ready requests.
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.