How to compare draft and executed versions for Patent License Agreements

Compare the executed patent license against the last approved draft using both a text comparison and visual review of the complete signing package. From the licensee’s perspective, prioritize changes to licensed patents, permitted activities, royalty calculations, sublicense rights, and termination consequences. Record each substantive difference with paired source references, its business effect, approval evidence, and an accountable reviewer. The deliverable is a version comparison checklist distinguishing approved changes, unexplained deviations, and missing evidence—not merely a redline showing different words.

When to use this workflow

Use this workflow when licensee counsel receives a signed patent license, assembles a closing record, or discovers that operating teams are using a different version from legal’s approved draft. It also supports acquisition diligence where negotiation records are available.

The task is to establish what changed at execution and whether those changes were authorized. It is not a fresh negotiation of every unfavorable provision or a freedom-to-operate assessment.

This general guide uses a US transactional perspective. Federal patent law may affect royalties; interpretation of other provisions depends on the actual language, governing law, facts, and deal context. Refer jurisdiction-specific questions arising from foreign patent schedules for appropriately scoped local review.

What you need

Collect the executed agreement, attached patent and financial schedules, signature pages, incorporated documents, amendments, side letters, and relevant consents. Obtain the last approved draft and its approval record—not simply the most recently modified Word file.

Also gather:

• The licensee’s negotiation checklist, approved fallbacks, and escalation owners.
• A product-and-use summary covering indications, territories, affiliates, manufacturers, distributors, and intended sublicensees.
• The approved patent schedule, including available identifiers, family relationships, ownership, and term information.
• Approved royalty assumptions, sample calculations, and allocations between patent and nonpatent rights.
• Correspondence explaining late changes, replacement schedules, and signing-package assembly.

Preserve originals and assign stable document IDs. Keep OCR and comparison copies separate. Record unavailable or redacted material as a gap rather than reconstructing supposed final terms from negotiations.

Use the template

Use the Patent License Agreements — Version comparison checklist below. You can copy this table into your working document or spreadsheet. Create one row per substantive difference or completeness issue; group presentational differences only after checking their effect.

In each source column, identify the document version, section, and page. For schedules, add the patent identifier or row reference because pagination may change. Put short exact excerpts or numerical values in “Difference / evidence”; keep interpretation in “Licensee effect.”

Identify the actual approval record and its scope. Silence in correspondence is not documented approval for purposes of this checklist. Use statuses such as approved, approval unverified, missing source, or resolved. Record severity separately in the effect field: an unresolved issue is not automatically high risk. Distinguish internal approval from any counterparty agreement needed to implement a correction.

Step by step

1. Fix the comparison baseline

Identify the draft that received final legal and business approval. Reconcile competing candidates through approval records, attachments, and later authorized revisions. File timestamps help locate candidates but do not establish authorization.

Inventory both packages before comparing them. Match the agreement body, patent schedule, royalty exhibits, development milestones, and signature pages. Check referenced exhibits, effective dates, party names, and whether signature pages belong to the identified agreement version. Separate amendments from differences introduced at execution.

Record: Add rows for missing components and disputed baselines, naming the person responsible for confirmation. Do not call a difference unauthorized before establishing the baseline.

2. Compare text and inspect the execution images

Run a comparison on working copies, then inspect the executed pages visually. Check handwritten edits, initials, blank fields, cut-off scans, footnotes, tables, signature-page identifiers, and attachment order. Verify decimal points, patent numbers, negations, and mathematical symbols against the images rather than trusting OCR.

Inspect moved text before dismissing it as formatting. Moving an exception outside a subsection may change its apparent application. Verify renumbered cross-references against their destinations.

Record: Capture paired references and the actual difference. Mark unreadable text for source confirmation; never silently substitute draft wording. Log apparently cosmetic changes that still require checking.

3. Reconcile the patent schedule and grant together

Match patent and application entries by identifier and jurisdiction, not title alone. Investigate additions, deletions, transposed digits, and changed treatment of continuations, improvements, or after-acquired rights. Test inclusion against the agreement’s definitions rather than assuming related applications are covered.

Trace each change through the grant’s field, territory, exclusivity, reserved rights, and permitted activities, including manufacturing arrangements. Section 3.1.1 of the University of Washington filed license illustrates a grant limited by Licensed Products, Territory, Field of Use, and expressly claimed inventions, with no implied grant to other university technology. Those provisions illustrate drafting dependencies, not market standards.

Record: Identify the affected product or activity, supporting schedule entry, and unresolved inclusion question. Keep the comparison’s scope distinct from third-party patent clearance.

4. Reperform the changed economic provisions

Compare rates, minimums, milestones, deductions, sublicense consideration, currency provisions, offsets, and patent-cost reimbursement. Trace changes to “Net Sales,” “Licensed Product,” “Valid Claim,” and similar definitions into payment clauses. Reperform an approved sample under both versions using identical assumptions.

Separate royalty accrual from payment timing. In Kimble v. Marvel, 576 U.S. 446, 453–454, the Supreme Court retained the restriction on royalties for post-expiration patent use while distinguishing deferred payment for pre-expiration use and discussing payments tied to nonpatent rights. A payment date after expiration therefore does not answer the question by itself.

Record: State the changed calculation, assumptions, and numerical effect. Assign patent-expiration and mixed-rights allocation questions to counsel; do not treat a “know-how” label as resolving them.

5. Trace consent, reporting, and exit changes

Review sublicensing, affiliate use, contract manufacturing, assignment, and change of control together. A definition change may narrow an exception without altering the consent clause. The Clyra filed license, section 3(d), illustrates distinct treatment of ordinary sublicensing, change-of-control transactions, and extinguishment of approval rights—not a default consent rule.

Compare reporting triggers separately from payment triggers. Check changed audit notice and dispute provisions, cure periods, development milestones, insurance, termination rights, and post-termination inventory or sublicense treatment. Review notice mechanics alongside deadline changes. Also inspect changed prosecution control, enforcement costs, indemnities, and liability limits where they affect the licensee’s exposure.

Record: Identify the affected transaction or obligation, its owner, and connected provisions. Carry changed obligations forward for implementation without expanding this exercise into a complete compliance program.

6. Resolve approvals and prepare corrective language

Match each substantive difference to approval evidence covering that change. Distinguish approval of a commercial concession from approval of its implementing language. Check connected consequences—for example, narrower sublicense rights combined with broader termination rights.

Preserve the executed document unchanged. Prepare any corrective redline in a separate working document clearly marked as proposed, identifying the executed version it would modify. Counsel should determine the appropriate correction, clarification, or amendment process from the agreement and circumstances. An internal approval entry does not itself change the signed text.

Record: Enter the approval reference, decision, proposed action, and accountable owner. Close the row only when supporting evidence satisfies its stated resolution criteria.

7. Issue a decision-focused comparison record

Review interaction effects before distributing the checklist. Several modest edits may collectively exclude a product, increase its royalty base, and shorten the opportunity to cure a reporting failure.

Provide a short summary identifying approved changes, material unexplained differences, missing documents, and required decisions. Link corrective language to checklist IDs. State which original files were compared and which documents were outside scope.

Record: Add resolution references and responsible reviewers. Preserve the comparison output with the checklist so another lawyer can reproduce a finding without rebuilding the review.

Worked example

Fictional scenario: Meridian Diagnostics LLC licenses assay technology from Alder Research Holdings for a US clinical laboratory product and planned contract manufacturing. Legal approved draft D7. Execution package E1 contains a narrower field definition, deletion of a freight deduction, and a replacement patent schedule. All parties, documents, provisions, identifiers, and amounts in this example are fictional.

An email expressly approves deletion of the freight deduction. No matching field-change approval has been located. Schedule row 4 contains a different application identifier, but the replacement schedule’s preparation history is unavailable. The shorthand identifiers below are internal example labels, not actual application numbers.

The royalty sample assumes $500,000 of otherwise eligible sales, $20,000 of qualifying freight, and no other adjustments. D7 produces a $480,000 base and $19,200 royalty; E1 produces a $500,000 base and $20,000 royalty. The freight amount is a calculation input, not a fixed contractual allowance.

The comparison changes the team’s priorities. The economic change has approval evidence; the shorter field edit may affect the intended use and needs immediate escalation. The schedule replacement remains unresolved. Neither the relationship between the applications nor the intended replacement can be inferred from the missing transmittal. Nothing identified so far establishes a change to contract-manufacturing permission, so that operating arrangement remains a contextual check rather than an invented fourth discrepancy.

Common mistakes

• Comparing only the agreement body. Match schedules and incorporated exhibits independently; portfolio scope and milestone amounts may change elsewhere.
• Treating the latest draft as approved. Anchor the baseline to approval evidence and isolate later authorized edits.
• Calling every difference a negotiation failure. Separate approved concessions, possible assembly errors, unresolved changes, and presentation-only differences.
• Treating an unchanged rate as unchanged economics. Recheck the sales base, product definitions, deductions, and sublicense receipts using identical inputs.
• Editing the executed file to reflect intended terms. Preserve the original and prepare a separately identified corrective proposal with an explicit resolution path.

Final quality check

• Both packages have stable IDs and a documented comparison baseline.
• Attachments, incorporated documents, and signature pages are matched or flagged.
• Material text differences are checked against original page images.
• Patent identifiers, financial figures, definitions, and cross-references are verified at source.
• Each substantive row separates extracted evidence from interpretation.
• Approval references cover the actual change and relevant dependencies.
• Open issues have named owners and next actions; closed issues have resolution evidence.
• The summary and corrective redline reconcile to the checklist without altering the executed original.

Complete the workflow with DecoverAI

DecoverAI’s contract review capabilities can support review of identified deviations. In Word, choose the licensee as the represented party and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes under the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across multiple documents; the checklist remains your work product. To discuss this workflow, book a demo, retaining lawyer control over verification, approvals, and corrective action.

Frequently asked questions

What if the last approved draft cannot be found?

Compare against the best-supported candidate, labeling the baseline provisional. Explain its selection and assign confirmation. Report textual differences without asserting that they departed from an approved bargain.

Should unchanged provisions appear in the checklist?

Include them when needed to explain a change’s effect. An unchanged grant may depend on a revised field definition or patent schedule. Avoid rows for unrelated unchanged provisions.

How should a scanned patent schedule be handled?

Verify identifiers against the image and approved schedule, not OCR alone. Request a clearer source for illegible entries. Record uncertain characters and assign verification before concluding that a patent was added or removed.

Does an approval email eliminate the need for review?

No. Confirm that it addresses the executed wording and connected effects. Approval of a higher royalty rate does not necessarily approve a broader sales base or changed patent-expiration treatment.

Sources

• Supreme Court: Kimble v. Marvel, 576 U.S. 446, especially 453–454.
• SEC-filed University of Washington exclusive patent license, §3.1.1.
• SEC-filed Clyra license agreement, §3(d).

The filed agreements illustrate particular wording, not market standards or the parties’ current contractual arrangements.

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.