Your Budget Is Not Your Forecast. Stop Asking Them to Agree.
The budget says what you committed to. The forecast says what you currently expect. When those numbers disagree, the gap is useful: it tells you where a decision is needed. A practical way to separate targets, expectations, and actuals without turning the revenue meeting into an argument about which number is right.
October. Next year’s budget is being discussed while this year’s final quarter still has rooms to sell. Someone asks for the latest forecast, sees a number below budget, and says: “We need to get that back to plan.”
As a commercial objective, fair enough. As an instruction to change the forecast, dangerous.
A budget records an agreed target and the assumptions behind it. A forecast estimates the outcome using what you know now. The gap between them is not a reporting error. It is the part of the conversation that needs attention.
Give each number one job
Keep three views of the same stay period, with the same revenue definitions and inventory basis:
| View | Question it answers | What should change it? |
|---|---|---|
| Approved budget | What did we agree to deliver? | A formally approved revision, with the original retained |
| Latest forecast | What do we now expect to deliver? | New evidence and credible changes to the plan of action |
| Actual | What did we deliver? | Recorded business and documented accounting corrections |
The owner can still hold the team accountable for the budget. The RM can still forecast below it. Both can be doing their jobs properly.
Keep an ambitious recovery scenario beside the base forecast if it helps. Label its assumptions: which campaign, account, event, or rate decision would produce the additional business? A stretch scenario becomes a credible forecast only when the evidence supports it. Moving a number because the gap looks uncomfortable changes none of the bookings underneath it.
Our hotel budgeting guide covers building the annual plan. This is about using that plan once reality starts disagreeing with it.
Explain the gap before prescribing a fix
An illustrative example, not measured hotel performance: an 80-room hotel is planning a 30-day month, with 2,400 available room nights. All revenue below is room revenue excluding VAT, on a consistent basis.
| Measure | Budget | Latest forecast |
|---|---|---|
| Sold room nights | 1,680 | 1,560 |
| Occupancy | 70% | 65% |
| ADR | €120 | €125 |
| Room revenue | €201,600 | €195,000 |
The revenue gap is −€6,600, despite the higher ADR. A simple bridge explains it:
- Volume effect, valued at budget ADR: (1,560 − 1,680) × €120 = −€14,400.
- Rate effect, applied to forecast room nights: 1,560 × (€125 − €120) = +€7,800.
- Together: −€14,400 + €7,800 = −€6,600.
This is one consistent way to split the arithmetic; a different ordering allocates the interaction differently. It is not proof that a pricing decision caused the higher ADR. A changed segment, room-type, or channel mix can move the average too.
Now investigate the missing nights. Are they low-demand Sundays, a lost corporate account, a group that moved dates, or peak nights where the hotel is already ahead? Those require different responses. A blanket discount might reduce the rate on business you would have won anyway, without solving the weak dates.
Keep ambition out of the pickup assumption
A useful forecast separates business already on the books from what you reasonably expect to add. For room nights, that means retained OTB business plus expected additional bookings, with a consistent allowance for cancellations and other attrition. Do not count expected pickup as if it were already booked, or deduct the same cancellations twice.
Check the assumptions by stay date and segment:
- What is booked at this point, compared with the same point before comparable past stays?
- Is there still enough booking time left for the missing business to arrive?
- Has an event moved, a contract ended, or the booking window changed?
- What evidence supports the additional demand assumed in the forecast?
“We need another €20,000” describes a target. “The account has confirmed these dates and is contracting these room nights” is evidence. A proposed campaign sits somewhere in between: include a defensible expectation, not the full amount needed to close the gap.
For a full-year outlook, combine actual revenue from closed months with the forecast for the remaining months. Adding year-to-date actuals to an already full-year forecast counts the closed months twice.
End the meeting with a decision, not a negotiated number
Take one material gap into the revenue meeting. Record the affected dates, the working explanation, one action, an owner, and a review date. State what would tell you the action is working.
For weak corporate Tuesdays, that might mean sales checking lost accounts before the next meeting. For a peak event date, it might mean reviewing discounted availability. For an unrealistic target, it might mean an explicit discussion with the owner about the remaining gap. The event calendar helps keep date-specific assumptions visible.
Preserve the forecast you made before the action. At month-end, compare actuals with that dated forecast to assess accuracy, and with budget to assess target achievement. Hitting budget does not prove a forecast was accurate; missing budget does not prove it was poor. Compare forecast accuracy at consistent horizons, not a forecast made yesterday with one made three months ahead.
(Where Peaqplus fits: BI Core includes the room-night, ADR, and revenue Budget and Forecasting tools. The separate Operating Budget add-on extends planning to departmental costs and expected GOP. It does not receive cost actuals: its plan-versus-actual comparison is revenue-only, and its outlook costs remain modeled. A revenue forecast and an accounting profit result are different things.)
Frequently asked questions
Should the forecast always equal the budget at the start of the year?
No. They may start close if they use the same recent assumptions, but a budget agreed months earlier can already differ from the evidence available in January. Explain the difference rather than forcing agreement.
Can we revise the budget?
Yes, through an agreed approval process. Keep the original, label the revised version, and make clear which one each comparison uses. Quietly replacing the original makes accountability harder, not easier.
Does a lower forecast mean the team has given up?
No. It should mean the team has made its current expectation explicit. Keep the recovery actions and their assumptions visible beside it. A realistic estimate gives those actions a starting point; an inflated estimate hides the work still needed.
Where to go from here
Use hotel budgeting to build the target, forecast accuracy to evaluate your estimates, and RevPAR versus profit to check what revenue performance leaves after operating costs.
The budget gives you a destination. The forecast tells you where the current route is taking you. You need both to decide what to change.
Reading is one thing — knowing your next step is another. Answer one question and we hand you the guide that matches where your hotel is today. Free, delivered by email.
Find your guide →