Booking Pace

In hotel revenue management, booking pace is the speed at which reservations are accumulating for a future date, measured against where the same date stood at the same point in a comparable prior period.

It answers one question a nightly occupancy report cannot: not how full you are, but whether you are filling faster or slower than you should be, while there is still time to do something about it.

See how ampliphi reads booking pace for independent hotels

Get a free revenue audit · Book a demo

What is booking pace?

Booking pace is a comparison, not a count. The count is called on the books: the number of rooms currently reserved for a future date. Pace is what you get when you put that count next to the same date, at the same number of days out, in a period you consider comparable. Usually that means the same date last year, or the same weekday in a recent comparable week.

The distinction matters because a raw on-the-books figure carries no verdict. Nineteen rooms sold for a Saturday six weeks out is neither good nor bad until you know that the same Saturday held twelve rooms at the same point last year. Nineteen against twelve is a date running hot. Nineteen against twenty-six is a date in trouble. The number on the screen is identical.

Pace is also directional rather than absolute. It tells you the trajectory a date is on, which is why it is the earliest useful signal in revenue management. Occupancy tells you what happened. A forecast tells you what is expected. Pace tells you whether the expectation is currently being beaten or missed, and it tells you weeks before either of the other two notice.

Most properties look at pace across a rolling window: the next thirty, sixty and ninety days, by date, against the same window last year. That grid is the working surface for pricing decisions.

Resources: Pickup · On the books · Booking window · Rate calendar

How booking pace works in practice

Pace is read date by date, not as a portfolio average. An average across a month hides the two dates that matter and flatters the twenty-eight that do not need attention.

The mechanic is simple. For each future date, record rooms on the books today and the number of days between today and that date. Find the same date in your comparison period, at the same days out, and record what was on the books then. The difference is your pace. Expressed as rooms, as a percentage, or both.

Worked example. A 46-room inn looking at Saturday 14 November, 45 days out, has 19 rooms on the books. At the same 45 days out last year that Saturday held 12. The date is running 7 rooms ahead, or 58 percent up on pace.

That property's booking curve says a November Saturday sitting at 12 rooms on day 45 typically finishes around 38. Running 7 ahead of that curve points at a sellout somewhere near 10 days out. The decision is to raise the rate now, while 27 rooms are still available to sell at the higher number, rather than at the point the date sells out and the chance has already gone.

The same property's Tuesday 17 November holds 4 rooms against 9 last year, at the same 45 days out. The instinct is to discount. At 45 days out that instinct is usually early, because a short-lead midweek date does most of its booking inside the final fortnight.

The two dates sit four days apart in the same month at the same property, and pace points in opposite directions. That is the case for reading it by date.

Resources: Demand forecasting · Need date

Why booking pace matters for independent hotels

At a chain property somebody watches pace for a living. At an independent it is usually the owner, between a supplier call and a staffing problem, if it gets watched at all.

That is what makes pace the highest-value number an independent can learn to read. It is the only widely available signal that arrives early enough to act on. Occupancy and ADR report the result of pricing decisions that were made weeks ago. By the time a slow date shows up in an occupancy report, the window in which a rate change could have filled it has closed, and all that is left is a discount.

The cost of not watching it is specific and it runs in both directions. Dates that fill early get sold at a rate set months ago, before anyone knew demand would arrive. Dates that fill late get discounted in the final week, when the guests who book at the last minute are the least price-sensitive of the year. Both are the same mistake: a rate that was set once and never revisited against how the date was actually selling.

Resources: Revenue management for independent hotels · Dynamic pricing

How to read booking pace at your property

You do not need a revenue management system to start. You need a consistent method and about twenty minutes a week.

1. Pick your comparison period first. Same date last year is the default. If last year was distorted by a renovation, a closure or an unusual event, use the same weekday in a recent comparable week and write down why.
2. Fix your reporting day. Pull the report on the same day each week. Pace read on a Monday and pace read on a Friday are different numbers for reasons that have nothing to do with demand.
3. Export on the books by date for the next 90 days, from your PMS or channel manager. Most will produce this as a pickup or pace report. If yours only gives you today's occupancy, export weekly and build the history yourself.
4. Compare at equal days out, never at equal calendar dates. This is the step most people get wrong. A date 30 days away has to be compared with where that date stood 30 days before it arrived last year, not with where the calendar sat last October.
5. Sort by variance, not by date. The dates furthest ahead and furthest behind are the only ones needing a decision this week.
6. Act on the extremes and leave the middle alone. A date within a room or two of last year does not need you.

Resources: Pickup · Channel manager

What booking pace will not tell you

Pace tells you that something changed. It never tells you why. A date running 8 rooms ahead could be a conference nobody told you about, a competitor closing for refurbishment, or one corporate account booking a block. Those three call for three different rates, and pace cannot distinguish between them.

It also says nothing about what you are earning. A date can run well ahead on pace because the rate is too low, which is the most common reason a date runs well ahead on pace. Read alongside ADR or you will congratulate yourself for selling cheaply.

And it is noisy at small room counts. At 25 rooms, a single booking is four percent of the house, so a two-room swing that means nothing will read as an eight percent move. The smaller the property, the more you should watch the direction over several weeks rather than reacting to a single week's variance.

How ampliphi approaches booking pace

Ampliphi's everyday rate suggestion is demand-based, built on booking pace and occupancy. The system watches how each future date is filling against its own history and suggests a rate accordingly, per date, rather than asking you to run the comparison by hand each week.

Two things worth being clear about, because they are often bundled together and should not be. Competitive insight is a separate view. You choose up to five competitors to watch, and it does not feed the everyday demand-based suggestion. Event data is a separate module again, not part of the base product.

The suggestion covers your base rate and the differential between room types, which is the part most tools leave to you. You approve every rate before it publishes. Auto-publish is available once you trust the suggestions, and it stays optional. Ampliphi runs on top of the PMS you already use, so the pace history you have been building does not move anywhere.

Key takeaways: booking pace

• Booking pace is on the books for a future date compared with the same date at the same days out in a comparable period. The comparison is the whole point.
• It is the earliest actionable signal in revenue management. Occupancy and ADR report decisions already made.
• Read it date by date. Monthly averages hide the dates that need a decision.
• Compare at equal days out, not equal calendar dates.
• Pace tells you that something changed, never why, and never whether your rate was right.
• At small room counts, watch the trend over several weeks rather than any single reading.

Frequently asked questions about booking pace

How far out should a small independent hotel start watching booking pace?

Start at your booking window plus roughly half again. If most of your reservations arrive 21 days before check-in, a 30 to 45 day view captures nearly every date while there is still time to change a rate. Watching 180 days out is mostly noise for a property with a three-week window, because almost nothing is on the books yet and a one-room difference reads as a large percentage swing.

The exception is dates you already know are different. Holiday weekends, local events and peak season weeks book far earlier than your average date and deserve a longer view. Many independents run two horizons: a rolling 45 days for normal trading, and a named list of ten or fifteen high-demand dates watched from six months out. That is more useful than extending the whole grid and drowning in dates that have not started booking.

My property is too seasonal for last year to be a fair comparison. Is booking pace still useful?

Yes, though you will need a different comparison period. Year on year at the same days out is the default because it controls for seasonality automatically, but it fails when last year was distorted, when you have changed your mix, or when the property has been repositioned.

The alternative is to compare a date against the same weekday in a recent comparable week, or against the trailing four-week average for that weekday. You lose the seasonal control, so you have to supply it yourself by only comparing like with like. A November Tuesday against other November Tuesdays, never against a July Tuesday.

There is a harder version of this objection, which is that a property is genuinely unlike anything nearby and so comparison of any kind does not apply. That argument has real force against comp-set pricing. It has much less force against booking pace, because pace compares your property to itself. You are not being measured against the hotel down the road. You are being measured against how this same date sold for you last time.

What is the difference between booking pace and pickup, and do I need to track both?

Pickup is the number of rooms added for a future date over a defined recent window, usually the last seven days. Pace is your cumulative position against a comparison period. Pickup is the increment. Pace is the running total.

They answer different questions. Pickup tells you what happened this week, which is the fastest way to spot a date that has just started moving. Pace tells you where a date stands overall, which is what you need before changing a rate. A date can have strong pickup and still be badly behind on pace, and that date needs a different decision from one with weak pickup that is comfortably ahead.

Most independents get most of the value from pace alone and add pickup once the weekly review is a habit. If you only track one, track pace.

Booking pace is ahead but my ADR is down. Which one should I act on?

Both, and in that order. Pace ahead with ADR down usually means the rate is too low for the demand arriving. You are buying occupancy you would have got anyway. The first move is to raise the rate on the dates furthest ahead on pace and watch whether pickup slows. If it holds, raise again.

Check the mix before you do, though. The same pattern appears when a lower-rated segment has grown, such as an OTA promotion running longer than intended or a negotiated rate picking up volume. In that case the fix is the channel or the rate plan, not the headline rate.

The mistake to avoid is treating strong pace as a result. Pace ahead of last year at a lower rate can be worse business than pace behind at a higher one. RevPAR is what settles it.

Can I track booking pace without a revenue management system?

Yes. A weekly export of on-the-books by date into a spreadsheet, pulled on the same day each week, gives you a usable pace view inside two months and a full year-on-year comparison after twelve. Plenty of independents run exactly this and price well from it.

What the manual version costs you is timeliness and coverage. A weekly snapshot misses a date that moves on a Wednesday. A hand-built grid tends to get checked for the coming month and not the one after. And the analysis competes with everything else in the week, so it is the first thing dropped when something breaks.

The honest framing is that pace is a discipline before it is a tool. If you are not watching it at all, a spreadsheet started this week beats software bought next quarter. If you are already watching it and losing the hour, that is the point where automating it starts to pay.

Related terms

Pickup

The rooms added for a future date over a recent window, usually seven days. Where pace is the cumulative position against a comparison period, pickup is the fresh increment. It is the faster of the two signals and the noisier one, which is why most properties act on pace and use pickup to spot a date that has only just begun to move.

Booking window

The average number of days between a reservation being made and the guest arriving. It sets how far ahead pace is worth watching, because a date that has not entered its booking window yet has almost nothing on the books to compare. A property with a three-week window and one with a three-month window need different pace horizons.

On the books

The count of rooms already reserved for a future date. It is the raw input to pace, and on its own it carries no verdict, because the same figure can mean a date running hot or a date in trouble depending on what it stood at last time.

Demand forecasting

The prediction of how many rooms will sell on a future date, built from history, pace, market conditions and known events. Pace is one of the main inputs. The difference is that a forecast states an expected outcome, while pace states whether that expectation is currently being beaten or missed.

Need date

A future date forecast to underperform, where extra demand is actively wanted. Need dates are usually identified from pace: a date running consistently behind its comparison period, far enough out that a rate or restriction change can still fill it.