Forecast Assumptions: The Model Should Remember What Changed

The forecast moved by $1.8 million.

The formulas are fine.

The model opens.

Nobody can immediately explain what changed.

This is not really a modeling problem. It is an assumption-memory problem.

Forecasts change because assumptions change. Price. Volume. Hiring dates. Churn. Conversion. Vendor timing. Launch dates. Collections.

Yet many models preserve the new number and quietly erase the old thinking.

If Finance cannot reconstruct why the forecast moved, the model is storing outputs better than it stores judgment.

An assumption is more than an input cell

A blue cell with 7.5% in it is not documentation.

I want to know what the assumption represents, who owns it, when it changed, what it replaced and why.

Not for every cell in the workbook.

For the assumptions that can materially move the outlook.

This is especially useful in driver-based forecasting, where a small number of operating assumptions may explain a large amount of financial movement.

Keep a simple assumption log

The log does not need software.

A table can work:

• Assumption
• Current value
• Prior value
• Effective period
• Owner
• Date changed
• Reason
• Material financial impact, if useful

The point is not administration.

The point is being able to answer the CFO when the forecast changes.

Separate facts from management choices

Some assumptions are observations.

Pipeline conversion is running lower. Customer usage increased. A signed contract starts in November.

Others are management decisions.

We are slowing hiring. We are increasing price. We are delaying a campaign. We are keeping inventory higher.

I like knowing which is which.

A forecast built from observed operating changes carries a different kind of uncertainty than one built around a decision management has not yet made.

That distinction becomes useful in scenario planning.

Do not overwrite the prior forecast and call it version control

Finance needs to be able to compare the current forecast with the prior forecast.

Not only actual versus forecast.

Forecast versus forecast.

What changed since the last time management saw the outlook?

Revenue moved because win rates changed. Payroll moved because hiring dates slipped. Cash moved because collections slowed.

That bridge is often more useful to leadership than another actual-versus-budget table.

Assumption ownership matters

Finance should not own every business assumption simply because Finance owns the model.

Sales should have a view on pipeline and bookings. HR and hiring managers should have a view on hiring timing. Operations should understand capacity. Finance should challenge, reconcile and translate those inputs into financial consequences.

Ownership does not mean accepting every number.

It means knowing where the judgment came from.

“Finance assumed it” is a weak answer when the assumption describes somebody else’s operation.

Watch for assumptions that never move

Some of the most suspicious assumptions in a forecast are the ones that remain perfectly stable while the business changes around them.

A conversion rate stays at 30% for nine months. DSO remains 42 days through a collections problem. Hiring time stays at 30 days while recruiting struggles to fill roles.

Stability can be real.

It can also mean nobody revisited the cell.

I like a periodic review of the assumptions with the greatest financial sensitivity, not every input in the model.

The forecast meeting should discuss assumption changes before output changes

If EBITDA is down $900,000, I want to know the operating reasons before we spend ten minutes admiring the bridge.

What changed in the business view?

That is the useful conversation.

The model then quantifies it.

This also makes variance analysis more productive because Finance can distinguish a bad original assumption from a genuinely new event.

A good model remembers what Finance used to believe

Forecasting is not a contest to predict one number perfectly.

It is a repeated process of updating a view as information changes.

That process becomes much more valuable when the organization can see the evolution of the thinking.

Six months later, I want to know why we believed the launch would happen in May.

Not because somebody needs to be blamed for May.

Because the reason we were wrong may be exactly what improves the next forecast.