Can you trust the forecast? The owner's questions behind the GM's numbers

Wednesday afternoon. Annette, the owner of Hotel Peaqplus City, gets an email from Adam, the general manager: the third-quarter forecast. One number jumps out of it: 84 EUR expected RevPAR (revenue per available room). Annette would be glad of it, except that just two weeks earlier an acquaintance who owns another hotel was complaining that his management promised a beautiful forecast every quarter — and then reality kept coming in below it. Now Annette is looking at the same kind of sheet, and the question isn’t whether 84 EUR is good, but whether she should believe it.

This lesson is about how an owner reads management’s forecast without becoming a revenue manager or getting drawn into daily pricing. A forecast on its own is neither true nor false — only credible or not credible. The owner’s aim here isn’t to catch management out, nor to make a better number — but to have well-founded trust: to know what the number she was given is worth, and to understand the thinking behind it. And the best news is that this takes no detective work. If the hotel runs on a shared system where forecast accuracy is measured continuously and visibly to everyone, then trust is structural — it comes from the track record, not from the owner’s questioning. The four questions we’ll walk through are therefore not an interrogation, but the language of shared understanding.

Budget, forecast and actual — why the gap is no disgrace

First, let’s clarify what we’re even looking at. Three numbers circle around a hotel, and owners often mix them up:

• Budget — what we set once, in advance, at planning time. Fixed, for the whole year.
• Forecast — what we expect now, based on today’s bookings and demand signals. Continuously updated.
• Actual — what it turned out to be in the end.

Many owners instinctively treat the budget as the sacred number, and experience every forecast that departs from it as a failure: “why aren’t we hitting plan?” This is a mistake. The budget was made months earlier, with incomplete information; the forecast reflects fresh reality. If the two differ, that’s not a disgrace but information — indeed, a forecast that always shows exactly the budget is suspicious, because it probably isn’t watching the market but is being fitted to the plan. The right owner’s question, then, isn’t “why not the budget?”, but “what does the gap tell us, and how believable is the forecast that shows it?”

Forecast accuracy: the number that validates the others

How do you know a forecast is reliable? Not from the number itself — but from how well past forecasts held up. This is what we call forecast accuracy: we measure what management promised earlier against what finally happened.

Forecast deviation = |forecast − actual| / actual

The smaller and more stable this deviation is over recent months, the more management’s next promise is worth. A forecast’s value comes not from its beauty but from its past hit rate. The owner doesn’t work this out by hand — the Peaqplus Forecast module continuously measures the forecast back against the actual and reports the accuracy — but she does need to be able to read it.

And here’s the crux that flips the whole relationship: if this forecast accuracy is visible in a shared system, automatically and in front of everyone, then the owner doesn’t have to interrogate anyone after the fact. Management’s track record is continuously there before her eyes, and trust builds on its own — or erodes on its own. This is the difference between a suspicious and a calm owner relationship: not more control, but shared visibility. Without it the owner either believes blindly or micromanages; with the shared number, neither is necessary.

Two GMs, two forecasts — which one should Annette believe

Imagine two managements that give the same 84 EUR RevPAR forecast for the same Q3. The number is identical. But let’s look at how they performed over the past three months — that’s what decides which one to believe.

Let’s work one row so you can see the logic: April, “A” management — |78 − 79| / 79 = 1 / 79 = 1.3%. “B” management for the same — |85 − 74| / 74 = 11 / 74 = 14.9%.

Both managements promise the same 84 EUR for Q3. But “A” management’s forecasts over the past three months were on average within 1.6% — tight, stable, small deviation in both directions. “B” management’s forecasts were off by 13.4%, and systematically on the over-optimistic side (twice it promised far higher than the actual). When “A” says 84 EUR, Annette can realistically count on a band between 82 and 86. When “B” says the same, the 84 EUR could just as easily be 72. The same number, diametrically different worth.

This is the core of the lesson: a forecast has no value of its own without its track record. On seeing a pretty forecast, the owner’s first reflex should be not delight but the question: “how well did the last three you promised come in?”

The four questions with which the owner understands the forecast

Annette doesn’t need to become a revenue manager to understand the 84 EUR. Four questions are enough — each one a credible management answers gladly, immediately and concretely, because it lets them show their work. These aren’t traps: in a well-run hotel on a shared system, most of the answers are already on the screen; the questions serve the shared interpretation more than anything.

1. “How well did your last three forecasts come in?” This is the first and most important filter — forecast accuracy. If there’s no ready answer to this, the other questions are moot.

2. “What pace is it based on?” Pace is the booking rate — how many bookings are already on the books for future dates. A forecast built on real bookings already in hand is far harder than one that just extrapolates from hope. The right answer is concrete: “Q3 is already at X%, versus Y% the same amount of time out last year.”

3. “What was the same moment last year?” Not last year’s final result, but last year’s same point — where the book stood the same number of days before the date. This is the only honest comparison: apples to apples. If at the same moment this year there are more bookings on the books than there were last year, the forecast is well supported.

4. “What decides whether we land at the top or the bottom of the band?” A credible forecast is a band, not a point number. This question uncovers whether management knows what the outcome hinges on — a particular event, the take-up of a corporate contract, the strength of the summer demand peak. If a precise answer comes back, management understands what it’s doing.

Notice: none of the questions is about pricing, none is micromanagement. Each illuminates the thinking behind the number. A good management welcomes them, because it gets to show its work — and if the hotel runs on a shared system, most of the answers are already there in common, so the conversation is about trust, not exposure.

Back to Annette

Annette writes back to Adam, but doesn’t dispute the 84 EUR. She asks four questions. Adam’s reply is quick and concrete: the last three forecasts were within 1.6%; Q3 is already at a higher pace than the same time out last year; the same-point comparison is favourable; and the top of the band hinges on the take-up of an August conference, on which an option is held. The bottom edge of the 84 EUR is all but certain, the top depends on the conference.

Annette closes the laptop. She hasn’t become a revenue manager, hasn’t looked at a single rate. But now she knows what the number she was given is worth — and knows that her management understands what it’s doing. This is the real foundation of owner trust: not the pretty forecast, but the measurable-back work behind it. She experiences the budget–forecast gap not as a failure but as information.

And notice what made this conversation easy: Annette and Adam were looking at the same forecast and the same accuracy number. Without a shared system this dialogue would have curdled into suspicion — the owner believing blindly or checking endlessly. The shared, real-time number is what makes trust structural: it doesn’t put management in the stocks, but makes its work visible and credible. The revenue manager wins from this too — a good forecast finally doesn’t have to be defended, because its track record speaks for itself. Building the forecast, measuring accuracy and pace-based forecasting from the revenue manager’s side are covered in the RM Academy lessons Forecasting basics, Simple forecast methods and Smart Forecast Enhanced.

Key takeaways

• A forecast on its own is neither true nor false, only credible or not — its value comes from its past hit rate (forecast accuracy), not its beauty.
• The budget–forecast gap is no disgrace but information: the budget is old and fixed, the forecast is fresh. A forecast that always shows exactly the budget is suspicious.
• The same number is worth very differently depending on who gives it: 84 EUR from a management with a ±1.6% history is reliable; from one with a ±13%, over-optimistic history it isn’t.
• The owner’s four questions: (1) how well did the last three come in, (2) what pace is it based on, (3) what was the same moment last year, (4) what moves the top/bottom of the band — none is micromanagement, each tests the thinking behind the number.
• A credible forecast is a band, not a point number — and management knows what moves it toward either end.
• Trust comes not from more control but from shared visibility: if forecast accuracy is visible to everyone in a shared system, the owner doesn’t have to interrogate, and management’s work becomes credible — both sides win.