How to prepare a due diligence request list for IP Portfolio Acquisition Transactions

Prepare the buyer’s request list by reconciling the proposed purchased assets with evidence of ownership, continuing rights, transfer restrictions, and operational dependencies. Organize requests by asset class, jurisdiction, and selling entity, then assign each request a stable ID, a precise evidence requirement, a priority, and an accountable reviewer. The deliverable is a controlled request register—not a generic questionnaire—that distinguishes seller assertions from verified documents and turns incomplete responses into targeted follow-ups before the buyer relies on assumptions about the portfolio’s scope and value.

When to use this workflow

Use this workflow when buyer’s counsel receives an initial portfolio schedule, draft asset purchase agreement, or data-room invitation for a patent, trademark, copyright, software, or mixed-IP acquisition. It suits in-house teams coordinating specialist counsel, technical reviewers, and deal leads.

The task is to prepare and refine diligence requests, not complete a title opinion or closing checklist. Start before the seller’s folder structure becomes the default definition of the purchased portfolio.

This guide uses U.S. federal IP transfer rules. State contract, employment, secured-transactions, insolvency, and foreign-law questions require separate analysis. The requests are practical recommendations; their significance depends on the transaction structure, governing law, and buyer’s intended exploitation of the assets.

What you need

Obtain the proposed purchased-asset definition, exclusions, seller entity chart, initial asset schedule, data-room index, and buyer’s intended uses. Identify whether the buyer expects exclusivity, enforcement control, sublicensing rights, source-code access, or continuity of an existing brand or business.

Gather these asset-specific starting materials:

• Patents: application and patent numbers, jurisdictions, family relationships, named inventors, recorded owners, prosecution contacts, and maintenance records.
• Trademarks: registrations and applications, filing bases, use filings, associated products or services, and the business assets proposed to accompany the marks.
• Copyright and software: work and repository identifiers, versions, contributors, registrations where available, transfer documents, and dependency inventories.
• Trade secrets and supporting assets: descriptions that avoid unnecessary disclosure, access controls, confidentiality arrangements, technical documentation, and domain or account inventories.

Identify the evidence custodians. The seller’s deal team may not hold inventor agreements, older licenses, financing releases, or repository histories. Ask which records sit with predecessors, outside prosecution counsel, lenders, or technical personnel.

Use the template

Use the IP Portfolio Acquisition Transactions — Diligence request list below. You can copy this table into your working document or spreadsheet. Keep one discrete evidence question per row; split requests when different entities, jurisdictions, or custodians must respond.

Use stable request IDs such as IP-001 and separate document IDs such as DOC-014. In Asset/entity, specify the asset identifier, jurisdiction, and purported owner. Buyer purpose identifies the decision the evidence supports: ownership, exclusivity, transferability, continuity, or valuation.

In Response/source, identify the file, version, execution status, and clause or page. Prefix the entry with a status such as “awaiting response,” “received—unreviewed,” or “reviewed—gap remains.” Distinguish seller assertions from document-supported findings. “Uploaded” alone is not an adequate response.

Use Gap/next action for missing exhibits, unanswered questions, follow-up requests, and closure or accepted-gap decisions. Owner/target identifies the buyer reviewer and response target; that target is not a statutory deadline. Keep seller custodians and confidentiality tiers in a supporting index linked by request ID.

Step by step

1. Define the acquisition perimeter before drafting requests

Compare the purchased-asset definition with the seller’s schedule and buyer’s investment rationale. Determine whether the buyer is acquiring entire rights, partial interests, specified territories, or assets subject to retained licenses. Identify omitted applications, related works, supporting know-how, and excluded business assets without presuming they belong in the sale.

Request a reconciled schedule showing included, excluded, and unresolved assets by selling entity and jurisdiction. Ask the seller to explain discrepancies rather than accepting the agreement or registry list as complete. Specify whether related continuations, foreign counterparts, technical files, and enforcement-related rights are intended to be included.

Record: a perimeter request for each unresolved category, citing the agreement definition and schedule.

2. Convert title questions into document requests

For each material asset, request the instruments connecting creators and intermediate owners to the seller, including exhibits and records explaining mergers or entity-name changes. Ask for executed copies and signature-authority support where authority is unclear. Identify partial interests and contributors whose rights require separate analysis.

For U.S. patents, §261 provides for written assignments. USPTO guidance explains that recordation is ministerial and does not determine validity or ownership effect. The statute protects a subsequent purchaser or mortgagee for value without notice unless the transfer is recorded within three months or before the subsequent transaction; it does not automatically invalidate a late-recorded transfer between the original parties. Request execution and recordation evidence separately. See USPTO MPEP §301.

Record: each missing transfer, exhibit, or unexplained registry discrepancy, rather than “all title documents” alone.

3. Tailor evidence requirements to the asset class

For trademarks, request assignment instruments, associated-goodwill and business information, application bases, and use filings. Section 1060 requires duly executed written assignments with associated goodwill. Intent-to-use applications face transfer restrictions before the specified use filings, subject to an exception for a successor to the relevant ongoing, existing business. Obtain facts for that analysis rather than assuming every pending application transfers identically. See 15 U.S.C. §1060.

For copyright assets, request contributor and intermediary transfer documents, plus the asserted ownership basis where the seller relies on employment or another route. Section 204 generally requires a writing signed by the owner or authorized agent for ownership transfers, except transfers by operation of law; it does not impose that requirement on every nonexclusive license. See Copyright Act §204.

For software, request dependency inventories and applicable third-party license terms. For trade secrets, request confidentiality and access-control evidence through restricted channels.

Record: asset-specific requests and specialist questions, including foreign-law dependencies.

4. Ask what rights will survive the acquisition

Request inbound and outbound licenses, amendments, side letters, settlements, covenants not to sue, funding restrictions, security documents, and proposed seller license-backs. Seek asset coverage, territory, field, exclusivity, duration, sublicensing, payment obligations, assignment consents, change-of-control provisions, termination, and enforcement control. Do not assume an asset sale triggers the same provisions as an equity acquisition.

A clean copyright record search cannot exclude surviving licenses. Section 205 conditions constructive notice on specified work identification and registration requirements; certain signed nonexclusive licenses can prevail over conflicting ownership transfers under its timing or good-faith conditions. See Copyright Act §205.

A SEC-filed asset purchase agreement, §§2.10(g) and (l), illustrates representations qualified by a closing license, permitted encumbrances, and disclosure schedules. It supports requesting exceptions and underlying contracts—not treating the representations as proof of unrestricted rights or market standards.

Record: restriction requests linked to the buyer’s intended use and asset group, including financing instruments and claimed releases.

5. Add status, dispute, and usability requests

Request prosecution records, pending office correspondence, maintenance evidence, dispute notices, settlement documents, and information about current proceedings. Ask the seller to identify upcoming actions and the source supporting each reported date. Assign counsel to verify dates before relying on them.

For operational usability, request repository and build documentation, technical-file inventories, domain-control information, and details of materials the seller cannot deliver. Separate evidence of control from credentials: do not request passwords in an ordinary diligence spreadsheet. Ask technical reviewers to identify dependencies essential to continued development or deployment.

Record: focused requests with the commercial consequence of a missing record, such as inability to assess prosecution status or reproduce acquired software.

6. Prioritize and route the first request list

Give highest priority to uncertain seller ownership, exclusivity inconsistent with valuation, material transfer restrictions, and dependencies without which the buyer cannot use the portfolio. Lower priority determines review order; it does not make a request dispensable.

Group related requests for the seller while preserving individual IDs. Identify legal, technical, and business reviewers. Specify approved restricted-review arrangements for source code or trade secrets. Obtain counsel approval before requesting or circulating potentially privileged analyses; initially seek underlying facts and nonprivileged records where appropriate.

Record: priority, buyer reviewer, seller custodian where known, response target, and access limitation.

7. Reconcile responses and issue targeted follow-ups

Compare every response with the evidence question. Check execution, asset coverage, schedules, amendments, and incorporated documents. Ask for an express response when records reportedly do not exist or a request is considered inapplicable; distinguish “not located” from “never created.”

Close a request when its question has been answered and reviewed, or an authorized buyer decision-maker accepts the identified gap. A complete response can reveal an adverse deal issue. Route that issue to the deal issues list without repeatedly requesting the same evidence. Preserve superseded responses and the basis for closure.

Record: exact sources, uncertainty, follow-up language, and the person responsible for resolving or accepting the issue.

Worked example

Fictional scenario: Bracken Devices LLC proposes to acquire sensor patents, the SIGNALFERN trademark application, and calibration software from Cobalt Orchard Inc. Valuation assumes exclusive licensing control and continued software development. All parties, documents, identifiers, and clause descriptions below are fictional.

The room contains a recorded patent assignment, an application summary, an unsigned contractor form, and a signed patent license missing its schedule. Counsel records:

IP-001 requires the missing schedule, not another general assurance of exclusivity. IP-002 requires filing and business facts before counsel can assess transferability. IP-003 requires contributor-to-code mapping to determine the significance of missing signed documents.

These rows do not establish defective ownership or an ineffective transfer. They identify uncertainties and the evidence needed to resolve them. The buyer defers reliance on the affected valuation assumptions while continuing unrelated review; an unresolved high-priority row remains visible in the decision package.

Common mistakes

• Sending a generic corporate checklist. Replace broad IP questions with asset identifiers, selling entities, and evidence tied to purchased rights.
• Equating recordation with title verification. Obtain underlying instruments and reconcile partial interests, intermediaries, and missing exhibits.
• Treating representations as evidence. Obtain disclosure exceptions and underlying contracts; negotiated assurances do not resolve every factual question.
• Bundling unrelated requests. Separate patent licenses, trademark transfer facts, and software contributors so one upload cannot conceal multiple unanswered questions.
• Closing requests when files arrive. Verify execution, coverage, completeness, and responsiveness; separately assign any adverse finding.

Final quality check

• Every material asset or coherent asset group maps to relevant requests.
• Selling entities, jurisdictions, and historical names are reconciled or flagged.
• Ownership evidence is distinguished from registry information and seller assertions.
• Licenses, retained rights, security interests, and transfer restrictions have specific requests.
• Document references identify versions, clauses, and pages that support the finding; legal sources support the proposition attributed to them.
• Restricted materials have an approved review route and responsible reviewer.
• Open issues are resolved, assigned, or expressly accepted by an authorized buyer decision-maker, with the decision recorded.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include bulk document classification to organize materials and prioritize human review. Tabular review supports work across multiple documents, while contract review can support examination of assignments and licenses. The request register remains the buyer’s work product: counsel defines scope, verifies evidence, and decides whether a gap requires further diligence or a deal response. To discuss this workflow, book a demo.

Frequently asked questions

Should every patent receive a separate request row?

Not necessarily. Group assets covered by the same instruments and evidence question. Split groups when ownership chains, jurisdictions, restrictions, or missing documents differ. Preserve asset-level traceability in the supporting schedule.

What if the seller cannot find an assignment?

Record a missing-evidence response. Ask about alternative custodians, predecessor records, and supporting documents. Assign counsel to assess the ownership basis and possible remediation; do not treat a registry entry as a substitute for the instrument.

Should source code be requested immediately?

Begin with repository, contributor, and dependency inventories. Agree on access scope and confidentiality arrangements before requesting sensitive code. Technical reviewers should define the inspection needed to answer ownership and usability questions.

When is the request list complete?

It is ready for decision-making when material evidence questions are answered or remaining gaps have named owners and explicit buyer decisions. Completion does not establish a risk-free portfolio or satisfaction of closing requirements.

Sources

• USPTO MPEP §301: patent assignments and recordation.
• 15 U.S.C. §1060: trademark assignments.
• U.S. Copyright Office, Chapter 2: §§204–205.
• SEC-filed asset purchase agreement: §§2.10(g), (l).

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.