How to prepare a deal issues list from transaction documents for IP Portfolio Acquisition Transactions

Prepare a buyer-side deal issues list by reconciling the purchased-IP definition and asset schedules against ownership instruments, licenses, security documents, and proposed assignments. Convert each material discrepancy into a negotiation decision: what right is uncertain, why it matters to the buyer, which provision needs revision, and what evidence would resolve it. The deliverable is a prioritized, source-linked list connecting diligence findings to drafting, closing protection, pricing, or expressly accepted risk—not a collection of unanswered diligence questions.

When to use this workflow

Use this workflow when buyer’s counsel or the in-house team has an acquisition-agreement draft and supporting documents sufficient to test the proposed transfer. It suits standalone patent purchases and mixed portfolios containing trademarks, copyrights, software, confidential know-how, and domains.

The trigger is usually a negotiation draft, a material diligence finding, or revised disclosure schedules. Keep the scope narrow: identify decisions requiring contractual treatment or buyer approval. Routine document collection belongs in the diligence request list; execution logistics belong in the closing checklist.

This is a general US-oriented workflow, not advice for a particular transaction. Federal IP transfer rules inform the review; state contract, secured-transactions, employment, insolvency, and foreign-law questions require separate analysis. Conclusions depend on the instruments, governing law, facts, and intended use.

What you need

Start with the current acquisition agreement, purchased-asset and excluded-asset schedules, disclosure schedules, and proposed assignments. Include seller license-backs and retained-rights provisions, which may narrow the acquisition’s practical scope.

Gather:

• Asset inventories identifying jurisdictions, registration or application numbers, owners, and software or content versions.
• Creator, employee, contractor, and intermediate-owner instruments, including referenced exhibits.
• Inbound and outbound licenses, amendments, settlements, financing documents, searches, and release evidence.
• Relevant prosecution, maintenance, dispute, technical-dependency, funding-restriction, and trade-secret access records.
• Buyer instructions identifying essential assets, intended exploitation, acceptable restrictions, and decision-makers.

Assign stable document IDs and record versions and execution status. Link missing materials to numbered requests. Distinguish seller inventory assertions from executed instruments and official records; none should silently substitute for another.

Use the template

Use the IP Portfolio Acquisition Transactions — Deal issues list below. You can copy this table into your working document or spreadsheet.

Assign one stable issue ID per decision. Identify affected assets precisely. In Evidence / status, cite document IDs, clauses, pages, or schedule cells, and distinguish verified text, seller assertions, and missing evidence.

Deal provision identifies the drafting destination: definition, representation, disclosure exception, covenant, indemnity, price mechanism, or condition. Buyer position / fallback states the requested protection and any authorized alternative. Owner / target names a person and transaction milestone; record any separately verified legal deadline expressly.

Use explicit resolution language: awaiting an identified instrument, agreed subject to drafting, accepted by a named decision-maker, or resolved with cited evidence. A revised representation does not necessarily cure an ownership gap.

Step by step

1. Establish the required rights and review baseline

Confirm whether the buyer needs ownership, exclusivity, enforcement control, sublicensing rights, or operational access. A portfolio acquired for licensing presents different priorities from software acquired to operate a product.

Fix the agreement and schedule versions used for review. Compare the purchased-IP definition with asset schedules, exclusions, retained rights, and license-backs. Check whether source code, technical files, brand materials, and confidential know-how are included where required.

Record each material mismatch in Asset / scope, cite the conflicting sources, and identify the affected definition. Explain the consequence—such as exclusion of a required software version—rather than writing only “scope unclear.”

2. Test ownership evidence without treating recordation as proof

Trace material assets from creators through intermediate owners to the selling entity. Examine signatures, descriptions, missing exhibits, name changes, mergers, and partial interests. Separate missing evidence from an affirmative conflict between instruments.

For US patents, §261 provides for assignment by written instrument. Its qualified priority rule protects certain subsequent purchasers or mortgagees without notice unless recordation occurs within three months or before the subsequent transaction. It does not automatically invalidate a transfer between the original parties after three months. USPTO guidance also explains that recordation is ministerial, not a determination of validity or ownership effect. See MPEP §301. (uspto.gov)

Record the gap and proposed response separately: obtain the missing instrument, revise the ownership assurance, or propose a condition tied to specified evidence. Do not resolve the row solely because the registry names the seller.

3. Identify transfer questions specific to each asset class

For trademarks, compare assignment wording with the goodwill and business facts. Identify intent-to-use applications and verify use filings. 15 U.S.C. §1060(a)(1), (3) addresses duly executed written assignments and associated goodwill. Before specified use filings, intent-to-use assignments are restricted, subject to the exception for a successor to the relevant ongoing, existing business. Do not assume goodwill wording alone resolves that restriction. (govinfo.gov)

For copyright assets, identify the ownership basis and request applicable signed transfer evidence covering the acquired works or versions. 17 U.S.C. §204(a) generally requires a writing signed by the rights owner or authorized agent for ownership transfers, except transfers by operation of law. That rule should not be extended to every nonexclusive license. (copyright.gov)

For software and trade secrets, identify required repositories, dependencies, confidential information, and delivery access. Record the specific transfer question, affected provision, and specialist responsible for unresolved analysis.

4. Translate licenses and encumbrances into restrictions

Compare material licenses by asset coverage, exclusivity, territory, field, duration, royalties, sublicensing, consent, termination, enforcement control, and survival. Read amendments and incorporated schedules before summarizing restrictions. Reconcile relevant IP and secured-transactions search results with financing instruments and proposed releases; do not infer complete coverage from one search.

Test representations against disclosure exceptions. An exception may disclose a restriction accurately without addressing the buyer’s objective. Decide whether the response requires consent, release, a narrower license-back, adjusted acquisition scope, or economic negotiation.

A clean copyright record search cannot establish that no surviving licenses exist. 17 U.S.C. §205(c), (e) conditions constructive notice on identification and registration requirements and allows signed nonexclusive licenses to prevail over conflicting ownership transfers in specified circumstances. (copyright.gov)

Record the restriction, affected buyer activity, and any missing instrument needed to verify its extent.

5. Convert each finding into a negotiating position

Write each issue as a decision: “Require release evidence covering listed patents before closing,” rather than “Check liens.” Identify the provision to change and explain why its present wording is insufficient.

Separate cure from fallback. Obtaining an ownership instrument and negotiating an indemnity address different concerns. Do not characterize indemnification as supplying missing ownership evidence. If proposed, evaluate its scope, exclusions, recovery limits, and practical value before seeking approval.

Consolidate findings only when facts and requested outcomes align. Record the preferred position, authorized fallback, and approving decision-maker. Keep unapproved alternatives visibly unapproved. A seller’s agreement to discuss a cure is not an agreed resolution.

6. Distinguish document delivery from closing protection

Check whether an assignment, consent, or release is only a deliverable or is also linked to the buyer’s requested closing condition. Read definitions, exceptions, and waiver provisions together.

One SEC-filed IP acquisition agreement, §§4.02 and 7.06–7.07, separately addresses seller deliverables and buyer conditions concerning consents and transaction documents. This illustrates negotiated drafting, not a universal requirement or evidence that the underlying assets were unrestricted. (sec.gov)

For proposed post-closing cooperation, specify responsibility, costs, duration, and required instruments. Keep contractual timing separate from applicable recordation-priority analysis. Record the requested clause change and any unresolved dependency. Transfer detailed execution tasks to the closing checklist without losing the issue’s decision history.

7. Prioritize and circulate for decisions

Rank issues by consequence to the acquisition objective, uncertainty, and available cure. Explain why a principal-asset ownership gap requires escalation; do not rely on a color alone.

Recheck rows against the latest draft and schedules. Cite revised clauses for agreed changes and preserve unresolved factual questions. Prepare the external negotiation list from approved positions without inadvertently sharing internal fallbacks, sensitive technical details, or legal analysis.

Record who must decide each open issue and by which milestone. The list should allow approval, an evidence request, or acceptance of a defined risk without reconstructing the document history.

Worked example

Fictional scenario. Cedar Arc Systems proposes to acquire an IP portfolio from Lantern Vale Technologies for $7.8 million. The buyer plans to commercialize a sensor product and offer exclusive software distribution rights. All parties, amounts, documents, identifiers, and provisions below are fictional.

The portfolio includes US patents, software copyrights, and a trademark application. Draft D-01, §3.9 represents that no third party holds software distribution rights, subject to scheduled exceptions. The supplied schedule lists none. Review identifies three decisions:

P-04 requires evidence, not merely stronger assurance. S-7 requires a commercial decision because correcting disclosure would not restore exclusivity. T-02 requires application and business facts before counsel selects transfer wording. The list neither assumes the missing exhibit covers P-04 nor predicts that the licensee will terminate its rights.

Common mistakes

• Listing assets instead of decisions. Replace “review patent schedule” with the identifier mismatch, conflicting sources, and requested correction.
• Treating disclosure as remediation. Explain whether a disclosed license still conflicts with intended exploitation.
• Equating ownership with operational readiness. Separately identify required software dependencies, technical materials, and access.
• Applying one transfer analysis throughout. Distinguish patent instruments, trademark goodwill and application status, copyright ownership evidence, and confidential-material delivery.
• Closing rows after drafting concessions. Verify required evidence and obtain approval for residual risk before recording resolution.

Final quality check

• Each material row identifies affected assets and intended buyer activity.
• Citations resolve to the correct source version, clause, page, or schedule cell.
• Verified facts, seller assertions, missing evidence, and conclusions remain distinct.
• Each requested change has a drafting destination and explained consequence.
• Deliverables, conditions, waivers, and post-closing obligations remain distinguishable.
• Fallbacks and accepted risks identify authorized decision-makers.
• Open issues have owners and milestones; resolved issues retain supporting evidence.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities support bulk classification to organize documents and prioritize human review; tabular review supports work across documents. In contract review, choose the represented party in Word and supply buyer-specific instructions. Findings quote and locate clauses, rank severity, and flag missing language as not present. Lawyers can revise or insert suggestions as ordinary tracked changes under the signed-in Word user’s name, or dismiss findings with reasons. Counsel verifies evidence and approves positions. Book a demo to discuss this workflow. (decover.ai)

Frequently asked questions

Should every diligence request become a deal issue?

No. Include missing information when its answer could change drafting, price, closing protection, or risk acceptance. Cross-reference routine collection requests rather than duplicating them.

How should foreign portfolio assets appear?

Identify the jurisdiction, asset, and unresolved question. Assign local-law review and record its effect on the proposed position rather than applying US transfer rules by default.

Where should a seller license-back be addressed?

Trace its scope through purchased rights, retained rights, exclusivity assurances, permitted uses, and schedules. Identify precisely which buyer activity it restricts and where revision is needed.

When is an issue ready to close?

When agreed drafting and required evidence are verified, or an authorized person expressly accepts the remaining risk. Preserve the distinction between an evidentiary cure and risk acceptance.

Sources

• USPTO MPEP §301, including 35 U.S.C. §261: patent assignments and limits of recordation.
• 15 U.S.C. §1060: trademark assignments, goodwill, and intent-to-use restrictions.
• US Copyright Office, Copyright Act Chapter 2, §§204–205: ownership-transfer writings, constructive notice, and license priority.
• SEC-filed IP acquisition agreement, Exhibit 10.3: illustrative deliverables and closing conditions, not market-standard evidence.

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.