What goes in a board package for a PE-backed company?
A working board package has seven sections: an executive summary in prose, results against budget and prior year, the reforecast, cash and covenant position, KPIs, decisions requested, and an appendix. The main body runs fifteen to twenty slides. Everything else goes behind the appendix divider, where it is available without being in the way.
Most packages fail for one of two reasons. They are too long, so nothing is prominent. Or they present numbers without interpretation, so the sponsor supplies their own — and their interpretation is formed without the context management has.
Section 1: Executive summary
One page, written as prose, and written last. It answers four questions in order: what happened this period, why, what it means for the year, and what is being asked of the board.
Prose, not bullets. The discipline of writing complete sentences forces a causal claim — "margin fell 240 basis points because the two largest new contracts carry lower rates during their ramp period" — where a bullet permits "margin down 240bps" and leaves the reader to guess. The guess is where the meeting goes wrong.
This is the only page some directors will read closely. Write it accordingly.
Section 2: Results against budget and prior year
Three or four pages. The financial results with two comparisons, always the same two, in the same order every period.
Show variance in both dollars and percentage. Percentages alone mislead on small bases — a 40% miss on a $50,000 line is noise, and looks identical to a 40% miss on a $4M line. Dollars alone hide the severity of a small line that has doubled.
Then decompose the variance rather than reporting it. A revenue miss of $1.2M is not information; it becomes information when it reads:
| Driver | Impact |
|---|---|
| Volume — units below plan | ($1,450,000) |
| Price — realised above plan | $380,000 |
| Mix — shift toward lower-margin segment | ($210,000) |
| Timing — contract slipped to next quarter | $80,000 |
| Total variance | ($1,200,000) |
Now the board can act. Volume is a demand or execution problem, price is a strength worth protecting, mix is a strategy question, and timing corrects itself. One number became four decisions.
Section 3: The reforecast
Two or three pages. The current view of the full year, what changed since last period, and why.
Show the walk from the prior forecast to the current one. Directors want to know the direction and the cause of revision, not just the new landing point:
| Bridge | Amount |
|---|---|
| Prior forecast — full year EBITDA | $6,400,000 |
| Q2 actual shortfall | ($310,000) |
| Revised H2 volume assumption | ($480,000) |
| Cost actions taken in June | $290,000 |
| Price increase effective September | $180,000 |
| Current forecast | $6,080,000 |
Keep the budget visible alongside it. The budget is the commitment and it does not move; the forecast moves monthly. Companies that overwrite the budget with the forecast lose the ability to say how far they have drifted from what they promised — which is the question the board is actually asking.
Section 4: Cash and covenants
One or two pages, and for a leveraged company this is often the first section a sponsor turns to.
Include the cash position, the 13-week outlook at least in summary, revolver availability, and the covenant calculations with headroom against each test. Forecast the covenants forward — a ratio calculated after the quarter closed cannot be influenced, whereas a projected breach two quarters out is still a set of choices. Covenant compliance reporting works through that arithmetic.
Never present a covenant as a single number. Present it as headroom: "leverage 2.52x against a 3.25x maximum, headroom of 0.73x, equivalent to roughly $1.1M of EBITDA."
Section 5: KPIs
Two or three pages, eight to twelve metrics. Every metric needs a target, a trend, and a definition that has been agreed and written down.
The test for inclusion: would a plausible movement in this metric change a decision this board makes? If not, it belongs in an operating review. Thirty metrics is the same as none — there is nothing prominent, so nothing is noticed. Picking the eight that matter covers the selection in more depth.
Section 6: Decisions requested
One page, and the most frequently omitted.
List what management is actually asking the board to approve or discuss, each with the recommendation, the alternatives considered, and the financial impact. A board meeting without a decisions page tends to become a status update, which is an expensive use of a room full of people who were assembled to decide things.
Section 7: Appendix
As long as it needs to be. Detailed financials, departmental P&Ls, the full KPI set, pipeline detail, headcount rosters, prior-period comparisons.
The appendix exists so the main body can be short. The rule is that nothing in the main body should require the reader to go to the appendix to make sense of it, and nothing in the appendix should be a surprise given the main body.
Distribution timing changes the meeting
Five business days before the meeting. This matters more than most of the content decisions above.
A package distributed the night before guarantees the first forty minutes of the meeting are spent reading it, in silence, in a room that costs a great deal per hour. Directors then ask first-reaction questions rather than considered ones.
Five days ahead, directors arrive having read it. The meeting starts at the second question. It is the cheapest available improvement to board effectiveness, and it is purely a scheduling problem: work backwards from the board date through distribution, review, and close, and put the resulting dates in a calendar at the start of the year.
What the length should be
| Section | Pages |
|---|---|
| Executive summary | 1 |
| Results vs. budget and prior year | 3–4 |
| Reforecast | 2–3 |
| Cash and covenants | 1–2 |
| KPIs | 2–3 |
| Decisions requested | 1 |
| Main body | 10–14 |
| Appendix | As required |
A seventy-slide main body is not thorough. It is undifferentiated, and it transfers the work of deciding what matters from the person who prepared it to the people receiving it — which is exactly backwards.
Consistency is a feature
Same sections, same order, same definitions, every period. Directors then learn where to look, and comparison across meetings becomes possible.
Redesigning the deck each quarter destroys that, and it also destroys the trend lines — every restated definition breaks the history. When a definition genuinely has to change, restate the comparatives and say so plainly in the package rather than quietly changing the basis and hoping the shift reads as performance. That disclosure costs a sentence and buys the credibility of every other number in the document.
Who prepares what, and when
A package that arrives five days early is a scheduling achievement, not a heroic one. It requires the production chain to be assigned and dated at the start of the year.
| Day | Step | Owner |
|---|---|---|
| 1–8 | Month-end close completed | Controller |
| 9 | Actuals loaded to the model | FP&A / CFO |
| 10 | Variance decomposition prepared | FP&A / CFO |
| 11 | Reforecast updated and bridged | FP&A / CFO |
| 12 | Covenant calculations and cash outlook | CFO |
| 13 | Draft commentary circulated to management | CFO drafts, CEO edits |
| 14 | Package assembled and reviewed | CFO |
| 15 | Distributed to board | CFO |
The step that most often slips is the commentary, because it is the only one requiring several people to agree on an interpretation. Drafting it from the variance analysis rather than from memory removes most of that friction: management is editing a position rather than starting from a blank page.
Note the dependency chain. Every date above is downstream of the close. A company closing on day 20 cannot distribute on day 15, no matter how efficient the rest of the process is — which is why board reporting problems are so often close problems wearing different clothes. Fixing the close usually comes before fixing the package.
The questions a good package answers before they are asked
A useful test when reviewing a draft: read it as a director who has been in one meeting per quarter and has not thought about the company since the last one. Does it answer these without a follow-up?
- Are we ahead or behind, and by how much, against what we committed to?
- What specifically caused the difference, and is it one-off or continuing?
- Has the full-year expectation changed, in which direction, and why?
- Is there enough cash and enough covenant headroom to execute the plan?
- What are you asking us to decide today?
If a director would have to email someone to answer any of these, the package is not finished. Most ad-hoc data requests between meetings are evidence of a question the package should have anticipated — which makes them a useful list to review when redesigning the template.