Name the leak paths first
Leakage is not a single failure. It is a set of them, and a facility usually runs several at once.
- Unaccounted tickets. Tickets issued but never reconciled to a paid exit, the most common leak in a gated operation.
- Validation abuse. Validations issued past policy, mis-programmed devices, and rates that a tenant device grants for free.
- Exception transactions. Lost-ticket charges, manual gate lifts, and overrides that pile up in a report nobody reads.
- Gates that open without payment. Equipment set to auto-vend after a few unanswered intercom rings, releasing unpaid exits on its own.
- Cash handling. The oldest leak, and the one a camera review still catches.
- Uncollected contract clauses. Operating agreements that penalize uncollected tickets above a threshold, written and then never enforced.
- Equipment downtime nobody logs. A lane down for a week is a week of free parking, unrecorded.
How to measure before guessing
Every one of those paths is measurable. The discipline is to measure it rather than assume it.
- Reconcile the ticket population to reported revenue. Rebuild the full set of tickets by serial sequence and trace each to a paid exit, rather than sampling around the gap.
- Read the exception and alarm reports. The system already logs the overrides and the auto-vends. Most operations have never printed the report.
- Compare lost-ticket rates to the norm. Lost-ticket transactions above the low single digits are a flag, not a rounding error.
- Test the lanes in person. Pull a ticket without a vehicle, attempt an unpaid exit, and watch a cash shift. Controls that pass on paper fail in the lane.
What disciplined review is worth
The point of the number is not the total. It is the ratio. An audit scoped to a facility's real risk returns several times its fee, because the leaks it finds were running every day it was not looked at.
Why findings decay without ownership
A report that ends at observation changes nothing. The leaks a facility fixes are the ones with an owner and a deadline attached; the rest reopen. Every finding needs a name against it, a date, and a re-check that confirms the fix in the field rather than in a memo. Between audits, a standing mystery shopping cadence keeps attention on the lanes, so a control that drifts in March is caught in April rather than at next year's review.
The first step
Start with a revenue control audit scoped to the facility's risk, not a boilerplate checklist. The commercial office and CRE page covers how it applies to garages inside office assets, where a single mis-programmed validation device can carry six figures. Where the remedy is continuous attention rather than a one-time review, Parking PI shops and inspects the lanes on a schedule.
If an audit is sitting unactioned, or a garage is running controls nobody has tested from the lane, scope the audit. Findings age badly.