How to extract obligations with source references for Trademark License Agreements

Extract trademark-license obligations by establishing the controlling document set, separating duties from permissions, and recording each duty as an actor, action, trigger, deadline, recipient, and evidence requirement. Link every record to its operative clause and dependencies, including mark schedules, brand standards, approval procedures, and notice provisions. From the licensor’s perspective, the deliverable is a source-linked obligations register for quality-control administration, royalty oversight, and the licensor’s own commitments. It should distinguish verified wording, calculated dates, unresolved interpretation, and documented performance rather than treating contractual rights as proof of compliance.

When to use this workflow

Use this workflow when an executed trademark license passes from deal counsel to brand management and finance, an amendment changes licensed products or territories, or existing records lack reliable clause references. It serves licensor counsel and in-house teams extracting administrable duties—not renegotiating the entire agreement.

The US federal context explains the emphasis on quality control. Section 1127 defines a related company through the trademark owner’s control over the nature and quality of the relevant goods or services, not corporate affiliation alone. Examining implementation evidence alongside contractual mechanisms is therefore a practical review priority, not a statutory inspection schedule. See 15 U.S.C. § 1127. (govinfo.gov)

This is a general US-oriented workflow. Contract interpretation, notice effectiveness, and remedies require analysis of the agreement, governing law, and facts. Refer foreign-law, franchise, competition, tax, or bankruptcy issues for separate analysis when implicated.

What you need

Collect executed counterparts, amendments, mark and product schedules, territorial definitions, side letters, incorporated brand manuals, and sublicense documents. Include any separation or transition agreement supplying definitions or priority rules. Record unavailable documents explicitly.

Obtain operational evidence separately: artwork submissions, approvals, samples, inspection reports, complaints, royalty statements, payment records, notices, and delivery confirmations. These establish events or performance; they do not replace the contractual source.

Assign stable document IDs and identify brand, finance, and legal owners. Define whether extraction covers current, contingent, and post-termination duties. Retain superseded wording for historical periods without presenting it as current. Fix an assessment date so “pending” and “overdue” statuses have a clear reference point.

Use the template

Use the Trademark License Agreements — Obligations register below. You can copy this table into your working document or spreadsheet. Maintain one row per independently actionable duty, restriction, administratively relevant right, or unresolved extraction issue; label its type.

Use stable row IDs, not spreadsheet row numbers alone. Source / text should identify document/version, section, PDF page, and exact operative wording. Keep longer extracts in a source log keyed to the row ID; cite definitions, exceptions, and schedules there too. Distinguish printed page numbers from PDF pages.

Actor → recipient identifies contractual entities, while Owner / next action assigns internal responsibility. Action / scope identifies affected marks, goods, territory, channels, or sublicensees. Due rule / date preserves the formula alongside any calculation. In Evidence / status, distinguish wording verification from performance status and link supporting records by document ID. Record uncertainty and its resolution task rather than hiding it in a general confidence score.

Step by step

1. Establish the controlling document baseline

Index execution status, effective dates, versions, and document relationships. Compare the final draft with the executed set, visually checking schedules, signatures, tables, and scanned pages. Verify extracted text against the image where OCR may distort dates, negatives, or numbers.

Read priority provisions before resolving inconsistencies. Honeywell–Solstice § 17.2 gives attachments priority over inconsistent agreement text and the license agreement priority over conflicting Separation Agreement provisions. That hierarchy belongs to that document set. See the filed agreement, § 17.2. (sec.gov)

Record: controlling document IDs and source gaps. Mark affected rows provisional until missing or conflicting sources are resolved.

2. Map license scope to the duties

Link each mark or logo variant to authorized goods, services, territories, channels, exclusivity, and sublicense permissions. Keep this map concise: its purpose is to qualify obligations, not produce a separate grant analysis. A carton-approval duty may cover one product family but not another.

Do not equate internet accessibility with territorial authorization. AT&T–DIRECTV §§ 2.01–2.02 distinguish territorial rights, limited US investor-focused uses, and digital uses subject to targeting conditions. See the filed agreement, §§ 2.01–2.02. (sec.gov)

Record: scope and schedule citations in affected rows. Separate conflicts or unavailable schedule entries from confirmed restrictions.

3. Separate duties, rights, conditions, and restrictions

Identify the operative verb and contractual actor. A licensor’s right to request samples differs from the licensee’s duty to deliver them after a qualifying request. An approval-response duty differs from a prohibition on launching without approval. Do not convert inspection discretion into a mandatory annual visit.

Extract licensor commitments deliberately: approval responses, maintenance, cooperation, enforcement communications, and reimbursement administration where present. Split compound clauses when actions have different triggers, recipients, or deadlines. Retain prohibitions as restrictions rather than forcing them into completion dates.

Record: typed entries with exact wording, actor, recipient, and action. Pure permissions without an administration task can remain in the scope map.

4. Trace definitions, exceptions, and cross-references

Follow dependencies until each entry can be administered without guessing. For royalties, capture the base, deductions, reporting period, currency, and relevant audit qualifications. For approvals, identify completeness requirements, applicable standards, permitted channels, and exceptions for unchanged materials.

Extract inspection access and sublicense supervision separately. AT&T–DIRECTV § 3.02 limits inspection frequency subject to an exception and requires reasonable cooperation; § 6.02 allocates sublicensee quality compliance and licensee monitoring responsibilities. These illustrate negotiated allocations, not a universal supervision model. See §§ 3.02 and 6.02. (sec.gov)

Record: dependency citations and exceptions beside the qualified action. Identify precisely which standards remain unresolved if an incorporated manual is missing.

5. Establish triggers before calculating dates

Classify timing as fixed, recurring, event-triggered, or indeterminable. Preserve the contractual period. Check day definitions, counting provisions, receipt rules, required copies, delivery methods, addresses, and any applicable governing-law issue before calculating. Do not import procedural deadline rules into contract administration without a basis.

Notice mechanics can change the trigger. Honeywell–Solstice § 17.4 conditions effective email notice on prompt duplicate delivery through another specified method or written receipt confirmation; automated replies do not qualify. See § 17.4. (sec.gov)

Record: formula, event evidence, calculation assumptions, and verified date. If receipt or submission completeness is unproved, assign an evidence task rather than inventing certainty. Keep payment and reporting dates separate when the clauses differ.

6. Specify evidence and internal responsibility

Define what would demonstrate performance. Artwork approvals should identify the version and permitted use. Sample records should identify product and packaging versions. Royalty records should connect statements, calculations, and payments. Distinguish requesting inspection access, completing a visit, and closing corrective actions.

Section 1055 provides that legitimate related-company use benefits the registrant or applicant without impairing validity, provided the use does not deceive the public. It does not prescribe particular inspection language. See 15 U.S.C. § 1055. Keeping implementation evidence is a workflow recommendation, not proof that any particular control program is legally sufficient. (govinfo.gov)

Record: expected evidence, available evidence IDs, performance status, and accountable internal owner. Describe absent implementation records as evidence gaps unless further analysis supports a breach conclusion.

7. Verify and release the register

Reopen each source clause and its dependencies. Prioritize launch restrictions, approvals, quality controls, royalty reporting and payment, sublicense supervision, cure periods, and sell-off conditions. Check extraction completeness section by section; explain exclusions in the source log.

Have a second reviewer check consequential or ambiguous entries. Reconcile duplicate rows without merging distinct actors or triggers. Record later amendments through versioned updates rather than overwriting historical duties needed for earlier reporting periods.

Record: verification status, reviewer role, assessment date, and unresolved questions with owners. Release only when each material uncertainty is resolved or expressly assigned for follow-up.

Worked example

Fictional scenario: Alder Beacon Brands LLC licenses the invented ALDER BEACON mark to Cedar Reach Goods Inc. for two insulated-bottle models in the United States. All parties, documents, clauses, and events below are fictional. The assessment date is October 13, 2026.

Executed agreement TL-01, Schedule A, lists Models A and B. Its fictional § 1.3 counts calendar days beginning the day after the triggering event, without weekend adjustment. Section 12 excludes routine artwork submissions and sample requests from formal-notice requirements. Section 1.6 makes compliance with incorporated Manual M part of submission completeness, but Manual M is missing. The brand team asks whether its carton response, samples, and quarterly statement are overdue.

The evidence supports two future deadlines, not three overdue tasks. O-01 requires urgent clarification: if the October 2 submission was complete, the response was due October 12 under the fictional counting rule. The missing manual prevents a reliable completeness conclusion; it does not suspend the contractual clock. Obtain the manual and submission evidence promptly. O-02 and O-03 are pending as of October 13. None is completed without its own evidence, and the reporting clause supplies no payment deadline.

Common mistakes

• Treating inspection rights as completed supervision. Separate the right from requests, visits, and corrective-action evidence.
• Using one row for incompatible product scopes. Split entries when schedules change applicable standards or duties.
• Copying a deadline without receipt mechanics. Preserve the formula and verify the triggering event.
• Extracting only licensee duties. Check licensor approvals, maintenance, cooperation, and reimbursement commitments.
• Treating a missing manual as no requirement. Identify affected entries and seek the source; uncertainty does not stop time.

Final quality check

• Each row identifies actor, action, recipient, and affected license scope.
• Each source reference retrieves the controlling version and supports the extract.
• Definitions, schedules, exceptions, and priority rules are reflected.
• Calculated dates retain formulas and verified trigger evidence.
• Duties, rights, restrictions, and evidence gaps remain distinguishable.
• Completion rests on performance evidence, not wording verification.
• Material open issues have owners and specific resolution tasks.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support clause checking: in Word, choose the licensor as the represented party and give agreement-specific instructions. Findings quote clauses, locate text, rank severity, and identify missing language as not present. Tabular review supports work across multiple documents. Your team maintains the register and verifies sources, interpretation, triggers, and dates. Book a demo to discuss this workflow.

Frequently asked questions

Should every inspection right become a scheduled task?

No. Extract the right, conditions, and limits. Keep internally scheduled reviews separate from contractual duties, with their policy basis clearly identified.

How should amended mark schedules affect existing rows?

Identify affected entries, preserve historical sources, and update scope from the verified amendment. Check its effective date against pending approvals and reporting periods.

Can a missing approval record establish unauthorized use?

Not alone. Record the evidence gap, check the requirement and exceptions, and seek submission, approval, and actual-use records before reaching a conclusion.

Should sell-off duties be extracted before termination?

Yes. Record contingent inventory limits, channels, reporting, continuing quality standards, and timing formulas where present. Activate dates only after verifying the contractual trigger and dependencies.

Sources

• 15 U.S.C. § 1055: conditional treatment of related-company use.
• 15 U.S.C. § 1127: related-company definition.
• AT&T–DIRECTV Trademark License Agreement: negotiated scope, inspection, and sublicense provisions.
• Honeywell–Solstice Trademark License Agreement: negotiated priority and notice provisions.

Research scope: October 13, 2026. Filed agreements illustrate wording, not market standards or enforceability.

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.