Your CFO Changed the Forecast. Was That Judgment or Wishful Thinking?

Picture a perfectly ordinary forecast meeting.

FP&A has spent two weeks reviewing sales pipelines, customer demand, hiring plans, pricing assumptions, and operating costs.

The forecast is complete.

Revenue is expected to finish the year at $118 million.

The CFO studies the numbers.

The sales leader studies the numbers.

Everyone studies the numbers.

Then someone says, “I think we can do $125 million.”

Well.

That’s encouraging.

I’d also like to believe I can finish every item on my weekend to-do list before lunch on Saturday.

Experience suggests we should probably discuss the evidence.

And that’s exactly what I’d want to do with the forecast.

Because management judgment can improve a financial forecast enormously.

It can also turn a reasonably accurate forecast into a very expensive expression of optimism.

The difference is worth understanding.

First, I Actually Like Management Judgment

I don’t want finance teams blindly accepting whatever a model produces.

Models have limitations. That’s why I also believe in reviewing a financial model before trusting it.

Historical relationships change. Customers behave unexpectedly. Salespeople learn things that haven’t appeared in the data yet. Operations may know about a capacity problem that hasn’t reached the financial forecast.

A good CFO should challenge the numbers.

A good FP&A team should welcome that challenge.

But here’s the distinction I care about.

A forecast override should introduce better information, not simply a more attractive outcome.

If the sales leader knows a major customer has accelerated a purchase, I want that information.

If the operations team has confirmed a production constraint, I want that information too.

If the only explanation is that the executive team feels confident about the fourth quarter, I’m interested in understanding why.

Confidence is useful.

It just isn’t a revenue driver.

Let’s See What Happens When We Add $7 Million

Imagine a hypothetical U.S. business with the following forecast:

Financial measure	FP&A forecast
Revenue	$118.0M
Gross margin	40%
Gross profit	$47.2M
Operating expenses	$35.0M
EBITDA	$12.2M

For simplicity, assume EBITDA equals gross profit less the operating expenses shown, with no other adjustments.

Management believes revenue should be $125 million.

That’s a $7 million increase.

If the additional revenue carries the same 40% gross margin, the incremental gross profit would be $2.8 million.

Assuming no additional operating expenses, EBITDA would increase from $12.2 million to $15 million.

Suddenly, the company has a much more attractive forecast.

Financial measure	Original forecast	Management override
Revenue	$118.0M	$125.0M
Gross profit	$47.2M	$50.0M
Operating expenses	$35.0M	$35.0M
EBITDA	$12.2M	$15.0M
EBITDA margin	10.3%	12.0%

All figures are hypothetical. The override column assumes unchanged gross margin and operating expenses.

A $7 million revenue adjustment has increased forecast EBITDA by approximately 23%.

That’s not a small change.

And before anyone starts celebrating, I’d like to know where the additional $7 million is coming from.

Preferably somewhere more specific than “strong momentum.”

Momentum is wonderful.

But I’ve never seen it listed as a customer on an accounts receivable aging report.

What Would Convince Me to Accept the Override?

Suppose the sales leader explains that three major opportunities have advanced.

One customer has signed a contract.

Another has confirmed an earlier delivery schedule.

A third is in final negotiations.

Now we have something to examine.

I’d separate the opportunities by their actual commercial status.

Opportunity	Potential revenue	Evidence	Forecast treatment
Customer A	$3.0M	Signed order, delivery confirmed	Include if recognition criteria and timing are met
Customer B	$2.0M	Customer requests accelerated shipment	Include only to the extent delivery and recognition are supportable
Customer C	$2.0M	Negotiations underway	Evaluate probability and timing; don’t treat as committed revenue

Notice what I haven’t done.

I haven’t automatically accepted all $7 million.

But I haven’t dismissed the sales leader either.

I’ve turned an opinion into a set of testable assumptions.

That’s the work.

And if the evidence supports the full increase, wonderful. Change the forecast.

I have no emotional attachment to $118 million.

I just want the number we use to make decisions to have a defensible relationship with reality.

The Override Has to Travel Through the Financial Statements

This is where a management adjustment can become particularly dangerous.

Suppose we accept $5 million of additional revenue based on credible new information.

Can the company deliver it?

Will the additional sales carry the same gross margin?

Does the business need more inventory?

Will customers pay before year-end?

Will overtime, freight, commissions, or temporary labor increase?

The answers determine whether the revenue adjustment also improves earnings and cash.

Let’s say the $5 million of additional revenue has a 32% incremental gross margin, rather than the original forecast’s 40%.

It also requires $400,000 of incremental operating expenses.

Then the EBITDA impact is:

$5.0M × 32% − $0.4M = $1.2M

The revised forecast becomes:

Financial measure	Original forecast	Evidence-supported revision
Revenue	$118.0M	$123.0M
Gross profit	$47.2M	$48.8M
Operating expenses	$35.0M	$35.4M
EBITDA	$12.2M	$13.4M

That’s a very different result from the original management override.

We still have a better forecast than we started with.

But we’ve stopped assuming that every additional dollar of revenue arrives with the same margin and no additional effort.

Which, if we’re being fair, would be a rather convenient business model.

And What Happens to Cash?

Suppose $4 million of the incremental revenue is expected to remain uncollected at year-end.

The company also needs an additional $1 million of inventory to fulfill the orders.

Ignoring other working-capital movements for this illustration, those assumptions imply a combined $5 million increase in receivables and inventory relative to the original forecast.

The $1.2 million EBITDA improvement does not mean cash will improve by $1.2 million.

In fact, the business may need additional financing or liquidity to support the growth.

This is why I wouldn’t approve a material revenue override without understanding its working-capital consequences.

A stronger income statement can coexist with a more demanding cash forecast.

The two are not having an argument.

They’re describing different parts of the same business.

I’d Keep the Original Forecast

Here’s something I consider essential.

When management changes a forecast, preserve the original version.

Don’t overwrite it.

Don’t quietly replace the assumptions and pretend the model produced the new answer all along.

I want to know:

• What did the original model predict?
• What did management change?
• Why was it changed?
• What evidence supported the adjustment?
• Who approved it?
• What actually happened?

That information allows us to learn whether overrides improve forecast accuracy.

Without it, we’re left with an organizational tradition of remembering the successful judgments and developing selective amnesia about the others.

An impressive human skill.

Not an ideal financial control.

Measure Whether Management Judgment Actually Helps

Imagine we review six completed quarterly forecasts.

We compare the original model forecast, the management-adjusted forecast, and actual revenue.

Quarter	Model forecast	Management forecast	Actual revenue
Q1	$28.0M	$30.0M	$28.5M
Q2	$29.0M	$30.0M	$29.5M
Q3	$30.0M	$32.0M	$30.5M
Q4	$31.0M	$32.0M	$31.5M
Q5	$32.0M	$34.0M	$33.5M
Q6	$33.0M	$35.0M	$33.5M

Hypothetical quarterly data, in millions of dollars.

Now calculate absolute forecast error.

For the original model, the errors are:

$0.5M + $0.5M + $0.5M + $0.5M + $1.5M + $0.5M = $4.0M.

Average absolute error: approximately $0.67 million per quarter.

For management’s adjusted forecasts:

$1.5M + $0.5M + $1.5M + $0.5M + $0.5M + $1.5M = $6.0M.

Average absolute error: $1 million per quarter.

In this hypothetical example, management’s adjustments made the forecasts less accurate overall.

That doesn’t mean management judgment is inherently bad.

It means this particular set of adjustments didn’t improve the result.

I’d want to understand why.

Were the overrides consistently optimistic?

Were they based on genuine new information that failed to materialize?

Were important delivery constraints overlooked?

Did management repeatedly confuse sales targets with likely outcomes?

Those questions tell us how to improve the next forecast.

Simply announcing that we need greater forecast accuracy does not.

A Forecast and a Target Have Different Jobs

This distinction might be the most important one in the entire discussion.

The distinction matters whether the company uses rolling forecasts or annual budgets.

A target describes what the organization wants to achieve.

A forecast describes what the organization currently expects to achieve.

Both are useful.

Both should influence management decisions.

But they should not be forced to agree.

If the target is $125 million and the evidence-supported forecast is $123 million, we have a $2 million performance gap.

Good.

Now management can decide what to do about it.

Can we accelerate sales activity?

Change pricing?

Improve customer retention?

Add capacity?

Reduce spending?

Or accept that the target is unlikely under current conditions?

Those are legitimate executive decisions.

Changing the forecast to $125 million doesn’t close the performance gap.

It just makes the gap harder to see.

It’s a little like changing the bathroom scale to display the number you prefer.

Lovely result.

The jeans remain surprisingly uncooperative.

Give Management a Place to Express Its Judgment

I wouldn’t solve this problem by forbidding overrides.

That would throw away valuable business knowledge.

Instead, I’d establish a transparent process.

For a material forecast adjustment, I’d want five things.

A specific assumption. What new information changes the expected outcome?

A financial bridge. How does the adjustment affect revenue, margin, expenses, cash, and relevant operational drivers?

An accountable owner. Who is responsible for the business assumption and who approves the financial treatment?

A preserved baseline. What would the forecast have been without the adjustment?

A later review. Did the override improve the forecast, and what did we learn?

The amount of scrutiny should reflect the materiality and risk of the adjustment.

A $50,000 timing change doesn’t necessarily require an executive committee.

A $7 million revenue increase that changes the company’s hiring, spending, and liquidity decisions deserves more attention.

And I would apply the same standard to downward adjustments.

Pessimism can distort decisions just as effectively as optimism.

What About the CFO’s Experience?

I value it.

Experience can recognize patterns a statistical model misses.

A CFO may know that a customer negotiation is more likely to close than the CRM stage suggests.

A finance leader may recognize that a business unit’s forecast has become unusually conservative.

Those observations deserve consideration.

But I would still ask for the reasoning.

Not because I distrust the CFO.

Because judgment becomes more valuable when we can examine it, compare it with outcomes, and learn from it.

An experienced executive should have no difficulty saying, “Here’s what I know that the model doesn’t.”

That’s a very different statement from, “I don’t like the number.”

And I suspect most good CFOs appreciate the distinction.

The Meeting I’d Rather Have

Instead of arguing about whether the forecast should be $118 million or $125 million, I’d rather put three numbers on the table.

$118 million: What the original operating model predicts.

$123 million: What the model predicts after incorporating new evidence that finance and the business can support.

$125 million: What management wants to achieve.

Now we can have a useful conversation.

The first number gives us a baseline.

The second is our updated expected outcome.

The third identifies the ambition.

We can decide what actions might close the $2 million gap, what those actions cost, and whether they are likely to work.

We can also evaluate the downside if they don’t.

This is the kind of discussion where FP&A earns its seat at the table.

Not by winning an argument over whose number is correct.

By helping management understand what each number means and what decisions follow.

The Best Forecast Isn’t Always the One Everyone Likes

I enjoy a confident leadership team.

I enjoy ambitious targets.

And I have no objection to a CFO who challenges the model.

Quite the opposite.

But I want the forecast to remain an honest estimate of what the business expects to happen.

If management has better information, use it.

If management has a bigger ambition, show it.

If the company needs a plan to close the gap, build one.

Just don’t make one number perform all three jobs.

That’s asking rather a lot of a spreadsheet.

And, frankly, the spreadsheet has enough problems.

When Every Forecast Meeting Ends With a Different Number

If your finance team keeps rebuilding forecasts after executive reviews, or nobody can explain which management adjustments actually improved accuracy, I think that’s worth addressing.

My Forecasting & Planning services focus on building more reliable financial planning processes and connecting forecasts to management decisions.

We can keep debating which number feels right.

Or we can establish a process that shows what changed, why it changed, and whether the adjustment helped.

I know which meeting I’d rather attend.