How to map licensed patents and fields of use for Patent License Agreements

Map licensed patents and fields of use by connecting each scheduled or definitionally included asset to the grant, defined products, permitted activities, territories, authorized entities, and exclusions. Test those connections against the licensee’s actual commercialization plan. The deliverable is a source-linked patent license scope matrix that separates supported conclusions from interpretation and missing evidence, identifies permission gaps, and assigns drafting or verification actions. A portfolio list alone is insufficient: the review must show whether the intended activity satisfies every relevant scope condition.

When to use this workflow

Use this workflow when licensee counsel receives a proposed patent license, reviews an amended portfolio schedule, or assesses whether a new product, indication, manufacturing arrangement, or distribution channel fits an existing grant. In-house IP teams can use the matrix to provide a qualified scope assessment without reducing conditional language to an unsupported “licensed” designation.

This is a US-oriented transactional workflow, not a validity opinion or complete freedom-to-operate assessment. Contract rights depend on actual wording, governing law, facts, and deal context. Identify foreign assets and activities separately for appropriate local review. The endpoint is a documented scope decision or an assigned unresolved question—not a complete license administration program.

What you need

Assemble the agreement, patent schedules, amendments, side letters, incorporated definitions, and relevant consents. Identify each document as executed, proposed, superseded, or incomplete. Do not treat a public exhibit as proof that the complete contractual record has been supplied.

Obtain a product-and-activity brief identifying intended indications, settings, users, manufacturing locations, sales destinations, distributors, affiliates, contractors, and proposed sublicensing. Include planned variants that could cross a field boundary.

Request jurisdiction-specific patent and application identifiers, family relationships, ownership information, status evidence, and available term analysis. Separate supplied assertions from verified facts. Obtain the licensee’s negotiation checklist: preferred scope, acceptable fallback, escalation threshold, and approval owner. That checklist is the team’s review standard, not evidence of existing rights.

Use the template

Patent License Agreements — Patent license scope matrix

Copy this table into your working document or spreadsheet. Use one row per asset-and-use question. Split rows when jurisdictions, activities, entities, or exceptions require different conclusions.

Assign document IDs and versions. In Source / text, record the clause, schedule, and page or paragraph reference, with a short exact excerpt or reference to an extraction note. Keep contractual wording separate from interpretation in Assessment / gap.

Status / term should identify the evidence date and verification dependencies. Acts / entities names both the activity and the entity performing it. Territory / limits captures geographic boundaries, reservations, and exceptions. Action / owner identifies the required evidence, decision, or edit, accountable reviewer, and approval status.

Use four assessment labels: supported, conditional, unresolved, or outside stated scope. Explain each classification. Cross-reference related rows rather than copying a conclusion that depends on different facts.

Step by step

1. Establish the controlling document set

Assign IDs to the agreement and every schedule, amendment, consent, and incorporated document. Check cross-references against materials received. Identify conflicting schedule dates, absent attachments, unsigned amendments, and redactions before assessing coverage.

Determine document priority from the contractual record rather than assuming the newest file overrides every earlier provision. Preserve competing readings if priority remains unclear.

Record in the matrix: the governing source version for each row, the document supporting any amendment, and missing materials assigned for collection. Distinguish an unsigned proposal from an operative provision.

2. Normalize the patent inventory without expanding it

Transcribe identifiers exactly, then organize patents and applications by jurisdiction and family. Keep separate entries where status, ownership evidence, or inclusion conditions differ. Family membership aids comparison; it does not replace the contractual inclusion analysis.

Read the licensed-patent definition for continuations, divisionals, continuations-in-part, improvements, foreign counterparts, and after-acquired rights. Tie inclusion to the stated conditions. An unscheduled asset may be included by a definition, while a related asset may remain excluded.

Record in the matrix: the identifier, family reference, status and ownership evidence, and contractual inclusion basis. Where inclusion is uncertain, identify the exact condition needing confirmation rather than automatically requesting a schedule amendment.

3. Translate the grant into separate scope conditions

Read the grant alongside definitions of licensed patents, licensed products, field, territory, and any valid-claim requirement. Separate permitted acts from restrictions. Do not let “exclusive” obscure the boundaries of the rights granted.

For example, §3.1.1 of the University of Washington agreement limits its exclusive grant by Licensed Products, Territory, Field of Use, and expressly claimed inventions, and disclaims implied grants to other university technology. Sections 1.6–1.7 and 1.15 supply related patent, product, and claim definitions. This illustrates interlocking conditions, not a universal drafting formula.

Record in the matrix: each controlling condition and citation. Mark the conclusion conditional when an unresolved definition determines the answer. Do not present contractual exclusivity as a freedom-to-operate conclusion.

4. Test concrete products and uses against the field

Ask technical and commercial owners to describe actual uses before translating them into contractual terms. Distinguish an instrument from its consumable, research from clinical use, and a current indication from an anticipated expansion.

Test borderline cases explicitly. If the field covers diagnostic applications, ask whether a proposed treatment-selection service fits the actual definition. Do not decide from the product name. Where coverage depends on claimed inventions, obtain patent counsel’s claim-to-product assessment; distinguish that analysis from whether the asset is contractually included.

Record in the matrix: the product configuration, indication, setting, supporting business input, and field conclusion. Identify the technical assessment relied on or assign it as outstanding.

5. Map entities, activities, and territories together

Trace who will make, commission manufacture, use, offer for sale, sell, import, or distribute each product. Check authorization for affiliates and contractors rather than treating them as interchangeable with the named licensee. Test manufacturing locations and sales destinations separately.

Distinguish direct authorization, have-made rights, and sublicensing permission. Check restrictions on subcontracting, permitted recipients, consent, and downstream rights. Do not assume every distributor needs a sublicense or that every manufacturer is authorized; preserve the agreement’s definitions and exceptions.

Record in the matrix: each material entity/activity/location combination, its authorizing provision, and any consent dependency. If the arrangement changes, retest the row rather than carrying forward the earlier assessment.

6. Check reservations and time-dependent boundaries

Read exclusions and reserved rights alongside the grant. Identify whether they qualify exclusivity, permitted activity, or both. Separate agreement duration from asset-level status, patent-term evidence, and any contractual valid-claim conditions.

If scope mapping reveals an expiration issue, refer the payment basis for separate review. Kimble v. Marvel, 576 U.S. 446, 449, 453–454 (2015) retained the rule against royalties for post-expiration use of a patented invention, while distinguishing deferred payment for pre-expiration use and discussing payments tied to nonpatent rights. A payment date after expiration is therefore not enough to classify the payment; a know-how label alone does not resolve its basis.

Record in the matrix: the affected asset and use, reservation or temporal condition, evidence date, and any separate payment-analysis referral. Do not calculate patent expiration from an unsupported spreadsheet entry.

7. Resolve gaps and issue the scope assessment

Review unresolved rows with patent counsel, transaction counsel, and the business owner. Prioritize by launch dependence and consequence: unresolved manufacturing permission may need attention before a peripheral future-use question.

Propose edits to the provision causing the problem. Expanding the product definition may not fix a narrow field; adding a patent may not authorize an affiliate. Retest linked conditions after revisions and distinguish proposed language from approved or executed language.

Record in the matrix: final classification, evidence request or proposed edit, decision owner, and approval status. Deliver a short summary identifying supported uses, conditions, and decisions that must precede the contemplated activity.

Worked example

Fictional scenario: Cedar Vale Diagnostics LLC proposes to license sensor technology from Northmere Research LLC. All parties, documents, asset labels, and clauses in this example are fictional.

Draft D1, §2.1, authorizes the licensee to make, use, and sell products in the United States for hospital-based monitoring of adult respiratory conditions. Schedule A lists patent P-01 and application A-02. Section 1.6 includes continuations only when added by written amendment. The supplied draft does not expressly address independent contractors.

Business brief B1 describes a hospital monitor, a home-use variant, and independent US assembly of a revised hospital monitor. Licensor email E1 identifies A-03 as a continuation relevant to that revision, but supplies neither an amendment nor supporting application records. No claim-to-product assessment or current patent-status evidence has been supplied.

The hospital product needs evidence and technical confirmation, not necessarily broader field language. The home-use variant needs a field change if it remains in the commercialization plan. The revised monitor presents two separate questions: whether A-03 is included and whether contractor assembly is authorized. Resolving one does not resolve the other. The email establishes neither A-03’s status nor its claim relationship to the product.

Common mistakes

• Treating a family list as the license definition. Identify the inclusion language and its conditions for every relied-on asset.
• Equating exclusivity with unrestricted use. Test product, field, territory, acts, and reservations independently.
• Using product names as field analysis. Compare the actual indication, setting, user, and activity with the definition.
• Collapsing entities into licensee operations. Identify affiliates, manufacturers, distributors, and sublicensees separately, with their permission basis.
• Closing a gap after one redline. Retest linked definitions, schedules, exclusions, and consents; confirm whether the revision is operative.

Final quality check

• Every relied-on asset has a precise identifier and cited inclusion basis.
• Source excerpts match the identified version and clause.
• Missing, redacted, unsigned, and conflicting materials remain visible.
• Technical conclusions identify supporting assessments or assigned reviewers.
• Product, field, activity, entity, and territory conditions have been tested together.
• Reservations and material status or term uncertainties are recorded.
• Open issues have owners and decision paths; unresolved coverage is not presented as confirmed.
• The delivered matrix distinguishes proposed fixes from approved or executed changes.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support this review: in Word, select the licensee as the represented party and provide deal-specific instructions. Findings quote clauses, locate text, rank severity, and identify missing language as not present. The lawyer can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across documents; the matrix remains your work product. Retain legal and technical judgment over scope. Book a demo to discuss this workflow.

Frequently asked questions

Does a scheduled patent establish product coverage?

No. Distinguish asset inclusion from the grant’s product, field, activity, entity, territory, and claim-related conditions. Obtain the technical assessment needed to support the conclusion.

How should we handle future continuations and improvements?

Extract the inclusion mechanism and conditions. Identify whether inclusion follows from the definition or requires an amendment, ownership condition, or other event. Do not infer it from shared technology.

Should every country have a separate row?

Split rows when assets, activities, evidence, or restrictions differ. Group only where the conclusion remains clear for each jurisdiction, including manufacturing and importation questions.

Can we issue the matrix with missing status evidence?

Yes, as a qualified assessment with explicit unresolved entries. Identify dependent conclusions, assign verification, and obtain the responsible decision-makers’ determination whether the uncertainty prevents the contemplated activity.

Sources

• University of Washington exclusive patent license, §§1.6–1.7, 1.15, and 3.1.1: definitions and interlocking grant limitations.
• Kimble v. Marvel, 576 U.S. 446, 449, 453–454 (2015): patent-expiration royalty distinctions.

The filed agreement illustrates particular wording, not market standards or the parties’ complete current arrangements. The decision does not resolve every mixed-rights payment question.

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.