How to build a clause extraction table for Trademark License Agreements

Build a trademark-license clause extraction table by fixing the document set, separating each operative permission or restriction into a traceable row, and recording the definitions, exceptions, and cross-references that change its meaning. From the licensor’s perspective, prioritize licensed marks, grant boundaries, quality control, sublicensing, ownership, economics, and exit rights. The deliverable is a verified table, supported by a document register, that lets counsel compare provisions and identify gaps without replacing the agreement with an oversimplified summary. Each material entry should connect source text to an identified reviewer decision.

When to use this workflow

Use this workflow when licensor counsel receives an executed license for administration, reviews a proposed license, or compares agreements during portfolio diligence. A concrete trigger is a request to identify which marks, products, territories, or sublicensees a license actually covers when those boundaries appear across several documents.

The task is extraction: establish what the documents say, how provisions interact, and what remains uncertain. Negotiation, legal assessment, and obligation tracking may follow, but should not overwrite the source record.

This guide uses a US federal trademark-law orientation. Contract interpretation and remedies depend on governing law, facts, and deal context. International territories and issues involving franchise regulation, competition, tax, bankruptcy, or foreign recordation require separate analysis when implicated.

What you need

Collect the proposed or signed agreement, amendments, schedules, side letters, incorporated brand manuals, written approvals, and provisions establishing document priority. Include attachments identifying marks, registration references, territories, products, services, permitted channels, and approved sublicensees.

Assign stable document IDs and record version dates and execution status. For scans, retain page images alongside searchable text: logos, schedule tables, and handwritten changes may not survive text extraction accurately.

Have the licensor’s own review checklist available, covering exclusivity, reserved uses, quality control, ownership, royalties, enforcement, assignment, termination, and sell-off. This checklist guides coverage; it does not establish what the agreement contains. Define the extraction scope before starting—for example, all operative provisions or selected grant and control provisions. Request implementation records separately if the assignment includes examining actual approvals, inspections, or monitoring.

Use the template

Use the Trademark License Agreements — Clause extraction table below. Copy this table into your working document or spreadsheet. Add rows rather than forcing independently qualified rights into one cell.

Give each row a stable identifier, such as GR-01 for a grant or QC-01 for an inspection right. Cite the section and PDF page when available, distinguishing PDF pagination from printed pagination. Preserve relevant wording in “Operative text”; put interpretation in “Scope / dependencies,” not inside the quotation.

Link defined terms to their source locations or separate definition rows. The scope field captures affected marks, products, territories, exceptions, and cross-references. Longer dependencies can occupy linked rows.

Distinguish verified text, ambiguous, missing source, and not located in reviewed set. Verification means the extraction matches the source, not that the provision is legally sufficient. Record reviewer initials and verification date in the status field; identify unresolved interpretation separately. The final field specifies the evidence or decision needed and its owner.

Step by step

1. Establish the controlling document set

Create a document register before extracting clauses. Distinguish executed copies from drafts, identify amendment relationships, and list referenced attachments. Do not substitute the newest available brand manual for the version incorporated by the agreement. If incorporation permits later revisions, extract that mechanism too.

Read any priority provision rather than assuming the main body controls. Honeywell–Solstice § 17.2, for example, gives attachments priority over inconsistent agreement text and gives the license priority over conflicting Separation Agreement provisions. That is this agreement’s hierarchy, not a general rule (filed agreement, § 17.2).

Record: baseline and hierarchy rows, document IDs, execution status, and missing-source requests with owners. Keep superseded wording identifiable but outside the current extraction view.

2. Break the grant into separately testable permissions

Extract licensed marks and logo variants, licensee identity, products or services, territory, channels, exclusivity, reserved uses, and duration. Give materially different permissions separate rows. Link each grant to the schedule supplying its boundaries; distinguish existing marks from any mechanism adding future marks.

Digital accessibility requires a separate check from territorial authorization. AT&T–DIRECTV distinguishes an exclusive territorial license from a limited nonexclusive US investor-use license and permits certain digital uses accessible outside the territory subject to targeting conditions (filed agreement, §§ 2.01–2.02). Normalizing those permissions as “worldwide online use” would lose material distinctions.

Record: one row per distinct permission, retaining reserved uses and territorial or channel qualifications. Flag unavailable mark or product schedules rather than inferring their contents.

3. Extract quality-control mechanisms as operational provisions

Separate standards, pre-use approvals, sample requests, inspections, complaints, corrective action, and suspension rights. Capture the actor, trigger, available access, response requirements, and limits. Link standards to the incorporated manual and identify whether approval rights cover products, packaging, advertising, or each separately.

The statutory definition of a related company turns on the owner’s control over the nature and quality of associated goods or services, not simply corporate affiliation (15 U.S.C. § 1127). Section 1055 conditionally provides that legitimate related-company use benefits the registrant or applicant without impairing validity when the use does not deceive the public (15 U.S.C. § 1055). Neither provision supplies a model inspection clause.

Record: separate rows for each control mechanism and its constraints. If operational review is within scope, request supporting records; a contractual entitlement does not demonstrate its exercise.

4. Connect sublicensing, ownership, and enforcement provisions

Extract whether sublicensing requires consent, which recipients qualify, whether further sublicensing is permitted, and who remains responsible. Distinguish a permitted sublicensee from a manufacturer or distributor that may use the mark only under a different authorization. Follow cross-references into quality standards and termination provisions.

AT&T–DIRECTV § 6.02 illustrates allocations concerning sublicensee quality compliance and licensee monitoring, enforcement, and responsibility (filed agreement, § 6.02). Preserve comparable allocations when present without treating that wording as mandatory.

Record: linked rows for sublicense consent, compliance responsibility, goodwill allocation, ownership challenges, registration restrictions, infringement notification, enforcement control, and costs. Missing approvals are evidence gaps, not established unauthorized conduct.

5. Preserve economic formulas and exit dependencies

Extract royalty definitions together with deductions, exclusions, currency provisions, reporting periods, minimums, and audit qualifications. Separate payment obligations from reporting and verification mechanisms. Do not reduce a defined royalty base to “sales” if the definition changes what counts. Preserve formula wording and identify each input’s source.

For termination, extract triggers, cure qualifications, notice dependencies, and consequences separately. Link sell-off rights to eligible inventory, duration, quality obligations, payment duties, and stated exclusions. Capture assignment restrictions, indemnities, and insurance provisions using the same source-first approach.

Record: formula inputs and qualifications, not unverified calculations. For event-based periods, retain the trigger and timing language rather than inventing a calendar date. Include licensor obligations, such as approvals or cooperation, where stated.

6. Normalize topics without flattening conditions

Apply consistent topic names across agreements while retaining agreement-specific wording. “Inspection right” is a useful category; “unrestricted inspection” is inaccurate if frequency, access, or cause conditions apply. Compare genuinely similar deal categories and keep exceptions visible.

Notice provisions require similar care. Honeywell–Solstice § 17.4 conditions email effectiveness on prompt duplicate delivery through another specified method or written receipt confirmation, excluding automated replies. Extracting only “email permitted” loses the qualification (filed agreement, § 17.4).

Record: normalized topic, exact condition, linked dependency rows, and status. Use “not located in reviewed set” only after checking relevant available documents and cross-references; identify the boundaries of that reviewed set.

7. Verify the table against the documents

Check each material row against its source, surrounding sentences, and incorporated definitions. Visually inspect mark images, schedule boundaries, footnotes, handwritten changes, and scanned pages. Reconcile amendments before marking text verified. For a draft-to-execution review, replace draft citations with executed-source citations and recheck changed dependencies.

Keep extraction accuracy distinct from legal sufficiency. Correctly transcribing an inspection cap does not resolve whether the overall control arrangement is adequate. Section 1127’s abandonment definition includes owner conduct or omissions causing a mark to become generic or lose its significance as a mark; missing inspection records alone do not establish that result (15 U.S.C. § 1127).

Record: reviewer initials, verification date, and unresolved actions. Close actions only when supporting evidence or a documented decision is recorded. Deliver the table with its register and bounded open issues.

Worked example

Fictional scenario. Alder Quay Brands LLC licenses the fictional TIDELARK word mark to Beacon Tableware Inc. Counsel receives signed agreement TL-01 and incorporated Brand Manual BM-01, but not referenced Schedule B. TL-01 § 1.2 defines Approved Products as ceramic mugs, § 1.3 defines Territory as Oregon and Washington, § 1.4 defines Contract Year, and § 1.8 identifies the word mark. The business team describes an exclusive regional license with routine quality checks.

All parties, documents, definitions, and excerpts below are invented.

The table changes three decisions. Counsel should qualify the exclusivity description because the licensor retains direct website sales. The brand team should investigate the complaint condition and implementation records before describing inspection access as generally available or exercised. The missing schedule prevents a reliable list of eligible sublicensees but does not establish that any particular sublicense is prohibited. The verified clause and its unresolved dependency remain separately visible.

Common mistakes

• Combining every grant into one row. Separate product, territory, channel, and reserved-use differences so comparison does not conceal restrictions.
• Copying text without definitions. Link modifying definitions and schedules before normalizing scope or economics.
• Treating missing attachments as absent rights. Assign retrieval and defer the substantive conclusion.
• Equating quality language with implemented control. Separate contractual mechanisms from operational evidence.
• Turning extraction into an unmarked opinion. Keep quotations, interpretation, uncertainty, and recommended action distinct; assign legal questions for analysis.

Final quality check

Accept the table when these checks pass or exceptions have assigned owners:

• The register identifies versions, execution status, amendments, incorporated materials, and unavailable items.
• Material quotations match cited sections and pages, including qualifications.
• Mark variants, products, territories, channels, exclusivity, and reserved uses remain distinguishable.
• Quality-control and sublicense rows preserve triggers, limits, and responsibility allocations.
• Royalty, notice, cure, and sell-off entries retain definitions and dependencies.
• Verification identifies the reviewer and date without implying legal sufficiency.
• Public-source propositions match their authority; filed examples are not characterized as legal requirements or market standards.
• Each ambiguity or evidence gap is resolved or expressly assigned with a next action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities support work across multiple documents; due diligence classification can help organize a license collection and prioritize human review. The table above remains your work product, with lawyers verifying citations, resolving hierarchy, and assessing significance. To discuss this extraction workflow, book a demo.

Frequently asked questions

Should the table contain exact language or summaries?

Use operative language plus a clearly separated summary. Preserve qualifications and split lengthy provisions into linked rows where that improves verification. A summary alone is insufficient for a disputed exception or formula.

How should logo images and registration schedules be handled?

Cite the schedule and image location, identify each variant, and verify it visually. Do not assume a word-mark grant includes every stylized logo or that registration references resolve contractual scope.

Does every missing provision require a finding?

Record gaps relevant to the assignment, distinguishing unavailable documents from language not located after review. Whether to add a provision is a separate licensor decision informed by the transaction and applicable law.

Can one row represent several licenses?

Maintain separate source rows for each license and version. A comparison view may group equivalent topics, but retain individual citations, exceptions, and verification status so differences remain auditable.

Sources

• 15 U.S.C. § 1055 — Related-company use.
• 15 U.S.C. § 1127 — Trademark definitions and abandonment.
• AT&T–DIRECTV Trademark License Agreement — §§ 2.01–2.02 and 6.02.
• Honeywell–Solstice Trademark License Agreement — §§ 17.2 and 17.4.

Scope: general professional workflow guidance using the supplied research cutoff of October 13, 2026. Filed agreements illustrate negotiated wording, not enforceability, suitability, or 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.