Field-of-use drafting: what the decision maker looks at

A decision maker checks three things in a field-of-use clause: whether the described use is measurable, whether it matches the commercial deal actually agreed, and whether it can be policed once the licence runs. Clauses built on open verbs and undefined channels create most disputes. A clause naming a product, a market segment and a route to market survives negotiation.

What the review actually covers

Reviewers do not read a field-of-use clause in isolation. They read it against the grant clause, the exclusivity carve-out and the term. A definition that looks precise on its own can still fail if it contradicts the scope stated elsewhere in the same agreement.

Element checked	Why it matters	Typical drafting failure
Product or technology scope	Sets the outer boundary of permitted use	Naming a category instead of a specific product line
Territory and channel	Determines where and how the use is exercised	Using a regional label without a defined list of countries
Duration and renewal trigger	Fixes when the field of use can be revisited	Silence on whether scope survives automatic renewal
Exclusivity carve-outs	Shows whether the licensor kept parallel rights	Carve-out drafted after the grant clause, creating a conflict
Sub-licensing rights	Confirms whether the field of use passes down the chain	No statement on whether sub-licensees inherit the same limits

When the licensed use overlaps with a registered mark, the same boundary logic applies as in Evidence of acquired distinctiveness, where scope and proof are drafted together rather than in sequence.

Where ambiguity creates risk

A clause that permits use "in the healthcare sector" without listing products invites two readings: one narrow, one broad. Both sides usually assumed a different reading at signature. The dispute rarely appears at signature. It appears when the licensee launches a product the licensor never expected to see under that clause, months or years later.

If the underlying right is jointly held, the risk doubles. A field-of-use clause granted by one co-owner without the consent of the other can be challenged on the ownership side rather than the licence side. The mechanics of that challenge are set out in Joint ownership in ownership of results: how it is.

Field-of-use language written for a token-based product raises a separate problem. A buyer of a token is not automatically the rights holder over the licensed asset behind it, and drafting that assumes otherwise fails on delivery. That distinction is explained in Crypto services — when the buyer of a token.

Drafting stages and who does what

The commercial team lists every intended use case in writing before drafting starts.
Counsel converts each use case into a defined term with an objective, checkable boundary.
Both parties confirm the definitions against the deal actually negotiated, not the term-sheet shorthand.
The drafting party circulates a mark-up showing where field-of-use limits touch exclusivity and sub-licensing clauses.
The receiving party flags any use case left outside the definition before signature, not after.
Both sides sign off on a schedule that lists covered uses and excluded uses side by side.

Turnaround at each stage is tracked internally against the same weekly cadence shown on Delivery statistics, published automatically overview step by step, so delay is visible before it becomes a deadline problem.

Who decides and how a stalled clause moves forward

During negotiation, the commercial leads on each side decide first. Counsel reviews language, but scope decisions are business decisions dressed in legal wording. If the parties cannot agree on a boundary, the point of no return is the signature date: after signature, the clause governs unless the contract's own amendment mechanism is used.

Once a dispute over scope exists, the forum is whatever the agreement names for disputes generally — negotiation window, then the escalation or dispute-resolution mechanism set out in the contract itself. A field-of-use disagreement rarely needs a separate forum from the one already agreed for the licence as a whole.

Common scenarios

If the licence covers software distributed to end users, define the install base and the update cadence explicitly, not by reference to "current version".
If the deal spans several territories, list each territory by name rather than using a regional label that can be read two ways.
If a scope dispute already exists, treat the field-of-use wording as evidence of intent at signature, not only as a forward-looking limit.

What this page does not resolve

This page describes drafting practice, not a template clause and not a pricing schedule. It does not cover the tax treatment of cross-border licensing income, and it does not set out national contract-law requirements for a specific jurisdiction. Those points need separate review once the jurisdiction is fixed.

Frequently asked questions

How long does field-of-use drafting take in practice?

Drafting usually runs alongside term-sheet negotiation rather than after it. A single round is enough when the use cases were listed before drafting started. Additional rounds follow whenever a new use case surfaces during negotiation.

Which documents are needed to start?

Start with the term sheet, a written list of intended use cases, the prior licence if this is a renewal, and an organisational chart if sub-licensing is intended. Missing any of these pushes the first draft into guesswork.

What happens if the other side does not respond?

The drafting party sets a response deadline in writing and proceeds with a placeholder scope built on the use cases already confirmed. Silence past the deadline is escalated to the commercial lead on each side before it reaches counsel again.

Proven

Reviewed on 14 January 2025. This note describes drafting and negotiation practice rather than statutory procedure, so no legal act is cited: none applies to a checklist of internal drafting steps.