Analytics · Measurement method
The first minute is
often invisible.
A digital request gives an operation a clean timestamp. It does not prove that timestamp is when the guest decided to leave. They may have searched for a ticket, waited for an elevator, stood at the desk, or tried to get someone's attention first.
The measurement problem
Intent is real and only partly observable.
The earlier Journal article Why Your Valet Queue Is Slower Than You Think explains the operational consequence: the guest's clock starts before the runner's. This article stays on the measurement side: which clocks exist, which gap must be estimated, and how to report uncertainty without inventing precision.
Do not replace system time with a stopwatch study. Use targeted observation to estimate the missing interval, then combine it with durable event timestamps.
The clocks
Separate observed time from inferred time
Build the guest-wait timeline
→The question mark is not a data defect that software can always eliminate. It is a boundary the report should disclose.
Use several measurement methods
System
Event timestamps
Request, acknowledgment, movement, ready, and handoff events provide consistent coverage when their definitions are enforced.
Observation
Short curb studies
A trained observer can sample when guests enter the request path and note delay before a digital event exists.
Guest
Brief intercept questions
Ask a small sample when they first wanted the car and which step delayed them. Recall is imperfect, so report it as such.
Journey
Interface start events
A link open or request-screen view can narrow the gap, but it still may occur after the guest formed intent.
Publish two numbers rather than one false certainty
Measured system wait
OBSERVED- High coverage and consistent timestamps
- Useful for workflow and retrieval analysis
- Begins after unobserved guest intent
Estimated full wait
INFERRED- Includes a sampled pre-request interval
- Closer to the guest's experience
- Carries sampling and recall uncertainty
→Label the method, sample window, property, cohort, and uncertainty. Do not merge the two clocks without showing the seam.
Protect against convenient timestamps
Every event definition should resist being moved merely to improve the metric.
Request
Valid receipt
Use the first durable valid request, not a later dispatch event selected because it starts the clock closer to completion.
Ready
Vehicle actually available
Do not mark ready when the runner starts or when the car is still blocked from guest handoff.
Complete
Guest handoff
Define whether payment, key transfer, and vehicle departure are inside or outside the service clock.
Missing
No event is still an outcome
Abandoned and manually handled journeys should remain visible rather than disappearing from the denominator.
The reporting standard
Say where the clock starts and what happened before it.
A manager can improve measured request-to-ready time while also studying the pre-request gap through focused observation. Those are complementary views of the same guest journey, not competing definitions.
The takeaway: honest wait measurement does not pretend to observe intent. It marks the boundary, estimates it carefully, and keeps the durable clocks exact.
