How to compare material contracts in a diligence table for IP Portfolio Acquisition Transactions

Compare material contracts by mapping each agreement to the IP being acquired, then extracting the rights, restrictions, economics, and transfer requirements that affect the buyer’s intended use. Review executed agreements with their amendments, schedules, and related instruments; separate seller assertions from verified language and counsel’s conclusions. The deliverable is a source-linked comparison table showing the rights the documents support, restrictions on planned exploitation, unresolved questions, and required buyer decisions. Use it to direct targeted requests and negotiations—not to replace the underlying agreements or an asset-level title analysis.

When to use this workflow

Use this workflow when buyer’s counsel or an in-house legal team receives contracts covering patents, software, copyrighted content, trademarks, or trade secrets and must compare their effect on an IP portfolio acquisition. Triggers include an initial data-room release, a revised purchased-asset schedule, or disclosure of a previously unknown exclusive license.

Materiality should follow the acquisition thesis. A low-revenue license may be critical if it grants exclusivity in the buyer’s intended field. A contributor agreement may matter more than a large customer contract if it supports ownership of core software.

This guide uses a US transactional orientation. Federal IP transfer rules inform particular checks; state contract law, foreign rights, and transaction structure require separate analysis. The immediate scope is contract comparison, not a complete title opinion, freedom-to-operate assessment, or closing checklist.

What you need

Start with the proposed asset perimeter and the buyer’s intended products, territories, and licensing channels. A field restriction cannot be assessed in isolation from the planned business.

Collect:

• The purchased-asset list, selling entities, excluded assets, proposed license-backs, and transaction structure.
• Executed inbound and outbound licenses, amendments, schedules, side letters, waivers, and relevant notices.
• Contributor assignments, development and funding agreements, settlements, coexistence agreements, and security documents affecting the portfolio.
• Royalty statements, consent correspondence, performance notices, and available evidence of termination or release.
• The seller’s contract list and disclosure schedules, including exceptions to ownership and licensing representations.

Give every file a stable document ID. Maintain a supporting index recording parties, execution status, version, asset identifiers, confidentiality restrictions, and related documents. For software, request dependency inventories to help identify licenses absent from the seller’s material-contract list. Route sensitive source code and trade-secret materials through approved review channels.

Use the template

Use the IP Portfolio Acquisition Transactions — Material contracts comparison template below. You can copy this table into your working document or spreadsheet. Use one row per material agreement or distinct issue, with linked rows where different restrictions require different decisions.

“Assets / role” identifies asset IDs and whether the agreement supplies inbound rights, grants outbound rights, supports ownership, or restricts exploitation. “Rights / limits” captures exclusivity, territory, field, sublicensing, and enforcement control.

“Economics / survival” records payment obligations and post-termination burdens. “Transfer / exit” separates assignment, change-of-control, consent, termination, and cure provisions rather than reducing them to a transferability flag.

In “Evidence / status,” cite the document ID, clause, page, and schedule. Distinguish verified language, seller assertion, missing evidence, and counsel conclusion. “Buyer impact” connects the finding to intended use and severity. “Action / owner” records the response, responsible person, milestone, and disposition. Enter “not provided,” “not present in reviewed package,” or “not applicable” where appropriate; do not leave substantive fields ambiguously blank.

Step by step

1. Define the comparison perimeter

List the asset groups and intended uses that drive value. Distinguish ownership from permission to use supporting technology: a patent portfolio may depend on licensed know-how, while acquired software may contain third-party components.

Set inclusion criteria around those dependencies, exclusivity, payment obligations, transfer restrictions, and title support. Include settlement covenants, funding restrictions, and standards-related commitments where they affect the acquired rights. Do not rely exclusively on the seller’s revenue threshold.

Record: Asset IDs, agreement role, and the reason for inclusion in the first two columns. Identify contracts spanning purchased and retained businesses for allocation review.

2. Reconstruct each operative agreement package

Connect the signed base agreement to amendments, exhibits, incorporated terms, waivers, and notices. Compare party names with the selling entities. Identify apparent predecessor relationships without assuming that succession or authority is established.

Where provisions conflict, examine amendment and precedence language; the newest file is not necessarily controlling. Request schedules defining licensed patents, software versions, deliverables, customers, or territories. Distinguish a missing amendment from an amendment known not to affect the issue.

Record: Source citations, execution status, and package completeness. Mark provisional summaries and assign targeted requests. Keep superseded provisions in the supporting index rather than presenting them as current terms.

3. Map the rights granted and retained

Extract inbound and outbound rights separately. Compare exclusivity, territory, field, duration, sublicensing, affiliate coverage, improvements, enforcement control, and any covenant not to sue. Identify version, patent-family, and business-activity limitations. For trademarks and confidential know-how, capture contractual quality-control or access obligations where relevant.

Read representations with their qualifications. One SEC-filed purchase agreement separately addresses inbound and outbound licenses and qualifies patent enforcement and licensing representations through a closing license, permitted encumbrances, and disclosure schedules. That wording illustrates why the exceptions and underlying instruments need review; it does not establish market practice or prove an unrestricted portfolio. See Exhibit 2.1, §§2.10(g), (l).

Record: Granted and retained rights, relevant definitions, and their effect on the buyer’s plan. State competing readings where coverage remains uncertain.

4. Compare transfer and termination language against the structure

Review assignment and change-of-control provisions independently. Identify language addressing asset sales, mergers, affiliates, successors, partial assignments, consent standards, and exceptions. Check related definitions before deciding whether the proposed structure triggers a restriction.

Assess termination rights, cure provisions, and whether consent correspondence covers the transaction, rights, and selling entity actually involved. A counterparty’s general support does not establish consent scope. Likewise, permission to assign does not necessarily expand the substantive license grant.

Record: The trigger, exception, supporting evidence, and unresolved interpretation. Assign consent or clarification requests as needed. Reserve enforceability conclusions for analysis of the actual language, governing law, and transaction facts.

5. Compare title-support instruments without overstating their effect

Keep ownership instruments distinct from licenses. For US patents, §261 provides for assignment by written instrument. USPTO guidance explains that recordation is ministerial and does not determine an instrument’s validity or ownership effect. A registry entry therefore does not complete title analysis. See USPTO MPEP §301.

For copyright ownership transfers, §204(a) generally requires a writing signed by the owner or authorized agent, except transfers by operation of law. This does not establish a signed-writing requirement for every nonexclusive license. See Copyright Act §204.

For trademarks, §1060 addresses duly executed written assignments with associated goodwill and restricts assignment of intent-to-use applications before the specified use filings, subject to its ongoing-business successor exception. Application status and transferred-business facts matter. See 15 U.S.C. §1060.

Record: The claimed interest, supporting instrument, missing links, and asset-specific referral. Do not turn a document gap into a definitive ownership conclusion or expand this table into a complete chain-of-title exercise.

6. Compare economics and continuing burdens

Extract payment bases, minimums, reporting duties, audit rights, milestones, and continuing obligations. Distinguish contractual amounts from amounts requiring sales data or other inputs. Identify whether the burden relates to purchased assets, retained operations, or both.

Read termination effects alongside survival language. Capture continuing licenses, sublicenses, confidentiality duties, sell-off rights, and access obligations where addressed. A terminated agreement may still contain provisions requiring comparison.

Record: The formula, source, missing inputs, and commercial consequence. Assign calculations to the appropriate finance reviewer and label estimates separately. Cross-reference related contracts to avoid counting the same payment burden twice.

7. Turn differences into buyer decisions

Prioritize findings by their effect on the acquisition thesis. Separate information requests from commercial choices, consents, drafting responses, and specialist legal questions.

Trace each response to the evidence. A field restriction may require a negotiated release or revised valuation assumption; an incomplete contributor assignment may require additional title evidence. A stronger general representation does not itself supply missing rights or remove a counterparty restriction.

Record: Severity, proposed response, owner, milestone, and status. Link proposed changes to the affected asset definition, disclosure exception, covenant, or condition. Close a finding only when supporting evidence resolves it or an authorized buyer decision accepts the specifically identified uncertainty.

Worked example

Fictional scenario: Alder Quay Systems proposes an asset acquisition of a sensor-software and patent portfolio from Vale Circuit Labs. All parties, documents, amounts, provisions, and facts below are fictional. The buyer intends to deliver integrated software and license patents to US warehouse operators and equipment manufacturers.

The seller supplies three agreement packages and describes the portfolio as transferable and unrestricted. Counsel compares that assertion against the documents. “Verified” below means the cited language was checked, not that every legal consequence is resolved.

R01 changes the valuation discussion because the apparent field restriction bears directly on planned licensing. The missing amendment could affect that reading; counsel should not assume it removed exclusivity.

R02 requires separate decisions on transfer permission and operating scope. Consent alone may leave customer redistribution unresolved. R03 requires evidence matching code to assigned deliverables. The missing payment evidence is a separate factual gap; the table does not assume payment conditions the assignment without reviewing the language. These distinctions prevent three different problems from becoming one generic “IP risk.”

Common mistakes

• Comparing titles rather than grants. A development agreement may reserve licenses. Extract operative rights, not merely document labels.
• Treating absence as permission. Distinguish language absent from a complete reviewed package from an exhibit or amendment not supplied.
• Using one transferability flag. Separate assignment, change-of-control, termination, and operating-scope questions.
• Equating ownership evidence with unrestricted exploitation. Compare title instruments with outbound grants, retained rights, and supporting inbound licenses.
• Closing issues on reassurance. Preserve seller assertions, request supporting evidence, and identify who may accept residual uncertainty.

Final quality check

• Every material agreement maps to an acquired asset, dependency, or explained portfolio-wide restriction.
• Executed versions, amendments, schedules, and notices are linked or identified as missing.
• Substantive extractions have verified document, clause, and page citations.
• Inbound rights, outbound grants, and ownership instruments remain distinguishable.
• Transfer conclusions address the actual structure, parties, definitions, and exceptions.
• Economics distinguish contract terms, estimates, missing inputs, and overlapping burdens.
• Buyer impacts reflect intended products, fields, territories, and licensing channels.
• Open issues have owners and milestones; closed issues retain resolution evidence or documented risk acceptance.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional and tabular review capabilities support work across multiple documents, while due diligence classification can organize the document population and prioritize human review. Keep the comparison table as your team’s work product and retain counsel’s responsibility for verification, interpretation, and buyer decisions. To discuss applying these capabilities to portfolio licenses and title-support agreements, book a demo.

Frequently asked questions

Should each agreement have only one row?

Use one row for a coherent comparison. Create linked issue rows when separate assets, fields, or consent questions need different decisions or owners. Preserve the shared document ID and agreement-wide context.

How should we handle contracts covering retained assets too?

Separate purchased and retained coverage. Examine whether rights, payments, and permitted uses can be allocated under the language. Do not assume the seller can split the agreement; record any required consent or amendment analysis.

Can registry searches replace license review?

No. Copyright Act §205(e), for example, permits a signed nonexclusive license to prevail over a conflicting ownership transfer under specified conditions. A record search alone cannot exclude surviving licenses. Review the instruments and relevant timing and notice facts. See §205(e).

What if the seller cannot locate a schedule?

Identify which conclusion depends on it. Seek contemporaneous records without presenting them as the missing schedule. Assign counsel to assess their evidentiary value and the buyer to decide whether further evidence or a negotiated response is necessary.

Sources

• USPTO MPEP §301, including 35 U.S.C. §261.
• 15 U.S.C. §1060 — Trademark assignments.
• US Copyright Office, Copyright Act Chapter 2, §§204–205.
• SEC-filed Asset Purchase Agreement, Exhibit 2.1, §§2.10(g), (l). Illustrative negotiated wording, not evidence of 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.