Budget vs. Forecast: What’s the Difference and When Should You Use Each?

I can usually tell when a company has confused its budget with its forecast.

It’s September.

The business has changed.

Sales are running below plan. Hiring moved. A product launch slipped. A large customer expanded unexpectedly. Marketing changed its spending.

And somehow the forecast still looks remarkably similar to the budget everyone approved nine months ago.

That’s when I start asking questions.

Sometimes the answers amount to:

“Well, that’s the number we’re trying to hit.”

Okay.

But that’s not what I asked.

I want to know what we currently think is going to happen.

This sounds like a small distinction.

It isn’t.

A budget and a forecast are both financial planning tools, but they have different jobs.

The budget describes the plan.

The forecast describes our current view of reality.

When companies blur those two, Finance can end up spending a surprising amount of time negotiating with reality.

Reality has historically been difficult in these negotiations.

What Is a Budget?

A budget is a financial plan for a defined period, usually a fiscal year.

It typically includes expectations for:

• revenue,
• gross margin,
• operating expenses,
• headcount,
• capital expenditures,
• cash flow,
• and other financial targets.

The annual budgeting process forces a company to make decisions.

How much are we planning to grow?

Where are we investing?

How many people are we hiring?

Which initiatives are getting funded?

What level of profitability are we targeting?

Where are resources going?

That’s why I still think budgets are useful.

They create commitment.

Without some kind of planning process, every department can have a perfectly reasonable idea that collectively requires twice the money the company actually has.

Finance tends to discover this.

The budget makes those tradeoffs visible.

What Is a Forecast?

A forecast is Finance’s updated view of what is likely to happen based on the information available today.

That last word matters.

Today.

Maybe we started the year expecting $100 million in revenue.

Three months later, pipeline changed.

A customer delayed implementation.

Pricing improved.

Hiring slowed.

Gross margin came in differently than expected.

The forecast should absorb that information.

If we now believe revenue will be $94 million, the forecast should say $94 million.

Even if the budget says $100 million.

Especially if the budget says $100 million.

Otherwise we’re not forecasting.

We’re hoping in Excel.

I’ve done enough of that in my personal life. I don’t need Finance joining in.

Budget vs. Forecast: The Simplest Difference

The simplest way I think about it is:

Budget: What did we plan to do?

Forecast: What do we now think will happen?

Those questions sound similar enough that companies frequently combine them.

But they serve different management purposes.

The budget gives you a baseline for accountability and resource allocation.

The forecast gives you updated information for decision-making.

One shouldn’t quietly become the other.

Budget vs. Forecast at a Glance

Neither is inherently better.

They answer different questions.

Problems start when we ask one to do the other’s job.

Why Companies Keep Turning the Forecast Back Into the Budget

This is where the human part gets interesting.

Let’s say the annual budget assumes $100 million in revenue.

By April, the evidence suggests $94 million is more realistic.

Finance updates the forecast.

Someone says:

“We can’t show $94 million.”

Why?

“Because our target is $100 million.”

I have been in versions of this conversation more than once.

The $100 million may still be the target.

Management may absolutely decide to fight for it.

But changing the forecast to $100 million doesn’t create the missing $6 million.

It creates a forecast that is less useful.

This is one of the reasons forecasting is as much a behavioral process as a financial one.

People become attached to targets.

Nobody enjoys taking expectations down.

A lower forecast can feel like admitting defeat.

So the organization begins putting pressure on the forecast until it says something more pleasant.

The spreadsheet eventually cooperates.

Spreadsheets are very accommodating that way.

The business may not.

The Budget Should Be Hard to Change

I generally don’t want the annual budget changing every month.

That’s part of its usefulness.

If we approved $10 million of operating expense and then spend $11 million, I want to see the variance.

If the budget simply changes to $11 million, we’ve lost the reference point.

The same applies to revenue, hiring and investments.

A budget gives management something stable to compare against.

What did we say we were going to do?

What actually happened?

Where are we ahead?

Where are we behind?

What changed?

Without that baseline, accountability gets slippery.

Imagine trying to keep score in a game where the scoreboard changes the target every quarter.

Finance has enough interesting conversations already.

The Forecast Should Be Allowed to Move

The forecast is different.

I want it moving.

Not randomly.

Not because someone had a feeling after lunch.

But because new information arrived.

A major customer churned.

Update it.

Hiring is running six weeks behind plan.

Update it.

Pricing is performing better than expected.

Update it.

A product launch moved.

Update it.

Collections slowed.

Update it.

The forecast should become more informed as the year progresses.

If it’s June and your forecast is still almost identical to the budget you built last October, one of two things has happened.

You are operating the most predictable company I’ve ever encountered.

Or the forecast isn’t listening very carefully.

I know which one I’d investigate first.

Your Target Can Stay the Same While Your Forecast Changes

This distinction solves a surprising number of arguments.

Suppose:

Budget: $100 million revenue
Current forecast: $94 million revenue
Target: still $100 million

Those numbers can coexist.

The forecast saying $94 million does not mean management has surrendered.

It means the current trajectory points to $94 million.

Now leadership can ask the useful question:

What would have to change to close the $6 million gap?

Maybe Sales needs more pipeline.

Maybe pricing changes.

Maybe retention improves.

Maybe a product launch accelerates.

Maybe the gap cannot realistically be closed.

That’s a management conversation.

But you can’t have it clearly if Finance quietly moves the forecast back to $100 million because everyone feels better looking at it.

A forecast should occasionally make people uncomfortable.

That’s not necessarily a defect.

When Should You Use a Budget?

Budgets are most useful when the company needs to establish an operating plan and allocate resources.

I particularly want one when management needs to make decisions about:

Headcount. How many people can we hire and where?

Spending. Which departments and initiatives receive resources?

Capital investment. What are we funding?

Profitability. What financial outcome are we targeting?

Cash. What liquidity does the plan require?

Accountability. What did each part of the organization commit to?

The annual budgeting process is also valuable because it forces cross-functional tradeoffs.

Sales wants more people.

Marketing wants more spend.

Operations wants equipment.

Product wants engineers.

Everybody’s request makes perfect sense individually.

Then Finance adds them together.

This is one of our less appreciated talents.

When Should You Use a Forecast?

Use a forecast when management needs an updated view of the business.

That can include decisions around:

• hiring,
• spending,
• cash,
• inventory,
• capacity,
• pricing,
• capital allocation,
• financing,
• and changing business conditions.

The forecast should answer questions like:

Where are we likely to finish the year?

What changed since the last forecast?

Where are the biggest risks?

Where are the opportunities?

What assumptions changed?

Do we need to adjust anything now?

That last question is important.

A forecast that doesn’t affect decisions eventually becomes another reporting exercise.

I’ve never been interested in forecasting merely to produce a newer number.

I want the newer number to tell us whether we should do something differently.

What About a Rolling Forecast?

A rolling forecast takes this one step further.

Instead of forecasting only through the end of the fiscal year, the company maintains a consistent forward-looking horizon.

For example, a 12-month rolling forecast updated in September would continue through the following August rather than stopping in December.

I like the logic behind this.

December 31 is very important to Accounting.

The business itself does not become mysteriously unknowable on January 1.

A rolling forecast keeps management looking forward rather than watching the forecast horizon shrink as the year progresses.

It can be especially useful in businesses where conditions change quickly or where decisions require visibility beyond the current fiscal year.

But adding months to the spreadsheet doesn’t automatically make the forecasting process better.

You still need good assumptions, business drivers, ownership and useful conversations.

A bad forecast with three extra months is just a longer bad forecast.

Should You Reforecast Every Month?

Maybe.

This is one of those questions where Finance would love a universal answer and the business refuses to provide one.

Some companies benefit from monthly forecasting.

Others may be fine quarterly.

Businesses with volatile revenue, cash or operating conditions may need more frequent updates.

Stable businesses may not.

I wouldn’t choose the cadence because somebody read that “best-in-class FP&A teams forecast monthly.”

I’d ask:

How quickly does our business change?

How often do meaningful new decisions need to be made?

How expensive is the forecasting process?

Does updating monthly produce materially better information?

I’ve seen companies spend so much time forecasting that they barely finish one forecast before starting the next.

At some point you have to operate the business.

Budget Variance vs. Forecast Variance

I like looking at both, because they tell me different things.

Actual vs. budget tells me how we’re performing against the original plan.

Actual vs. forecast tells me how well our most recent expectations reflected reality.

Suppose revenue comes in at $8.5 million.

Budget was $10 million.

Forecast was $8.4 million.

Against budget, we missed badly.

Against forecast, we were pretty close.

Those facts aren’t contradictory.

They tell me two different things.

The business is underperforming the original plan.

But the forecasting process may have recognized that deterioration before the month closed.

That’s useful.

Now reverse it.

Budget was $10 million.

Forecast was $10 million.

Actual was $8.5 million.

Now I have another question:

What did we fail to see?

That’s where forecast accuracy becomes interesting to me.

Not as a trophy.

As evidence about how well Finance understands what’s happening in the business.

The Forecast Should Not Be a Negotiation

This is probably the behavior I’d watch most closely.

Sales submits a forecast.

Finance challenges it.

Leadership wants the number higher.

A business unit doesn’t want to lower its outlook.

Someone says, “Let’s leave it for another month.”

Now we’re no longer asking what is likely to happen.

We’re negotiating what number everybody is comfortable seeing.

That’s dangerous.

I understand why it happens.

Forecasts affect expectations.

Expectations affect people.

Sometimes compensation.

Sometimes investors.

Sometimes boards.

Sometimes careers.

Humans enter the spreadsheet.

But Finance has to protect the distinction between target and expectation.

Otherwise the forecast slowly becomes a political document.

And political documents aren’t especially good at predicting cash.

A Simple Budget and Forecast Process

If I were designing this from scratch, I’d keep the roles very clear.

1. Build the budget around strategy and resource allocation.

What are we trying to accomplish, and what resources does that require?

2. Lock the budget once approved.

Keep it as the original operating baseline.

3. Establish a regular forecasting cadence.

Monthly, quarterly or whatever fits the business.

4. Update the forecast using actual results and current information.

Don’t automatically anchor it back to budget.

5. Make assumptions explicit.

Revenue drivers, hiring, pricing, margins, spending, collections and other meaningful inputs should have owners.

6. Compare actuals with both budget and forecast.

Each comparison answers a different question.

7. Explain what changed.

Don’t just report the variance.

8. Turn the forecast into decisions.

What needs to change because our view of the future changed?

That last step is where FP&A earns its keep.

The Question I Ask When Budget and Forecast Match Too Closely

When I’m looking at a company and the forecast keeps landing almost exactly on budget, I don’t immediately congratulate everyone.

I get curious.

Has the business genuinely performed exactly as planned?

Or has the planning process become anchored to the number everyone wants?

I start looking underneath it.

What changed in Sales?

What changed in hiring?

What happened to pricing?

What happened to margins?

What happened to customers?

What information arrived during the year?

And did any of it materially change the forecast?

Because a forecast that refuses to change when the business changes isn’t disciplined.

It’s stubborn.

I have enough experience with stubbornness outside Finance. I don’t need it from Excel too.

Budget and Forecast Should Disagree Sometimes

I actually become more comfortable when they do.

Not because missing budget is good.

It isn’t.

But because disagreement can be evidence that the forecasting process is doing its job.

The budget was built with the information we had then.

The forecast uses the information we have now.

Those two information sets should occasionally produce different answers.

That’s normal.

What matters is understanding why.

Maybe the business is outperforming.

Maybe it’s underperforming.

Maybe the market changed.

Maybe assumptions were wrong.

Maybe execution changed.

Maybe timing moved.

Whatever the reason, Finance should be able to explain it.

That’s far more valuable than forcing two numbers created nine months apart to remain friends.

The Budget Is a Commitment. The Forecast Is an Opinion.

That’s probably the cleanest way I know to separate them.

The budget says:

This is what we planned to do.

The forecast says:

Given everything we know now, this is what we think will happen.

Both matter.

I want the budget because companies need plans, targets and accountability.

I want the forecast because plans encounter reality.

And reality is remarkably inconsiderate about annual planning calendars.

Good FP&A doesn’t choose between the two.

It keeps them separate enough that each can do its job.

Then when the forecast moves away from budget, we don’t spend the meeting trying to convince the spreadsheet to come home.

We ask the much more useful question:

What changed, and what are we going to do about it?