How to flag co-tenancy clause risk using parking lot counts
A co-tenancy clause doesn't care about your model. It cares about a calendar. Once a named anchor goes dark, most leases start a clock, and if that clock runs out before the anchor reopens or gets replaced, the in-line tenant gets to pay reduced rent, pay percentage rent only, or in some leases just walk. The problem for anyone covering the REIT is that the first public confirmation of an anchor closure often comes out on the landlord's own earnings call, well after the clause has already started ticking.
Parking lot occupancy is one of the few signals you can watch yourself, on your own schedule, without waiting for that call.
Why the lot moves before the leasing update does
Co-tenancy provisions are usually keyed to one of three triggers: a named anchor (or a defined percentage of anchors) ceasing operations, gross leasable area falling below a stated threshold, or the center's total occupancy dropping below a set percentage. Each of those triggers has a physical footprint in the lot before it has a footprint in a filing.
When an anchor stops operating, its dedicated parking field empties out fast, usually within days, not quarters. Inline tenants that depend on anchor-driven cross-shopping traffic follow with a lag, often a few weeks, as their own draw thins out even though they're still technically open. That lag is the window. If you've got a daily read on the lot, you can see the anchor's section go flat and watch the inline segments decay against it, rather than finding out when the operator discloses a co-tenancy cure period already half spent.
This matters most for centers where the lease language lists specific named anchors rather than a generic "major tenant" standard, since those triggers fire on a single store's door closing, not an aggregate vacancy number you'd only get from a rent roll.
Setting an occupancy threshold worth watching
Most co-tenancy clauses don't actually specify a parking occupancy number; the threshold language is almost always framed around GLA percentage or a named-tenant list. That means you build your own internal watch level from the property's own history, because the lease itself won't hand you a parking number to key off.
A reasonable approach:
- Pull a daily occupancy series for the lot covering at least a full prior year, so you have a seasonal baseline (holiday peaks, back-to-school, slow months) to compare against.
- Segment the lot by anchor pad versus in-line parking where the site layout allows it, since a lump-sum count across the whole lot can hide an anchor-specific drop.
- Mark the lease's cure period on your own calendar the moment you hear any signal of an anchor closure, whether that's a sublease filing, a going-out-of-business sale, or a dark storefront noted in a site visit.
- Watch the index against the baseline weekly during that cure window. A sustained drop that tracks the anchor's footprint and doesn't recover is your flag; a dip that's explained by a slow month on the seasonal curve is not.
Reading the actual lease language still matters here. Cure periods, substitution rights, and GLA percentages vary lease to lease, and only the document tells you the real trigger date. What the occupancy series gives you is a way to watch for the underlying event itself, continuously, instead of relying on the tenant or the landlord to tell you when the clock started.
For analysts modeling anchor vacancy risk across a coverage list, the value isn't one lot checked once. It's a running index you can pull up the way you'd pull a same-store sales comp, sitting next to the lease abstract so the occupancy trend and the clause language inform the same call. Parking Lot Counts builds exactly that: a daily occupancy read per site, indexed so a drop shows up against the property's own history rather than a guess at what's normal.
If an anchor vacancy is sitting in your model as a question mark, put the lot on a daily index and let the data answer it before the next earnings call does.