Separate Booking Pace From a Forecast in an Owner Review

A booking pace report tells you what has already happened. A forecast tells you what you expect to happen next. In an owner review, those two things get mixed together fast, and once they blend, every number in the room starts to feel like an opinion. Your job as the revenue manager is to keep the line between the two visible, put a source and a date on every figure, and be ready to say which decision depends on which number.

Why this conversation goes wrong

Owners look at pace against last year's pace on the same lead time, see a gap, and expect the forecast to close that gap or explain it. When you hand over a single blended number, or when you present the forecast with the same certainty as the pace report, you set yourself up for a hard question you cannot answer cleanly. The owner pushes on the gap, you start hedging, and now every number you shared that day looks shaky, even the ones that came straight from the reservation system. This happens most often around big demand drivers, a concert, a conference, a shoulder season shift, where the forecast leans on an assumption that has not shown up in bookings yet. The pace is fact. The forecast is a judgment call built on a handful of inputs. If you cannot name those inputs on the spot, you have not prepared the forecast, you have guessed at it.

Prepare before you walk in

Pull the pace number for the exact stay period the owner will ask about, along with the comparison period from last year at the same lead time. Write down the source and the date you pulled it, since pace changes daily and an owner will ask when the number was current. List every assumption behind the forecast on its own line, the added room nights from an event, the expected cancellations, any shift in length of stay, and give each one a confidence level in plain words, high, moderate, or low. Note the date you expect real data to confirm or contradict each assumption, so you are not guessing again next month. Decide ahead of time what decision each number supports, whether that is holding a rate, opening a rate plan, or adding staff for a weekend. Walk in without that mapping and you will find yourself answering pace questions with forecast language, and the owner will hear indecision instead of judgment.

What to say in the room

Owner Priya opened with the number that worried her. She said, we are 22 room nights behind where we were last year at this point for the weekend of the sixteenth, why does the forecast still show us matching last year.

Revenue manager Sam answered by separating the two figures. He said, the pace as of this morning is 158 room nights booked. Last year at the same lead time we had 180. Our forecast for the weekend is 210, and that number assumes 60 additional room nights from the festival two blocks from the property, plus 8 cancellations we expect based on the typical pattern for this date. The festival related bookings have not started showing up in our numbers yet, so I would call that part of the forecast moderate confidence, not high.

Priya asked what happens if the festival demand does not show up. Sam said, if we are still below 175 room nights by next Friday, I recommend we open our lowest rate plan to the wider market and stop holding rooms for festival rate shoppers. I will have that comparison ready either way.

Priya asked if 210 was a real number or a hope. Sam said, it is our best estimate given what we know today, and I am treating it as a working number until the festival pickup either shows up or does not. I will bring an updated figure Friday regardless of which way it moves.

That exchange works because Sam never lets one figure carry two meanings. Pace is booked. Forecast is a bet with named inputs. Every claim carries a source, a date, or a plan attached to it.

Mistakes to avoid

Do not present the forecast number first without giving the owner the pace number that grounds it, since a forecast with no anchor invites the owner to challenge the whole thing at once. Do not describe every assumption with the same level of confidence, because owners remember which prediction failed and will hold you to it the next time you claim certainty. Do not answer a pace question with forecast language, if an owner asks how many rooms are booked today, give the booked number, not the number you expect by the stay date. Do not skip the check date, an assumption with no date to confirm or kill it just sits there unresolved and comes back at the next review as if nothing happened. Do not treat pushback as an attack, an owner asking hard questions about a gap is doing their job, and a defensive answer reads as weak even when the underlying analysis was fine.

Practice it before the real review

Run this conversation before you are in the room with real ownership money on the table. Give an analyst one pace report and one forecast sheet and ask them to talk through both out loud, naming which claims come from booked reservations and which depend on an assumption that has not happened yet. A manager coaching a team can score the answer on three things, whether pace and forecast stayed clearly separated, whether every assumption had a named input and a confidence level, and whether the answer ended with a specific next step and date rather than a vague reassurance. DealSpeak builds these owner review conversations as rehearsal scenarios, so a revenue manager can practice against an AI owner who pushes back the way a real one does and get scored on exactly this kind of clarity. The Hospitality and Travel practice conversations cover related situations worth rehearsing the same way, including how to Explain an Unusual Cancellation Pattern With Clear Data Limits and how to Explain Who Handles a Cancellation Request Across Suppliers.

Owners do not expect a forecast to be perfect. They expect you to know which parts of your answer are facts and which parts are judgment, and to say so plainly. Get that separation right and a gap between pace and forecast becomes a normal part of the conversation instead of a crisis.