When exclusive and sole are used interchangeably: what to do first
When a licence calls a grant both "exclusive" and "sole", the words are not interchangeable: an exclusive licence excludes even the licensor's own use, a sole licence does not. The first step is to identify the right licensed, check whether a register already fixes the term, and record the conflict in writing before anything else moves.
Basis
Where the licensed right is a registered EU right, the register itself can carry a fixed meaning for "exclusive". Regulation (EU) 2017/1001 (EUTMR) treats an EU trade mark licence as a recorded fact: the type entered against the mark is the reference point an office and a court look to first when the underlying agreement is ambiguous. Regulation (EU) No 1257/2012 places unitary patent protection on comparable footing, with the recorded licence sitting alongside the patent rather than inside the contract alone.
For other rights, this anchor does not exist. Directive 2009/24/EC, which governs the legal protection of computer programs, does not define "exclusive" or "sole" licensing. Directive 96/9/EC, which governs database rights, does not define these terms either. For software and for databases, the meaning of the words comes from the contract itself and from the law chosen to govern it, not from any register entry.
Practical consequence
The consequence tracks the anchor. On a registered EU right, a mismatch between the contract's wording and the register entry can decide who is entitled to act against an infringer and who may grant further licences down the chain. On software or a database right, the mismatch stays inside the contract: it affects who is bound by the exclusivity, but no register can settle it, and any dispute over interpretation runs on the timetable set by the governing law rather than by an office.
A licence that uses both words for the same grant also weakens the licensee's position if it later needs to show, to a third party or to a court, exactly what was excluded. Ambiguous drafting is read narrowly against whoever drafted it more often than it is read in the licensee's favour.
What to do
- Counsel identifies which right the licence covers: an EU trade mark, a unitary patent, software copyright, a database right, or a bundle of several.
- The IP team pulls the current register entry, where one exists, and lines up its wording against the contract clause by clause.
- The licensee puts the discrepancy to the licensor in writing before taking any step that assumes one meaning over the other.
- Counsel applies the default rule of the law chosen to govern the agreement to whichever element has no register to consult.
- The parties amend the clause to remove the interchangeable wording and, where a register exists, file the corrected licence type with the office that holds it.
Who decides
| Right licensed | Who decides the meaning | Basis on record |
|---|---|---|
| EU trade mark | EUIPO register entry, or a court on dispute | Regulation (EU) 2017/1001 (EUTMR) |
| Unitary patent | Patent register, or the Unified Patent Court | Regulation (EU) No 1257/2012 |
| Software copyright | A court, under the governing law of the contract | Directive 2009/24/EC (silent on the terms) |
| Database right | A court, under the governing law of the contract | Directive 96/9/EC (silent on the terms) |
Forks
If the right is a trade mark or a design and a competitor has already copied the licensed sign, the licence question and the infringement question move together and neither waits for the other — see A design is copied by a competitor trade mark.
If the licensed right was created by a team spread across several jurisdictions, the ownership question comes before the licence question, because a licence cannot grant more than the licensor actually holds — see When the team is spread across three countries in.
If the underlying asset is tokenised rather than a registered IP right, enforcement against a holder follows a separate track with its own evidence rules — see When enforcement is sought against a holder in detail.
Limit
This page does not draft the amended clause, does not calculate the limitation period that applies under the governing law, and does not file a correction with any office. It sets out the anchor that applies to the right in question and the order of steps that precede those tasks.
Verified
Checked against the current text of each act cited above. Sources: Regulation (EU) 2017/1001 (EUTMR); Regulation (EU) No 1257/2012; Directive 2009/24/EC; Directive 96/9/EC. For the tier and delivery route behind every figure and reference on this site, see Sources by tier and delivery route and the deadline.
Related publications
A licence dispute over wording is a different problem from a break in ownership itself — see When an assignment breaks the chain of title: what.
FAQ
What is the first step when exclusive and sole are used interchangeably?
Identify which right the licence covers and check whether a register already records its type. Compare that record with the contract wording before relying on either term.
Which deadline is already running?
No EU regulation fixes a specific deadline for this point on its own. The deadline running is whichever limitation period the governing law sets for a claim on the licence, together with the recordal window the relevant office publishes for updating a licence type on its register.
Who decides, and on what evidence?
For a registered EU right, the office holding the register decides on the entry itself. For software or a database right, a court decides under the governing law, on the wording of the contract and any earlier course of dealing between the parties.