Guide

How to plan a stacked valet car park

Stack parking fits more cars in. Done well, every car is at the front of its row by the time its owner comes back.

In a stacked row only the front car can drive out. Every car behind it waits. So the whole job of planning a stack car park comes down to one rule, and a lot of care in following it.

The rule: the car going home soonest is nearest the front

Within a row, park cars in order of pickup: the latest pickup at the back, the earliest at the front. Then each car leaves from the front, the next comes up behind it, and nobody is moved twice.

A row only stays in order if every car added to it is going home before every car already in it. A car coming in for two weeks can't go in front of a car leaving tomorrow. That is why the order cars arrive in matters as much as the order they leave in.

Group by pickup day, not by drop-off

Cars arrive in the order customers turn up, which tells you nothing about when they leave. Plan rows by pickup instead:

  • Give long stays rows of their own, filled from the back.
  • Keep a few rows, or the front of rows, for the shortest stays, so a car back in two days is never behind a car away for two weeks.
  • Leave single spaces or open bays for cars with no fixed return, and for cars that need to be reached at any time.

Plan the space before the car arrives

When a driver takes a car off the customer, they should already know where it goes. Deciding at the barrier, when the desk is busy, is how a car leaving tomorrow ends up at the back of a full row. Work through the day's drop-offs in advance and give each one its row and its place in the row.

Check the morning before it starts

For each car due out, look at the row it's in: is every car in front of it leaving earlier? If not, you have a boxed-in car. Finding it the evening before costs a couple of moves in a quiet hour. Finding it at five in the morning costs a customer waiting at the desk.

When a flight changes

An early or late return breaks the order of its row. When it happens:

  1. Find the row the car is in and the cars in front of it.
  2. Work out the fewest moves that bring it to the front in time: often one or two cars moved to a free space or another row.
  3. Know which cars have to come out first and go straight back, so the row is left in order for everyone else.

A late return is the easier case: the car can usually wait where it is, as long as it isn't now in front of a car that leaves before it.

Washes, valets and other extras

A car sent to the wash bay comes back to a different gap than the one it left. Plan where it parks on its return as if it were a new arrival, by its pickup time, rather than squeezing it back into its old place.

Get it out of one person's head

Many stack car parks run well because one experienced driver remembers every row. Write the rows down, or keep them in a system the whole team can see: a sheet for the day and a screen in the drivers' room. Then the car park runs the same on their day off.

Where Lane Marshal fits

Lane Marshal does this planning for you. You draw your car park once, import your bookings from a CSV export of your booking system, and Plan gives every car due in a space that keeps it clear of cars going home sooner. It lists any booking whose car can't get out in time, says which car is in the way, and Fix gives the fewest moves to sort it. See Lane Marshal for valet and airport parking.

Plan tomorrow's stacking

Import your bookings and Lane Marshal gives each car due in a space, then shows any car that won't get out in time.

Download for Windows See it at a valet car park Windows may say it protected your PC while we're new. Click More info, then Run anyway.