When the forecast simply repeats the budget

A common failure is the forecast that never leaves the budget. It begins when cost centre owners copy approved figures forward instead of re-estimating. It hides behind small variances until a sudden late break. The cure is to build forecasts from live commitments and to stop punishing people who move the number.

How it starts

The budget gets approved after a long negotiation. Everyone is tired of it. When the first forecast cycle arrives, the template is pre-filled with budget values, and most owners accept the defaults. Nothing has visibly changed yet, so this feels reasonable.

The habit sets in because of what happens next. An owner who lowers a spending forecast often sees that money pulled back by the centre. An owner who raises it gets questioned in a review meeting. So the safe move is to leave the line alone and explain the gap later. Over time the forecast stops being an estimate. It becomes a restatement of a promise.

Policy can make this worse. If the budget procedures say forecasts must be "reconciled to budget" without saying how, owners read that as "match the budget." The written rule and the lived rule drift apart, and nobody notices because the outputs look tidy.

Why it stays hidden

Variance analysis is usually where this should surface. It often does not, for a simple reason: if the forecast equals the budget, the forecast variance and the budget variance are the same number. Analysts end up explaining one gap twice and calling it timing.

Timing is the favourite explanation. Some of it is genuine. Revenue that has been earned but not yet billed will lag unless someone records an accrual for it, and spending on contracts often lands later than planned. These real timing effects give cover to the fake ones. A line that is underspent because the project was cancelled looks identical, on the report, to a line that is underspent because an invoice is late.

There is a quieter cause too. When the actuals feeding the variance report are pulled from a side system or a spreadsheet, and nobody checks that they trace back to general ledger balances, the comparison itself is unreliable. People lose faith in the variances and stop reading them closely.

How it gets spotted

The clearest sign is a forecast line that holds perfectly flat across several cycles while the actuals beneath it wander. Pull the forecast history for a sample of cost centres and plot it. Honest forecasts move. Copied ones sit still.

Another sign comes from the treasury side. If cash flow projections are built separately from the operating forecast, and the treasury team keeps its own adjustments because it does not trust the official figures, that is a strong hint. Ask treasury how they arrive at their numbers. Their workarounds reveal what the forecast is missing.

Watch the explanations as well. When the same commentary reappears cycle after cycle ("phasing, expected to catch up"), and the catch-up never comes, the forecast is not doing its job.

The final sign is the late cliff. Late in the year, a large release or overrun appears all at once. Leadership asks why nobody saw it. Usually someone did, but there was no safe place to say so.

How it gets fixed

Start with the source of actuals. Make sure every figure used in budget execution reporting traces to ledger balances, and publish that tie-out alongside the variance pack. Once people trust the actuals, the conversation can move to the forecast.

Next, change how the forecast is built. Seed it with committed spend, open purchase orders, signed contracts and known payment schedules. The pending payment data held in accounts payable is useful here, since it shows what is due and when. On the revenue side, include accruals for work delivered but not invoiced. The budget can sit in a separate column for reference. It should not be the starting value in the cell the owner edits.

The harder change is behavioural. Agree, in writing, that a lowered forecast will not automatically trigger a funding clawback within the same cycle. Treat a well-explained movement as good practice in reviews. Some teams track forecast accuracy by owner and recognise those who call changes early.

Finally, rewrite the policy line that caused confusion. Say plainly that the forecast is the best current estimate of outcome, and that differences from budget are expected and must be explained, not removed.

Questions to ask the people who run it

• When the forecast template opens, what values are already in it, and who decided that?
• What happened the last time someone lowered their forecast?
• Where do the actuals in the variance report come from, and has anyone checked them against the ledger recently?
• Does treasury use the official forecast for cash planning, or its own version?
• Which variances do you explain as timing, and how do you know they are?
• Is there anything you know about future spend that you have not put in the forecast? Why not?
• What does the written procedure say a forecast is for, and does that match how reviews treat it?

What to watch while changing it

The first honest forecast often looks worse than the copied one. Variances widen, and some leaders read that as a decline in control. Prepare them for it before it happens. A forecast that moves early and lands close is worth more than one that looks calm and breaks late.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.