Booking pace and pickup reports: reading hotel demand early
Pace tells you the position, pickup tells you the velocity. How to read both, the right baselines, and the channel segmentation that makes the difference.
Luska Research
Pricing & Yield Team
Most hotels know last night's occupancy. The good ones know what next Saturday's occupancy will be by Wednesday — and have already repriced twice because of it. That gap is what booking pace and pickup reports close.
The two reports, plainly
- Booking pace — for a future stay date, how fast rooms are filling vs the same days-out window last year (or a chosen baseline). Answers: are we ahead or behind?
- Pickup — how many net rooms were added (or cancelled) for a future stay date over a given period (last 24h, last 7d, last 14d). Answers: how fast is demand changing right now?
Worked example
Why pace alone isn't enough
Pace tells you the position. Pickup tells you the velocity. You need both because the same pace number can mean very different things:
- Ahead + accelerating pickup — confidently raise the rate, close the cheapest LOS/channel restrictions.
- Ahead + decelerating pickup — hold. The market may have peaked; pushing rate now risks killing momentum.
- Behind + accelerating pickup — hold or nudge up. The market is catching up; discounting would leave money on the table.
- Behind + decelerating pickup — act. Open restrictions, push promo channels, consider a tactical drop.
14–21d
Typical pickup window most useful for weekend leisure
60–90d
Typical pace window for group/corporate
Daily
Minimum cadence — anything weekly misses the inflection
Choosing the right baseline
Comparing to "same day last year" is the default but often the wrong choice. A 2025 baseline contaminated by a one-off event, a renovation, or a comp-set change will make every pace number lie. Better options:
- Same day-of-week, same weeks-out — controls for weekly demand cycles which matter more than calendar date.
- Trailing 4-week median — smooths out one-off weeks and adapts to the current demand regime.
- Forecast-vs-actual — the most honest version. Pace becomes "rooms on the books vs what our forecast said we should have by now".
The pickup horizons that matter
Most PMS reports show 1-day, 7-day, and 14-day pickup. Use them differently:
- 1-day pickup — noise + signal. Useful only for the next 7-10 nights where one big pickup day can fill the hotel.
- 7-day pickup — the workhorse. Best signal for stays 14-45 days out, which is where most leisure repricing happens.
- 14-day pickup — group and conference business. Smooths out the lumpiness of B2B booking patterns.
The biggest pickup-report mistake
How pace and pickup feed the pricing engine
A yield engine that ignores pace is just a rate shopper with extra steps. Pace and pickup are the inputs that let you separate price-driven demand from market-driven demand. That difference is what tells you whether to raise rate (market pulling) or cut rate (price doing the work).
For more on the underlying KPIs, see what is RevPAR and ADR vs RevPAR vs GOPPAR.
What "good" looks like
- Daily refresh, not weekly. A 7-day-stale pickup number is a story, not a signal.
- Channel-segmented. At minimum direct vs OTA vs group/wholesale. Channel mix changes meaning.
- Paired with comp-set rate shop. Pace context only matters relative to what competitors are doing on the same dates.
- Tied to a recommendation. A pace report nobody acts on is overhead. Every pace reading should land on raise / hold / drop.
Pace, pickup, and the reprice in one view
Luska's hospitality dashboard surfaces pace vs flexible baselines, channel-segmented pickup, and an attached recommendation per stay date — no spreadsheet stitching.
See it for hotels