Every month, without fail, actuals are finalised, variance reports are produced, and detailed commentary goes out explaining what happened to revenue and costs. The commentary took two days to write. Business unit leaders skim it for their own numbers. The CFO may read the summary. Nobody else engages with it.
And yet next month, the process runs again.
Ritual vs. Value
Monthly variance commentary became standard practice when it was the primary mechanism for communicating financial performance. That was a long time ago.
Most organisations now have dashboards, weekly business reviews, and constant informal communication about performance. The detailed monthly written commentary exists largely because it has always existed.
Ask honestly if this commentary drive decisions or change behaviour? Or is it a ritual something the finance team produces because it has always been produced?
If the honest answer is ritual, either redesign it significantly or stop doing it. Your team's time has better uses.
Volume Over Substance
Typical variance commentary is a lengthy document explaining every line item variance above a modest threshold. Department by department, account by account.
Flip the approach by only explaining variances that are material to decisions. If revenue was 3% above plan due to timing that everyone anticipated, one sentence is sufficient. Save the detailed explanation for genuine surprises or items that require a decision.
Two paragraphs that get read are more valuable than ten pages that get skipped.
Backwards-Looking Without Forward Implications
Variance commentary typically explains what happened last month. That is historical. Leadership needs to understand what last month's performance signals about the rest of the year.
Revenue came in below plan is a historical observation. “Revenue missed plan because three enterprise deals slipped, two of the three are now expected to close in Q2, but the third may be at risk due to budget constraints at the customer. I have adjusted the Q2 forecast accordingly and flagged this for the account team.” That is forward-looking and actionable.
Always connect historical variance to forward implications. The past is only useful as a window into what comes next.
Excuse-Making vs. Analysis
Much variance commentary reads as a list of explanations for why targets were missed. These may all be accurate. They are not particularly useful. Leadership is looking for understanding and, where relevant, action instead of explanations.
“Revenue missed plan. We now believe our Q1 forecast was optimistic because we underestimated the impact of customer budget freezes in January. We have revised Q2 down by 3% to reflect a more cautious assumption, and we are accelerating our retention programme in the most affected accounts.” Same facts, different framing. From explanation to analysis to action.
Passive Voice
"Revenue was impacted by market conditions." Which market conditions? How?
Passive construction obscures accountability and reduces clarity. Active construction forces you to identify what actually happened.
"Our largest competitor launched an aggressive promotional campaign in Q1 that we believe won three deals we expected to close" is specific and actionable. "Revenue was impacted by competitive dynamics" is not.
Cross-Functional Context
Finance writes variance commentary based on financial data. We frequently lack operational context that would change the narrative significantly.
Revenue was down 5%. Finance sees the number, but Sales knows it was because three enterprise deals slipped due to reorganisations at the customer. The account team knows one of those customers is now evaluating a competitor's solution and may not renew.
That context transforms the commentary from "revenue timing variance" to "potential competitive risk requiring a response."
Talk to the business before writing. Your variance explanation should reflect commercial reality, not just what the ledger shows.