Parking Lot Counts

How parking lot counts help verify a co-tenancy clause trigger

A co-tenancy clause only works if someone can prove the trigger happened. That sounds simple until you're the one holding a lease that says "if Anchor Tenant ceases operations for more than X consecutive days," and the actual facts on the ground are murky: a dark store with the lights still on, a phased closure with no public announcement, or a landlord who has every incentive to sit on the news.

Parking lot counts don't replace the lease language. They give you an independent, dated record of whether the box was actually operating, which is the thing most co-tenancy disputes turn on.

What the clause is actually asking you to prove

A typical co-tenancy clause ties rent relief, kick-out rights, or percentage-rent adjustments to a condition: an anchor closes, goes dark, or drops below a stated occupancy threshold in the center. The hard part is establishing, with a date attached, when the triggering condition started and whether it's still running.

Landlords and anchors report on their own schedule. A big-box tenant might stop staffing a store weeks before it files anything with the shopping center, and a dark store clause specifically exists because operators know that "still on the lease, still paying rent, zero customers inside" is a gray zone some tenants try to sit in as long as possible. If your only inputs are the lessor's notice letter and the anchor's next 10-Q, you're reconstructing the trigger date after the fact, from parties who had reasons to delay.

Why a dark anchor still looks occupied on paper

The dark store problem is exactly this gap. A store can be contractually "open" (fixtures in place, sign lit, utilities on) while having no real foot traffic and no inventory turning. Lease audits and site visits catch this eventually, but a site visit is a point-in-time check, and most portfolios have more properties than analysts have travel budget.

The parking lot shows an anchor's decline before the storefront or any press release does. A tenant that's quietly winding down shows fewer cars at open, fewer at the Saturday peak, a flattening pattern that breaks from the seasonal baseline for that trade area. That pattern is a dated, repeatable data point you can set next to the lease clock, separate from the legal question of whether it crosses the clause's threshold.

Building the timeline before the tenant does

This is where a daily occupancy read earns its keep. Instead of waiting for a quarterly disclosure or a notice letter to establish when an anchor went dark, you get a per-site occupancy series you can chart against the reporting period in question. If the clause requires 60 or 90 consecutive days of closure, you want a day-by-day record covering that whole window, not a single site photo from whenever someone happened to drive by.

For an equity or REIT analyst modeling co-tenancy exposure across a watchlist, that series does a few concrete things:

None of this tells you what the lease says or whether a given drop meets the contractual threshold. That's still a legal read on the specific clause. What it gives you is the operational fact pattern, built from actual vehicle counts in the lot, that the legal read depends on.

A few things it won't do

A count series doesn't explain why traffic dropped. Road construction, a competing center opening nearby, or a seasonal dip can all produce an occupancy curve that looks like an anchor going dark. Treat a sustained, unexplained drop as a prompt to dig into that specific store rather than a standalone legal conclusion. The notice and audit provisions in the lease still control the legal outcome. This just gives you your own dated record of when occupancy started falling, instead of waiting on the landlord's or tenant's disclosure to learn it already had.

If you've got a co-tenancy clause riding on an anchor you can't get a straight answer about, start watching the lot.

Start a project
← Back to the blog