Two clauses in a retail lease can look, on a fast read, like the same provision wearing different words. Both involve a threshold. Both involve a remedy. Both usually sit somewhere in the same article of the lease, often within a few paragraphs of each other. And both get abstracted wrong often enough that it's worth asking why — not just what the difference is, but why a competent reviewer under time pressure keeps missing it.
We've already written up what a co-tenancy clause is and what a kick-out clause is on their own terms, including the core distinction between them. This post is about the failure mode: why these two specifically — not tenant improvement allowances, not holdover provisions — are the pair that keeps showing up wrong in rent rolls and diligence files.
They use the vocabulary of the same test
A co-tenancy clause and a kick-out clause both describe themselves in the language of a test: a threshold, a measurement period, a notice window, a remedy if the test fails. Read either one in isolation and the shape is nearly identical — "if [condition] is not met by [date], tenant may [remedy] upon [notice]." That structural similarity is exactly what makes a skim-read dangerous. A reviewer who has internalized the pattern of one test-and-remedy clause will often pattern-match the second one as "more of the same" rather than stopping to ask what's actually being tested.
The two clauses test entirely different facts. A co-tenancy clause tests what's happening elsewhere in the shopping center — an anchor's presence, the property's overall occupancy. A kick-out clause tests the tenant's own performance — its gross sales at that specific location. One is about the tenant's neighbors; the other is about the tenant itself. That's not a subtle distinction on a careful read, but it's exactly the kind of distinction a fast read glides past, because the sentence structure surrounding both clauses looks the same.
They're drafted into the same article, on purpose
It's common for a single lease article — often titled something like "Co-Tenancy" or "Tenant's Termination Rights" — to house both provisions back to back, sometimes even cross-referencing each other (a lease might specify that a kick-out right is suspended while a co-tenancy remedy is active, or vice versa). That's not an accident of drafting; the two rights are conceptually related enough that lawyers group them. But it means an abstractor working through the lease document sequentially can hit both triggers within the same page or two, under the same section heading, described in overlapping language — precisely the condition under which two distinct fields get collapsed into one field, or one gets abstracted and the other skipped because it read like a restatement of the first.
The remedy, not the trigger, is where speed causes the real damage
Even a reviewer who correctly separates the two clauses can still get the abstract wrong at the remedy stage, because time pressure pushes toward the shorter, more familiar answer. Co-tenancy remedies are usually structured — alternate rent, a cure period, then termination only if the failure persists — which takes real reading to capture correctly. Kick-out remedies are more binary — sales miss the threshold, tenant gets a termination window — which is faster to write down and easier to feel confident about after a quick pass.
Under deadline, that asymmetry produces a specific pattern: kick-out clauses get abstracted reasonably well because they're structurally simple to summarize fast, while co-tenancy clauses get flattened into an oversimplified "tenant can terminate if occupancy drops" note that drops the alternate-rent mechanic, the cure period, and the difference between a named anchor and an anchor category — the details that actually determine what happens when an anchor closes, not just whether something happens.
What a careful abstraction process does differently
Catching both clauses correctly isn't about reading faster — it's about treating "co-tenancy" and "kick-out" as two separate fields from the start, regardless of how close together they sit in the document, and refusing to let either default to "not present" or a one-line summary without confirming which trigger and which remedy the actual clause language describes.
That means, at minimum, abstracting each one against its own checklist: for co-tenancy, the named anchor or anchor category, the occupancy threshold and how it's measured, the cure period, and whether the remedy is alternate rent, abatement, or termination. For kick-out, the sales threshold, the test period, the notice deadline, and whether the landlord holds a cure or recapture right that can defeat the tenant's termination. Neither field is complete without a citation back to the exact page and clause it came from — a note that says "co-tenancy clause present" without the threshold, the measurement basis, and the remedy mechanics isn't an abstract, it's a flag that more reading is needed.
This is the specific place where PropETL's specialist QA pass earns its keep: every material clause, co-tenancy and kick-out included, gets checked against the source document by a human reviewer before delivery — not just confirmed present, but confirmed to carry the right trigger, the right threshold, and the right remedy, distinct from its neighbor in the same article.
Get it read carefully the first time
If your portfolio includes retail leases where co-tenancy and kick-out rights sit in the same article — which is most of them — reach out through the lease abstraction page for a free sample round. Send a representative lease and see how the two get separated, cited, and captured with the mechanics that actually matter intact.
