Prepare a buyer-side asset purchase diligence request list by defining what the buyer will acquire, what it needs to operate, and which liabilities or transfer obstacles require investigation. Convert those questions into evidence requests tied to assets, contracts, locations, and seller entities. Assign priorities, custodians, and response standards, then reconcile each production against the request. The resulting deliverable is a controlled list that distinguishes reviewed responses from missing evidence and directs follow-up toward buyer decisions, agreement protections, and transfer planning.
Use this workflow when buyer’s counsel and the in-house deal team have an initial acquisition perimeter but need evidence to test it. Typical triggers include an agreed term sheet, seller data-room access, or a draft asset purchase agreement with incomplete schedules.
The scope is preparing and administering requests—not completing every substantive diligence analysis. For a carve-out, emphasize shared infrastructure and assets held outside the named seller. For an operating-site purchase, emphasize ownership, equipment, occupancy, permits, and environmental records.
This is a general US legal-workflow guide. State successor-liability, tax, lien, employment, and transfer requirements need transaction-specific review based on asset location, industry, governing law, and structure. The agreement examples below illustrate negotiated language, not market standards or generally applicable rules.
Gather these inputs before sending a broad questionnaire:
Confirm access limits rather than assuming the request list creates rights. Section 5.1 of the Sensata–Cypress agreement provides negotiated access while limiting information creation and requiring prior written consent before unilateral employee contact. Follow the actual deal documents when setting request scope and contact protocols.
Use the Asset Purchase Transactions — Diligence request list as the working record. You can copy this table into your working document or spreadsheet. Keep one independently answerable request per row; split requests requiring different custodians or evidence.
| ID | Asset/entity | Request and purpose | Priority/target | Custodian | Response/source | Status/gap | Buyer owner/next action |
|---|---|---|---|---|---|---|---|
Asset/entity identifies the seller, site, contract population, or asset category. Request and purpose states the evidence sought and the buyer question it answers. Request equipment ownership and financing records, for example, to investigate title and release needs—not simply to obtain another machinery list.
Use Priority/target for sequencing and a response target, not an assumed legal deadline. Response/source should contain stable document IDs, versions, and clause, page, or schedule references. Record written negative responses there too.
Distinguish “not applicable,” “none reported,” “unavailable,” “partially produced,” and “received—review pending.” “None reported” means the seller says an item does not exist; “unavailable” means relevant evidence cannot currently be supplied. Neither establishes the underlying legal conclusion. Keep a buyer owner and next action until review is complete or the gap is expressly accepted.
Read the purchased-asset and excluded-asset definitions alongside the operating plan. Identify tangible assets, inventory, receivables, contracts, intellectual property, records, permits, and shared resources the buyer expects to receive or use.
Ask who owns each asset, how it is identified, whether it is included, and what supports continued use after closing. Treat “all business assets” as a description to test, not evidence of completeness. Request reconciliations where the operational asset list differs from the proposed schedules.
Record: initial rows by asset category and owning entity, each request’s business purpose, and mismatches requiring clarification.
Trace important activities to the assets and relationships supporting them. A product line may depend on third-party tooling, licensed software, technical records, and employees retained by a seller affiliate.
Request ownership records, relevant agreements, shared-service descriptions, and supporting schedules. Include workforce information appropriate to the proposed hiring plan and access restrictions. Ask finance and tax reviewers to identify records needed for inventory, receivables, assumed payables, and transaction-specific tax inquiries.
Request existing records first; separately identify explanations or reconciliations the seller must prepare. Where independent operation is uncertain, request the proposed transition arrangement.
Record: the affected operation, custodian, and whether the request seeks existing documents or a new explanation. Prioritize essential operating dependencies.
For contracts, request executed agreements, amendments, schedules, side letters, notices, and consent correspondence. For equipment, request ownership and financing records, available lien information, and proposed releases. For permits, request the instrument, issuing authority, named holder, and transaction-related correspondence.
Separately request defaults, disputes, outstanding obligations, and facts relevant to the assumed/excluded liability boundary. Sections 1.3–1.4 of the Ellie Mae–AllRegs agreement illustrate different treatment of post-transfer contract obligations and pre-transfer obligations or breaches, including contracts transferred later. That negotiated allocation is not evidence resolving third-party claims.
Record: linked but separate requests for transfer and liability evidence, including timing questions for deferred transfers. Do not assume a closing-date cutoff answers every obligation.
Use transaction facts to activate specialist questions. Chemical storage calls for environmental records and specialist assessment, not merely a general litigation response. Federal customer contracts require government-contract review rather than ordinary commercial-consent assumptions.
CERCLA §107(e)(1) prevents private arrangements from transferring away liability imposed by that section while preserving agreements to insure, hold harmless, or indemnify. An excluded-liability clause therefore does not resolve environmental exposure. Request site assessments, investigation reports, storage records, and agency correspondence for specialist review without presuming contamination, liability, or a defense.
FAR 42.1204 addresses government recognition of a successor following specified asset transfers and supporting documentation. Recognition is not automatic. Request agency correspondence and assign review of applicable deviations and contract-specific requirements.
Record: the factual trigger, specialist owner, requested evidence, and unresolved question. For permits or tax matters, identify the relevant jurisdiction before defining follow-up.
Rank requests by their effect on the buyer’s decision: acquisition perimeter, continued operations, transfer obstacles, material exposure, then supporting detail. Explain urgency through the transaction consequence rather than marking everything critical.
Agree who may contact seller personnel, how questions are routed, and how restricted materials will be handled. Use staged access or specialist-only review where appropriate. Ask the seller to respond by request ID and identify the producing entity. Allow references to existing productions, but require precise locations rather than “see data room.”
Record: priority, target response date, seller custodian, buyer reviewer, and any access restriction or staged-production arrangement.
Check each response against the requested entity, period, asset population, and document type. An unsigned contract does not answer a request for the executed agreement. A current asset schedule may not establish title. A permit list is not the underlying permit or evidence addressing transfer.
Assign stable document IDs and preserve earlier versions. Link amendments and schedules to their base document. Use a separate document index where volume warrants it, retaining the request ID as the connection.
Write follow-ups identifying the precise omission and its consequence. If one missing amendment prevents assignment analysis, request that amendment rather than repeating the entire questionnaire.
Record: source citations, completeness status, missing evidence, and a focused follow-up with an owner and target.
Treat receipt, review completion, and issue resolution as different events. The seller may fully answer a request while revealing a consent problem that remains open. A commercial decision may permit progress despite unavailable evidence, but does not make that evidence verified.
Move substantive findings into the buyer’s issues record while preserving the request link. Identify whether the next decision concerns price, agreement language, a proposed condition, transition support, or investigation. Keep closing deliverables in the closing checklist rather than expanding the request list into a complete transaction tracker.
Record: disposition, supporting evidence, residual uncertainty, related issue reference, and the buyer decision-maker accepting or resolving the gap.
Fictional scenario: Harbor Vale Components LLC proposes to buy a pump-assembly business from Cedar Quay Industrial LLC. Draft schedules include machinery, customer contracts, and records. The buyer expects to operate at the existing site using the seller’s production software. All parties, documents, and circumstances below are fictional.
The seller uploads an equipment register and a customer contract, but no software license. Written responses identify an affiliate-held software subscription and historical solvent storage without investigation reports. The team creates three decision-focused entries:
| ID | Asset/entity | Request and purpose | Priority/target | Custodian | Response/source | Status/gap | Buyer owner/next action |
|---|---|---|---|---|---|---|---|
| R-01 | Machinery/Cedar Quay | Ownership and financing records; test title and release needs | High/before perimeter approval | Controller | D-014 equipment register, rows 8–19 | Partial; machines identified, ownership and financing evidence missing | M&A counsel: request purchase and financing records; register alone does not establish clear title |
| R-02 | Production software/affiliate | License, amendments, holder, and transition proposal; test operating access | High/before operating-plan approval | IT lead | M-003 written response, paragraph 2: affiliate holds subscription | License not produced; permitted use and transfer unknown | Technology counsel: request affiliate agreement; assess buyer license or transition options after review |
| R-03 | Operating site/Cedar Quay | Environmental reports and solvent-storage records; scope investigation | High/before site-risk decision | Facilities lead | M-004 written response, paragraph 4: historical storage reported | No reports produced; report existence and site condition unresolved | Environmental counsel: clarify records search and recommend investigation based on available facts |
The software response changes the inquiry from a missing upload to an affiliate-dependent operating risk. The buyer should not approve its access plan without reviewing the license or identifying an acceptable alternative. The machinery response calls for ownership evidence, not another asset list. Historical solvent storage warrants investigation but does not establish contamination or liability.
No row assumes missing documents exist. Each identifies what is known, what remains uncertain, and why the next request affects a buyer decision.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include bulk document classification to organize productions and prioritize human review. Contract review and tabular review can support analysis across responsive agreements. Keep the request list as your team’s work product, verify source references, and retain legal judgment over completeness and buyer risk. To discuss this asset-purchase workflow, book a demo.
No. Cover the known perimeter and operating dependencies, then add conditional requests as facts develop. Document deliberately deferred areas and who will revisit them so a shorter initial list does not become an accidental scope limitation.
Identify the owner and request ownership records, relevant agreements, and the proposed route for providing the asset or service. Treat the seller’s proposed solution as something to verify, not evidence that the buyer will receive sufficient rights.
It can complete the response stage if it addresses the requested entity, period, and subject. The buyer reviewer must still assess consistency with other evidence and whether corroboration or further inquiry is warranted. Record the response source and review decision.
Link them where appropriate, but keep their functions distinct. Diligence identifies restrictions and evidence gaps; the closing checklist records agreed deliverables and acceptance requirements. Check the actual agreement before treating a missing consent as a closing condition or deciding who may waive it.
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.