Tracking Exclusive-Use Clauses Before You Sign a Tenant

What exclusive-use and co-tenancy clauses actually do

An exclusive-use clause is a landlord's promise that no other tenant in the property will sell a defined category of goods or services. A nail salon gets the exclusive on nail services. A pizza restaurant gets the exclusive on pizza-by-the-slice. Break it, and that tenant has a contractual claim against you, not the offending neighbor.

A co-tenancy clause ties a tenant's obligations to the presence of other tenants, usually a named anchor or a minimum occupancy percentage. If the anchor goes dark or occupancy drops below the threshold, the protected tenant can cut rent to a percentage-of-sales figure or, after a cure period, walk.

Both clauses share one dangerous trait: they sit in leases signed years before the person leasing the vacant suite today ever opened the file. The obligation is live. The memory of it is not.

How a conflicting signature happens

Here is the version that keeps mixed-use managers up at night. A 40,000 square foot center has 22 leases. Suite 14 goes vacant. Leasing finds a strong national quick-service tenant, a smoothie and acai concept, and moves fast because good credit tenants do not wait.

Nobody remembers that the juice bar in Suite 6, signed in 2021, holds an exclusive on 'blended fruit and vegetable beverages.' The lease is a 90-page PDF with the exclusive tucked into a rider on page 71. The new tenant opens. Ninety days later the juice bar's attorney sends a demand letter citing the exclusive and invoking the lease's remedy: rent abated to 3% of gross sales until the violation is cured.

Now you are choosing between two bad options: terminate a signed tenant and face their damages claim, or keep bleeding rent from the protected tenant every month. Neither is cheap. Both were preventable by reading page 71 before the smoothie deal closed.

The uncomfortable truth: most centers do not have a clause register at all. The protection lives in individual leases, scattered across formats, and the only defense is that someone happens to remember. Human memory is not a compliance system, and in a portfolio of dozens of leases it fails silently and expensively.

Which clauses create conflicts you must check

Before any new lease is signed, someone or something has to cross-check the prospective use against every restriction already granted. These are the clause types that create conflicts.

How an AI agent abstracts and cross-references before signing

The workflow that prevents the smoothie disaster is abstraction plus cross-reference, run automatically at the moment a prospective use is entered. An AI abstraction agent reads every lease in the portfolio, extracts each restrictive clause into a structured record, and checks a proposed new use against all of them before the deal moves to signature.

1. 01

   Abstract every existing lease

   The agent parses each lease PDF, including riders and amendments, and pulls exclusive-use grants, co-tenancy conditions, prohibited uses, and radius clauses into a structured register with the exact clause text and page cited.

2. 02

   Define the proposed use

   When leasing enters a prospective tenant and their intended use, the agent normalizes that use into the same categories it used to tag the exclusives, so 'acai bowls and smoothies' maps against 'blended beverages.'

3. 03

   Cross-check and flag

   The agent runs the proposed use against every restriction in the register and surfaces conflicts with the specific lease, clause, and page. A borderline match (coffee vs bakery-with-coffee) is flagged as ambiguous, not cleared.

4. 04

   Escalate to a human

   The agent does not approve or kill deals. It produces a conflict memo for the leasing lead and, where the clause is ambiguous, routes it to counsel. The human decides whether the match is real and whether to negotiate around it.

This is squarely the pattern One Home Agent builds for property management operators: an agent that does the documented, deadline-driven reading no human reliably does at 4 p.m. on a Friday, then hands a clean flag to the person who owns the judgment call. The abstraction is machine work. The decision stays human.

Where it breaks: a badly scanned lease with no OCR layer, a hand-negotiated exclusive written in genuinely vague language, or an amendment that was signed but never filed with the lease. The agent flags what it cannot read with confidence rather than guessing, which is the correct failure mode. A tool that silently clears an unreadable exclusive is worse than no tool.

Why the leasing human still runs the deal

The agent flags conflicts. It does not negotiate leases, and it should not. Whether a flagged conflict kills a deal, narrows the new tenant's permitted use, or gets carved out with the protected tenant's written consent is a negotiation, and negotiation is human work.

“The agent is not there to make the leasing call. It is there so that nobody ever makes the leasing call blind. Reading page 71 of a lease from three years ago is not judgment. Deciding what to do about what is on page 71 is.”

Todd Paton, Partner, One Home Agent

What a clean clause register looks like

A clean clause register is a single structured table, updated as leases sign and amend, where every restriction is one row with the tenant, clause type, protected category, source lease, and page cite. It is the thing that turns 'does anyone remember?' into a five-second query.

Build the clause desk