How to compare draft and executed versions for Copyright License Agreements

Compare the executed copyright license against the last approved draft, including schedules, incorporated specifications, signature pages, and relevant amendments. Identify textual changes, then test whether each changes the licensee’s permitted uses, payment exposure, operating duties, or remedies. Record paired source citations, uncertainty, approval evidence, and corrective action in a version comparison checklist. The deliverable should distinguish approved changes from unexplained deviations and missing documents, with a clear decision on which planned uses can proceed and which require further approval or documentation.

When to use this workflow

Use this workflow when licensee counsel receives a signed copyright license, before licensed content launches, or when a transaction team discovers competing versions of an existing agreement. It is particularly useful when execution copies were assembled outside counsel’s document system or asset schedules circulated separately.

The task is reconciliation, not renegotiation of every provision. Establish what changed, whether it was approved, and how the executed language affects intended use. Escalate unchanged defects separately from version discrepancies.

This is a general transactional workflow using US federal copyright concepts. Contract interpretation and remedies depend on actual language, governing law, facts, and deal context; foreign rights and specialized licensing arrangements require separate analysis.

What you need

Collect the last approved native draft, complete signed file, signature records, exhibits, incorporated specifications, amendments, and correspondence authorizing final changes. Preserve originals and compare working copies. For an existing agreement, identify which amendments changed which provisions rather than treating the original signature date as the entire agreement history.

Obtain the licensee’s intended-use specification: works and asset identifiers, formats, channels, territories, audiences, editing requirements, vendor access, affiliate use, and launch dates. A narrowed grant cannot be evaluated reliably without knowing the planned activity.

Have commercial approvals available, including royalty assumptions, minimum commitments, reporting arrangements, and accepted exceptions. The licensee’s negotiation playbook is its own dated checklist of preferred positions, fallbacks, and escalation rules—not an assumed software feature.

Assign stable document IDs: D01 for the approved draft, E01 for the signed agreement, and A01 for an amendment. Keep provenance and approval records in a linked document register.

Use the template

The companion template is Copyright License Agreements — Version comparison checklist. Copy this table into your working document or spreadsheet. Use one row per material discrepancy or unresolved package issue; split changes requiring different decisions.

Include document ID, clause, page, and a short exact excerpt in each citation field. For schedules, add the asset identifier or row. Retain each version’s own pagination.

“Change / evidence” describes the difference and references its approval record. “Uncertainty” distinguishes ambiguous wording, unreliable extraction, and unavailable documents. Write “not present in E01” only after inspecting the complete relevant document; write “schedule unavailable” when the source itself is missing.

The action field identifies the required decision or corrective document and its owner. Record the approver, supporting evidence, and closure status in the final field. A signature is not a substitute for evidence of internal approval of a particular deviation.

Step by step

1. Establish the approved baseline and execution package

Identify the last draft actually approved by the licensee, not simply the newest filename. Match it to approval correspondence and record qualifications, such as approval subject to a revised asset schedule. If a last-minute change was separately approved, preserve that approval alongside the baseline rather than silently reconstructing an approved draft.

Inventory the execution package against its attachment list. Check party names, effective dates, signatures, handwritten additions, schedule versions, and incorporated specifications. Where a linked specification was incorporated, obtain the relevant version if available; do not assume today’s webpage reproduces it.

Record baseline and execution IDs in the checklist. Add rows for missing attachments, conflicting counterparts, or uncertain approval evidence. Do not assemble inconsistent counterparts into an apparently complete agreement without explaining the discrepancy.

2. Generate the comparison and verify material differences

Compare native text where available, then inspect signed PDFs visually. Treat OCR output as a working extraction requiring verification, especially for royalty percentages, territory names, dates, negations, and asset numbers.

Review every apparent material addition or deletion against both originals. Compare schedules independently: asset versions or image IDs may change while the main agreement remains identical. Check tables, footnotes, handwritten edits, and cross-references before dismissing a difference as cosmetic.

Record confirmed differences with paired citations. Mark extraction artifacts explicitly rather than leaving them indistinguishable from negotiated changes. If source quality prevents verification, assign a request for a legible copy and leave the issue open.

3. Test changes against the licensee’s intended uses

Compare works, exclusivity, permitted acts, media, channels, territory, audience, duration, and reserved rights. Trace definitions: unchanged grant wording can convey less if “Licensed Content” or “Authorized Users” has narrowed.

Section 106 separately identifies reproduction, derivative-work preparation, and public distribution rights; public performance and display rights apply to specified work categories, subject to statutory limitations. Do not assume a reproduction grant also authorizes every adaptation or public-facing use. See 17 U.S.C. §106.

Test concrete activities: cropping illustrations, translating captions, hosting through a vendor, distributing downloads, and allowing affiliate reuse. For exclusivity, compare its field, territory, duration, and licensor reservations rather than relying on the word “exclusive.”

Record the affected activity and proposed response in the checklist. Preserve uncertainty where contract interpretation remains unresolved; do not convert an ambiguous grant into a definitive permission statement.

4. Check execution-sensitive rights and supporting evidence

If exclusivity changed, identify the rights actually conveyed. Section 101 includes exclusive licenses within transfers of copyright ownership but excludes nonexclusive licenses. Under §204(a), a transfer other than by operation of law requires a written instrument, note, or memorandum signed by the rights owner or duly authorized agent. This is not a blanket statutory signature rule for nonexclusive licenses. See §101 and §204(a).

Compare the named licensor, signature capacity, works, and rights description. Treat ownership and authority as separate verification questions: record the supporting evidence available rather than assuming a matching signature page resolves them.

Enter unexplained licensor substitutions, changed exclusivity, and missing rights schedules in the checklist, with requested evidence and a reviewer. Keep execution questions separate from internal commercial approval.

5. Compare economics, operating duties, and remedies together

Review royalty bases, exclusions, minimum payments, reporting, audit rights, approvals, warranties, indemnities, liability limits, and termination consequences. An unchanged rate can produce different payments if the revenue base expands. Check whether a changed cap or exclusion also changes the protection expected from an indemnity.

For changed duties, identify actor, action, trigger, deadline, recipient, delivery method, and completion evidence. Compare attribution specifications, metadata handling, takedown obligations, and treatment of distributed copies after termination. Verify changed effective dates against fee commencement, license duration, and renewal language.

These are contract-specific checks. An SEC-filed content license, §§3.2(d), 3.2(f), and 4.2, illustrates separate editing-consent, removal, and attribution provisions; it establishes neither statutory defaults nor market standards.

Record the changed burden, business consequence, and operational owner’s feasibility assessment. Where a deadline changed, identify its trigger and notice requirements before recording a calendar date.

6. Reconcile each deviation with approval evidence

Classify material differences as approved negotiated changes, unexplained deviations, extraction errors, or unresolved interpretation issues. Link approval to the particular wording, not merely an email accepting the deal generally. “No approval located” describes the available evidence; it does not prove that approval never occurred.

Prioritize by effect on planned use, financial exposure, implementation difficulty, and reversibility. Deleted download permission may require a prelaunch decision; a revised reporting contact may require only an operational update. Keep contractual breach, termination, and possible infringement consequences as distinct analysis questions rather than assigning the same consequence to every discrepancy.

Record the response: accept with documented approval, seek clarification, obtain corrective documentation, or defer the affected use. Identify the authorized decision-maker and business decision date.

7. Close the comparison while preserving the executed record

Prepare a reconciliation summary identifying the baseline, execution package, material deviations, approvals, and unresolved items. Link each conclusion to checklist rows and source documents. State expressly whether package gaps prevent a complete comparison.

Do not overwrite the signed file to match the draft. Preserve it and prepare corrective wording separately for the appropriate documentation process. If an amendment resolves a discrepancy, compare that instrument against its approved draft and check that it addresses the intended works, provision, and effective period.

Update each row with resolution evidence, owner, and status. The review can finish with assigned open issues, but those issues are not substantively resolved merely because the comparison report is complete.

Worked example

Fictional scenario. Harborleaf Learning LLC licenses illustrations from Cedar Lantern Studio LLC for a subscription training site and downloadable course packs. All parties, documents, amounts, identifiers, and excerpts below are fictional.

D01 is the approved draft; E01 is the signed PDF. Both state a $36,000 annual fee. Launch is planned in three weeks, using cropped thumbnails and downloadable lessons. Available correspondence approves the fee and term but does not address these discrepancies.

The unchanged fee does not support an unchanged launch decision. R1 separates download permission from website use, but R2 prevents asset-level clearance for either channel until the schedule is obtained and checked. R3 requires consent or a revised production plan. Counsel cannot infer the executed schedule from D01 or treat the proposed thumbnail consent as already granted. Each row closes only on supporting evidence.

Common mistakes

• Using the latest circulated draft as the baseline. Match the draft to approval evidence and preserve conditional approvals.
• Reviewing only changed grant text. Trace definitions, asset schedules, reservations, and incorporated channel specifications.
• Calling an unavailable attachment a deletion. Distinguish an incomplete package from a verified textual omission.
• Accepting extracted differences without verification. Check numbers, negations, tables, handwriting, and references against originals.
• Treating signature or fee approval as approval of every deviation. Seek language-specific evidence and document unresolved approval questions.

Final quality check

• Baseline selection has an identifiable approval record or an explicit uncertainty designation.
• Execution documents and incorporated materials are accounted for or marked unavailable.
• Material differences have paired source citations and visual verification.
• Intended uses have been tested against changed grants, definitions, and reservations.
• Economic, operational, and remedial changes have been assessed together.
• Approval evidence supports each deviation marked accepted.
• Open issues have owners, required evidence, and stated effects on planned use.
• Corrective instruments are checked without overwriting the original executed record.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its contract review workflow in Word, counsel can select the licensee and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Counsel can edit or insert suggestions as ordinary tracked changes under the signed-in Word user’s name, or dismiss findings with reasons. Use these capabilities to support review and corrective drafting—not to alter the preserved executed record or replace source verification and legal judgment. Book a demo to discuss this workflow.

Frequently asked questions

Should every formatting difference appear in the checklist?

No. Retain the full comparison, but use the checklist for material differences and unresolved issues. Include formatting changes affecting meaning, attachment identity, numbering, or reliable interpretation.

What if the approved draft cannot be identified?

Mark the baseline uncertain, compare plausible candidates, and request approval evidence. Explain which conclusions depend on baseline selection. A difference from one candidate alone does not establish an unauthorized change.

Can an unchanged clause still require escalation?

Yes. Record it as an existing issue, not a version change. Both versions may omit planned affiliate use; that gap still requires a rights decision without distorting the reconciliation findings.

Can counsel simply correct the signed PDF?

Preserve the signed record. Prepare proposed wording separately and determine the appropriate corrective documentation. Close the issue on evidence of its resolution, not merely production of a cleaner working copy.

Sources

• U.S. Copyright Office, Title 17, Chapter 1, §§101 and 106: transfer definitions and distinct copyright rights.
• U.S. Copyright Office, Title 17, Chapter 2, §204: writing and signature requirement for copyright ownership transfers.
• SEC-filed Exhibit 10.1, §§3.2 and 4.2: illustrative editing, removal, and attribution provisions, not 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.