Operations · Curb Layout
Split the curb only when interference costs more than duplication.
A second stand looks like extra capacity. It is also a second place to staff, sign, reconcile, stock, and explain. The right question is not how many cars the property serves. It is how often arrival and departure work block each other in the same minutes.
The decision
Measure simultaneous demand, not daily volume.
A property can serve many cars across a day and never need two stands. Another can serve fewer but experience a compressed checkout or event release that makes one shared curb fail. The threshold belongs to the observed arrival-departure overlap and the geometry of that property.
One queue or two
Choose the simpler system until it stops working
What a split actually buys
One shared stand
Simple- One guest destination and one team
- Flexible labor across arrival and return
- Conflicting movements share one lane
Arrival + departure
Specialized- Queues and handoffs stop crossing
- Guests can wait away from intake
- Labor, signage, and key routing split
Build an illustrative overlap test
Use your own observations. The bars below show the method, not an industry threshold.
→For each short interval, record arrivals being processed, departures being returned, lane blockages, and staff pulled across tasks. A recurring conflict window is evidence; a busy daily total is not.
Before building a permanent second stand, test a reversible version during the actual peak. Use clear temporary signage, assign one lead to each function, define how keys and requests cross the boundary, and keep one shared escalation owner. Watch for a new failure: the departure side may stand idle while the arrival side queues, with employees reluctant to cross the line because the layout has made ownership too literal.
Keep the split only if it improves the whole curb: fewer blocked movements, clearer guest wayfinding, stable custody, and acceptable labor. If it merely moves the queue from vehicles to people, the property may need a waiting-zone or staging change instead.
Below the conflict threshold, collapse back to one stand. Operational maturity is not keeping every peak configuration visible all day; it is revealing complexity only when demand makes it useful.
