This issue in one sentence:
Everything I’ve learned about writing variance commentary that actually drives decisions — in one place.
I’ve reviewed hundreds of variance reports over the years. Most of them answered one question: what happened?
The best ones answered a different question entirely: what do we do now?
That gap — between a report that records history and one that drives action — usually comes down to how the commentary is written. Not the data. Not the tool. The narrative around the numbers.
This issue pulls together the framework I use, the most common mistake I see, and the one question that separates good commentary from great.
The framework I always come back to
When something moves — revenue, cost, margin — a good variance comment answers five things, in this order:
What happened? State the variance clearly. Direction, size, period. No jargon. “Revenue missed plan by €2.3M in March.”
Why did it happen? Dig past the surface. One cause rarely explains everything — but one cause is usually primary. If you can’t name it, keep digging.
What’s the business impact? Connect the number to something that matters — margin, cash, a strategic target. Numbers without consequences are just bookkeeping.
Is it permanent or temporary? This is the question leadership always asks. Answer it before they do — and be honest if you’re not sure yet.
What happens next? A comment without a next step isn’t finished. Either name the corrective action, or give an honest read on what you’re monitoring.
That last question is where most commentary stops short. It’s also where the most value is.
The hardest call: permanent or temporary?
This is the hinge of every good variance commentary. Get it right, and the rest of the conversation flows — forecast adjustments, resource decisions, corrective actions. Get it wrong, and you’re rebuilding trust one reforecast at a time.
Four questions I run through every time:
What would have to be true for this to reverse? If you can’t name the specific condition, you don’t have enough to call it temporary yet.
Is the underlying driver still active? A supplier price increase still in the contract is not a one-off.
What does the forward data actually say? Optimism is not a forecast. There should be something concrete — a signed order, a confirmed date — supporting a “temporary” call.
Has the business adapted, or is it still exposed? If costs have risen permanently and pricing hasn’t moved, the variance will keep coming back.
And three ways to write it, depending on what you actually know:
✅ Temporary: Name the reversal condition + expected timing “Volume shortfall of €1.2M expected to recover in Q2 — two delayed enterprise deals confirmed for April close.”
✅ Permanent: Name the structural shift + forecast implication “Logistics costs up €0.4M/month reflecting new carrier contract from February. Forecast updated accordingly.”
✅ Uncertain: Say so — with what you’re watching “Driver unclear at this stage. Monitoring B2B pipeline through April before updating the forecast assumption.”
That last one takes confidence to write. But it’s more useful than a false call in either direction.
One thing to try this cycle
Before you send your next variance commentary, run this quick check:
Is the variance actually stated — direction, size, period?
Is there one lead driver named?
Is there a so-what — a consequence that matters?
Is there a next step or an honest status?
If all four are there, it’s done. If one is missing, that’s your fix.
Same data. A comment that passes this check is a completely different read from one that doesn’t.
A question for you
Which of the five framework questions do you find hardest to answer consistently — and why? Hit reply, I read everything.
If someone forwarded this to you and you’d like to receive future issues, you can subscribe here. Finance with Ola is published bi-weekly.