Lead time: the metric almost no one cross-references

Almost every hotel counts how much it books. Very few count when it books. And it turns out that second number, the days between when someone makes a reservation and the night they arrive, predicts things the “how much” simply can’t see: whether a date is heading toward full or short, which bookings are most at risk of falling through, and why each channel behaves differently. Lead time is probably the most revealing metric your hotel isn’t cross-referencing with anything.

What lead time actually is

Lead time is the distance in days between two dates your operation already stores: the date the reservation was created and the arrival (check-in) date. If someone books on May 1 to arrive June 20, their lead time is 50 days. If they book today to arrive tomorrow, it’s 1 day. There’s nothing new to capture; the figure is already hiding between two fields almost no one subtracts.

That simple subtraction is, at heart, a measure of intent. Someone booking far ahead is planning (an organized trip, a dated event, a vacation bought with time to spare). Someone booking at the last minute is solving (a layover, an unexpected need, a price opportunity). These are two different behaviors with two different risks, and blending them into a single average erases exactly what’s interesting.

Why an average alone falls short

Imagine, an illustrative example, not real data, that your average lead time is 18 days. It sounds tidy. But that 18 can hide two completely different hotels inside the same hotel: half your bookings arriving at 60 days and the other half at 2 days, with almost no one in between. The average hands you a comfortable number and a false picture. Lead time only starts to speak when you stop looking at it in isolation and cross it against the other dimensions you already have in the operation.

Cross-referencing means asking “lead time, but of what?” Of which channel. Of which season. Of which guest type. Against which cancellation rate. Each cross turns a flat number into a pattern with contour, and the contour is what you can actually read and, eventually, decide on.

The crosses that change the read

Lead time by channel

Channels don’t behave alike. It’s common, not a universal rule, but something every hotel should measure in its own data, for OTA bookings to carry a different lead time than direct ones, and for last-minute to weigh more in some channels than others. When you see lead time split by channel, you stop treating “the bookings” as one mass and start understanding that each source fills your calendar at a different point in the cycle.

Lead time by season

The same calendar date isn’t bought with the same notice all year. A holiday or a high season tends to be booked further ahead because people plan it; an ordinary low-season Tuesday tends to fill, if it fills, much closer to the date. Watching how lead time shifts across the year tells you when your demand travels “calmly” and when it arrives “all at once.”

Lead time by guest type

Someone traveling for work, someone traveling for leisure, someone who repeats with you and someone who finds you for the first time don’t plan on the same horizon. Crossing lead time with guest type reveals which segment gives you early visibility (you can read it weeks out) and which shows up late (you only see it once it’s nearly here).

Lead time against cancellations

This is perhaps the most useful cross and the least made. The chance a booking falls through isn’t uniform: certain lead times cancel more than others. A reservation made with a great deal of time had more chances to change plans; a last-minute one tends to be firmer because it’s nearly the present. When you cross lead time against cancellation, you stop seeing your “on the books” as a solid block and start seeing how much of that promise is firm and how much is fragile.

A date isn’t going well or badly because of how much you have on the books. It’s going well or badly because of when that was booked and how firm it is. Two calendars with the same number can be two opposite stories.The principle behind lead time

How it changes your read of “going well or badly”

Suppose, again, an illustrative example, two dates that today both show 60% booked. Without lead time, they reassure you equally. With lead time, they’re two worlds: if on one date your demand historically arrives very early, that 60% at 40 days out may mean you’re ahead of pace; if on the other your demand historically arrives late, the same 60% at 5 days out may mean it won’t grow much more. The identical number tells two opposite stories, and only lead time tells them apart.

That’s why lead time is, in practice, an early-warning system: it lets you compare a date’s “pace” against how that date usually fills, instead of staring only at today’s frozen snapshot. The question stops being “how much do I have?” and becomes “am I on the pace this date demands?”

What you discover by crossing lead time

When you stop watching the average and start crossing, findings like these tend to surface:

• Which channels give you early visibility of demand and which always arrive right on the date.
• Which dates of the year are bought calmly and which depend on the last minute to fill.
• Which guest segment is a planner and which improvises, so you don’t judge them by the same yardstick.
• Which lead-time range concentrates most of your cancellations, and therefore where your most fragile “on the books” sits.
• Whether your demand this year is arriving earlier or later than in comparable periods, before the final result confirms it.
• At what point in the cycle a date usually stops moving, so you know when what you see is nearly the final word.

Where the figure comes from and where you read it

Spider Data crosses eight sources of your operation into a single structure, reservations, cash, channels, payments, guests, orders, shifts and cash movements, and lead time is born there, alongside other calculated fields like ADR, nights or reconciliations. That keeps lead time from living alone and places it next to the dimensions it makes sense to cross it with.

From there, the no-code report builder (drag and drop, in Spanish) lets you set lead time against channel, season or cancellation without writing a line; cross-table joins and totals do the rest. Live dashboards with cross-filters let you move through the pattern, filter one channel and everything else rearranges, and the AI layer lets you ask in plain language, request a summary or flag anomalies and hidden patterns in how your lead time shifts. And because the data is live, you’re not reading last night’s close.

None of this is a cage. If you’d rather model lead time in your own tool, the open connectors expose the same data to Power BI, Tableau or Looker via API with a Bearer token; and with R2-Index you can contrast your behavior against a reference index, not just against yourself. If you get stuck, there’s human support in Spanish.

The when says as much as the how much

Measuring how much you book tells you the size of your business. Measuring when it’s booked tells you its nature: how your demand forms, how firm the promise in your hand is, and why two dates identical on paper behave differently in reality. Lead time isn’t one more metric to collect; it’s the lens that makes almost everything else legible once you cross it. The hotel that only counts how much people book is reading half the story. The when says as much as the how much, and, often, it says it sooner.