Operations Research · Perception

The clock starts
before you do.

Ask an operator how long retrievals take and they'll quote the time from when the runner leaves to when the car arrives. But the guest's wait started earlier - and that gap is why the queue feels slower than your numbers claim.

The reframe

You're measuring from the wrong moment.

The guest's clock starts when they want the car - walking up, getting in line, trying to find someone. Your clock often starts later, when the request is finally in the system. The difference is invisible wait the guest absolutely feels and you never count.

The hidden time

Where the extra minutes hide

01

Measured time vs. felt time

The guest experiences the whole bar. Most operations only measure the second half.

What you measure
runner → car
What they feel
want → car

The gap between the two bars is pure perceived wait - and it's the part that ends up in the review.

02

The four hidden delays

Each happens before your clock starts, so none of them show up in your average - but all of them are wait the guest counts.

01

Finding someone to ask

The guest walks up and waits to even get a valet's attention. The clock is running; yours isn't.

02

The ticket fumble

Digging for the stub, reading off the number - friction before the request is even logged.

03

The request relay

Said over a radio, maybe repeated. More time before anyone moves toward the car.

04

Queue behind others

Even a fast retrieval feels slow if the guest watched three people get served first.

Add these up and a “four-minute” retrieval can be an eight-minute experience.

Where Valletto changes the math

The fix is to start the clock - and the retrieval - earlier.

If the guest can request their car the moment they want it, from their phone, the hidden delays collapse: no hunting for a valet, no stub fumble, no radio relay. Your measured time and their felt time finally line up.

The takeaway: your queue is slower than you think because you're not measuring the part guests feel most. Let them request the instant they want the car - and time it from there - and both the wait and the perception shrink. That's what Valletto is built to do.

Keep reading.

OperationsRetrieval

How to Reduce Average Vehicle Retrieval Time by 50%

Retrieval time is the number guests actually feel. Here are the five levers that cut it in half - most of them cost nothing but a change in how you work.

Jun 24, 2026 · 7 min readRead
Behind the ScenesOperations

Snow, Sand, and Salt

The curb is local, even for a national operation. Snow, beach sand, road treatment, altitude, and ice change what careful vehicle handling looks like from one market to the next.

Aug 10, 2026 · 5 min readRead
Behind the ScenesOperations

When We Are the Ones Who Damaged It

The professional response to possible vehicle damage is not a cover story. It is a calm, factual sequence that protects the guest, the team, and the truth of what happened.

Aug 8, 2026 · 5 min readRead

When reading is not enough

See it on your drive.

Twenty minutes on your own property, with your own volumes. We would rather show you the parts an article can only describe.

or keep reading the journal