Board Report Template: What Boards Actually Read

Board reports fail in a predictable way. They are long, they are assembled in the two days before the meeting, and roughly a third of the content exists to demonstrate effort rather than to inform a decision.

A board report has one job: let the board arrive prepared enough to spend the meeting on the two or three things that actually need their judgement. Everything else is housekeeping.

The template

BOARD REPORT — [Company] — [Month Year]
Sent: [date, ≥5 days before the meeting]

1. THE HEADLINE (3 sentences)
   Where we are against plan. Good, bad, and what changed since last time.

2. THE NUMBERS (one page, same format every time)
   Metric | This period | vs Plan | vs Last period | Trend
   Cash / runway | | | |
   Revenue / ARR | | | |
   Net retention | | | |
   Pipeline | | | |
   Headcount | | | |

3. AGAINST THE PLAN
   Priority | Owner | Status | Confidence | Change since last report
   1. | | On track / At risk / Off | H/M/L |
   2. | | | |
   3. | | | |

4. WHAT WE NEED FROM YOU (the reason for the meeting)
   Decision 1: ______  Options: ______  Recommendation: ______
   Decision 2: ______

5. RISKS
   Risk | Owner | Early warning sign | Change since last report

6. APPENDIX (nobody is required to read this)

Six sections, five pages maximum excluding the appendix.

Section by section

1. The headline

Three sentences, written last. If a director reads only this, they should know whether the quarter is going well and what changed.

Write it honestly. A headline that says "strong progress" for four consecutive quarters while the plan slips teaches the board to skip the headline and read the numbers — which is a bad trade for you, because the headline is where you get to frame.

2. The numbers

Same metrics, same order, same format, every single time. The value of a board pack compounds through comparability; a board that has to re-learn the layout each month reads less of it.

Include the comparison columns. A number without "versus plan" and "versus last period" is data the board has to do arithmetic on, and they won't.

3. Against the plan

The section most reports handle worst, usually because it is assembled by hand from whatever each owner emailed in.

Two things make it useful:

• Confidence, separately from status. "On track with low confidence" is a materially different situation from "on track with high confidence," and only one of them needs discussing.
• Change since last report. A priority that has been "at risk" for three consecutive reports is a different conversation from one that just moved. Boards notice trajectory, and this column is the trajectory.

4. What we need from you

This is the section that justifies the meeting, and it is the one most often missing.

Each item: the decision, the realistic options, your recommendation. A board asked to decide without a recommendation will either rubber-stamp or defer, and both waste the room.

If there is genuinely nothing you need from them, say so — and consider whether the meeting needs to be as long as it is.

5. Risks

Two or three, with an observable early warning sign for each. "Market conditions" is not actionable. "We are two weeks past the target start date for the second engineer" is.

Carry them forward between reports so the board can see what's aging.

6. Appendix

Everything you want on the record and nobody needs to read: full financials, detailed metrics, department updates. Its existence lets you keep the main body short without losing anything.

The four things boards skip

Worth knowing, because producing them costs real hours:

1. Long narrative department updates. Directors read the numbers and the exceptions.
2. Metrics with no comparison. A number with no plan or prior period is noise.
3. Anything that changed format since last time. Reformatting resets their reading pattern and they skim instead.
4. Good news at length. Boards calibrate on problems. Detail on what's working reads as padding — one line is enough.

Timing

Send five days before the meeting, not the night before. A pack sent the night before is read in the first ten minutes of the meeting, which converts your meeting into a reading room.

Say explicitly that the meeting assumes the pack has been read, then run the meeting that way. It takes one or two cycles for that to become the norm, and it roughly doubles the useful time in the room.

The part that should not be manual

Section 3 — status against the plan — is where most of the assembly effort goes, and it is the section most likely to be subtly wrong, because it is collected from owners who each have their own definition of "on track."

If the underlying work is already linked to priorities, that section can be generated rather than gathered. That is a meaningful difference: a generated status section is as current as the work, whereas a gathered one is as current as the last email. It also removes the incentive to round optimism upward on the way to the board.

Getting there depends on the plan actually reaching the work — see how company, department and individual KPIs connect, and how to evaluate software that maintains those links.

Where this fits in the year

The board calendar should anchor the annual planning calendar — work backwards from the board meeting at which next year's plan is approved, and everything else has a date.