When to Bring Actual vs Forecast Into a Monthly Finance Review

April 25, 2026 · 6 min read

Actual vs forecast should not appear randomly in a monthly finance review.

It should come after the team understands what actually happened to cash.

And it should come before the team decides what changes next.

That timing matters.

If actual vs forecast appears too early, the review can turn into a variance explanation before the cash picture is clear.

If it appears too late, the team may already be discussing actions without understanding which assumptions were wrong.

The best place is usually in the middle of the review:

cash movement first, actual vs forecast next, decisions after that.

That order keeps the review practical.

The first answer

Bring actual vs forecast into the monthly finance review after you have confirmed the cash movement, but before you update the forecast or set action items.

A simple order is:

1. confirm month-end cash
2. explain how cash moved during the month
3. compare actual vs forecast
4. identify why the difference happened
5. decide what should change in the next forecast
6. assign actions before the next review

This keeps actual vs forecast in the right role.

It is not the opening headline.

It is not the final appendix.

It is the bridge between what happened and what should change.

The purpose is not to explain every variance.

The purpose is to learn which assumptions, cash risks, spending choices, or collection actions need to change.

Why timing matters

Actual vs forecast can easily become a reporting exercise.

The team compares actual cash, revenue, burn, expenses, collections, or runway against forecast.

Finance explains the variance.

Everyone agrees the explanation makes sense.

Then the review moves on.

That can feel complete.

But it may not change anything.

A useful monthly finance review should use actual vs forecast to answer a more practical question:

What did the company believe would happen, what actually happened, and what should change because of the gap?

That question only works if actual vs forecast appears at the right moment.

The team needs enough context to understand the variance.

But it also needs enough time left in the review to act on it.

Do not start with actual vs forecast too early

It can be tempting to start the review with actual vs forecast.

The comparison looks clean.

It gives the meeting structure.

It shows what was above or below plan.

But if the review starts there too quickly, the team may overfocus on explaining line items before understanding the cash story.

For example, actual cash may be higher than forecast.

That sounds good.

But it may be higher because:

• a customer paid early
• a vendor payment moved into next month
• a hiring plan slipped
• a one-off inflow arrived
• a planned investment was delayed

Those are very different signals.

If the team jumps straight into variance explanation, it may miss whether the difference came from real improvement or timing.

That is why the review should first explain cash movement.

Ask:

How did opening cash become closing cash?

Then actual vs forecast becomes much more useful.

Do not leave actual vs forecast too late

The opposite mistake is also common.

The team reviews cash balance, runway, burn, cash bridge, collections, spending, hiring, and risks first.

Then actual vs forecast appears near the end as a finance detail.

That is also weak.

If actual vs forecast appears too late, it may not influence the decisions.

The team may already have decided that cash looks fine, spending can continue, or the forecast does not need to change.

Then the variance comparison becomes a supporting note instead of a management tool.

Actual vs forecast should happen early enough to shape the next decisions.

It should influence:

• whether the forecast needs to change
• whether collections need more attention
• whether spending should be paused or delayed
• whether hiring should continue as planned
• whether payment timing needs closer control
• whether downside control is improving or weakening

If it does not affect those decisions, it is probably appearing too late or being used too narrowly.

The best sequence

A practical monthly finance review can use this sequence.

1. Start with the cash position

Begin with the month-end cash balance.

But do not stop there.

The balance tells you where the month ended.

It does not explain whether the company is safer.

2. Explain cash movement

Next, explain how cash moved.

What came in?

What went out?

What was expected?

What was unusual?

What was timing-related?

This gives the review a cash story before the variance conversation begins.

3. Bring in actual vs forecast

Now compare actual vs forecast.

At this point, the team knows enough to interpret the gap.

The question is not only:

Was actual better or worse than forecast?

The better question is:

Which forecast assumptions were wrong, and why?

4. Separate timing from structural change

Then classify the variance.

Was it timing?

Was it one-off?

Was it a structural change?

Was it a collection issue?

Was it a spending decision?

Was it a forecast assumption that needs to change?

This step is where the comparison becomes useful.

5. Update the forward view

Actual vs forecast should feed the next forecast.

If collections are slower, the next forecast should reflect that.

If a payment moved into next month, the next forecast should include it.

If fixed spend increased, the downside case should become more realistic.

If a one-off item improved cash, the team should avoid treating it as recurring strength.

6. Set action items

Finally, decide what changes.

The review should end with action, not only explanation.

What actual vs forecast should answer

Actual vs forecast should answer a specific set of questions in the review.

Use it to ask:

• What did we expect to happen?
• What actually happened?
• Was the difference timing, one-off, or structural?
• Did cash safety improve or weaken?
• Did spending direction change?
• Did collection risk change?
• Did fixed cost pressure increase?
• Does the forecast need to be updated?
• What decision should change before the next review?

This is the difference between variance reporting and cash management.

The comparison should not exist to prove that the forecast was right or wrong.

It should help the team read what the variance means.

Where it sits relative to runway

Runway is important.

But actual vs forecast should usually come before the final runway discussion.

Why?

Because runway is only useful if the cash assumptions behind it are current.

If the team discusses runway before reviewing actual vs forecast, it may rely on outdated assumptions.

For example:

• collections may be slower than expected
• burn may be higher than forecast
• one-off cash may have improved the current month
• a delayed payment may make the next month weaker
• fixed costs may be rising faster than expected

Those findings should change how runway is read.

So the better sequence is:

cash movement → actual vs forecast → updated runway read

Runway should not be read as a separate comfort number.

It should be read after the team understands what actual cash behavior is saying.

Where it sits relative to burn

Actual vs forecast should also come before the final burn read.

A burn number can look acceptable or worrying depending on why it changed.

Burn may be lower than forecast because the company controlled spend.

That may be positive.

But burn may also be lower because payments shifted into next month.

That is not the same thing.

Burn may be higher because spending became less controlled.

That is a warning.

But burn may also be higher because the company made a planned investment with a clear reason.

That needs context.

Actual vs forecast helps explain whether burn variance is a real spending signal or a timing effect.

That is why burn should not be read without the variance story.

Where it sits relative to the cash bridge

The cash bridge should come before actual vs forecast.

The bridge explains what happened.

Actual vs forecast explains what was different from expectation.

That order matters.

If the team has not yet explained how cash moved from opening balance to closing balance, the variance discussion may become too abstract.

The bridge gives the raw movement.

Actual vs forecast gives the learning.

A useful order is:

cash bridge first, actual vs forecast second, forecast update third.

That keeps the review grounded in actual cash.

Where it sits relative to action items

Actual vs forecast should come before action items.

This is one of the most important rules.

Action items should be based on what the variance revealed.

If collections were late, who follows up?

If a payment moved into next month, who updates the cash view?

If spend exceeded forecast, who reviews the commitment?

If a one-off inflow improved cash, who prevents the team from overreading it?

If fixed costs increased, who checks downside control?

Without actual vs forecast, action items can become generic.

With actual vs forecast, action items become tied to the real gap between plan and reality.

A simple monthly review flow

For a founder or finance lead, the flow can be simple:

1. Where did cash end?
   Start with month-end cash.
2. How did cash move?
   Explain major inflows and outflows.
3. What was different from forecast?
   Bring in actual vs forecast.
4. Why was it different?
   Separate timing, one-off, and structural causes.
5. What does that change?
   Update forecast assumptions, runway, burn, and cash safety.
6. Who does what next?
   Assign owners and deadlines.

This is enough for most teams.

The goal is not a long finance meeting.

The goal is a better cash read.

A common mistake

A common mistake is treating actual vs forecast as a scorecard.

The team asks:

Were we above or below forecast?

That question is useful, but not enough.

A better question is:

What did the variance teach us about the next month?

For example, being better than forecast does not automatically mean cash safety improved.

It may only mean cash came in early or payments moved out.

Being worse than forecast does not automatically mean the company is failing.

It may reflect a planned investment, a timing shift, or a one-off payment.

The comparison is not the conclusion.

It is the beginning of a better question.

What founders should check first

When actual vs forecast appears in the review, founders should focus on the variances that change decisions.

Not every small difference deserves equal attention.

Start with:

• material cash variance
• collections variance
• burn variance
• timing differences
• one-off items
• fixed cost changes
• forecast assumptions that no longer look safe
• changes that affect cash safety or downside control

The most important variance is not always the largest number.

It is the variance that changes the next decision.

What good looks like

A good monthly finance review does not treat actual vs forecast as a finance slide.

It treats it as a decision point.

Good looks like this:

• the cash movement is clear before variance is discussed
• actual vs forecast explains what the team learned
• timing and structural differences are separated
• the next forecast is updated
• runway and burn are read with the updated assumptions
• action items are tied to the variance
• owners and timing are clear

When this happens, actual vs forecast becomes useful.

It helps the company move from reporting the month to managing the next one.

What to read next

For the deeper Core article on this topic, read:

Actual vs Forecast in a Monthly Cash Review: What the Comparison Should Actually Change

That article explains how actual vs forecast should change forecast assumptions, cash safety, spending direction, and downside control.

This page explains where actual vs forecast should sit inside the monthly finance review.

The Core article explains what the comparison should change.

Where RunwayDigest fits

RunwayDigest takes your inputs, processes them, and returns a structured runway, burn, and cash direction report by email.

The goal is not to replace judgment.

It is to make the current cash read clearer, faster, and easier to act on.

The free version is monthly free use.

Once per month per email.

It returns a simplified text report by email.

The paid version adds updated inputs, updated reports, compare input cases, monthly reminder, and stakeholder update draft.

← Back to Insights