The reframe
The question isn't distance. It's departure time.
“Closer or farther” is the wrong frame. The right one is: which cars deserve the close spots? Fill the closest spaces with cars that won't leave for hours and you've blocked the exit with the wrong vehicles.
The logic
Why closest-first backfires
Closest-first vs. departure-first
The instinct is to grab the nearest open spot every time. The better rule sorts by who's leaving soon.
Closest open spot
Feels efficient- Fast to park right now
- Long-stays clog the prime spots
- Soon-to-leave cars stuck in back
- Every retrieval fights the layout
By departure time
Actually faster- Soon-to-leave cars sit closest
- Long-stays go to the back
- Retrievals get shorter on average
- Requires knowing departure windows
→A guest checking out at 8am shouldn't be parked behind someone staying three more days — even if that spot was open first.
What the right rule actually optimizes
The goal isn't shortest parking trip. It's shortest average retrieval — and those point in different directions.
→Guests never see the parking trip. They feel every second of the retrieval. Optimize for the one they experience.
Where Valletto changes the math
The right spot depends on knowing when each car will leave.
Departure-first staging only works if you have a sense of each car's departure window at intake — from checkout times, reservations, or patterns. Without that, you're back to grabbing the nearest spot and hoping.
The takeaway: stop asking “closer or farther” and start asking “leaving sooner or later.” With Valletto surfacing departure context for each car, the close spots go to the cars that are actually about to leave — which is what makes retrievals fast.
Valletto