What institutional CRE owners need from a parking performance layer — and where NOI is won or lost across each.
In most institutional portfolios, an asset manager can pull occupancy data, rent rolls, lease expirations, and tenant credit for every property in under a minute. Ask the same person to pull parking revenue — net of leakage, benchmarked across assets, broken out by transient versus monthly versus event — and the answer changes. The data sits with three different operators. The report takes a week. The benchmarking doesn’t exist.
That gap is what I wrote about in my last piece: parking is misclassified inside most institutional portfolios, treated as a delegated operating function rather than as income that should be measured and governed at the portfolio level. The diagnosis resonated, but the next question was immediate: if parking should be managed as a performance system, what does that system actually consist of?
Every dollar of parking revenue passes through five interconnected systems. In most portfolios, each one is managed separately, by different vendors, on different platforms, with no shared data layer connecting them. That fragmentation is where NOI is lost.
If the exit isn’t reconciled, the revenue never existed
This is the foundation. If a vehicle enters the asset and exits without a recorded, reconciled transaction, nothing else in the performance layer matters. Dynamic pricing, demand activation, portfolio analytics — all of it sits on top of whether the facility captures payment from every vehicle, every time.
Most access and revenue control systems were built for a world of gates, tickets, and on-site servers. They work at the individual facility. They do not connect to a portfolio-level reporting layer. They do not talk to the payment system, the enforcement system, or the demand channels that route drivers to the asset.
When access control is disconnected from the rest of the operating layer, revenue leaks at the margins — unpaid exits, manual exceptions, flat pricing that never adjusts to demand. Industry estimates put those losses at up to $1.3 billion annually across private parking facilities.
The portfolios closing this gap have moved to cloud-native access and revenue control that eliminates the distance between the vehicle entering the asset and the transaction being recorded, reconciled, and visible at the portfolio level. No on-site servers. No offline black boxes. Every transaction captured, every exit closed.
Parking is one of the last physical transactions in CRE that hasn’t caught up
Across the broader economy, the shift to contactless payment is no longer a trend — it is the baseline. Mastercard reports that more than half of Americans now choose contactless over other payment methods at checkout, and Gen Z consumers — who have doubled their spending power since 2019 — are twice as likely to abandon a purchase entirely if their preferred payment method is not available.
Parking has not kept pace. Walk into most commercial garages and the payment experience is a kiosk built a decade ago, a gate that takes one card at a time, or a cash-only lane with a line. The cost is not just inconvenience. It is lost revenue — abandoned transactions, slower throughput, lower conversion on transient demand — and it is tenant friction. A monthly tenant whose guest cannot figure out how to pay at the gate does not blame the parking operator. They blame the building.
The portfolios ahead of this curve offer a payment layer that meets drivers where they already are: contactless tap, mobile wallets, QR-based scan-to-pay, and automated license-plate-based billing that eliminates the transaction entirely. Drive in, drive out, pay automatically. No app at the lane. No kiosk. No friction.
Invisible assets don’t generate demand
Most parking assets are invisible to the driver until the driver is already on the property. That is a structural revenue problem.
If a parking facility is not discoverable on the platforms drivers already use to search, navigate, and plan — Google Maps, Waze, Apple Maps, ParkMobile, Ticketmaster, event apps — then the asset is competing for drive-up traffic only. In a market where digital booking and pre-arrival reservation are becoming standard, that means ceding revenue to locations that are visible where the driver is looking.
I saw this play out recently at a mixed-use asset near a major arena. Event-night parking revenue was running roughly 40 percent below comparable assets in the same submarket. The difference was not price, location, or capacity. The comparable assets had reservable inventory visible inside the ticketing platform. This one did not. Drivers were booking parking before they left home — and this asset was not in the consideration set.
At scale, the demand network is not a marketing channel. It is a permanent connection between supply and demand that routes paid traffic into owner assets as a built-in feature of the operating system.
Event-day revenue is the highest-yield hour in the portfolio — if the system can flex
For any asset near a stadium, arena, convention center, or entertainment district, event days represent the highest-revenue hours of the year — and often the most operationally chaotic.
Most parking systems are configured for steady-state operations: weekday commuters, monthly tenants, predictable demand curves. When a concert or game floods the area with ten times the normal vehicle volume, the system needs to flex — pricing, access rules, capacity allocation — without breaking the base business that serves tenants and daily users. When that flex capacity does not exist, event days become a choice between under-monetizing the surge or alienating the tenants who park there every day.
What this requires is event-day infrastructure built into the operating layer: dynamic pricing based on real-time demand, bundled parking through integrated ticketing partnerships, managed capacity allocation across transient and reserved inventory, and automatic return to normal operations when the event ends. Revenue from a single well-managed event night can exceed a full week of standard operations. The system that captures it has to be the same system that runs the asset every other day.
The best enforcement is invisible to everyone except violators
Enforcement is where revenue protection meets tenant experience — and where the wrong approach damages both.
Over-enforcement creates tenant complaints, gate disputes, and negative first impressions. Under-enforcement creates revenue erosion as tolerated abuse compounds across the portfolio. The traditional model — manual patrols, paper citations, disconnected violation systems — scales poorly, responds slowly, and generates friction that owners rarely see until it shows up in lease renewal conversations.
What works is enforcement integrated into the access and payment layer, not bolted on as a separate system. When enforcement can see in real time which vehicles have valid credentials, which have paid, and which are in violation — automatically — compliance improves while friction decreases. The best enforcement is invisible to compliant parkers and decisive with violators.
The through-line: tenant and guest experience
Each of these five systems shapes revenue directly. But there is a dimension that runs through all of them and shows up on the income statement indirectly: the experience tenants and guests have arriving at, parking in, and leaving the asset.
CRE valuation in 2026 increasingly incorporates occupant experience metrics — not as a replacement for traditional financial analysis, but as an input that shapes vacancy assumptions, renewal probability, and rent premium justifications. Properties that deliver strong arrival experiences are underwritten with higher retention assumptions and lower frictional vacancy. Properties that don’t face compressed valuations regardless of other quality indicators.
Parking is the first and last physical interaction a tenant or guest has with the asset. Friction at the gate, confusion at payment, inability to reserve in advance, disconnection from the apps drivers already use — these are not parking problems. They are tenant retention problems and asset valuation problems.
When all five systems are connected — when access, payment, demand, events, and enforcement share a common data layer and present a coherent experience to the driver — the result is not just higher revenue capture. It is a measurably better-performing asset. That is the difference between a collection of parking products and a parking performance layer.
What this requires
No single point solution addresses all five. Most address one, sometimes two, in isolation. The result is the same fragmentation that creates the problem: five vendors, five platforms, five data silos, no portfolio view.
Flash has spent more than a decade building an operating layer that connects all five systems into one ecosystem — revenue capture, digital payments, demand, events, and enforcement running on one cloud-native platform, across every asset in the portfolio, regardless of operator. Customers who connect their portfolios to that ecosystem see consistent NOI lift, not from raising rates but from finally closing the gaps between systems that were never designed to talk to each other.
Every dollar passes through five systems. The question is whether they are connected — or whether value is leaking between them.
That is the performance layer worth building.
Peter Weiss
Chief Business Officer
Flash