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
Summarize material deviations by comparing the complete trademark-license draft against the licensor’s dated standard terms and approved deal instructions, then translating each consequential change into a decision. The deliverable is a source-linked deviation summary identifying the baseline, proposed departure, affected marks and licensed uses, practical consequence, recommended response, approval owner, and residual uncertainty. Prioritize changes to brand control, license scope, economics, and exit rights rather than reporting every textual difference. Keep unresolved evidence gaps separate from confirmed concessions.
When to use this workflow
Use this workflow when licensor counsel receives a licensee markup, prepares an internal exception request, or checks a near-final draft against negotiation approvals. In-house intellectual-property teams can use the summary to obtain focused decisions from brand, quality, finance, and commercial owners without circulating an unexplained redline.
The scope is review and decision support, not ongoing administration or an enforceability opinion. The orientation is US trademark practice; foreign territories require separate local-law consideration. Actual language, governing law, facts, and deal context affect interpretation and remedies. Flag franchise, competition, tax, bankruptcy, or foreign recordation questions separately when implicated. The steps below are workflow recommendations, not statutory requirements.
What you need
Collect the current draft, prior comparison version, amendments, schedules, side letters, incorporated brand guidelines, and written approvals. Include mark, product, territory, channel, royalty, and sell-off schedules—not merely the agreement body.
Establish a dated licensor baseline containing preferred wording, permitted fallbacks, prohibited concessions, and approval owners. This is the team’s own negotiation checklist and instructions, not an assumed software feature. If no approved form exists, counsel must identify the working baseline before labeling language a deviation.
Obtain deal context: exclusivity expectations, planned distribution channels, approved manufacturers, expected sublicensees, and the licensor’s capacity to review samples or inspect facilities. Record unavailable documents rather than treating them as reviewed.
Use the template
Use Trademark License Agreements — Deviation summary as the decision record. Copy this table into your working document or spreadsheet. Keep operative extracts and detailed comparisons in supporting notes linked by row ID.
| ID / topic | Source / status | Baseline | Departure | Impact / priority | Response | Decision owner | Residual issue |
|---|---|---|---|---|---|---|---|
In Source / status, identify the document version, clause, page, and whether the change is confirmed or evidence remains incomplete. Cite the corresponding baseline clause in Baseline. Describe the operative change, including exceptions, rather than saying “nonstandard.”
Use Impact / priority for the consequence and escalation level. Distinguish brand-control concerns, commercial preferences, drafting ambiguity, and unresolved legal questions. Response states the preferred correction and any authorized fallback. Record the approver’s decision and date alongside their role in Decision owner. Residual issue preserves remaining exposure or an assigned question, including the next required input.
Step by step
1. Fix the comparison set and document hierarchy
Assign stable IDs to the licensor form, licensee draft, schedules, and incorporated materials. Confirm which versions belong together. Check precedence language before deciding whether body text overrides a schedule.
For example, the Honeywell–Solstice agreement gives attachments priority over inconsistent agreement text in § 17.2. That is an agreement-specific hierarchy, not a universal rule. Honeywell–Solstice, § 17.2.
Record comparison versions in the template’s source field. Create a gap row for any unavailable potentially controlling document, with an owner responsible for obtaining it. Do not characterize an apparent conflict as resolved until the hierarchy and relevant documents have been checked.
2. Map the grant before evaluating individual concessions
Identify each mark or logo variant, licensed product or service, territory, channel, exclusivity provision, reserved use, and sublicense permission. Compare that map with the baseline and deal instructions. A definition change can expand several operative provisions simultaneously.
Separate online accessibility from authorized targeting or sales. The AT&T–DIRECTV agreement distinguishes territorial rights, limited US investor-focused and compliance uses, and qualifying digital uses accessible outside the territory. Accessibility is not unrestricted authorization. AT&T–DIRECTV, §§ 2.01–2.02.
Record each material scope departure with the affected marks, products, and territories. If a schedule is missing, state which part of the grant cannot yet be compared; do not imply the entire grant is necessarily unknown.
3. Assess changes to practical quality control
Compare product approvals, packaging review, sampling, inspection access, corrective action, subcontractor supervision, and sublicensee compliance. Ask whether a restriction would impede the licensor’s intended control in this deal—not simply whether an inspection clause exists.
The federal definition of a related company turns on the owner’s control over the nature and quality of the relevant goods or services, not corporate affiliation alone. 15 U.S.C. § 1127. Section 1055 conditionally 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 inspection wording. 15 U.S.C. § 1055.
Record the restriction, operational consequence, proposed correction, and implementation evidence needed. A weakened provision warrants analysis, not an unsupported conclusion that trademark rights have already been lost.
4. Identify linked economic and exit effects
Review ownership and goodwill, ownership challenges, registrations, enforcement control and costs, assignment, royalties, audit rights, indemnities, insurance, termination, and sell-off provisions. Read definitions and exceptions together.
A royalty-base concession may become more significant when paired with restricted audit access. A sell-off extension may matter more if quality controls or reporting cease at termination. Summarize the combined effect in one row where it requires one decision; use linked rows where different owners must decide.
Record baseline citations, the changed allocation, and the commercial dependency. Where useful, quantify exposure using identified deal assumptions, not invented market percentages. If the baseline supplies no approved sell-off duration or royalty position, request instructions rather than inventing a standard.
5. Rank materiality and formulate the response
Assess legal exposure, brand impact, economic impact, likelihood, and detectability. Apply priority labels consistently: an approval blocker prevents sign-off under current instructions; a negotiation issue needs a response but may have an authorized fallback; a clarification needs evidence or drafting resolution.
Explain why the issue matters to this license. “High risk” without a consequence is not decision-ready. An unauthorized concession is not necessarily a legal defect: identify whether the concern is legal, commercial, operational, or evidentiary.
Record preferred language or a drafting instruction, an authorized fallback if available, and the approving role. Where research is needed, frame and assign the question. Do not present a provisional theory as settled law or treat a reviewer’s proposed fallback as already authorized.
6. Verify the evidence and reconcile approvals
Re-read every cited clause with its definitions, exceptions, and cross-references. Check the visual document where tables, scans, or formatting could obscure changes. A finding of missing language should mean absent from the reviewed set, not absent from an unavailable attachment.
Test related mechanics. Cure rights may depend on effective notice. Honeywell–Solstice § 17.4 conditions effective email notice on prompt specified duplicate delivery or written receipt confirmation, excluding automated replies. Those mechanics belong to that agreement. Honeywell–Solstice, § 17.4.
Record verification status and reconcile each accepted concession against the actual approval, including conditions. Business acceptance should not silently resolve an outstanding legal question.
7. Produce a decision-focused summary
Lead with approval blockers, requested exceptions, and unresolved evidence gaps. Keep accepted deviations visible with conditions and residual exposure. Move immaterial edits to supporting comparison notes.
State which version the summary covers. Before circulation, confirm that subsequent drafting has not changed the summarized concession. Each open row should end with a decision request, owner, and next required input. If signature versions later change, update affected rows before relying on the summary. The result should distinguish “reject,” “accept subject to conditions,” and “cannot decide yet.”
Worked example
Fictional scenario: Aster Vale Brands LLC proposes to license its ASTER VALE mark to Juniper Basin Goods Inc. for reusable drinkware sold through approved US retailers. All parties, documents, clauses, and facts below are fictional.
Aster Vale’s baseline, Form L-4, requires written approval for new channels, permits routine and cause-based inspections, and limits sell-off to approved finished inventory. Juniper’s draft D-7 adds marketplace rights, caps inspections, and expands sell-off eligibility. Schedule C, referenced as the inventory schedule, was not supplied. The commercial team wants wider distribution but has not approved marketplace sales. No fallback has been authorized for these changes.
| ID / topic | Source / status | Baseline | Departure | Impact / priority | Response | Decision owner | Residual issue |
|---|---|---|---|---|---|---|---|
| 01 / Channels | D-7 § 2.2, p. 4; confirmed | L-4 § 2.2: approved US retailers | Adds marketplaces without separate consent | Blocker: exceeds channel instructions | Restore written approval; request platform list | Commercial lead and IP counsel; pending | Platforms and targeting controls unknown |
| 02 / Inspections | D-7 § 6.3, p. 9; confirmed | L-4 § 6.3: routine and cause-based access | One inspection annually; no cause exception | Blocker: may prevent repeat inspection after a quality concern | Restore cause exception; confirm corrective-action linkage | IP counsel and quality lead; pending | Quality lead to verify workable access process |
| 03 / Sell-off | D-7 § 12.4, p. 17; incomplete set | L-4 § 12.4: approved finished inventory only | Adds work in process; references Schedule C | Evidence hold plus confirmed eligibility expansion | Obtain schedule; propose finished-inventory restriction | Commercial lead and IP counsel; pending | Inventory quantities and categories unverified |
The summary changes the decision from “approve three drafting exceptions” to two approval blockers and one issue combining a confirmed departure with an evidence hold. Marketplace authorization requires a scope decision. The inspection cap requires an operational assessment of repeat access, not a prediction that control has already failed. The missing schedule prevents quantifying sell-off exposure, but it does not erase the confirmed expansion to work in process. Counsel can negotiate that restriction while requesting the schedule.
Common mistakes
- Treating a filed agreement as the standard. Use the approved licensor baseline. Filed examples illustrate wording, not market acceptance or suitability.
- Summarizing only changed sentences. Trace definitions, schedules, sublicense provisions, and survival language before describing the effect.
- Equating contractual rights with implementation. Identify operational evidence needed and obtain the quality team’s assessment.
- Calling missing material a concession. Distinguish an unavailable brand manual from a confirmed deletion of compliance obligations.
- Recording acceptance without limits. Preserve conditions, fallback boundaries, approver identity, decision date, and approved version.
Final quality check
- Every row identifies the reviewed version and clause or page location.
- Baseline positions trace to dated instructions or approved form language.
- Grant analysis covers marks, goods or services, territories, channels, and sublicensing.
- Exceptions, hierarchy provisions, and incorporated documents have been checked.
- Consequences distinguish legal questions, commercial preferences, and evidence gaps.
- Responses preserve conditional approvals and identify authorized decision owners.
- Sources support the stated propositions; open issues are resolved or explicitly assigned before sign-off.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. For contract review, choose the licensor as represented party in Word and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. 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; counsel verifies sources, the baseline, and conclusions. To assess this workflow for your team, book a demo.
Frequently asked questions
What counts as standard terms if the licensor has several forms?
Choose the form appropriate to the goods, distribution model, and deal structure, then record approved deal-specific departures. Do not combine favorable clauses from unrelated forms into an undisclosed baseline.
Should every difference appear in the summary?
No. Preserve the full comparison separately. Include changes affecting decisions, exposure, operational feasibility, or confidence in the review. A short deletion may be material; extensive wording changes may preserve the approved position.
Is an annual inspection limit automatically unacceptable?
No. Evaluate exceptions and the complete control structure. AT&T–DIRECTV § 3.02 illustrates an annual limit with an exception where the licensor reasonably believes Article III was breached. This negotiated clause is not a legal safe harbor. Agreement, § 3.02.
Can business approval close a quality-control deviation?
It records commercial acceptance within the approver’s authority. Counsel should separately address legal concerns and confirm operational feasibility with the quality owner. Keep those decisions distinct where implementation evidence or controlling documents remain unavailable.
Sources
- 15 U.S.C. § 1055 — Related-company use.
- 15 U.S.C. § 1127 — Trademark definitions.
- AT&T–DIRECTV Trademark License Agreement, §§ 2.01–2.02 and 3.02.
- Honeywell–Solstice Trademark License Agreement, §§ 17.2 and 17.4.
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.
