Exclusive use clauses are among the least complicated provisions in a retail lease and among the most expensive to breach. The landlord agrees not to lease other space in the centre to a competing use, the tenant gets protection from direct competition, and the remedy for breach is typically a rent reduction that takes effect while the violation continues.
The provision is not hard to negotiate and it is not hard to comply with. What is hard is knowing it exists at the moment it matters. The exclusive was granted in a lease signed years ago, possibly by a prior owner, possibly by a leasing professional who has since moved on. The person negotiating a new lease today is working from a permitted use the prospective tenant proposed and has no practical way to check it against a restriction buried in another document.
This is a visibility problem with a straightforward fix, and it recurs across portfolios of every size. The cost of getting it wrong is ongoing and self-executing, which means the landlord is often paying for the error for some time before a dispute even begins.
The three ways violations occur
Violations arise through a small number of mechanisms. Understanding which one is in play determines whether the fix is a process change, a drafting change or a monitoring change.
- New lease overlap, a new tenant is granted a permitted use that encompasses a category already protected by an existing exclusive, usually because the exclusive was not checked.
- Broad permitted use drafting, a use clause written generally enough to cover a protected category, so the overlap exists in the documents even if the tenant never operates that way.
- Merchandise or service drift, an existing tenant expands its offering into a protected category with no lease change, creating a violation without any landlord action at all.
- Assignment and subletting, a permitted transfer brings in an operator whose use differs from the original tenant and collides with an exclusive nobody re-checked at consent.
- Acquisition inheritance, exclusives granted by a prior owner transfer with the leases and bind the acquirer, whose leasing team has no knowledge of them.
Only the first two are preventable purely through a check at lease signature. The others require monitoring or a check at a different trigger point, specifically at consent to assignment and at acquisition close. Building the check into all three moments is what separates a portfolio that has this under control from one that responds to violations after the fact, and it depends on the same abstraction discipline described in lease lifecycle management.
Where the remedy is self-executing rent abatement on notice, the tenant identifies the violation and the rent reduces. The landlord may believe the claim is wrong and may ultimately be right, and in the meantime the reduced rent is what is being collected. Detection by the tenant is sufficient to start the clock.
Why portfolios cannot see their own restrictions
The obstacles are practical rather than conceptual, and they compound as a portfolio grows or changes hands.
- Exclusives live in individual leases. The restriction is a clause in one tenant document, and nothing consolidates it into a view organised by property and protected category.
- Abstraction captures dates, not restrictions. Lease abstraction programmes prioritise financial and date fields, so exclusives and use restrictions are frequently summarised loosely or omitted.
- Categories are described, not coded. An exclusive protecting a merchandise category is written in prose, so comparing it to a proposed permitted use requires judgement rather than a lookup.
- No check at the decision point. Even where a matrix exists, it is not consulted during negotiation because it lives with lease administration and the negotiation happens in leasing.
- Acquisitions import unknown restrictions. Due diligence focuses on income and term, and inherited exclusives arrive with the portfolio without being surfaced into the new owner process.
Getting exclusives under control
Step 1, Abstract exclusives as a specific field set
Extract, for every lease, whether an exclusive is granted, what category it protects, its geographic scope within the property, its duration, any conditions such as continuous operation requirements, and the remedy. Treat it as a first-class abstraction field rather than a note.
Step 2, Build a per-property matrix
Consolidate the extracted exclusives into a single view per property showing every active restriction and its holder. This is the artefact the leasing team consults, and it needs to be current rather than periodically refreshed.
Step 3, Check at three trigger points
New lease negotiation before permitted use is agreed, consent to assignment or sublet, and acquisition close. Each is a moment when a violation can be created and each is a moment when the check is cheap.
Step 4, Draft permitted use to be checkable
Use specific descriptions rather than broad categories in new leases, so future checks against future exclusives are possible. A portfolio of vaguely drafted use clauses makes every subsequent check a judgement call.
Step 5, Monitor operating tenants for drift
Periodic review of what tenants actually sell or provide against their permitted use and against active exclusives. Drift is the violation type no document check will catch, and the cost of a walkthrough is trivial against the remedy.
One view of every restriction on the property
See exclusive use provisions abstracted, consolidated by property and checked at the moment of negotiation.
The negotiation position this creates
There is a commercial benefit to this beyond avoiding remedies. A landlord who knows precisely what exclusives exist across a property can negotiate new ones deliberately, granting narrow protections where they win a tenant and declining broad ones that would constrain future leasing. Without the matrix, exclusives tend to be granted generously because nobody can articulate the cost, and the cumulative effect is a property whose remaining space becomes progressively harder to lease. Landlords with the consolidated view frequently find they have granted overlapping or redundant protections that could have been narrowed at no cost to the tenant relationship, and they can price the concession properly in the next negotiation. That is the same shift from reactive to informed that a complete lease obligation register produces for dates and financial duties.
Where to check, and what to check against
The table sets out each trigger point, what creates the risk at that moment, and the check that addresses it. The pattern to notice is that four of the five checks happen before a signature, which is where the cost of prevention is close to zero.
| Trigger | Risk created | Check required | Owner | Cost if missed |
|---|---|---|---|---|
| New lease negotiation | Permitted use overlaps an exclusive | Proposed use against the matrix | Leasing | Abatement for the lease term |
| Consent to assignment | New operator use differs | Assignee use against the matrix | Lease administration | Abatement plus consent dispute |
| Lease renewal or expansion | Expanded use or expanded area | Revised use and area against the matrix | Leasing | Abatement from the change |
| Acquisition close | Inherited unknown exclusives | Extraction into the matrix at close | Transactions | Violations from day one |
| Operating period | Tenant merchandise drift | Periodic use review on site | Property management | Abatement until cured |
Exclusive use clauses are a small drafting matter and a significant operational one. The provision itself is rarely contentious and the compliance requirement is rarely onerous; what fails is the portfolio ability to know what it has already promised. Abstracting exclusives properly, consolidating them per property and checking them at the four moments before a signature turns a recurring source of abatement into a routine step in a leasing process. It also gives the landlord a much better idea of what the next exclusive is actually worth, which is the difference between granting a concession deliberately and granting one because nobody could say what it would cost.
For related guidance, see Tenant improvement allowance tracking for lease teams, Co-tenancy clauses, tracking the trigger before it fires and SNDA agreement tracking for landlords: a datasheet.
