Revenue blog · 11 min read · 21 May 2026
Hotel Pickup and Pace: The Daily Metrics That Actually Drive Pricing
The first revenue manager I worked under had one rule before any pricing decision: read the pickup. Not the forecast, not the budget variance, not the comp-set rate floor. The pickup. Twenty seconds with a printed report and the rest of the day fell into place. Two years later I had moved properties twice, seen four forecasting modules, and still ran the same rule. Hotel pickup and pace are the two daily numbers that should drive every pricing decision you make. Everything else is supporting evidence. If you only read two reports a day, read these two — in this order.
What hotel pickup and pace actually mean in 2026
The textbook definitions are clean: pickup is the change in rooms-on-the-books between two snapshot points; pace is the cumulative on-the-books position versus a reference. The first is a flow, the second is a stock. They answer two different questions.
Pickup answers: what came in overnight? Pace answers: where are we against where we should be? Both matter, but they trigger different decisions. Pickup tells you whether to move rate today. Pace tells you whether the strategy is working over the rolling window. Mix them up and you either over-react to noise or under-react to a quietly drifting forward book.
When I talk about hotel pickup and pace, I mean a specific operating pair: a daily 24-hour pickup snapshot for the next 90 dates, plus a same-time-last-year pace comparison for the next 14, 30, 60 and 90 days. Two reports. One ritual. Twenty minutes.
Pickup: the formula and the worked example
The pickup formula is the simplest piece of arithmetic in revenue management:
Pickup for date D over window W = rooms-on-the-books for D at end of W, minus rooms-on-the-books for D at start of W.
The window is almost always 24 hours, measured at the same time each morning. D is every future date in the booking horizon, usually 90 days. The output is one pickup number per future date — letting you see not just how many rooms came in, but which dates they came in for.
A worked example on a 120-room urban property. Yesterday at 06:00 the rooms-on-the-books position read: Mon 62, Tue 71, Wed 74, Thu 85, Fri 96, Sat 102, Sun 58. This morning at 06:00 the same view reads: Mon 64, Tue 73, Wed 77, Thu 91, Fri 109, Sat 113, Sun 60. Daily pickup is Mon +2, Tue +2, Wed +3, Thu +6, Fri +13, Sat +11, Sun +2 — a total of +39.
That +39 headline is the least useful number on the page. The signal is in the shape: Friday and Saturday together accounted for 24 of the 39, the Sunday is dragging, and the Thursday-Friday combination is firming faster than the rest of the week. The forecasting habit covered in hotel demand forecasting tells you what each future date should do. Pickup tells you what each date actually did in 24 hours. The gap between the two is your daily decision queue.
Pace: the formula and the worked example
Pace is harder than pickup, because the reference point matters and the reference point is almost always something other than yesterday. The most useful reference is same-time-last-year — rooms-on-the-books for the same future date at the same days-out point a year ago. The formula:
STLY pace for date D = rooms-on-the-books for date D today, minus rooms-on-the-books for date D at the same days-out point last year.
Same-day calendar comparisons do not work for hotels because day-of-week shifts year on year. The correct comparison is days-out. If today is Tuesday 21 May 2026 and the future date is Friday 26 June, the days-out is 46. The reference is rooms-on-the-books for the equivalent Friday in 2025 as recorded 46 days out from that date.
For that Friday, today's on-the-books is 67. The 46-days-out snapshot last year was 52. STLY pace is +15 rooms, or +29 percent. That is decision-useful. Run it for every date in the next 90, plot on a colour scale (red behind, amber flat, green ahead), and the demand calendar starts writing itself. The same logic feeds the metric stack covered in ADR vs RevPAR vs GOPPAR.
Pickup versus pace, side by side
The cleanest way to keep the two straight is a small comparison table you can pin above the desk:
| Pickup | Pace | |
|---|---|---|
| Question it answers | What came in overnight? | Where are we against where we should be? |
| Type | Flow (delta) | Stock (cumulative) |
| Window | Usually 24 hours | Cumulative to a future date |
| Reference point | The previous snapshot | Same-time-last-year or budget |
| Triggers | Today's pricing moves | Strategic adjustments and channel actions |
| Review cadence | Daily, every morning | Weekly for 90d, daily for 14d |
| Failure mode | Over-reacting to a single day of noise | Reading the headline number without segment context |
Both belong on the morning report. Pickup is the front page. Pace is the back page.
Where hotel pickup and pace break down
Three failure modes I see repeatedly:
1 — reading pickup without segmentation. A +39 daily pickup is meaningless without knowing where it came from. Forty rooms of corporate-rate pickup is a different signal to forty OTA rooms or to a single group block landing. Every pickup report should break out by segment and by channel.
2 — reading pace without booking-window context. A pace of +12 on a date with a normal six-week booking window is genuinely ahead. The same +12 on a date inside a two-week-lead market is the booking happening on schedule. Pace must be read against the typical lead-time for the segment mix on that date.
3 — treating pickup as a forecast. Extrapolating the last seven days of pickup linearly is wrong for any date with non-linear booking behaviour — every event date, every public holiday, every long-weekend Friday. Pickup refines the forecast. It is not the forecast.
The way out of all three is the same: a disciplined daily ritual that reads both numbers, segments them, and writes a one-line note for every override.
What to do about it — the five-step pickup-and-pace ritual
The morning sequence I run on every property. Twenty minutes when the data is clean, forty when it is not. It is the foundation the rest of the day's pricing decisions sit on.
- Pull yesterday's 06:00 and today's 06:00 snapshots. Same time, every morning. Different snapshot times produce different pickup numbers and a moving baseline.
- Compute daily pickup by date for the next 90 days, segmented by market and channel. Total pickup is the headline. The shape is the signal. Three dates picking up together in the same week is rarely random.
- Compute STLY pace for the next 14, 30, 60 and 90 days. One number per window. A widening gap between the 14-day and 90-day pace numbers signals the booking window is shifting — usually because rate, demand, or both are moving.
- Identify the three dates with the largest pickup-versus-forecast gap and the three with the largest pace deviation. Those six dates are the day's decision queue. Everything else can wait.
- Make the call and write the note. For each of the six dates, decide: hold rate, lift rate, drop rate, or open and close restrictions. One line per move. Reviewed at month-end against the actual outcome.
The ritual is deliberately boring. Boring is the point. The advantage is not in any one day's number — it is in the cumulative effect of reading them properly, every morning, for two hundred and fifty trading days a year.
A real scenario: 90-key boutique, soft-shoulder Tuesday
A 90-key boutique in a regional capital, mid-2024. Soft Tuesday three weeks out — 28 on the books, forecast 41, STLY pace at the same days-out was 38. Top-line pickup the previous morning was +3 across the next 90 days. Headline was unremarkable. The forecasting module had flagged nothing.
The shape told a different story. Of the +3, the Tuesday in question picked up zero. Of the previous five days, the same Tuesday had picked up minus 2, zero, plus 1, zero, and zero. Cumulative six-day pickup on that single date: minus 1. STLY pace had drifted from +4 to minus 10 over the same week — pace had gone from green to red without ever flagging on the headline because the headline was averaging across every other date in the window.
The override was a 9 percent rate reduction on that specific Tuesday plus re-opening one shoulder-rate channel. Pickup the following morning was +4 on that date alone. The property ended at 64 occupied — eleven short of forecast, but twenty-six ahead of the no-action trajectory. Roughly A$3,200 in incremental revenue on a single soft Tuesday. Across a year of disciplined pickup-and-pace reading, the same property added two to three points to annual occupancy without lifting ADR.
How pickup and pace fit the rest of the stack
Pickup and pace are not the strategy. They are the input that makes the strategy readable. The broader stack of channel decisions, segment work, and owner reporting covered in hotel revenue management strategies for 2026 all runs off the same daily ritual.
Macro context also matters. The Australian Bureau of Statistics short-term visitor data and the Tourism Research Australia outlook are free reference points. Pace red while macro shows growth → property-specific. Pace red while macro is softening → same trend as the country.
FAQ — hotel pickup and pace
What is hotel pickup?
The change in rooms-on-the-books between two snapshot points, usually 24 hours apart, for one future date or a window of future dates. If the property had 38 on the books for next Friday yesterday and 47 today, pickup for that Friday is 9 rooms. Read it by date, segment, and channel — not just as a headline.
What is hotel pace?
The cumulative on-the-books position for a future date at a specific days-out point, compared against a reference. Most commonly the reference is the same date last year at the same days-out (STLY pace). Most useful when read across 14, 30, 60 and 90-day windows so the booking-window shape is visible.
What is the difference between hotel pickup and pace?
Pickup is a flow — how many rooms came in over a 24-hour window. Pace is a stock — where the cumulative position sits versus where it should be. Pickup triggers today's pricing moves. Pace triggers strategic adjustments. Read pickup first, pace second.
What does negative pickup mean for a hotel?
More rooms were cancelled or released than were booked over the measurement window. A single day is rarely a signal. Three days in a row of negative pickup on the same future date is a signal that demand for that window is softer than expected.
How do I calculate STLY pace?
Take rooms-on-the-books for a future date today, then for the same future date at the same days-out point last year. The difference is STLY pace. Forty today versus 35 at the same point last year is +5 rooms or roughly +14 percent. The comparison must be days-out, not calendar-date.
How often should hotel pickup and pace be reviewed?
Pickup daily, first thing in the morning. Pace weekly for the 90-day window, daily for the 14-day window. Properties with a heavy short-window segment mix should be running daily pace reads across the next 21 days at minimum.
Can pickup and pace be automated?
The arithmetic can and should be automated. The interpretation cannot. A pace of +12 on a Friday in a quiet quarter and the same +12 on a Friday in a compressing market are two completely different signals. Automation handles the numbers. The human reads the context.
A note on what this is for
Pickup and pace are the cheapest, most repeatable advantage in this industry. No licence, no module, no consultant required — twenty minutes a day and the discipline to do it for two hundred and fifty mornings in a row. Done properly, they make every other lever easier. Done poorly, they turn into a headline number nobody acts on.
That discipline is what we built RevPerfect for: a daily pickup-and-pace view that segments automatically by channel and market, ranks the dates with the largest pace deviation, and keeps override notes alongside the numbers so the calendar compounds month over month. One input into the broader habit covered in hotel revenue management strategies for 2026, but pickup and pace are where most operators get the most immediate value because the ritual pays back on day one. Try RevPerfect free → or book a 20-minute walkthrough.