Pace and pickup: reading the future of your bookings

Almost every number in a hotel tells a story that is already over. What you sold yesterday, last month’s occupancy, the average rate of the quarter that just closed. They are true and useful, but they share one flaw: by the time you read them, you can no longer change what they describe. Pace and pickup are different. They are the two metrics that look forward, toward dates that have not arrived yet, and that is why they are the only ones that let you react while the play is still open.

The difference between explaining and anticipating

Picture two dashboards in front of you. The first tells you, in exquisite detail, what happened in April: the occupancy, the average rate, which channels your guests came from. It is an excellent report. But April is gone. There is no decision left to make about April; there is only understanding it.

The second dashboard tells you something uncomfortable and valuable: for June, which has not arrived yet, you are running slower than you were last year at this same point. That sentence does not explain the past; it warns you of a future you can still bend. That is the whole difference. The first dashboard makes you wiser. The second makes you react in time.

The past is understood. The future is worked. Pace and pickup are the only metrics that put you on the future’s side while there is still something to do.

What pace is, in plain language

Pace is the rhythm at which bookings come in for a date that has not happened yet, compared against how you were tracking for that same date when you were the same number of days out last year or last period. The key word is compared. Knowing you have 80 rooms sold for June, on its own, says nothing: is that good or bad? Pace answers by setting it next to your own history. If last year, with 40 days to go before June, you had 100 rooms sold, then today with 80 you are behind. If you had 60, you are ahead.

That is why pace is always measured at the same lead time, not on the same calendar date. Comparing May 1 this year against May 1 last year is meaningless if Easter fell differently or if the event that fills the city moved months. The fair comparison is like for like: how you were tracking for June with 40 days to go, against how you are today, also 40 days out. That gap is the lead time: the days between the moment a booking comes in and the moment the guest arrives.

What pickup is, and why it is not the same

If pace is the accumulated snapshot of where you are heading, pickup is recent speed. Pickup is the bookings that came in over a short, near window: how many rooms you added in the last week, say, for future dates. It does not look at the total; it looks at the change in the total.

The distinction matters because two hotels can share the same accumulated pace and live opposite realities. One got there through a steady trickle that has now cooled. The other got there through a slow start that suddenly took off last week. Same total number, different future. Pickup is what separates “was bad and still bad” from “was bad but has rebounded.” One metric tells you where you stand; the other, which way you are moving.

An analogy so you never confuse them

Think of a road trip. Pace is how much ground you have covered against the plan: you are ahead or behind the time you wanted to arrive. Pickup is your speed right now on the dashboard. You can be behind on the plan but accelerating, or ahead but braking. Only by seeing both together do you really know whether you will arrive on time.

How these metrics are built

Here is the beautiful part: pace and pickup need no exotic data. They come from something your operation already generates every day. Every booking carries, at minimum, two dates that almost nobody crosses: the date it was created (when it was made) and the stay date (when it is for). The secret is looking at them together instead of apart.

• The creation date says when the booking came in. It is the clock of rhythm: grouping bookings by their creation date shows how many you added each day or week.
• The stay date says when that booking is for. It is what lets you ask “how much have I sold for June?”.
• The distance between the two is the lead time. It is the bridge that lets you compare at the same point: you group by lead time, not by calendar date.
• Crossing the three, creation, stay and lead time, is what turns a list of bookings into a pace curve and a pickup pulse.

In Spider Data this is built without writing code. You drag in the bookings table, set the stay date as the target-date axis, group by creation date to see the rhythm, and let a calculated field derive the lead time by subtracting one date from the other. A cross between tables (a JOIN) adds any missing context, the channel it came through, the rate, the segment, and a running total (a ROLLUP) gives you the curve. What used to live in the head of the most experienced revenue manager becomes a dashboard anyone on the team can read.

What pace tells you

Read well, pace is not a loose figure: it is a signal with consequences. Here is what an honest pace puts on the table.

1. If you are ahead for a date: demand is arriving earlier than usual. You may not need to give away price yet, and you should watch that you do not fill up so cheap and so soon that you leave money on the table.
2. If you are behind: there is a gap that time alone will not fill. It is the early signal to push sales, review your presence across channels, or weigh a promotion, while there are still days for it to take effect.
3. If you are on track but pickup is cooling: the total looks healthy, but the engine lost power this week. Worth understanding why before the shortfall shows up in the accumulated number.
4. If one specific date drops off the pattern: sometimes it is not the whole month, it is a single weekend or holiday running soft. Pace by stay date surfaces what the monthly average would hide.
5. If the lead comes from a single channel or segment: the cross tells you whether your good rhythm is solid or hangs on one source that could switch off.

From dashboard to decision, live

A metric that anticipates is only useful if it arrives in time. That is why pace and pickup earn their real value when read on live data, not on last night’s close. A dashboard that updates with the operation lets you see the pickup rebound the same day it happens, filter by a stay date, and instantly understand why a weekend is running soft. And because you can schedule deliveries and alerts, no one has to be staring at the screen: the system warns you when a date’s rhythm steps outside what was expected, and the AI can flag the hidden pattern or the anomaly that the naked eye would miss.

If your team already lives in Power BI, Tableau or Looker, the same data travels there through an open API with a Bearer token: the pace you built here is not locked in. And if you want an outside yardstick, the R2-Index lets you compare your rhythm against an index, to know whether your shortfall is yours or the whole market’s.

The past explains; pace anticipates

You will still need the reports that look back: they are the ones that teach you, that give context, that close the books. But no hotel wins its best month in what has already happened. It wins it in the weeks before, in that window where the date has not arrived yet and every decision, push, wait, move the price, still fits. Pace and pickup are the two metrics that light up exactly that window. The past explains why you are where you are. Pace tells you where you are heading while you can still change course. Deciding better starts with looking at the right clock.