Asset Purchase Transactions

How to prepare a deal issues list from transaction documents for Asset Purchase Transactions

Prepare a buyer-side asset purchase deal issues list with a copyable template, review steps, and a fictional example connecting evidence to negotiation decisions.

October 18, 2026  ·  10 min read
Book a Demo →

Prepare a buyer-side deal issues list by reconciling the asset purchase agreement with its schedules, underlying asset records, material contracts, and ancillary documents. For each unresolved point, identify the source, explain the buyer’s operational or economic exposure, and record the requested change, seller’s position, fallback, and decision-maker. The deliverable is a prioritized negotiation document—not a summary of every clause—that connects acquisition scope, liability allocation, transfer restrictions, and closing protections to decisions the buyer can make.

When to use this workflow

Use this workflow when buyer’s counsel or an in-house acquisition team has a substantive asset purchase agreement (APA) draft and supporting documents sufficient to test its assumptions. Typical triggers include preparing a consolidated markup, briefing the buyer before negotiations, or reconciling revised schedules before signing.

Diligence findings enter the list when they require a drafting change, commercial decision, further evidence, or express risk acceptance. Routine collection belongs in the request tracker unless missing information prevents a material decision.

This guide uses a US practice orientation and selected federal authorities, not a fifty-state survey. Governing law, asset location, seller organization, industry, and structure require separate review. State successor-liability, tax, lien, permit, and employment questions should be assigned where relevant; contractual allocation alone does not resolve them.

What you need

Assemble a version-controlled review set containing:

  • The current APA, prior markup, definitions, and disclosure schedules.
  • Purchased- and excluded-asset lists, ownership evidence, lien information, and proposed transfer instruments.
  • Assumed-contract schedules, underlying agreements, amendments, consent correspondence, and shared-service arrangements.
  • Assumed- and excluded-liability provisions, claims records, employee information, and relevant environmental materials.
  • Price-adjustment and allocation procedures, indemnity terms, closing conditions, termination provisions, and ancillary agreements.
  • The buyer’s operating plan, negotiating instructions, materiality judgments, and approval authorities.

Give documents stable IDs and preserve execution status and versions. A draft consent, executed consent, and email promising consent are different evidence. Record unavailable schedules as missing rather than treating silence as confirmation that no exception exists.

Use the template

The companion template is Asset Purchase Transactions — Deal issues list. You can copy this table into your working document or spreadsheet.

ID / priority Source / version Issue / evidence gap Buyer impact Buyer request Seller position Fallback / links Owner / decision Status / proof

Use one row for each negotiable decision, not every problematic sentence. Cite document IDs, versions, clauses, and schedule entries in Source / version. Distinguish verified discrepancies from suspected issues in Issue / evidence gap.

Buyer request states the desired outcome. Seller position reflects an actual markup or communication; use “not received” where appropriate. Fallback / links captures alternatives and dependencies. Owner / decision identifies the responsible lawyer and authorized risk approver. Status / proof records resolution evidence, not merely that a discussion occurred.

Link complex rows to a liability map or conditions tracker, but keep the decision understandable without opening every supporting document.

Step by step

1. Establish the buyer’s acquisition perimeter

Compare the buyer’s day-one operating requirements with purchased assets, exclusions, assumed contracts, intellectual property, facilities, and shared systems. Check seller-entity names and distinguish owned assets from licensed or leased rights.

Read the operative asset definition before treating a schedule omission as exclusion: a schedule may be exhaustive or illustrative. Even where broader language may capture an omitted asset, inconsistent descriptions can require correction.

Create actionable rows: “verify ownership and reconcile rig T-17 across the purchased-asset schedule and bill of sale,” rather than “confirm assets.” Record the discrepancy, operational consequence, and requested correction. Missing title evidence is uncertainty, not proof that seller lacks ownership.

2. Reconcile liability boundaries with the assets

Read assumed and excluded liabilities together, including definitions and timing language. Test pre-closing breaches, customer credits, warranty obligations, employee obligations, and contracts transferred later. Determine whether deferred transfer changes when buyer assumes performance obligations.

The Ellie Mae–AllRegs agreement, §§1.3–1.4, illustrates separate treatment of post-closing assigned-contract obligations, pre-closing obligations and breaches, and later-transferred contracts. These are negotiated allocations, not protection against every third-party claim.

Record the requested allocation and its indemnity consequences. Separately assign statutory exposure for assessment. CERCLA §107(e)(1) prevents agreements from transferring away liability imposed under that section while preserving agreements to insure, hold harmless, or indemnify. An environmental row therefore should not close solely because contamination is labeled an excluded liability; buyer liability and applicable protections need separate analysis.

3. Test transfer restrictions against the closing structure

Compare APA transfer mechanics with each material underlying instrument. Distinguish consent from notice, prohibited transfer, and unresolved interpretation. Inclusion on an assumed-contract schedule does not establish permission.

Determine the proposed treatment of outstanding consent: deferred transfer, omission, or an interim arrangement. Identify performance obligations, costs, operating dependencies, and effects on buyer recourse.

The Ellie Mae–AllRegs agreement, §5.10, illustrates restrictions on assignment without specified consent and a limited recourse waiver when buyer elects to close without particular scheduled consents. Neither feature should be assumed in another deal.

For federal contracts, separately assess government recognition of the successor. FAR 42.1204(a), (e)–(g) addresses recognition in specified asset-transfer circumstances and supporting documentation; recognition is not automatic. Record contract-specific review, applicable agency deviations, and agency confirmation as dependencies—not merely a private-counterparty consent request.

4. Convert findings into negotiation requests

Write each row around four elements: established fact, unresolved question, buyer consequence, and requested protection. Decide whether the response is evidence, revised drafting, consent, an economic adjustment, or risk acceptance.

Separate requests requiring different decisions. Obtaining a missing customer amendment does not resolve an unacceptable liability assumption. Conversely, combine conforming edits when one decision resolves them together.

Record a usable fallback and its conditions. If buyer could accept deferred transfer only with interim services, identify required service scope, duration, rights evidence, and approval owner. Do not describe an interim arrangement as permissible before reviewing contractual and legal constraints.

5. Connect requests to agreement protections

Trace each issue through representations, schedules, covenants, conditions, indemnity, price provisions, and termination rights. Disclosure may qualify a representation without providing the operational protection buyer needs. Indemnity may not replace access to an essential asset.

Keep a condition, evidence of satisfaction, and waiver authority distinct. The Sensata–Cypress agreement, §§6.1–6.2, distinguishes jointly waivable conditions from buyer-waivable conditions and specifies supporting deliverables. It illustrates drafting choices, not a universal checklist.

Record conforming changes and cross-references in Fallback / links. For price disputes, check whether acquired receivables, inventory, assumed obligations, or deposits also enter the adjustment calculation; flag inconsistent treatment or possible double counting. Identify both contractual waiver requirements and internal buyer approval before recording an accepted closing gap.

6. Rank issues and obtain buyer instructions

Prioritize consequences: inability to operate, uncertainty about acquired assets, material exposure, economic disagreement, or drafting ambiguity. Assess evidence confidence separately; uncertain facts can warrant urgent attention.

Obtain instructions from appropriate stakeholders. Operations assesses service dependencies; finance evaluates price mechanics; specialist counsel handles environmental or regulatory exposure. Counsel converts those instructions into requests and proposed wording.

Record the approved opening position, fallback, escalation point, and any decision date tied to negotiations. Preserve seller’s stated objection: a narrower solution may address it without sacrificing buyer’s objective. Do not present counsel’s proposed compromise as an approved buyer position.

7. Reconcile the next draft and close rows with evidence

Compare revised documents against every open row. Verify accepted wording in the correct version and check whether definitions, schedules, or ancillary instruments undermine it.

Use statuses such as open, awaiting evidence, agreed pending drafting, resolved, or accepted risk. A verbal agreement is not completed drafting; an unanswered request is not accepted risk.

Record final clause citations, relevant executed evidence, or documented risk approval. If negotiations remain open, assign a named owner and next action. Transfer implementation tasks to the appropriate tracker while retaining links. The issues list should preserve the decision record, not become the entire closing checklist.

Worked example

Fictional scenario: Harbor Vale Components LLC proposes to buy a production line from Cedar Point Manufacturing Inc. for $18 million. All parties, documents, amounts, and proposed terms below are fictional. Buyer needs a testing rig, customer supply contract, and production-software access immediately after closing.

APA version 3 defines purchased equipment by reference to the items listed on Schedule 1.1. It assumes scheduled customer-contract obligations and excludes seller’s software platform. The review set includes equipment register AR-04, executed customer agreement CT-08, and a draft transition services agreement (TSA). No software licensing documents or customer consent have been provided. Seller’s email SE-02 supplies the positions below.

ID / priority Source / version Issue / evidence gap Buyer impact Buyer request Seller position Fallback / links Owner / decision Status / proof
A1 / High APA v3 §1.1, Sch. 1.1; AR-04 p. 6; SE-02 Rig T-17 in register, omitted from exhaustive schedule; title unverified Testing capacity uncertain Verify title; add rig to schedule and bill of sale Says clerical omission Rental only if operationally acceptable Buyer counsel / COO Awaiting ownership record and revised documents
A2 / High CT-08 §14; APA v3 §§2.3, 7.2; SE-02 Written assignment consent required; none supplied Customer continuity at risk Require consent; exclude pre-transfer breaches Requests closing without consent Assess permitted interim performance and preserve agreed recourse Contracts counsel / deal lead Open; seller email is not consent
A3 / High APA v3 Sch. 1.2; TSA v1 §3; SE-02 Software excluded; TSA omits production access; licenses missing Line may not operate independently Define services and access; obtain rights evidence Offers 60 days’ assistance Test migration feasibility and license constraints Technology counsel / COO Awaiting licenses and revised scope

The evidence changes three decisions. A1 requires both title verification and drafting because this fictional APA uses an exhaustive equipment schedule. A2 requires transfer analysis and a separate liability decision; consent alone would not settle pre-transfer breaches. A3 requires an operating solution, not simply another warranty or an arbitrary service duration.

The record establishes neither rig ownership, customer consent, nor permission for software access. Seller’s assurances remain negotiation positions, not verified resolution evidence.

Common mistakes

  • Copying diligence observations unchanged. Convert material findings into buyer requests and decisions; retain routine collection elsewhere.
  • Treating exclusions as complete protection. Separate contractual allocation from statutory and third-party exposure, assigning specialist analysis where needed.
  • Reading only the APA assignment clause. Review underlying restrictions, consent evidence, and deferred-transfer consequences together.
  • Substituting indemnity for operability. Test whether monetary recovery addresses the missing asset or service before accepting that fallback.
  • Closing rows after favorable markup. Verify connected schedules, definitions, ancillary instruments, and required approvals.

Final quality check

  • Each material row cites a stable document ID, version, and clause or page.
  • Facts, evidence gaps, and legal assessments remain distinguishable.
  • Asset descriptions reconcile across the APA, schedules, and transfer instruments.
  • Liability timing addresses closing and deferred transfers.
  • Consent gaps identify proposed treatment and risk-acceptance authority.
  • Requests, seller positions, fallbacks, and connected protections are current.
  • Resolved rows contain proof; every open issue has an owner and next action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In contract review, choose the buyer as represented party in Word and provide deal-specific instructions. Findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name and dismiss findings with reasons. Tabular review supports cross-document work, while due diligence classification can organize documents and prioritize human review. The issues list remains your work product; counsel retains verification and negotiation judgment. Book a demo to discuss this workflow.

Frequently asked questions

Should every diligence finding become a deal issue?

No. Include findings affecting drafting, economics, acquisition scope, closing decisions, or material risk acceptance. Link supporting diligence rather than reproducing it.

How should an unavailable disclosure schedule be recorded?

Identify the missing schedule and decisions it prevents. Assign follow-up and keep affected conclusions provisional; do not infer that no exceptions exist.

Can related asset and liability issues share one row?

Yes, when one decision resolves both. Split them when ownership, transfer permission, and liability allocation require different actions or approvers.

When can buyer accept a missing consent as a resolved issue?

When authorized acceptance is documented and agreed treatment is reflected accurately. Use “accepted risk” where appropriate; that status does not establish consent or transfer validity.

Sources

Scope: General professional workflow guidance, not advice for a particular matter. Filed agreements illustrate negotiated wording, not 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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo