Revenue and pricing

Demand signals in hotel revenue management: pace, searches, lead time and other terms

Learn how to define and use hotel demand signals like pace, lead time and pickup. Build a one-page sheet with baselines and owners to guide your revenue decisions.

  • 10 min read
  • AI Otel Editorial

AI draft · awaiting editorial review

Contents

Key takeaways

  1. Pickup is a quantity and pace is a speed; neither means anything until you state the baseline date you are comparing against.
  2. Lead time is only useful as a distribution by segment and channel, because an average hides a mix of very early and very late bookers.
  3. Website visits and quote requests measure intent, not commitment, so they belong next to bookings, never instead of them.
  4. A cancellation is information twice: once when it happens, and again when you see which rate plan and which dates it clustered on.
  5. A signal earns its place on the sheet only if it arrives early enough to change a decision, and if you can check later whether it was right.

Demand signals are early readings a hotel takes before bookings arrive: booking pace (how fast rooms are being taken), pickup (rooms added since a set date), lead time (days between booking and arrival), website visits, inquiries, cancellations and competitor moves. Each is a clue to check, not a forecast.

The pace report says the month is behind last year, the website just had its best week of the season, and two agencies asked for quotes that went quiet. Three readings, three different stories, and only one of them is about demand. This article defines each hotel demand signal, says where to find it, and shows how each one misleads when read alone. After reading, you will be able to build a one-page signal sheet with baselines, thresholds and owners.

What are hotel demand signals?

A demand signal is any reading taken before the booking that changes what you would do today. It is not a forecast: it is evidence you weigh, date and compare.

Start by separating a metric from a signal. Occupancy last month is a metric: it describes what already happened. A rise in quote requests for a date three weeks out is a signal: it hints at what is still coming. Both belong on reports, but only the second one can change today's decision.

Signals come in three families. Commitment signals are bookings, deposits and group contracts. Intent signals are searches, website visits and quote requests. Removal signals are cancellations, no-shows and rooms taken out of sale. Read all three, because they move at different speeds: intent moves first, commitment follows, removal runs alongside both.

Apply three tests before a signal goes on your sheet. Is it early enough to act on? Is it specific to a date, a segment or a channel? Can you check later whether it was right? A signal that fails any of the three is decoration.

Every signal needs a comparison base: the same point last year, the budget, or last week. A number without a base is a mood, not a reading. Write the reading down before the outcome: a short note of what you saw, what you decided and what happened turns a habit into a feedback loop. And never act on one signal alone. Pace, lead time and cancellations frequently point in different directions, and the disagreement is the useful part.

Key pointA demand signal is a reading taken before the booking that would change a decision today. It needs a date, a baseline and an owner, or it is just a number on a screen.

A demand signal is a reading taken before the booking that would change a decision today. It needs a date, a baseline and an owner, or it is just a number on a screen.

Pace vs pickup: what is the difference?

Pickup is how many rooms were added to the books between two dates. Pace is how fast they were added, usually expressed per day or week, or as a comparison with the same point in a previous period.

Pickup answers "how much". Pace answers "how fast". A hotel can show strong pickup for a month and still be behind, if the comparison period added more in the same window. Both require a stated baseline date. "Pickup of 40 rooms" is meaningless until you say "since the first of the month" or "since the same day last year".

Pace hides mix. Forty rooms taken as long low-rate stays is a different month from forty rooms taken as short high-rate stays, even though the pace line looks identical. Read pace by segment and by channel, not only in total. Groups, corporate and online travel agency business move on different clocks, and a total can mask one segment collapsing while another carries the month.

Calendar shifts break naive year-on-year comparisons. School breaks, religious holidays and fairs move between years, so compare against a demand calendar rather than the same calendar date. A pace report is a snapshot of a moving object, so read it on the same weekday each week to keep the comparison stable.

TermWhat it countsBaseline you must stateHow it misleads
PickupRooms added between two datesThe earlier dateLooks strong when the comparison period was weak
PaceRooms added per day or week, or versus a prior periodThe prior period and the reading dayHides segment and length-of-stay mix
Rooms on the booksTotal committed for a stay dateToday's dateSays nothing about fill speed or cancellations
CancellationsRooms removed from the booksOn-the-books at period startA healthy pickup figure can be net of heavy churn

For a day-by-day reading method, see our guide on how to read a hotel pickup report day by day.

What does lead time tell you?

Lead time, also called the booking window, is the number of days between the day a booking is made and the arrival date. It tells you when your demand arrives, which decides when you can still change price and availability.

Track it as a distribution, not an average. A hotel with a 30-day average may be taking half its rooms 90 days out and half in the final week; the average hides both behaviors, and the two need opposite decisions. Lead time is also segment-specific. Leisure, group, corporate and agency business each have their own rhythm, so measure per segment and per channel.

A shortening window is neutral on its own. It can mean late demand is strengthening, or that early demand never came and the rooms are simply still open. Pair the window with pace. Short lead time plus strong pace means the market is buying late. Short lead time plus flat pace means you have a gap to fill and less time to fill it.

Lead time sets your deadlines, not your prices. It tells you the date after which a discount stops being an early-booking decision and becomes a clearance decision. Watch the tail as well: the share of bookings made inside seven days is the part of the month you cannot influence, so it should be planned for rather than reacted to. For the segment-level method, see booking window analysis by segment.

What do website visits and searches tell you about demand?

They measure intent, not commitment. Visits and searches show that people are considering a stay; they do not show that anyone will book, and they are easy to misread.

Use a look-to-book ratio: visits or availability searches divided by completed bookings for the same period. Read it against your own history, not against an industry figure, because no reliable public benchmark exists. Distinguish branded interest from destination interest. People searching your hotel's name already know you; people browsing the destination have not chosen a hotel yet, and that is where share can be won or lost.

Weight dated actions above general browsing. A view of the availability calendar for specific dates is a far stronger signal than a homepage visit. Separate human visits from automated ones: price-comparison crawlers and monitoring tools inflate traffic without any intention to book, so a spike should be checked before it is believed.

A visit spike with no bookings is a question, not a conclusion. It can mean price, minimum-stay rules, sold-out dates or friction at the booking step. Treat the numbers as a relative index against your own baseline, and do not present search volumes you cannot see reliably as market measurement.

Watch outA traffic spike is not demand until it passes three checks: is it human, is it tied to specific stay dates, and is it new rather than the same visitors returning?

A traffic spike is not demand until it passes three checks: is it human, is it tied to specific stay dates, and is it new rather than the same visitors returning?

What do inquiries, cancellations and no-shows signal?

Inquiries show intent with a price attached, and cancellations show commitment being withdrawn. Both are early, both are specific, and both are usually logged badly or not at all.

Log every quote request with the date received, the stay dates, the party size, the channel and whether it converted. Without the stay dates, a quote log cannot be compared with anything. Quote requests that never convert cluster: if they gather around one date range or one price level, that is a reading about your position, not about the enquirer.

Track cancellations as a share of the rooms on the books at the start of the period, and split them by rate plan. Flexible bookings cancel first, so their movement is the earlier warning. Separate a cancellation from a date change and from a room move. A modification keeps the demand; a cancellation removes it; mixing the two in one figure hides both.

No-show rates belong by channel and by market, because they reflect how the booking was taken and who took it, not how the month is going. When cancellations cluster on a single date, look outward before looking inward: a cancelled event, a competitor promotion or a travel advisory can explain a pattern that no pricing change will fix. Re-sell cancelled rooms immediately and note how long they took to return to the books. That recovery time is itself a demand reading.

How do competitor set changes show up as a signal?

A competitor set is the small group of properties you actually lose bookings to, not every hotel nearby. Changes in what they sell and how they sell it are public, dated and free to observe.

Define the set by lost business, not by postcode. Ask which properties appear when guests compare, and which ones your team hears about at the desk. The strongest public signal is a closed date. A property that stops selling a night is telling you it believes it can fill it, which is a reason to re-check your own availability and rate for that night.

Watch structural changes as well as prices: a new room type, a changed minimum-stay rule, a new package, a renovation, a change in board basis. Review volume and rating movement are slow signals but honest ones: a property gaining review volume is gaining guests.

One screenshot on one day proves nothing. Rates move, channels differ and availability is often opened and closed within hours. Keep the observation routine fixed: same days of the week, same channels, same future dates. A comparable series beats a large one.

How do you keep a signal sheet?

One page, one row per signal, read on a fixed day, with a baseline, a threshold and a named owner. The sheet exists to force a decision, not to store data.

Start with three signals you can already read from systems you have: pickup against a stated baseline, lead-time distribution by segment, and cancellation movement by rate plan. Add a signal only when it passes the three tests: early enough to act on, specific to a date or segment, and checkable afterwards.

Record the reading, the decision and the reason on the same row. Six weeks later, the reason is worth more than the number. Review the sheet monthly and retire signals that never changed a decision; a long sheet that nobody reads is worse than a short one that is read every week. Keep the sheet next to the on-the-books view, not instead of it: signals explain the forecast, they do not replace it. Anchor the calendar side of the sheet to known holidays, school breaks and events, so a pace gap can be read against what the month actually contains. For the forward view, pair the sheet with estimating the next 90 days from what is on the books, and build the calendar side from a hotel demand calendar with holidays and events.

ChecklistThe one-page signal sheet needs

  • A named signal
  • Where it comes from
  • How often it is read
  • The baseline it is compared with
  • The threshold that triggers a decision
  • The owner
  • The reading, the decision and the reason, dated
  • A monthly note on whether the signal was right

What to do next

Build the one-page sheet this week with three signals you can already read, give each one a baseline, a threshold and an owner, and read it on the same day every week for a month. Pace, lead time, visits, inquiries, cancellations and competitor moves only become useful when they sit side by side and are checked against what actually happened.

Frequently asked questions

What is the difference between booking pace and pickup?

Pickup is the number of rooms added to the books between two dates; pace is the speed of that addition, per day or week, or compared with a prior period. Both need a stated baseline date. Pickup answers how much, pace answers how fast, and neither says anything about the mix of segments or length of stay behind the number.

Is a rise in website traffic a reliable demand signal?

It is a signal of intent, not of commitment, and it must be checked first. Confirm the visits are human rather than automated crawlers, that they are tied to specific stay dates rather than general browsing, and that they are new rather than returning visitors. A spike with no bookings is a question about price, availability or the booking step, not proof of demand.

Should a hotel track average lead time or the full distribution?

Track the distribution by segment and channel. An average can hide a mix of very early and very late bookers who need opposite decisions. The share of bookings made inside the final week is the part of the month you cannot influence, so plan for it rather than react to it.

Do cancellations count as a demand signal?

Yes, and an early one. Track cancellations as a share of the rooms on the books at the start of the period and split them by rate plan, because flexible bookings cancel first. Keep cancellations separate from date changes and room moves, and look outward when they cluster on a single date.

How many demand signals should a hotel follow?

Few enough to read every week and act on. Start with three: pickup against a stated baseline, lead-time distribution by segment, and cancellation movement by rate plan. Add a signal only if it arrives early enough to change a decision, is specific to a date or segment, and can be checked afterwards.

AI Otel EditorialEditorial team

Drafted with AI assistance from AI Otel’s published fact base. Not yet reviewed by an editor.

For hotels: OtelCiro.

OtelCiro, AI Otel’s hotel growth and consultancy arm, is operating today.

Talk to OtelCiroRequest a briefing