Field-of-use drafting: stages and deadlines
Field-of-use drafting runs through four stages: scope mapping, clause drafting, cross-check against adjacent rights, and sign-off. Each stage carries a working deadline set by the parties, not by statute. The point of no return arrives when the licence is executed with an unqualified field-of-use clause. After that, narrowing the scope needs an amendment, not a notice.
Stages of drafting
The sequence below reflects how a field-of-use clause typically moves from a business instruction to an executed term. Timing depends on how many products, territories or channels the licence covers, and on how quickly each side confirms its own position.
| Stage | What happens | What triggers the next stage | Typical duration in a straightforward case |
|---|---|---|---|
| Scope mapping | The licensor and licensee list every product, channel and market the licence should cover or exclude. | A written list both sides confirm in writing. | Days |
| Clause drafting | The field-of-use wording is drafted around that list, together with carve-outs for sublicensing and improvements. | A draft clause circulated for comment. | A few days |
| Cross-check | The draft is checked against ownership, employment and any adjacent licences already in force. | Confirmation that no clause overlaps or contradicts another agreement. | Days, longer if co-owners are involved |
| Sign-off | Both sides sign. From this point, the field-of-use boundary is contractual, not merely discussed. | Execution of the licence. | Same day as final approval |
Documents you need before drafting starts
- The underlying right register entry or application number for the licensed right.
- A list of products, services or territories the licence should include or exclude.
- Any prior licence or assignment touching the same right.
- Corporate authority confirming who may sign on each side.
- A note on which internal approvals are required before either side can sign.
Where the licensed work was created by an employee rather than acquired externally, the ownership chain should be confirmed before drafting starts. See Employee-created program in ownership of results for how that chain is usually documented.
Practical consequence: why the field-of-use clause changes the deal
A field-of-use clause turns a broad grant into a bounded one. It affects royalty calculation, breach exposure and what the licensee may sublicense. A licence silent on field of use is read as unrestricted, which is rarely what either side intended.
Where the clause is left open, a licensee can expand into markets or products the licensor never intended to include. The licensor's practical leverage to object tends to shrink with each month of unchallenged use, even before any formal deadline is reached.
Who decides and where
Drafting decisions sit with the contracting parties and their advisers. No registry or authority approves the wording in advance. On the business side, the decision usually sits with whoever owns the commercial relationship; on the legal side, with whoever signs off the risk. A dispute over an already-signed clause goes to whichever forum the licence names, usually arbitration or the courts named in the governing-law clause.
Deadlines and the point of no return
Three deadlines matter in practice.
- The deadline the parties set for exchanging drafts, which is commercial, not statutory.
- The deadline for recording any related assignment, where recordal affects who can enforce the field-of-use boundary against a third party. A missed recordal deadline can weaken that position later; see An assignment was never recorded trade mark the deadline.
- The point of no return: execution. Once signed, a field-of-use clause can only be changed by amendment agreed by both sides.
Common forks
If the licence covers a digital product with usage-based royalties, the field-of-use clause should align with how royalty is measured. See Royalty tokenised rights for how that measurement is typically defined.
If the parties cannot agree on scope before a deadline they set themselves, drafting usually pauses rather than proceeds on an undefined field. Proceeding without agreement on scope is the most common source of later disputes.
If the underlying right is jointly owned, every co-owner's consent should be confirmed before the field-of-use clause is drafted, not after signature.
How the file works
A field-of-use file is opened once scope mapping starts and stays open through sign-off. Drafts, comments and the confirmed scope list are kept together so that later disputes over what was agreed can be checked against the file, not against memory.
Files are closed and archived after execution, in a form stripped of identifying detail before any internal use for comparison. No file is kept open beyond sign-off unless a co-owner consent or a recordal step is still pending.
What lengthens or shortens the timeline
Four factors move the timeline more than any other. The first two are the number of products or territories to be mapped, and whether a prior licence on the same right already exists. The other two are whether both sides use the same governing law, and how quickly each side confirms authority to sign.
A single-product, single-territory licence between parties who already have a relationship moves fastest. A multi-territory licence with a co-owned right and no prior relationship moves slowest.
Limit
This page does not cover how a field-of-use clause is enforced once breached, how royalty rates are set, or what happens when open-source terms sit inside the same licence. It also does not cover tax treatment of royalty flows or how competition rules constrain field-of-use restrictions. Each of those needs separate advice.
Verified
Reviewed for currency by the author. This page describes procedure and does not cite statutory provisions; where a step depends on a specific jurisdiction's rules, confirm the current requirement before relying on the timeline above. For how facts on this site are collected, checked and dated, see Methodology: collection, cross-checking and dating and who decides.
Related publications
A field-of-use dispute that escalates follows its own sequence of stages; see Dispute escalation clauses.
FAQ
How long does field-of-use drafting take in practice?
A single-product licence between parties already in a relationship can move through all four stages within days. A licence covering several territories or products, or requiring co-owner consent, typically takes longer, because scope mapping and cross-check both take more time.
Which documents are needed to start?
Scope mapping needs the register entry or application number for the right, a list of the products, services or territories to include or exclude, any prior licence touching the same right, and confirmation of signing authority on each side.
What happens if the other side does not respond?
Drafting pauses. Without an agreed scope list, the clause cannot be drafted with confidence, and proceeding on an assumed scope is the most common cause of later disagreement over what was actually licensed.
Next step
If open-source terms sit inside the same licence, scope and field-of-use wording need to be checked together before drafting continues; see What to do first in this situation.
If the underlying right expires before the licence term ends, the field-of-use clause needs a separate check; see The right expires mid-term IP licence.