top of page
Insight

When Actual + Forecast disagree with Budget. The bridge owners need

Joël Fremondiere

15 February 2026

4

min read

When Budget, Actual, and Forecast conflict, owners need one bridge that reconciles drivers and forces decisions with dates.

Owners rarely struggle because a hotel misses Budget. They struggle when the pack presents competing baselines. Budget says one story. Year-to-date Actual says another. Full year Forecast says a third. Next month, Forecast moves again, and the discussion becomes “who changed what” instead of “what do we do now”.

The owner tool that fixes this is a bridge. It reconciles Budget, Actual, and Forecast into one baseline, one driver stack, and a short list of actions.


1) What “disagree” means


Variance is normal. Disagreement is a governance problem.

Budget, Actual, and Forecast disagree when:

  • Full year (FY) Forecast is materially away from FY Budget, and

  • Forecast moves month to month without a clear driver explanation, and

  • The discussion blends operating performance, accounting timing, and one-offs.

In that state, owners are not comparing performance. They are guessing which number should anchor decisions.


2) What each number is for (owner lens)


Budget is the accountability reference. It is the baseline intent behind the plan and the performance conversation.

Actual is evidence. It shows what is already locked in and what cannot be recovered.

Forecast is trajectory. It is the best estimate of the year-end outcome, stated as outcomes plus assumptions. It matters because owners fund risk. Forecast accuracy affects cash planning, covenants, and capital timing.

Owner rule: when these numbers diverge, you need one reconciled story, not three separate explanations.


3) The bridge owners need


A one-page reconciliation that answers four questions, in this order:

  • What changed versus FY Budget.

  • Is it structural or timing.

  • Is it controllable or exogenous.

  • What decision is required now, with an owner and a due date.

If a pack does not answer these questions, it is informative but not decision-grade.


4) Bridge architecture: FY Budget to FY Forecast


Step A. Choose anchors
Pick two anchors only:

  • Total revenue

  • Gross Operating Profit (GOP) ratio (GOP divided by total revenue)

Optionally add Owner Free Cash Flow (OFCF) once the operating bridge is clear. Owners ultimately underwrite cash yield, but the driver logic should be visible first.


Step B. Reconcile with a small set of driver buckets
Build a simple waterfall from FY Budget to FY Forecast using buckets that move value.


1) Rooms revenue
Split the variance into:
Occupancy
Average Daily Rate (ADR)
Mix (segment and channel)


2) Non-Rooms revenue
Frame as operating model drivers:
Volume (covers, utilisation, event count)
Price and yield (average check, package structure)
Mix (banqueting versus outlets, resident versus non-resident)
Constraints (closures, seasonality, staffing limits)


3) Margin conversion
Revenue variance is not value variance unless it converts. This bucket answers what dropped through to GOP, and what did not.


4) Undistributed cost drift
Focus on fixed and semi-fixed lines that did not behave like the budget assumptions:
Payroll structure and resourcing model
Utilities and contracted services
Sales and marketing deployment versus expected Return on Investment (ROI)


5) Owner-sensitive lines
Show impacts on fees and major owner-paid or owner-exposed lines where relevant (for example insurance, property taxes, reserve logic).


Step C. Add the second bridge: forecast movement
Owners also need to see discipline. Add a mini-bridge from prior forecast to current forecast, limited to 3–5 reasons. Examples:

  • Pickup pace reset (by segment)

  • Rate assumption reset (by month)

  • Cost run-rate reset (wage inflation, staffing model)

  • One-off recognised or reversed

  • Timing shift (opening, outlet closures, project phasing)

If this movement cannot be stated clearly, Forecast becomes a rolling guess rather than a managed projection.


5) Normalisation: separate performance from noise


Disagreement often comes from timing and one-offs being argued as “performance”.

Two rules:

  • Timing and accounting noise must be labelled as such (accrual timing, reversals, reclasses, prior-period true-ups).

  • When noise is material, show both reported and normalised GOP in the bridge so decisions anchor to run-rate, not phasing.


6) The three tests on every variance line


For each bucket, apply:

  • Structural or timing.

  • Controllable or exogenous.

  • Action now or monitor with a trigger.

Each line ends with: Decision needed. Owner action. Operator action. Due date.


7) Governance closure


A bridge that ends with “noted” is not a bridge.

Owners should require:

  • A short Decision List for the month (maximum 3–5 items)

  • A linked Action Register with accountable owners, operator leads, and due dates

  • Carry-forward of open items until closed


8) Monthly cadence owners should insist on


Current month and Year-to-date views
Actual, Budget, Prior year, and deltas tied to the bridge buckets


Full year view
Budget, Forecast (current), Prior forecast, Prior year, and Movement (current forecast versus prior forecast)

This makes drift visible and forces baseline alignment.


Close


When Budget, Actual, and Forecast disagree, the bridge is the mechanism that protects pace, accountability, and cash yield. If the bridge cannot be stated clearly on one page, the asset is being governed through noise.

Related Insights

Mix moves profit faster than pricing by steering contribution: what you accept, what you cap, and what you displace.

Mix is strategy. Contribution decisions that move profit faster than pricing

Performance and Profitability

7

min read

When RevPAR rises but GOP stalls, make drop-through visible and force decisions on mix, costs, and closure.

When RevPAR grows but profit does not. Making drop-through visible

Performance and Profitability

7

min read

bottom of page