Education · Demand
Three customers sharing one garage.
A dinner guest, a resident, and an overnight traveler can each occupy one space. Operationally, that is nearly the only thing they have in common.
The category error
Daily car count hides the shape of demand.
Transient, monthly, and overnight vehicles arrive at different times, stay for different lengths, return with different urgency, and pay under different promises. Combining them into one volume number produces a property that exists only in a spreadsheet.
Demand profiles
The same space behaves three ways
Transient: the turn
Pattern
Visit-driven
Arrivals follow meals, appointments, shopping, and events.
Price
Session or duration
The guest may pay directly or receive validation.
Labor
Sharp handoffs
Arrival and retrieval waves can be more important than occupancy.
Risk
Queue concentration
Many unrelated guests can request at once.
Monthly: the commitment
Monthly parking reserves or promises recurring access. It stabilizes revenue, but it can also commit inventory before transient demand arrives. Usage may look predictable in aggregate while individual arrival times remain uneven.
Overnight: the carry
An overnight vehicle crosses operating days. Hotel departures can synchronize around checkout, and a vehicle present at midnight may belong economically to yesterday's arrival and operationally to tomorrow's retrieval.
Why the mix matters
→Conceptual profiles, not benchmark values: each category stresses a different part of the operation.
The planning habit
Forecast the mix before the total.
Count expected arrivals, occupied inventory, and retrievals by demand class and interval. Then price each class against what it actually consumes. A space-hour, a curb movement, and a reserved right are three costs even when one vehicle causes all of them.
Make class changes explicit. A restaurant guest who leaves a car overnight, a hotel guest who converts to monthly parking, or a resident whose guest receives validation has crossed a commercial boundary. Preserve the original session, record the approved change, and show the guest which price now applies. Quietly recategorizing demand may fix tonight's report while making tomorrow's invoice impossible to explain.
The useful dashboard therefore has three views: flow by interval, inventory by demand class, and revenue by promise. None replaces the others.
Review the boundaries with frontline staff. They see the vehicle that became an overnight, the subscriber using an unregistered car, and the event guest whose validation expired while waiting. A clean category model should make those cases easier to resolve, not force attendants to disguise them as ordinary sessions.
