Review a Commercial Test When Results Differ From the Forecast

A commercial test on a weekday offer, a member rate, or a package almost always produces a number that does not match the forecast. That gap is not a verdict. It is a prompt to check what actually happened before anyone decides whether to kill the test, extend it, or call it a failure. As a revenue manager, your job in that moment is not to defend the forecast or apologize for it. Your job is to read the evidence and lead the room toward a decision it can trust.

Why this conversation goes wrong

This conversation typically happens under pressure. An owner or general manager sees a number below the forecast and treats it as an established fact. They want an answer fast, in a hallway or a five minute call, before you have looked at anything. If you defend the forecast on instinct, you sound defensive. If you agree the offer failed without checking the underlying data, you hand over a decision based on one weak data point. Both responses skip the actual work, which is comparing what was planned against what happened before assigning a cause.

The forecast itself is often the missing piece of context. A number like 30 room nights booked through an offer carries assumptions about audience size, open inventory, and the length of the test window. When someone treats that number as gospel, they forget it was built on inputs that can change without anyone noticing, a smaller email send, a blocked out Tuesday, a group booking that ate open rooms. Explaining that clearly, without sounding like an excuse, is the actual skill here.

How to prepare

Before you sit down with the owner or the general manager, pull three things, the original test brief, the actual delivery data, and the calendar for the test period. Confirm the dates, the segments, and the measure used to judge success. Then check three things against reality. First, did the offer reach the audience the plan assumed, at the size the plan assumed. Second, did inventory stay open at the level the plan assumed, or did an override, a group hold, or a blackout close it early. Third, did anything else move demand during the same window, a rate change, a competitor promotion, a shift in the group calendar.

Write the comparison down before the meeting. Put the forecast number next to the actual number, then list which assumptions held and which changed. This step is not optional. Reciting numbers from memory in a live conversation invites the other person to argue with your recollection instead of the facts. A one page comparison ends that argument before it starts.

Have a proposed next step ready too. A revenue manager who shows up only with an explanation for the past forces the other person to ask what comes next. A revenue manager who shows up with a comparison and a recommendation controls the pace of the conversation.

What to say

Picture a general manager who saw the report and wants an answer now. He might open with, "The weekday member offer forecast 30 room nights booked through it. Only eight came in. Do we kill it."

Answer with the comparison, not a defense. "The forecast assumed the email would reach 12,000 members and that 20 rooms would stay open each night through the test. The campaign actually reached 9,100 members, and Tuesday inventory closed early after a group extension. Eight room nights booked through the offer, well below the forecast. Before we say the offer failed, we need to compare this against similar weekdays without the offer, because a smaller audience and less open inventory would lower the result regardless of how members responded."

He may push back and ask what you actually think happened. Answer plainly and admit the limit of what you know. "I do not have enough evidence yet to say the offer underperformed on its own terms. The audience was smaller than planned and the inventory was tighter than planned, so this test was not run the way we designed it. What I can say is that the current number does not tell us whether the offer itself works."

He will likely ask what you recommend doing next. Give him one option, not three. "I propose running the offer again for two weeks after we confirm the full member list goes out and we protect the agreed inventory for those nights. We compare that result against similar weekdays, and I bring both the assumptions and the outcome to the commercial review, not just the final number."

That last line matters as much as the analysis. A recommendation with a clear owner and a clear next check is what turns a disappointing number into a decision the group can stand behind.

Mistakes to avoid

The most common mistake is answering with a cause before checking the evidence. Saying members did not want the offer, or the price point was wrong, sounds confident in the room and falls apart the moment someone finds the delivery numbers were off. Say only what the evidence supports, and say clearly when you do not yet know something.

A second mistake is treating the forecast as untouchable. If you argue the number should have hit 30 no matter what changed in delivery or inventory, you look like you are protecting your own model instead of learning from it. The forecast was a plan built on assumptions. When the assumptions changed, the forecast needed to change with them, and saying so out loud builds more trust than silence does.

A third mistake is leaving the room without a next step. A revenue manager who explains the gap well but stops there leaves the owner to invent their own plan, often one that ignores what you just explained. Always close with a specific proposal and a specific date to review it.

How to practice and score it

A revenue director coaching an analyst can hand them a test brief and an outcome report with one assumption changed, a smaller audience, a shorter window, or an inventory block that closed early. Ask the analyst to walk through the comparison out loud, the way they would in the room. Score three things. Did they compare the actual result against the forecast using the same dates and segments. Did they avoid naming a cause the data does not support. Did they end with a proposal that includes a way to check it later.

This is exactly the kind of rehearsal DealSpeak is built for. Practicing the exchange with an AI counterpart that pushes back the way a real owner does, asking for the answer now, questioning the forecast, demanding a recommendation, builds the habit of leading with evidence under real pressure. The scoring shows whether you controlled the conversation or just reacted to it.

If you want more scenarios like this one, the Hospitality and Travel practice conversations cover related situations a revenue manager runs into often. Two worth a look are Handle a Competitor Rate Request With Enough Commercial Context and Handle a Concession Request Outside Approved Authorityboth built around the same idea, that a good outcome depends on preparation before the conversation starts.

A result that misses the forecast is not a failure to explain away. It is a set of facts to check before anyone decides what happens next. Do the comparison, say plainly what you know and what you do not, and leave with a next step the group can act on.