How to prepare a contract diligence findings report for Patent License Agreements

Prepare a licensee-side patent license diligence report by establishing the operative documents, testing the grant against intended activities, and tracing material restrictions and obligations to specific clauses. Separate confirmed wording from legal interpretation and missing evidence. Prioritize findings by their effect on product rights, economics, compliance, and the proposed transaction. The deliverable should combine a concise decision summary, a source-supported findings table, and assigned actions for consents, amendments, investigation, or express risk acceptance.

When to use this workflow

Use this workflow when acquiring a business dependent on licensed patents, investing in a licensee, evaluating a proposed license, or reviewing an existing license before launch or restructuring. It is designed for IP counsel, transactional lawyers, and in-house teams reporting to business decision-makers.

Define the decision first. An acquisition report should emphasize transfer permissions and continuity; a launch report should emphasize product coverage, territory, manufacturing, and commercialization obligations. Keep the report focused on findings that affect that decision rather than producing an exhaustive clause digest.

This guide assumes US transactional practice. Federal patent law informs expiration-related royalty analysis, as discussed below. Other conclusions require the agreement’s language, governing law, and facts; material foreign rights require local analysis. These are recommended review procedures, not mandatory reporting requirements.

What you need

Obtain the executed license, patent schedules, amendments, side letters, incorporated documents, sublicenses, consents, and relevant notices. For a proposed license, identify the controlling draft and unresolved points. Preserve originals and assign document IDs and version dates.

Request product descriptions, intended fields or indications, sales territories, manufacturing arrangements, affiliate roles, distribution channels, and transaction steps. Without these inputs, the report can describe the grant but cannot assess its business fit.

Collect ownership and patent-status evidence, royalty workbooks, sales reports, milestone records, patent-cost invoices, and default or audit correspondence. Obtain the licensee’s review checklist, escalation thresholds, and materiality criteria. The checklist is the team’s own work product, not evidence of market practice.

Set a document cutoff and identify contacts in IP, finance, operations, and the deal team. Maintain a request list for missing material.

Use the template

Use the Patent License Agreements — Contract diligence findings report template below. Copy this table into your working document or spreadsheet. Use one material finding per row and link supporting workpapers where necessary.

In Source / evidence, record document ID, version, clause, page, and a short supporting extract. Reference patent schedules separately. For calculations, identify workbook cells and source inputs.

Limit Confirmed position to supported facts or wording. Put interpretation, missing schedules, and unverified business assertions under Gap / uncertainty. Clear language can still have uncertain application.

Explain priority through commercial impact, legal uncertainty, likelihood, and operational burden—not an unexplained color. Action / owner identifies a deliverable, responsible person, and decision point. Status / decision distinguishes investigation, approved mitigation, and accepted residual risk. Keep supporting extracts separate from reviewer conclusions.

Step by step

1. Establish the operative documents and review boundary

Reconcile the document index against amendment recitals, exhibit references, and the parties’ document lists. Determine which amendments replace definitions, update schedules, or modify selected provisions. Do not carry superseded language into the report.

Compare executed terms and schedules against the last approved draft where available, including signatures, numerical terms, and cross-references. Investigate missing attachments or unexplained differences without assuming their legal effect.

Put the business purpose, cutoff, and exclusions in the report header. Record material document gaps in the template, with request owners. The output is an identified review set, not an unsupported assurance of completeness.

2. Map the grant to intended products and activities

Read the grant with definitions of licensed patents, products, field, territory, affiliates, and sublicensing. Build a supporting schedule showing patent or application number, jurisdiction, family, owner, status source and date, and relevant term information. Check continuation, improvement, and after-acquired-right language rather than assuming related technology is included.

Test making, outsourced manufacturing, use, sale, distribution, and territorial expansion. Identify reserved rights and exclusions. Technical coverage questions may require a separate claim analysis; mark that dependency rather than resolving it from a patent title.

The University of Washington example limits its grant by product, territory, field, and expressly claimed inventions, and disclaims implied rights to other university technology (§3.1.1). Record both the clause and business activity tested. Do not turn an exclusivity finding into a conclusion about third-party patent rights.

3. Review permissions and continuity together

Read assignment, change-of-control, sublicensing, affiliate use, termination, and survival provisions together. Map each transaction step and the post-closing operating model against them. A headline description such as “stock acquisition” is not a substitute for reviewing the complete structure.

Separate permission requirements from fees, notices, and conditions. The Clyra example distinguishes discretionary approval for third-party sublicenses outside specified change-of-control transactions from sublicensing within those transactions (§3(d)). That is negotiated wording, not a default consent rule.

Record the trigger, interpretation, missing facts, and proposed response. Assign responsibility for any consent and specify whether resolution is needed before signing, closing, or changing operations.

4. Test economics and expiration dependencies

Reconstruct representative royalties using contractual definitions rather than finance labels. Trace deductions, affiliate sales, bundles, sublicense receipts, currency conversion, offsets, minimums, and patent-cost reimbursements where applicable. Reference calculation cells and disclose the sample’s limits.

Separate the royalty-generating period from the payment date. In Kimble, the Supreme Court retained the restriction on royalties for post-expiration use of a patented invention, while distinguishing deferred payment for pre-expiration use and payments tied to nonpatent rights (576 U.S. 446, 449, 453–454). A payment due after expiration is therefore not, by itself, enough to establish unenforceability.

Record the actual payment basis, term evidence, contractual step-downs, and any know-how allocation. Identify specialist analysis still required; a know-how label alone should not close the issue. Enter tested discrepancies and unresolved dependencies as separate findings when they require different actions.

5. Compare compliance obligations with performance evidence

Separate payment, reporting, development diligence, insurance, audit cooperation, and reimbursement obligations. Compare each material trigger with evidence of performance. Missing evidence creates an investigation gap, not necessarily a breach.

Do not collapse distinct deliverables. The Clyra example requires quarterly reporting and payment plus a separate licensee-funded annual independent accountant report (§§6(b)–(c)). The quarterly reports do not substitute for the annual report.

Read possible failures alongside default, cure, termination, notice, and survival provisions. Verify delivery methods, deemed receipt, and business-day definitions before calculating any response date. Record the obligation, evidence reviewed, missing proof, potential consequence, and remediation owner—not an unverified compliance certification.

6. Assess control, cost allocation, and mitigation

Review prosecution and maintenance control, abandonment notices, enforcement authority, litigation costs, warranties, indemnities, and liability limits. Ask what contractual options the licensee has if the licensor declines to maintain or enforce commercially essential rights, and who bears the expense.

Check termination treatment of inventory, sublicenses, accrued payments, confidential information, and necessary technology access. Connect each finding to the operating model instead of listing every unfavorable clause.

Propose a specific response: amendment, consent, additional evidence, operational control, transaction protection, or informed acceptance. Record the rationale and approval owner. Distinguish a preferred negotiating position from a requirement the team considers necessary to proceed.

7. Assemble the report and reconcile decisions

Lead with essential rights not established, permissions requiring resolution, material economic uncertainty, and compliance issues affecting continuity. Support each executive-summary statement with a findings-row reference.

Keep confirmed facts, counsel’s interpretation, and unanswered questions distinct. Reconcile duplicates across IP, corporate, and finance workstreams; retain linked rows where one issue has different legal and financial consequences.

Assign each open issue an owner, next deliverable, and decision point. Record who approved mitigation or accepted residual risk. The completed report should explain what the decision depends on, not merely inventory clauses.

Worked example

Fictional scenario: Larkspur Devices LLC proposes to acquire Alder Sensor Co., which licenses diagnostic-cartridge technology from Northline Research LLC. All parties, documents, clauses, and facts in this example are invented.

The review set includes signed license PL-01 and amendment PL-02. Business plan BP-01 adds veterinary use; structure paper TS-01 moves manufacturing to an acquisition affiliate. PL-01’s referenced patent schedule is absent. Finance index FI-01 lists quarterly reports but no annual accountant report. No default notice has been supplied; its absence from the review set does not establish that none exists.

The report changes the decision in three ways. Field expansion becomes a negotiation item rather than an assumed benefit of exclusivity. Manufacturing becomes a permission question requiring resolution before the operational move. Reporting remains an evidence request unless further facts support a default analysis. The missing schedule independently prevents confirmation of the licensed patent set; expanding the field would not cure that gap.

Common mistakes

• Treating schedules as administrative attachments. Obtain and reconcile them before concluding that essential patents are included.
• Reviewing permissions in isolation. Read transfer, sublicense, affiliate, and change-of-control provisions against every relevant transaction step.
• Calling every post-expiration payment prohibited. Identify the accrual period and actual consideration before stating the legal concern.
• Equating missing records with nonperformance. Request corroboration and distinguish absent evidence from an established failure.
• Delivering a clause digest without decisions. Pair material findings with consequences, proposed responses, owners, and approval points.

Final quality check

• Verify material conclusions against operative clauses, definitions, and source extracts.
• Confirm schedules and amendments are present, versioned, and correctly applied.
• Test coverage against products, territories, and operating participants.
• Reconcile royalty samples to contractual inputs and referenced cells.
• Separate facts, interpretation, missing evidence, and accepted risk.
• Check that agreement examples are not described as law or market standards.
• Resolve material open issues or assign owners, deliverables, and decision points.

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 diligence and prioritize human review; tabular review supports work across documents. For proposed amendments, contract review supports licensee-directed review in Word, with findings that quote and locate clauses, rank severity, and identify missing language as not present. Lawyers retain responsibility for source verification, interpretation, and the report. Book a demo to discuss this workflow.

Frequently asked questions

Should the report list every licensed patent?

Keep the complete available mapping in supporting workpapers. Summarize material coverage findings in the report and identify missing or unverified entries explicitly. Link findings to the relevant schedule rows.

Can an SEC-filed license supply missing terms?

Do not use it to fill gaps. It can illustrate wording, but even an exhibit involving the relevant parties should not be treated as proof of their complete operative arrangements without verification.

How should unresolved consent questions appear?

State the clause, transaction step, competing readings, and missing facts. Identify the resolution owner and whether consent, clarification, or another mitigation is required before the relevant decision.

Is this a freedom-to-operate opinion?

No. This workflow assesses the reviewed license and its business fit. Scope any requested third-party patent analysis separately, and do not imply that an exclusive grant answers that separate question.

Sources

The sources below support narrow legal propositions or illustrate contractual wording; the filed agreements are not market benchmarks or proof of current contractual completeness.

• Supreme Court, Kimble v. Marvel Entertainment, 576 U.S. 446, particularly 449 and 453–454.
• SEC Exhibit 10.7, University of Washington exclusive patent license, §3.1.1.
• SEC-filed Clyra license agreement, §§3(d) and 6(b)–(c).

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.