The annual planning cycle: from the budget to the daily decision

Early November. Adam, the general manager, and Annette, the owner, are sitting over next year’s budget (the annual plan). Annette is happy with the numbers, then puts the document away with one sentence: “Good. So we lock this in, and next year this is the plan.”

Adam gently stops her. “We lock it in, yes. But it’s not ‘done’. This number is our best knowledge in November about next year. By March we’ll know things we don’t today — and then we won’t throw the budget away, we’ll refine against it. The budget is the starting point, not the final stop.”

This lesson is about what goes wrong in many hotels: they see planning as a one-off event, not a cycle. Yet the annual budget, the seasonal strategy, and daily pricing aren’t three separate things — they’re three views of a single system. For those who grasp this, the November plan isn’t a paper that ends up in a drawer, but a living frame that the forecast refines all year, right down to the daily decision.

The three levels: budget, seasonal strategy, daily decision

Planning is a funnel. At the top the widest, annual picture; at the bottom the narrowest, today’s decision. Each level follows from the one above it.

The budget is the annual frame. It’s born once, in advance, typically in the last quarter for the coming year. It says what we expect at the annual level: what occupancy, what ADR, what RevPAR and revenue. It’s the reference point we measure against all year — the owner accepts this, and holds us to account against it.

The seasonal strategy breaks the frame down. The annual number doesn’t spread out evenly: an urban hotel has a strong spring and autumn and a weaker summer or winter. The strategy says which month we go for volume (fill the house), which for rate (protect the ADR), where to put the marketing budget, when to let a group in.

The daily decision is the execution. This is where a specific Wednesday’s rate, a given group’s fate, a last-minute promotion get decided. But not out of nowhere: every daily decision takes its frame from the seasonal strategy and the budget — the daily rate isn’t an “idea”, it’s the smallest unit of an annual logic.

The mistake is always the same: the three levels come apart. The budget in the drawer, the daily pricing in gut feel, nothing in between. The leader’s job is to keep the connection between them alive — and that’s what the forecast is for.

The forecast links the plan to reality

The budget is made in November, with the best knowledge available then. But life doesn’t unfold according to the budget: along comes a strong events calendar, a weak economic month, a competitor’s price war. The forecast is what updates continuously: it doesn’t say what we planned, but what we expect now, based on the fresh pace and pickup.

The relationship between the two is the leadership read. If the forecast diverges from the budget, that isn’t a failure — it’s information. The weak leader is ashamed of the variance and hides it (“we’ll make it up”). The good leader reads from it what’s happening, and acts while it’s still possible. The budget says where we wanted to get to; the forecast says where we’ll get to on the current path; the difference between the two is the room to act.

Peaqplus’s Budget and Forecast modules make exactly this dialogue visible: they place the plan and the current forecast side by side month by month, so that the variance surfaces not at year-end, when nothing can be done about it, but 8–12 weeks ahead, while there’s still room to move.

A worked example: from the annual budget to correcting one month

Let’s look at Hotel Peaqplus City’s budget for next year. 80 rooms, 365 days = 29,200 available room nights. The budget at the annual level:

Occupancy 74%, ADR 105 EUR → RevPAR = 0.74 × 105 = 77.70 EUR

Annual room revenue: 77.70 × 29,200 = ~2,268,840 EUR

This 2.27-million-euro frame isn’t even. Let’s break it down by seasonality into a few representative months (summer and deep winter are weaker, spring and autumn strong):

Let’s zoom in on October. The budget is 80% / 112 EUR. October has 31 days, 31 × 80 = 2,480 available room nights. The budgeted October room revenue:

0.80 × 112 EUR × 2,480 = 89.60 × 2,480 = 222,208 EUR

Now let’s jump to mid-August. The Forecast module builds the October forecast from the fresh pace — and it diverges from the budget:

Forecast: occupancy 72%, ADR 116 EUR → RevPAR = 0.72 × 116 = 83.52 EUR

Forecast October revenue: 83.52 × 2,480 = 207,129.60 EUR

The variance against the budget: 222,208 − 207,130 = −15,078 EUR short. This is where the leadership work begins — not the complaint, but the diagnosis.

Adam doesn’t ask “why not the budget?”, but what the variance is saying. And the variance is telling: the ADR is actually above plan (116 vs. 112) — there’s nothing wrong with the price. The gap comes purely from volume: 72% instead of the planned 80%, meaning 8 percentage points of occupancy are missing. This isn’t a pricing problem but a demand/pace problem — typically on a few specific weak weeks, not across the whole month.

The right answer, then, isn’t the panic move (an across-the-board price cut, which would drag down the otherwise strong ADR too), but targeted action: marketing budget on the weak dates, perhaps a tactical midweek offer, maybe a group we’d otherwise turn away on a strong date. Suppose this targeted work brings back 4 percentage points, while roughly holding the ADR (115 EUR):

Corrected forecast: 0.76 × 115 = 87.40 EUR RevPAR × 2,480 = 216,752 EUR

The remaining gap to the budget: 222,208 − 216,752 = −5,456 EUR — instead of the starting 15,078. The targeted correction brought back nearly two-thirds of the gap, without sacrificing the strong ADR on a panicked, blanket action. And all of it was decided in August, not October — the forecast pulled the decision forward, while there was still something to be done.

Back to Adam and Annette

Adam puts this logic in front of Annette. “The budget stays our yardstick — you’ll measure me against it. But during the year the forecast will show where we diverge, and the variance isn’t a problem: it’s the signal for where I need to act. If we fall behind on volume in a month, we see it in August, not December — and then we can still win.”

Annette nods. This is exactly what reassures her: not that the plan never diverges from reality (that would be suspicious), but that there’s a living system that signals in time, and a leader who doesn’t hide the variance but uses it. The budget is the contract between the two of them; the forecast is the shared dashboard; the daily decision is the execution. One system, three views — and the leader is the one who holds it together.

The revenue-manager work of building the annual budget and continuously updating the forecast is covered by the RM Academy lesson Budget and the planning cycle, from Daniel’s angle.

Key takeaways

• Planning is a cycle, not an event. The budget isn’t “lock it in and done”, but our best knowledge at the start of the year, which the forecast refines all year long.
• Three levels, one system: annual budget → seasonal strategy → daily decision. The daily rate isn’t an idea, it’s the smallest unit of the annual logic.
• The forecast links the plan to reality. The budget–forecast variance isn’t a failure, it’s information and room to act — the difference between the two shows where something needs doing.
• Diagnose, don’t complain. The October 15,078 EUR gap was purely a volume problem (the ADR above plan) — so it needed targeted marketing, not an across-the-board price cut.
• Timing is everything. Seeing and correcting the variance in August is still profit; seeing it in October is only an explanation.