Booking Pace vs Pickup, in Plain English
Pickup is the net change between two snapshots. Pace is how fast a date fills against a benchmark. Both formulas, and the rule for using them together.
Pickup is the net change in reservations for a future date between two points in time — what you sold since you last looked. Pace is how fast that date is filling compared to a benchmark, usually the same date last year at the same number of days out. Pickup needs no baseline and tells you what just happened. Pace needs a baseline and tells you whether what happened is good. You move rate from pace and confirm the move with pickup.
The confusion is not your fault
These two words get used interchangeably in daily conversation, in reports, and in more than a few software glossaries that define one using the other. If you felt like the only person in the room who could not separate them, you were not.
They are genuinely different measurements with different inputs. One is a difference between two dates. The other is a comparison against a benchmark.
Get that distinction and the rest is easy.
Pickup: what sold since you last looked
Pickup is arithmetic on two snapshots of the same future date.
Pickup = rooms on the books today − rooms on the books at the previous snapshot
If your Saturday three weeks out had 19 rooms on the books last Monday and has 28 today, your seven-day pickup is +9.
That is the whole calculation. It needs no history, no last year, no budget. It works for a brand new hotel on its first week of trading, which is why it is usually the first number an operator learns.
Pickup can be measured in rooms or in revenue, over any interval — daily, weekly, or the classic "pickup since last Monday."
Pace: how fast is fast?
Pace answers the question pickup cannot: is +9 good?
Pace = your rooms on the books for a date, versus a benchmark at the same days-out
The benchmark is normally the same date last year at the same point in the booking curve — the industry says "same time last year," or STLY. It can also be your budget, or an average of comparable dates.
The critical part is at the same days-out. Comparing today's on-the-books to last year's final occupancy is not pace. It is a comparison between an incomplete number and a finished one, and it will make every date look catastrophic.
The difference, side by side
| Pickup | Pace | |
|---|---|---|
| Question it answers | What sold since I last looked? | Am I ahead or behind normal? |
| Inputs | Two snapshots of the same future date | On-the-books now vs a benchmark at the same days-out |
| Needs a baseline? | No | Yes — STLY, budget, or comparable date |
| Typical unit | Rooms or revenue, per interval | Rooms or percentage points vs benchmark |
| What it is good at | Detecting a change this week | Deciding whether your rate is right |
| How it misleads you | Nets off cancellations before you see it | Breaks when last year was abnormal |
| Time horizon | Between two points | Cumulative, along the whole booking curve |
Where they disagree — and what to do
The interesting cases are when the two point opposite ways. Take a 40-room hotel looking at a Saturday 21 days out.
| Scenario | Pickup last 7 days | On the books | STLY at 21 days out | Read |
|---|---|---|---|---|
| A | +9 | 19 | 26 | Busy week, still 7 rooms behind — do not relax |
| B | +2 | 34 | 22 | Quiet week because you are nearly full — hold or raise |
| C | +9 | 28 | 20 | Ahead and accelerating — move the rate up now |
| D | +1 | 14 | 15 | Genuinely soft. Check for a reason before touching rate |
Scenario A is the one that costs money. A strong pickup week feels like everything is fine, and pace says you are still seven rooms down on a date with three weeks left.
Scenario B is the mirror image — weak pickup is meaningless when there is barely any inventory left to pick up.
The rule: move from pace, confirm with pickup
Pace is your decision signal. It is the one that carries a judgment about whether your rate is right, because it holds your position against a night you already know the outcome of.
Pickup is your confirmation signal. After you change the rate, pickup over the next seven days tells you whether the market responded.
That order matters. Acting on pickup alone means reacting to noise. Acting on pace alone means never checking whether your action worked.
One caution on the benchmark: if last year's equivalent date had a festival, a closure, or a renovation, STLY is worthless for that date. Substitute a comparable date and note why.
The trap: pickup is a net number
This is the failure mode that catches experienced people. Pickup is calculated from on-the-books totals, so cancellations are already subtracted by the time you see it.
A week showing +4 could be four new bookings. It could equally be twelve new bookings and eight cancellations — a completely different business with a completely different risk profile.
The scale is not trivial. Cloudbeds' 2026 State of Independent Hotels, drawn from 90 million bookings across 180 countries using 2025 data, reported a cancellation rate of 21.8% on OTA bookings against 10.6% direct. If your channel mix is OTA-heavy, a meaningful share of your gross bookings is being netted away before it reaches your pickup figure.
The fix: pull gross new reservations and cancellations separately, at least monthly. Your property management system has both. If net pickup is flat while gross bookings and cancellations are both climbing, you have a cancellation problem, not a demand problem.
What you need to make either number work
Both metrics need snapshots — a stored record of rooms on the books for each future date, taken on a fixed day. No snapshot, no pickup and no pace.
Pick one day a week and export on-the-books by arrival date for the next 90 days. A spreadsheet tab per week is enough to start. Within three months you have a pace benchmark of your own, which is better than STLY for a hotel that has changed since last year.
How far out to look depends on your booking window — the gap between booking and arrival. Cloudbeds' panel put the independent booking window at 40 days; SiteMinder's Hotel Booking Trends panel for 2025 put the global figure at 32.15 days. The two disagree, so use them as a rough shape and build the real curve from your own snapshots.
The mistakes to avoid
Comparing on-the-books to last year's final number. Always compare at the same days-out.
Reacting to one week of pickup. Booking behavior is lumpy. Two data points are not a trend.
Using STLY for a date that is not comparable. An event that moved, a closed floor, a road works. Substitute and annotate.
Reading pickup as gross demand. It is net. Split out cancellations before you conclude demand is falling.
Tracking totals only. Pace by arrival date is the useful view. A strong month can conceal three disastrous Saturdays.
The bottom line
Pickup is the net change between two snapshots and needs no benchmark. Pace is your position against a comparable date at the same point in the booking curve, and it is the number that justifies a rate change. Take a weekly snapshot of on-the-books by arrival date, read pace to decide, read pickup to confirm, and split out cancellations before you trust either.
The tedious part is maintaining the snapshot history by hand for every future date. Our occupancy forecasting module builds the forward occupancy picture from a baseline percentage, by painting individual days, or from your own CSV or Excel upload. The benchmark you compare pace against then stays your own data, not an industry average.