← The Finance Station ~ dish 04 of 10 · the finance station

Variance Commentary

The actual vs. budget delta needs to be explained in plain English. What moved, why, what to watch. The leverage isn't the math. The math is done. The leverage is Output Over Process. The Chef defines what a board member needs to understand in two minutes, then the station writes to that standard. Most operators never write down the destination.

The job

Variance commentary is where spreadsheets become stories. Actuals came in $50K over budget on revenue. Why. Was it one customer with a big order. Was it price-per-unit higher. Was it volume growth. The leadership team reads the numbers cold if nobody explains it. They don’t understand what happened or what to do next.

The CFO today writes variance commentary in a spreadsheet comment or in a standalone memo. Five lines per line item. Actual. Budget. Variance. Explanation. The explanation is where the leverage lives, and it’s where most operators write too little or too much. Too little and the board member has to ask questions. Too much and they zone out.

The station runs this recipe right when it has the variance data, understands what “explained well” looks like in your company’s voice, and drafts the commentary the CFO would have written if they had 30 minutes instead of four hours.

The recipe

All seven ingredients still apply. The leverage on this dish is Output Over Process (Ingredient #5). The Chef defines what done looks like. A board member should understand this in two minutes. Not the steps. The destination.

Training matters. Show the station how you explain variance when you’re talking to the board. That’s your voice. Context matters. The station reads the variance data, the prior-month performance, the season patterns, and the forward-looking signals. Examples matter. Show the station three variance commentaries you wrote by hand, labeled by line item and by season.

How to build it

  1. Define the destination. Write this down: “A board member should understand the variance, the reason, and what we’re watching in 120 seconds.” That’s the North Star. Everything is measured against it.
  2. Pull three variance commentaries you wrote yourself. Revenue variance. COGS variance. OpEx variance. One from a slow season, one from growth, one from a normal month. Label each by line item and season.
  3. Show the station your commentary structure. Variance amount. The primary reason. The secondary reason if relevant. What we’re watching. That structure is what the board expects.
  4. Pipe in the actual variance data from the last 12 months. Month-by-month. Variance by line item. Compare to budget and to prior year.
  5. Pipe in context data. Seasonality. Customer mix. Product mix. Pricing changes. Anything that explains why the variance landed the way it did.
  6. Test on a mock run. Give the station this month’s variance data. It drafts commentary for three line items. You read each one. Does a board member understand it in two minutes. Is it your voice. Adjust.
  7. Go live with CFO review. The station drafts. The CFO reads, edits, approves. When the CFO edits, they’re teaching the recipe what “better” looks like.

What breaks it

  • No destination defined. The CFO gets variance commentary that’s too short. The board asks a question. Too long and they skip it. You never wrote down what “right” looks like. Define the two-minute rule upfront and measure against it.
  • Examples don’t match the tone. The station’s commentary reads like a bookkeeper explaining. Your examples read like the CEO explaining. The station learns from examples, so the examples have to be in the voice you want the output in.
  • Variance data is incomplete. The station has the number but not the reason. Revenue variance up $30K. The station doesn’t know it was a one-time order. It writes “strong sales momentum.” That’s not what you meant. Pipe in the context.
  • Feedback loop death. The CFO edits the station’s draft. The edit never updates the recipe. Three months later, the station is still writing commentary the wrong way because the miss never made it back into the training.

When it’s working

At week four, the CFO can read the station’s variance commentary and send it to the board as-is without rewrites. Board members understand the variances without asking follow-up questions. Decisions in subsequent calls show the board paid attention to the explanation.

The signal that the recipe is sharp: the CFO finishes the month-end close one day faster because variance commentary is done and done right.

Monday Move

Write down your definition of good variance commentary: “A board member should understand it in two minutes.” Pull three variance commentaries you wrote by hand from the last three months. Pipe in this month’s variance data and context. The station is running.

Dish 4 of 10 on the Finance Station. Build-note leverage: Output Over Process (Ingredient #5).