The CFO's 12-Paragraph Board Commentary Framework
Jamie Saveall ·
Estimated reading time: 7 min
The last board pack you wrote was twenty-two pages. Six of them were commentary. The chair read three.
You know which three because she pinged you on the Tuesday after the meeting, asking about a number that lived on page four. The pages she didn't read were the pages you spent the most time on — the ones explaining what happened in Q1, why gross margin slipped 80 basis points, and how the new logo cohort was tracking against the plan.
This is not a writing problem. It's a structure problem.
Most board commentary fails for three reasons, and they're all related. It's too long, because the writer hadn't decided what mattered. It's too defensive, because the writer was bracing for a question that never came. And it's too retrospective, because the writer treated commentary as an explanation of last month rather than a steer for next month.
Boards read commentary that does four things in order. It tells them what happened. It explains why it happened. It says what's coming. And it asks for a decision.
Twelve paragraphs is enough.
The structure
Three paragraphs on each of four sections. Twelve paragraphs total. No section longer than 250 words. No paragraph longer than five sentences. If you can't make the point in that envelope, you haven't made the point.
Performance, paragraph 1 — the headline
One number. One sentence on direction. One sentence on whether it matters. Revenue of €2.1M, up 14% on prior year and 4% above plan. Plan was set in October, before the EMEA pipeline accelerated. That's the whole paragraph. The board doesn't need a four-sentence wind-up.
Performance, paragraph 2 — the drivers
What actually moved the number. Volume, mix, price, FX, customer mix. Name them. Quantify the top two. If one driver explains 80% of the move, say so and stop. The board has been in this business longer than you have. They will not be impressed by an exhaustive list.
Performance, paragraph 3 — quality
Was the result earned, timed, or fluked? A €100K deal that closed two weeks early is not the same as a €100K deal that arrived because the product is selling itself. Boards can tell the difference. Telling them you can tell the difference is half the battle.
Variance, paragraph 4 — versus budget
Material gaps only. A 3% miss on travel is not material. A 12% miss on gross margin is. State the gap, name the cause, and say whether it's a one-off or a trend. If you genuinely don't know yet, say that too. Boards forgive uncertainty when it's named.
Variance, paragraph 5 — versus prior period
Direction and magnitude. Quarter-on-quarter or year-on-year, not both. Pick the comparison that tells the story this quarter. If neither is interesting, skip the paragraph and use the words on something that matters.
Variance, paragraph 6 — versus expectations
The board approved a plan in October. They asked specific questions in February. What did you tell them to expect, and how does the actual compare? This is the paragraph everyone forgets and the chair always remembers. It's also the paragraph that builds your credibility quarter on quarter.
Forward view, paragraph 7 — leading indicators
The next 90 days, framed by data not optimism. Pipeline coverage. Renewal rates. Hiring against plan. If a leading indicator is flat or down, say so on this page rather than at the back of a deck nobody opens. Boards forgive bad weather. They don't forgive surprises.
Forward view, paragraph 8 — risks
Concrete risks, not the boilerplate four (FX, talent, competition, macro). Name one risk you're actively managing this quarter, name one you're watching, and name one that has gone away. The third item is the one most teams skip and the one that buys the most credibility.
Forward view, paragraph 9 — opportunities
Same rule. Specific opportunities the executive team is moving on, with the size of the prize attached. If you can't quantify it, you don't yet have an opportunity. You have an idea, and the board pack isn't where ideas belong.
Action, paragraph 10 — decisions taken
Close the loop on what the board approved last quarter. Did the new pricing land? Did the headcount freeze hold? Did the renegotiation on the Dublin lease save what you said it would? Boards remember what they decided. They notice when nobody tells them what happened next.
Action, paragraph 11 — decisions needed
What does the board have to do at this meeting? Approve a budget reforecast? Sign off on a hire above the cap? Bless a change in the audit committee charter? State it in one sentence and put the supporting paper behind a tab. The job of commentary is to surface the ask, not to argue it.
Action, paragraph 12 — the watch list
Two or three items you're tracking but aren't ready to bring for decision. This paragraph signals you know what's on the horizon and the board doesn't need to ask. It also gives the chair somewhere to start the next meeting, which is a quiet kindness she will remember.
That's twelve paragraphs. Done well, it lands under 1,800 words. Done with discipline, under 1,400.
A worked example
Imagine an €8M-revenue B2B services company, two regions, twelve people in the room. Here is what two of the twelve paragraphs look like in practice.
Performance, paragraph 1. Revenue of €2.1M, up 14% on prior year and 4% ahead of plan. Plan was set in October, before EMEA pipeline accelerated in late January. The two-month lag from pipeline acceleration to recognised revenue was shorter than the team modelled, which explains most of the variance.
Variance, paragraph 6. In February we told the board Q1 would land between €2.0M and €2.05M, with upside dependent on three named accounts. Two of the three closed in the quarter. The third slipped to April but remains live. The €60K beat against the top of the February guide is therefore mostly the two accounts, not a broader uplift in conversion. We are not raising the H1 guide on the back of one quarter.
Two paragraphs. A hundred and forty words combined. The reader knows the result, the cause, the comparison to what they were told to expect, and the implication for the next steer. The version most finance teams ship would use 600 words to say the same thing, and the chair would still ping you on the Tuesday.
Five phrases to cut
These are the tells that the writer hasn't thought hard enough. They show up in commentary pasted quarter to quarter with the numbers swapped.
"We are pleased to report." Nobody cares whether you're pleased. State the result and let the result speak.
"As expected." If it was expected, the board doesn't need a paragraph on it. If it wasn't, "as expected" is a lie.
"Continued strong performance." Continued from what. Strong by which measure. Strong against whose expectations. Either say the number, or don't write the sentence.
"Headwinds" and "tailwinds." Weather metaphors are a way to avoid naming the thing. The thing has a name. FX. Customer churn. The new pricing tier. Use the name.
"Going forward, we remain confident." Confident is not a forecast. Replace it with what you'll do, by when, and what you expect to see if it works.
If your last commentary contained three of these, you are not alone. If it contained all five, the board has stopped reading the commentary and is going straight to the numbers — which is fine, until the numbers need context and there is no context to be had.
Why this is harder than it looks
The structure is simple. Sticking to it is not. Every quarter, finance teams find a reason to add one more paragraph, one more chart, one more reassuring sentence. The pack swells because nobody has the authority to say cut this.
Twelve paragraphs is a constraint. Constraints are how you find what matters.
We built the Prompt Runtime v3 to generate exactly this structure from your underlying data: performance, variance, forward view, action, four sections, twelve paragraphs, every claim grounded in the figures behind it. It's how our customers go from a two-week commentary cycle to a two-hour one. The runtime produces a draft, not a final. The CFO still has the view. The runtime just stops the team rewriting the same scaffolding from scratch every month.
What to do on Monday
Pull your last commentary. Count the paragraphs by section. Most teams find they have nine paragraphs of variance, one of forward view, and zero of action. That is the problem. The board has stopped reading the variance section because they were in the room when it happened.
Rewrite the next one as twelve. See what falls out.