Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Map permitted rights by translating each planned use into a source-linked entry: the work and version, copying activity, delivery channel, audience, territory, and duration. Test reproduction and distribution separately against the grant, definitions, restrictions, schedules, and amendments. Record conditions, missing evidence, and approval needs instead of treating silence as permission. The resulting copyright rights matrix gives the licensee a practical decision record showing which uses have contractual support, which require clarification or additional rights, and who must resolve each gap before release.
When to use this workflow
Use this review when a licensee proposes a downloadable product, print run, new publication channel, affiliate rollout, or change to an existing content service. It also supports pre-signature review when the business needs an answer more precise than whether an agreement permits “commercial use.”
Licensing counsel and in-house legal teams lead the review, with product, publishing, and technical owners supplying operational facts. Keep it focused on permission for identified uses rather than expanding into a complete commercial-contract review.
This is a general US-oriented workflow, not advice for a particular matter. Contract interpretation, foreign exploitation, and specialized licensing regimes require separate analysis where relevant. Record contractual permission separately from any proposed reliance on a statutory exception; neither an unresolved matrix entry nor a contractual restriction alone establishes an infringement conclusion.
What you need
Obtain the operative agreement, signatures, asset schedules, incorporated policies, amendments, side letters, and written consents. Give each document a stable identifier and execution status. An unavailable schedule is an evidence gap, not proof that relevant language is absent.
Ask the business for a use specification identifying:
- Works, asset identifiers, versions, and embedded third-party material.
- Copies generated during ingestion, conversion, hosting, caching, printing, backup, and download.
- Delivery channels, recipients, geographic availability, quantities, and release dates.
- Vendors, affiliates, customers, and other actors handling content.
- Editing, translation, excerpts, resizing, and notice or metadata changes.
Obtain the licensee’s dated negotiation checklist, including preferred scope, acceptable fallback, escalation thresholds, and approvers. This is the team’s own work product. Assign unanswered technical questions rather than substituting assumptions about how the service operates.
Use the template
Use the Copyright License Agreements — Copyright rights matrix below. Copy this table into your working document or spreadsheet. Create one row for each materially distinct work-and-use combination; split rows when permission, actor, channel, or territory changes.
| ID / work | Planned use | Right tested | Scope limits | Source / text | Conditions | Status / uncertainty | Action / owner |
|---|---|---|---|---|---|---|---|
Planned use describes an activity, such as generating subscriber-downloadable PDFs. Right tested distinguishes reproduction from distribution and flags adjacent rights. Scope limits records medium, audience, territory, dates, quantities, and permitted actors.
In Source / text, record the document ID, clause, page, and a short exact extract. Keep longer passages, definitions, and execution details in a linked source log. Preserve stable row IDs when sorting.
Use four statuses: supported, conditional, unresolved, and outside grant. “Conditional” requires an identified permission and an identified compliance condition; uncertain interpretation remains unresolved. “Outside grant” describes the contractual scope conclusion, not a determination of infringement. Record confidence separately where useful. The final column identifies the action, accountable owner, and approval evidence.
Step by step
1. Establish the operative document set
Identify every document that could alter scope. Compare the executed agreement with amendments and incorporated schedules. Apply the document’s precedence provisions rather than assuming the latest filename controls. Match the asset list to the versions proposed for use.
Escalate ownership and signing-authority gaps. Section 101 includes exclusive licenses within copyright ownership transfers but excludes nonexclusive licenses. Section 204(a) generally requires a transfer, other than by operation of law, to be evidenced by a writing signed by the rights owner or authorized agent. It is not a blanket signature requirement for nonexclusive licenses. See §101 and §204(a).
Record: document IDs and execution status in the source log; mark affected matrix rows unresolved when missing evidence prevents a conclusion.
2. Translate operations into discrete uses
Trace receipt, conversion, storage, publication, delivery, and retention with the business owner. Identify where copies arise and who receives them. Distinguish internal access from customer downloads, and a printer making copies from a distributor selling them.
Check service-provider, sublicensing, and affiliate provisions rather than assuming an actor is covered because it assists the licensee. Determine whether geographic limits concern customers, access, sales, server location, or another defined measure. Record technical copy creation without assuming every transient process necessarily requires separate authorization.
Record: distinct uses with actor, medium, audience, geography, quantities, and dates. Assign unresolved architecture questions to a technical owner.
3. Test reproduction and distribution independently
Locate the affirmative grant, then follow definitions, reservations, and restrictions. Section 106 separately identifies reproduction, derivative-work preparation, and distribution to the public, with performance and display rights applying to specified work categories. These rights are subject to §§107–122. See §106.
For each activity, identify wording supporting copying and wording supporting delivery to intended recipients. For digital delivery, describe the actual operation rather than assuming the commercial label “distribution” resolves its legal classification. Route editing, public display, and performance questions for adjacent review; a reproduction grant does not answer them by itself.
Record: each right tested, supporting text, relevant restrictions, and preliminary status. Where grouped in one row, state the conclusion for each right separately.
4. Apply scope restrictions and downstream permissions
Intersect the grant with channel, territory, term, audience, exclusivity, quantity, and permitted-party limitations. Determine whether customers may view, retain, print, or redistribute content. Check whether affiliates and vendors receive direct permission, may act for the licensee, or require additional authorization.
The SEC-filed content license, §§3.1–3.2, illustrates separate channel, territory, sublicensing, affiliate, and modification restrictions, including prior written consent for editing. These are drafting examples, not statutory defaults or evidence of market practice.
Record: applicable limitations with citations. Split rows when different audiences or channels produce different conclusions. Preserve reservations rather than summarizing the grant as simply “exclusive” or “worldwide.”
5. Attach conditions to the permitted activity
Identify approvals, credits, notices, file specifications, and payment or reporting provisions expressly linked to permission. Test implementation on downloads, thumbnails, printed copies, and transformed files—not only the main website. Distinguish the existence of an obligation from the legal consequences of violating it.
The filed agreement’s §4.2 requires notices and source attribution with each content item. Separately, §1202(b)–(c) addresses copyright management information and specified removal or distribution conduct with mental-state requirements. A missing credit does not automatically establish a statutory violation.
Record: each condition, implementer, required evidence, and verification status. Leave the use conditional until the identified compliance requirements are confirmed.
6. Test duration and post-term uses
Compare permission with release, access, and retention periods. Read expiration, termination, removal, and survival provisions together. Examine unsold inventory, existing downloads, backups, and continued service separately. Do not infer a sell-off right from silence.
Contract duration also differs from statutory termination. Section 203 permits termination of qualifying author grants, subject to eligibility and timing requirements; works made for hire and grants by will are excluded. Escalate plausible issues rather than deriving statutory dates from the commercial term.
Record: permitted dates, express post-term treatment, and retention uncertainties. Assign specialist questions without treating every contractual termination or breach as an established infringement.
7. Resolve gaps and issue the decision matrix
Distinguish unavailable evidence, ambiguous wording, and an express restriction. Obtain missing documents, clarify ambiguity, or negotiate additional rights as appropriate. Do not use an internal business approval as a substitute for licensor permission.
Propose a correction covering the actual operation. A download addendum should address file creation, customer delivery, permitted recipients, territory, retention, and notices. Recheck definitions and cross-references after revisions.
Record: final status, business consequence, proposed response, owner, and approval reference. Date the matrix and identify the reviewed document versions and use specification. Keep unresolved entries visible even when launch is imminent.
Worked example
Fictional scenario: Cedar Quay Learning licenses 40 illustrations from Marlow Studio. Fictional executed agreement F1, §2.1, p.2, permits reproduction on a named training portal and display to US subscribers for two years. Section 2.4, p.3, excludes downloadable compilations. Schedule A lists the illustrations; §4.1, p.4, requires notices beside each image. A hosting-vendor provision refers to Schedule C, which has not been supplied.
The business proposes portal publication, downloadable lesson packets, and vendor-produced printed workbooks. Its portal mockup includes notices, but no print authorization or completed hosting review is available. All parties, documents, and terms are fictional.
| ID / work | Planned use | Right tested | Scope limits | Source / text | Conditions | Status / uncertainty | Action / owner |
|---|---|---|---|---|---|---|---|
| R1 / 40 illustrations | Vendor-hosted portal | Reproduction; display | Named portal; US subscribers; two years | F1 §2.1 p.2; §4.1 p.4; Schedule A; Schedule C unavailable | Notices; vendor authorization | Unresolved overall: portal grant supports reproduction/display, but vendor evidence is missing | Legal obtains Schedule C; product verifies notices before release |
| R2 / 12 illustrations | Downloadable lesson packets | Reproduction; distribution | Subscriber downloads | F1 §2.4 p.3 excludes downloadable compilations | Additional permission | Outside grant: proposed packets fall within stated exclusion | Legal seeks addendum; product holds downloads |
| R3 / 20 illustrations | Vendor-printed workbooks | Reproduction; distribution | Print; US recipients; quantities unconfirmed | F1 §2.1 p.2 grants portal use; no print permission in supplied record | Print scope and vendor role | Unresolved: supplied documents do not support print use | Publishing confirms quantity and recipients; legal requests print grant |
The matrix changes the release decision. Portal publication has affirmative support, but the proposed hosting arrangement remains unresolved; an identified permission cannot cure a missing vendor schedule. Downloads encounter an express exclusion. Printing lacks supporting evidence, which warrants a hold and further inquiry—not an invented prohibition. Any addendum must cover both making the workbooks and delivering them, including the printer’s role and agreed quantities.
Common mistakes
- Treating “digital rights” as a complete answer. Separate hosted viewing, downloads, redistribution, and editing; identify support for each.
- Stopping at the grant clause. Check definitions, restrictions, incorporated schedules, and amendments before assigning status.
- Combining all participants into “licensee.” Identify hosts, printers, affiliates, and recipients and verify their permitted roles.
- Calling an unavailable schedule “language not present.” Mark an evidence gap; reserve absence findings for the documents actually reviewed.
- Treating approval as expanded permission. Confirm that the consenting party has authority and that the consent covers the proposed use, not merely artwork appearance.
- Ignoring retained copies. Address inventory, customer downloads, backups, and continued access separately at expiration.
Final quality check
- Every proposed use has a stable row ID and identified work version.
- Reproduction and distribution have separate conclusions where relevant.
- Clause and page references match operative documents and amendments.
- Actors, channels, audience, geography, quantities, and dates match the use specification.
- Conditions have implementers and verification evidence.
- Missing documents, absent language, ambiguity, and express restrictions remain distinct.
- Open issues have owners and release decisions; unresolved uses are not shown as cleared.
- Final permissions reflect executed amendments or consents, not merely proposed language.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. In contract review, select the licensee as represented party in Word and provide the planned-use specification. Findings quote clauses, rank severity, locate text, and identify missing language as not present; counsel must distinguish those findings from unavailable schedules. Lawyers 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 and permission conclusions remain the team’s responsibility. Book a demo to discuss this review workflow.
Frequently asked questions
Does reproduction permission cover customer downloads?
Not by assumption. Identify file creation, delivery, retention, and onward use, then test the relevant grant and restrictions. Record the copying and delivery conclusions separately.
Should every illustration have its own row?
Group assets only when versions, source provisions, restrictions, and uses align. Split an asset with different ownership evidence, notice requirements, or permissions.
How should unclear affiliate permission be recorded?
Mark it unresolved. Identify the affiliate, intended activity, applicable definition, and restriction. Seek clarification or revised language rather than treating corporate affiliation as authorization.
Can the matrix clear post-term customer access?
Only when the reviewed record supports it. Distinguish the licensee’s continued service from customers retaining previously delivered copies. Record any relevant survival language and unresolved legal questions.
Sources
- US Copyright Office: Title 17, Chapter 1, §§101 and 106.
- US Copyright Office: Title 17, Chapter 2, §§203–204.
- US Copyright Office: Title 17, Chapter 12, §1202.
- SEC-filed Exhibit 10.1, §§3.1–3.2 and 4.2, cited only as an example of contractual wording.
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.
