Update a Pricing Recommendation When Booking Lead Time Changes

A Saturday ten days out looks soft against last year's numbers. The pressure to raise or hold the rate lands on you before you finish the morning pickup report. Booking lead time shifts quietly. Guests start reserving later or earlier than the comparable period, and the number on your screen stops meaning what it used to. Update the rate on the old lead time assumption and you either leave revenue on the table or price out guests who are about to book. Getting this conversation right with your commercial director or general manager takes more than a good report. It takes a clear read of what changed, what that change actually means, and a specific plan for when you will look at it again.

Why this conversation goes wrong

The trouble starts with a simple mismatch. Your commercial director or general manager looks at rooms on books and sees a number lower than the same date last year. To them, that gap reads as a demand problem, and the fix looks obvious, drop the rate or raise it, depending on which story is running that week. You know the picture is more complicated. Guests may be booking the same rooms, just later, because they trust the property to still have availability close to the stay date. Or the channel mix has shifted, and mobile bookings that used to land at three days out are now normal at seven. If you cannot separate a lead time shift from an actual change in demand, you end up defending a number instead of explaining a pattern, and the conversation turns into a standoff.

There is a second failure mode that is just as common. Some revenue managers see the shift, understand it correctly, and then say nothing more than trust me, the data supports holding. That answer is true and useless at the same time. Leadership is not asking you to be right. They are asking you to show your work so they can make the same call you would make if they had the report in front of them. A recommendation without the comparison behind it invites a second guess. A recommendation with the comparison behind it, and a date to revisit it, tends to end the conversation instead of restarting it every morning.

Prepare the data before you defend the rate

Walk into this conversation with the comparison already built, not assembled on the fly while your director watches. Four pieces of preparation matter most.

1. Pull the comparable date, or better, the last three or four comparable dates, and compare rooms on books at the same lead time point, not just the same calendar date. Ten days out this year against ten days out last year, not October 10 against October 10.
2. Break the pickup down by channel. A shift toward direct and mobile bookings closer to the stay date looks very different from a broad drop in demand across every channel, even though both can produce the same rooms on books number.
3. Check for anything that changes the comparison itself. A citywide event, a competitor closing or opening rooms, a change in group business on the books, all of these can explain a gap that has nothing to do with price sensitivity.
4. Look at cancellations along with new bookings. A property that is picking up rooms but also losing them to cancellations at a higher rate than usual is not in the same position as one simply picking up more slowly.

Once you have this, decide the actual point in the calendar where you will look again, and write down what would change your recommendation. That single sentence, stated in advance, is what turns a defensive answer into a plan.

What to say when the rate looks too low for the date

On September 30, commercial director Helen asks Sam, the revenue manager, why the property has not raised the rate for Saturday, October 10, now just ten days out. Sam starts with the comparison, not an opinion. Last year's comparable Saturday had 64 rooms on books out of 100 sellable rooms at the same ten day mark. This year the same date has 49 rooms on books out of the same 100 sellable rooms. Sam adds that the last four comparable Saturdays all picked up heavily inside seven days, mostly through direct and mobile channels, and recommends holding the current rate while reviewing pickup and cancellations every morning through October 3.

Helen is not satisfied yet. She asks whether the market will actually fill without a rate cut. Sam does not guess and does not retreat either. Sam says the pattern from the last four comparable weekends supports holding the rate today, but calls it an estimate, not a guarantee, and commits to a specific date, October 3, seven days before the stay, to revise the recommendation if pickup slows, cancellations rise, or new event information changes the picture.

Helen asks the harder question next, what happens if pickup still has not shown up by October 3. Sam has an answer ready instead of building one on the spot. If the pattern breaks, the plan moves to a targeted rate reduction on direct and mobile channels first, rather than cutting the base rate across every channel at once. That keeps the property from discounting broadly on a signal that might turn out to be a timing shift rather than a real drop in demand.

Mistakes that weaken your recommendation

The most common mistake is treating a lower rooms on books number as proof that demand is soft, without checking whether the booking pattern itself has moved later. That confuses a timing change with a demand change, and it leads to rate cuts the market did not actually need.

The second mistake is leaving the review open ended. Saying you are watching it is not a plan, and it invites a repeat of the same conversation every single morning until someone forces a decision. Name the date and the trigger up front.

The third mistake is presenting the data without a recommendation attached to it. Your director does not want a spreadsheet read aloud, they want your judgment backed by the spreadsheet. The same habit, state what happened before you explain why, matters in other hotel conversations too, including when you Align Meal Service Timing With the Event Agenda for a group booking, where a schedule shift looks like a service failure until someone lays out what actually changed and when.

The fourth mistake is skipping the fallback plan. If you only have one answer, hold the rate, and no answer for what happens if the pattern breaks, you look unprepared the moment the numbers move against you.

Practice and score the conversation before it happens live

Run this scenario before you need it for real. Build a pickup report that shows bookings arriving later than the comparable period, add a pending local event to the mix, and have someone play the role of a commercial director who pushes on whether the market will fill. Then score the exchange on three things. Did the revenue manager state the observed change, the lead time shift itself, before offering any explanation for it. Did they separate that observed pattern from the forecast, naming it as an estimate rather than a fact. Did they name a specific date and a specific trigger for revisiting the recommendation, rather than leaving it open.

DealSpeak is built for exactly this kind of rehearsal, an AI counterpart plays the pushback and scores how you handled it, so you can run the exchange more than once before the real conversation happens with real revenue on the line. Find more Hospitality and Travel practice conversations for other scenarios you will face at a property, including how you Review a Disputed Minibar Charge With Clear Ownership when a guest disputes a charge at checkout.

Get this right and the conversation stops being a monthly argument about instinct versus numbers. It becomes a five minute update with a clear next checkpoint, and your director learns to trust the process even when the rate does not move the way they expected.