How to build a clause extraction table for Copyright License Agreements

Build a licensee-side clause extraction table by mapping each intended use of copyrighted content to the operative grant, restrictions, conditions, and supporting documents. Preserve exact clause text and source locations separately from interpretation, then record uncertainty, required action, and an accountable owner. The resulting deliverable should show which works may be used, by whom, in which formats and territories, for how long, and subject to which obligations—without treating silence, missing schedules, or a proposed amendment as confirmed permission.

When to use this workflow

Use this workflow when reviewing a proposed copyright license, checking an executed agreement before launch, or comparing licenses across a content portfolio. It helps counsel distinguish activities that business teams may describe collectively as “content use”: hosting an image, cropping it, distributing a download, and allowing customer reuse present different extraction questions.

This is a US-oriented transactional workflow for practicing lawyers and in-house teams, not advice for a particular transaction. Federal copyright categories inform the review; contract interpretation depends on actual language, governing law, facts, and deal context. Foreign rights and specialized licensing regimes require separate analysis where relevant. The table records counsel’s analysis rather than independently authorizing deployment.

What you need

Collect the proposed or executed agreement, amendments, content schedules, incorporated policies, approval correspondence, and signature pages. Distinguish drafts from executed documents. Obtain the applicable incorporated policy version rather than assuming today’s webpage governed the deal.

Ask the business for:

• Work identifiers, versions, and content categories, including photographs, illustrations, video, music, or text.
• Planned copying, editing, translation, display, performance, downloads, and redistribution.
• Channels, territories, audiences, launch dates, and expected duration.
• Affiliate, hosting-provider, agency, and downstream customer activities.
• Payment model, reporting data, credit implementation, and removal capability.

Obtain the licensee’s review checklist, escalation criteria, and business owners. These instructions establish review priorities, not granted rights. Identify unavailable ownership or authority evidence rather than treating content delivery as proof of title.

Use the template

Use the companion Copyright License Agreements — Clause extraction table below. You can copy this table into your working document or spreadsheet. Create one row per distinct issue; split a clause when its permissions and restrictions produce different decisions.

Assign stable references such as CL-001. The document field should contain a unique ID, version, and execution status. Cite clause and page; for unpaginated documents, identify the section and paragraph.

Keep Exact text free of paraphrase. Place definitions, amendments, schedules, and related row references under Terms / dependencies. The Licensee reading should answer a business-use question, not simply repeat the clause.

Under Evidence / review, distinguish verified source text, unresolved interpretation, language not present in reviewed materials, and an unavailable document. Add reviewer initials and confidence where useful, distinguishing confidence in transcription from confidence in interpretation. Neither establishes the licensor’s ownership. Record a specific action, accountable owner, and required decision point in the final column.

Step by step

1. Establish the operative document set

Assign document IDs before extracting clauses. Identify signed versions, amendment effects, incorporated materials, and missing schedules. Read the priority provision before resolving inconsistencies; a later file is not necessarily an operative amendment.

Include signature and authority checks, particularly for exclusive rights. Section 101 includes exclusive licenses, but not nonexclusive licenses, within transfers of copyright ownership. Section 204(a) requires a transfer other than by operation of law to be evidenced by a writing signed by the rights owner or authorized agent. It does not impose that requirement on every nonexclusive license. See §101 and §204(a).

Record: document status, missing components, signature evidence, and unresolved authority questions. Link affected extraction rows to the missing material.

2. Convert the business plan into rights questions

Identify each work, version, actor, and activity. A learning application might require server copies, cropped thumbnails, full-screen display, offline downloads, and agency access. Do not reduce these to one “digital use” row.

Section 106 separately identifies reproduction, derivative-work preparation, and public distribution; public performance and display rights apply to specified work categories, subject to statutory limitations. Keep those categories distinct when testing a grant rather than assuming reproduction language answers adaptation or distribution questions. See 17 U.S.C. §106.

Record: a question for each material activity, including medium, territory, audience, duration, and actor. An unanswered row is more useful than an untested assumption.

3. Extract grants together with their boundaries

Read grants, definitions, reservations, exclusions, and schedules together. Separate exclusivity from scope: identify the works, rights, channels, territories, and duration covered. Preserve exceptions instead of reducing exclusivity to a yes-or-no label.

Check affiliates, sublicensing, vendor activities, editing, and customer permissions independently. The SEC-filed content license, §§3.1–3.2, illustrates separate restrictions on channels, territory, affiliates, sublicensing, and modifications. It illustrates drafting choices, not statutory defaults or market standards.

Record: exact grants and exceptions, linked definitions, the activity supported, and any unresolved permission. Where text is absent, identify the reviewed materials rather than claiming the entire transaction contains no permission.

4. Extract conditions affecting practical use

Capture approval requirements, credit placement, notice preservation, technical restrictions, and removal duties. Identify actor, action, trigger, timing, recipient, method, dependency, and completion evidence. Use linked rows where one clause contains several obligations.

Test implementation across desktop, mobile, thumbnails, downloads, and syndication. The filed agreement’s §4.2 requires notices and source attribution and prohibits alteration, removal, or obstruction of delivered notices. Extract those contractual duties without presenting them as universal copyright requirements.

Record: the condition, affected use, approval evidence, implementation uncertainty, and operational owner. Keep a requested relaxation separate from the obligation currently stated.

5. Link economics and remedies to licensed activities

Extract royalty bases, minimum payments, reporting, audits, warranties, infringement indemnities, liability limitations, and termination consequences. Preserve definitions and exceptions: “net receipts” alone does not explain a royalty calculation.

Link financial rows to scope rows where a new channel or customer use affects charges. For an indemnity, extract triggers, exclusions, defense procedures, and its relationship to liability limitations. Capture relevant wording and cross-references without turning the table into a complete negotiation memorandum.

Record: the economic or remedial provision, linked activity, interpretation, and reviewer. Flag whether counsel must assess breach, termination, or infringement consequences separately; do not collapse them into one exposure label.

6. Separate duration, removal, and statutory issues

Distinguish the agreement term, work-specific license periods, renewal, cure, takedown, and post-termination permissions. Extract notice addresses, methods, receipt rules, and relevant date definitions before calculating deadlines. Check express treatment of existing downloads, archives, backups, and previously distributed products.

Keep potential statutory termination separate. Section 203 addresses qualifying author-executed grants made on or after January 1, 1978, including exclusive and nonexclusive grants, with exclusions and detailed requirements. Works made for hire are excluded. A contractual expiration date alone does not answer eligibility or timing. See 17 U.S.C. §203.

Record: distinct triggers, notice dependencies, survival language, and any assigned specialist review. Do not derive a statutory termination date from the contract alone.

7. Verify and release the table

Compare material extractions against their sources, including negations, exceptions, and cross-references. Ensure shortened excerpts do not conceal qualifications. For scanned files, check extracted text against the image, particularly tables, handwritten changes, and schedules.

Normalize content category, license type, territory, and use case before portfolio comparison. Have a second reviewer check launch-critical rights and materially uncertain interpretations. After amendments, recheck dependent rows rather than updating only the changed clause.

Record: reviewer disposition, approved interpretation or escalation, and an owner for every open issue. Release a dated table identifying document versions and the business plan tested. Preserve unresolved questions visibly in any executive summary.

Worked example

Fictional scenario: Cedar Lantern Learning LLC plans to use 80 illustrations licensed from Harbor Finch Studio LLC in a US subscription application. The product team wants cropped thumbnails, full-size images, and downloadable lesson packs. The fictional signed agreement is CLA-01, version 1. Its Schedule A, intended to identify the illustrations, was not supplied.

All parties, documents, and excerpts below are invented. No written cropping consent has been supplied, and counsel has not reviewed underlying ownership evidence. The lesson-pack format remains undecided.

The table changes the launch decision. The display grant cannot clear unidentified assets. Cropping requires evidence of consent. Downloads require both a concrete format and analysis of the affirmative grant; avoiding standalone files does not itself establish authorization.

The deliverable is a conditional assessment with three assigned actions, not “license approved.” Missing ownership evidence remains a separate diligence issue, not a qualification invented from §2.1. If the schedule or consent arrives, update the evidence and dependent readings without overwriting the original agreement text.

Common mistakes

• Extracting only the grant paragraph. Read definitions, schedules, reservations, and amendments before summarizing scope.
• Treating “digital rights” as a complete answer. Test hosting, modification, display, downloads, and customer reuse separately.
• Calling an unavailable schedule absent language. State which document was not supplied; reserve “not present” for text absent from reviewed materials.
• Combining credit and editing permissions. Give modification approval, credit placement, and notice preservation separate rows and implementation checks.
• Recording requested changes as existing rights. Preserve current text and interpretation; label negotiation requests and update only against the resulting operative documents.

Final quality check

Before circulating the table, confirm:

• Every row identifies a document version, execution status, and retrievable location.
• Quotations, negations, exceptions, and cross-references match the source files.
• Every planned use has a supported answer or explicit unresolved question.
• Work identifiers match supplied schedules; unavailable schedules remain flagged.
• Scope, approvals, attribution, economics, and survival remain distinguishable.
• Legal propositions match their cited authority; filed agreements remain wording examples.
• Each open issue is resolved or assigned an owner and decision point.
• The release identifies the reviewed document set, business-use assumptions, and reviewer disposition.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional workflows include tabular review across multiple documents. In Word-based contract review, lawyers can choose the represented party and provide deal-specific instructions; findings quote clauses, locate text, rank severity, and identify missing language as not present. Counsel must verify documents, distinguish missing materials from missing language, and decide what the grant permits. To discuss this workflow for your license portfolio, book a demo.

Frequently asked questions

Should each agreement occupy one row?

Usually not. Use issue-level rows so reproduction, modification, distribution, and attribution can carry different evidence and decisions. A portfolio summary can reference those stable row IDs.

How much clause text should the table retain?

Retain enough operative wording to preserve permissions and qualifications. Split lengthy provisions into linked rows with precise citations rather than presenting an incomplete excerpt as the whole provision.

What if the agreement says nothing about vendors?

Identify the vendor’s actual activities and examine the grant, definitions, and restrictions. Record any unresolved permission question. Silence alone should not become a confirmed hosting, copying, or sublicensing permission in the table.

Can the table replace a redline?

No. The table records source language and analysis; a redline proposes changes. After negotiation, update from the operative documents so accepted requests are not mistaken for executed terms.

Sources

• U.S. Copyright Office, Title 17, Chapter 1: §§101 and 106.
• U.S. Copyright Office, Title 17, Chapter 2: §§203 and 204.
• SEC-filed Exhibit 10.1, content license agreement: §§3.1–3.2 and 4.2, illustrating contractual wording only.

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.