Actual vs Forecast in a Monthly Cash Review: What the Comparison Should Actually Change
Key takeaways
- Actual confirms what already happened. Forecast tells you what that reality is likely to do next.
- The real job of the comparison is not to explain the month better. It is to improve the next decision.
- Actual without forecast misses direction. Forecast without actual becomes a hope structure.
- The most useful monthly sequence is actual, variance vs plan, revised forecast, then decision.
- This comparison becomes most useful when it helps management read cash safety, spending direction, and downside control together.
Most teams compare actual and forecast every month.
Far fewer use that comparison well.
Actual tells you what already happened. Forecast tells you what that reality is likely to do next.
The real job of the comparison is not to make the month easier to explain. It is to make the next decision harder to avoid.
That is why this matters.
This is not just a checklist of what founders should look at.
It is about how actual and forecast should work together in a monthly cash review, and what that comparison should actually change.
Who this is for
This article is for founders, CFOs, and finance leads who already review monthly numbers, but still feel one of these problems:
- actuals are there, but the review still feels too retrospective
- forecast exists, but it still feels too optimistic or too protected
- the team can see the variance, but not what it means for cash safety
- the month-end cash number looks manageable, but control feels weaker than it did one month earlier
If that sounds familiar, the issue is usually not missing data.
The issue is that actual and forecast are being shown, but not used as a true comparison.
What actual and forecast are really for
The practical difference is simple.
Actual is the fixed record of what already happened.
It tells you what cash actually did, what revenue actually came in, what burn actually landed at, whether collections actually slipped, and whether spend actually ran ahead of plan.
Forecast is the forward read on what that reality is likely to do next.
It tells you what the current conditions are likely to mean over the next few months if nothing meaningful changes.
That means their roles are different.
- actual is for reality confirmation
- forecast is for decision preparation
Actual should stop wishful thinking.
Forecast should stop late reactions.
That is the most useful way to frame this comparison.
Why one without the other is dangerous
If you only look at actual
The risk is that the current month still looks manageable while the next few months are already getting tighter.
That happens when:
- a decent month is flattered by payment timing
- revenue still looks acceptable, but collections are weakening
- spend has risen, but its future impact is still hidden
- the cost base is becoming more rigid than the month-end number suggests
Actual can confirm the month and still miss the direction.
That is why actual alone is not enough.
If you only look at forecast
The risk is that forecast becomes a protected story instead of a management tool.
That happens when founders assume:
- delayed revenue will come back next month
- spend can always be cut later
- cash pressure is temporary without proving it
- the old forecast still deserves trust even though actuals already broke its assumptions
Forecast without disciplined actual review is usually not a forecast.
It is a hope structure.
What this comparison should make you ask
A useful actual-versus-forecast comparison should make the team ask better questions.
1. What changed?
Not just whether the month was good or bad.
What actually moved cash?
Revenue timing? Collections? Hiring? Margin? One-off spend? Delayed payments? A temporary bump that flatters the month?
2. Was the change temporary or structural?
This is where the comparison becomes useful.
A one-month delay is different from a broken assumption.
A timing issue is different from a weaker model.
A temporary spike in spend is different from a more rigid cost base.
This matters because the wrong diagnosis creates the wrong forecast.
3. What did the change do to cash safety?
A company can still look fine at month-end and be less safe than it was one month earlier.
That happens when the buffer still looks acceptable, but the structure underneath it is weaker.
The comparison should tell you whether the month only moved the number, or whether it weakened the company’s ability to absorb normal variance.
4. What is current spending actually buying?
This matters more than founders often admit.
If spend is increasing, is it buying stronger delivery capacity, better operating control, more dependable revenue, or just more activity?
The comparison is not just about variance.
It is about whether the spend direction still makes sense.
5. What gets tighter first if nothing changes?
This is where downside control becomes visible.
If the forecast weakens, what breaks first?
- hiring flexibility
- collections tolerance
- margin room
- ability to absorb one bad month
- room to delay financing pressure
That is the management read that matters.
How to use actual and forecast in a monthly cash review
The best order is usually:
- Actual
- Variance vs plan
- Revised forecast
- Decision
Start with actual to lock reality.
Then explain the variance.
Not every miss matters equally. The point is to identify which variance actually changed the cash picture.
Then update the forecast using the new reality.
Do not defend the old forecast. Rebuild the next view from what the month actually revealed.
Then decide what changes now.
That might mean slowing hiring, tightening collections work, reducing lower-return spend, changing assumptions in the next forecast cycle, or re-prioritizing what current spend is supposed to buy.
That is what makes the review useful.
What founders often get wrong
The most common mistake is not misunderstanding the definitions.
It is misunderstanding the function.
Founders often use actual as reassurance and forecast as optimism.
That sounds like this:
- cash did not drop that much this month
- revenue was late, not lost
- we can adjust later
- next month should normalize
- the forecast still looks fine
But if actual has already weakened the assumptions, the forecast should not still look the same.
That is the discipline this comparison is supposed to create.
Another common mistake is treating all variance as equal.
It is not.
A miss in collections, a miss in gross margin, and a miss caused by timing do not mean the same thing.
You need to know which variances are temporary and which ones are quietly changing the structure underneath the number.
What actual and forecast become easier to read together
When founders use both together, three things become much easier to read.
Cash safety
You can see whether the month only moved the number or actually weakened the buffer underneath it.
Spending direction
You can see whether current spend is still buying stronger delivery, better control, or more dependable revenue — or whether it is now buying less than leadership assumed.
Downside control
You can see whether the next few months still leave room to respond, or whether the business is drifting into a tighter position before management fully admits it.
That is why this comparison matters more than a simple reporting side-by-side.
What else you should check with actual and forecast
This comparison gets much stronger when you also look at:
- plan or budget — otherwise the variance has no anchor
- cash bridge — so you can see what actually created the movement from opening cash to closing cash
- revenue quality and cash conversion — growth alone does not tell you whether the forecast deserves trust
- fixed vs flexible spend — so you can tell whether a weaker forecast still leaves room to respond
- assumption changes — so the forecast reflects management learning, not just updated numbers
- year-over-year seasonality context — especially when timing patterns matter and the business wants to know whether the month is normal or structurally different
Without those, actual and forecast can still look precise while remaining hard to use.
What this comparison should change
This is the part founders often miss.
The comparison is not useful because it helps explain the month better.
It is useful because it should change something.
It should change:
- what management still believes
- what management now doubts
- what spending is still justified
- what assumptions have to be rewritten
- what has to move before the next month starts
If none of that changes, the comparison probably did not do its job.
What to check next
If you want the shorter first-pass version of this topic, read:
Actual vs forecast: what founders should actually check
That page is narrower.
This article is the fuller Core version.
It is not just about what to look at. It is about how actual and forecast should work together in a monthly cash review, and what that comparison should actually change.
Want a clearer monthly cash review?
RunwayDigest turns your inputs into a structured runway, burn, and cash direction report and sends it by email. Start with the free version.
Start free