Operations · Events
“Big night” is not a demand curve.
A wedding, gala, and convention may produce the same total cars and require completely different operations. What matters is when people arrive, what causes them to leave, whether they know the property, and how event traffic overlaps the normal business around it.
Plan the shape
Staff the curve, not the guest count.
Start with intervals: expected arrivals and departures by short time block, plus the uncertainty around them. Then place intake, parking, retrieval, cashiering, staging, and leadership where the work actually accumulates.
Three shapes
Each event concentrates pressure somewhere else
Wedding: a defined arrival, an emotional departure
Arrival
Ceremony deadline
Guests cluster before a known start and may be navigating an unfamiliar entrance while dressed for the event.
Departure
Soft, then sudden
Early departures trickle, then speeches, music, or transportation timing can release a large group.
Plan
Protect guest assistance
Wayfinding, covered handoff, accessible loading, and clear request instructions matter as much as runner count.
Gala: compressed arrival and a hard program end
Arrival
Presentation at the curb
Sponsors, VIPs, rideshare, and photographed entrances can all compete for the same frontage.
Departure
One visible release
The end of the program can move most guests at once, making pre-request and deliberate staging especially valuable.
Plan
Separate functions
Keep vehicle intake, guest greeting, rideshare, and returns from collapsing into one unsupervised line.
Convention: repeated waves across a long day
Arrival
Multiple agendas
Exhibitors, staff, attendees, speakers, and hotel guests may arrive on different clocks.
Departure
Partial releases
Breaks, session changes, and evening events create several smaller peaks instead of one clean finish.
Plan
Sustain the handoffs
Relief, meals, shift changes, validation rules, and communication across a long operating window become core capacity.
→For conventions, the handoff plan can matter more than the opening deployment because the event outlasts any one crew.
For every event, ask five questions before quoting labor: What ends the arrival wave? What triggers departure? How many guests will be unfamiliar with the request or payment process? Which shared curb users remain active? What happens if the program runs late?
Build a base plan and a trigger plan. The base assigns expected positions. The trigger plan says what changes when the arrival curve shifts, weather arrives, validation fails, or the lot enters constrained status. After the event, compare the predicted and actual curve. That history is more valuable for the next wedding or convention than a generic rule about cars per valet.
