The PE-Backed CFO Board Reporting Package: What Sponsors Actually Read

Published by

on

TL;DR
Sponsors read three pages of your board deck closely: the KPI dashboard, the cash and covenant page, and the forecast update. Everything else gets skimmed at best. The right structure is 12 pages plus an appendix. Cover, dashboard, P&L variance, cash and covenant, top five initiatives, forecast update, risk register, appendix. Anything more is either filler or an attempt to hide something. Both get noticed.

Nobody in a portfolio-company board meeting reads a 60-page deck. The deal partner skims for the three numbers they care about, the operating partner flips to the initiatives page, and the independent director reads the risk section. If your deck buries any of those, the meeting devolves into people finding what they need instead of discussing what matters. Below is the actual page-by-page structure I use, what a good version looks like on each page, and what a bad version looks like.

The 12-page structure

Page Section Purpose Time on page
1 Cover and headlines Three bullets. Where are we vs plan, what changed, what needs a decision 30 seconds
2 KPI dashboard 10 to 12 metrics, actual vs plan vs prior year, colored 3 minutes
3 P&L variance summary Revenue and EBITDA vs budget with a two-column driver walk 5 minutes
4 P&L detail Full income statement, month and YTD, vs budget and prior year 2 minutes
5 Cash and covenant Balance, availability, 13-week forecast summary, covenant cushion 5 minutes
6 Working capital AR aging, DSO, DPO, inventory turns, working capital as percent of revenue 2 minutes
7 Top five initiatives What we said we would do, status, dollar impact, next milestone 5 minutes
8 Forecast update Revised full-year forecast with a bridge to prior forecast 4 minutes
9 Commercial and pipeline Bookings, pipeline coverage, churn, key wins and losses 3 minutes
10 People and org Headcount actual vs plan, open roles, key departures, comp cycle status 2 minutes
11 Risk register Top five risks, owner, mitigation, change from prior meeting 3 minutes
12 Decisions requested Explicit list of what needs a board vote or a sponsor sign-off 5 minutes
App Appendix Everything the operating partner might drill into. Not for reading in the room Reference only

Page 1: cover and headlines

Good version: Three bullets on the cover. “Q2 revenue $18.4M, 4 percent above plan. EBITDA $3.1M, on plan. Cash cushion to covenant test tightened from $2.1M to $1.4M, driving decision request on page 12.” That is the whole page. Big font. Nothing else.

Bad version: A logo, a title slide, a table of contents, and a photo of a factory. Now you have burned two pages and the sponsor has learned nothing.

Page 2: KPI dashboard

Good version: 10 to 12 metrics, chosen because they actually drive the business. Revenue, gross margin, EBITDA, cash, DSO, headcount, bookings, backlog, churn, and one or two industry-specific numbers. Each in three columns: actual, plan, prior year. Color coded green, yellow, red on plan variance. Trend arrow. No commentary on this page. The commentary is on page 3.

Bad version: 40 metrics in six-point font. Every KPI the finance team could think of. Sponsors do not read this page, they scan it for red, and if half the page is red because you chose metrics that are always red, you have desensitized the audience.

Page 3: P&L variance summary

Good version: Two waterfall charts. One for revenue variance to budget with three or four bars showing volume, price, mix, and other. One for EBITDA variance to budget showing revenue flow-through, gross margin drivers, opex overruns, and one-time items. Two sentences of commentary under each. Done.

Bad version: A table of 60 GL accounts with a variance column and a “commentary” column populated by the controller with things like “insurance increased due to renewal.” Nobody at the board table reads that.

Page 5: cash and covenant

This is the page the deal partner reads first. Get it right or the meeting starts badly.

Good version: Top of page shows current cash balance, revolver availability, and total liquidity. Middle shows a 13-week cash forecast summary (weekly bars, cumulative line) and the minimum liquidity point in the quarter with a date on it. Bottom shows every covenant, the actual result, the required threshold, and the cushion in dollars and percent. If a covenant is within 20 percent of tripping, that line is red and the mitigation plan is called out.

Bad version: A table of 12 bank accounts with balances. No forecast. No covenant math. Just “we have $6.2M of cash.” That does not answer the question the sponsor came to ask, which is whether you can make it through the quarter without a covenant amendment.

Page 7: top five initiatives

Good version: Five rows. Each row: initiative name, owner (one named person, not “finance team”), status (on track, at risk, off track), dollar impact if delivered, next milestone with a date, one-sentence commentary. Same five initiatives quarter over quarter until each one closes. Then a new one takes its slot. You should be swapping in a new initiative every 1 to 2 quarters. If the same five have been on the page for four straight quarters, either the initiatives were too big or nobody is executing.

Bad version: 15 initiatives. No dollar impact. Status is “in progress” on every row. Milestones are things like “continue implementation.” This tells the sponsor you have not actually decided what matters.

Page 8: forecast update

This page is where trust gets built or lost. See the FP&A budget cycle article for the mechanics behind a real reforecast.

Good version: Two columns. Prior forecast on the left, updated forecast on the right, delta in the middle. A bridge below showing what changed and why: volume, price, cost, timing. If you took the number down, own it in one clear sentence. If you took it up, prove it with pipeline or booked backlog.

Bad version: A brand new forecast with no reconciliation to the prior forecast. Now the sponsor cannot tell whether you missed by $2M or beat by $500K. That is the exact feeling you want to avoid creating.

Page 12: decisions requested

Good version: Numbered list of specific asks. “Approve $600K capex for the second-shift production line. Approve amendment to credit agreement extending the net-debt-to-EBITDA covenant step-down by two quarters. Ratify offer letter for VP of Sales at base $265K + 40 percent variable.” Each with a recommendation and a one-line rationale.

Bad version: “Board discussion of strategic priorities.” That is not a decision, that is a conversation you did not prepare for. Board members hate showing up and being asked to have unstructured discussions.

Three slides that get you a follow-up call, and not in a good way

  1. The color-code slide where everything is green. Nothing in any operating business is all green. If your dashboard is all green, either you chose the wrong metrics or you are managing perception. Sponsors know both. The follow-up call is either “walk me through why this looks better than what I heard from the CEO” or “why are we not stretching harder.”
  2. The initiatives page that looks identical to last quarter. Same five initiatives, same status, same dollar impact, same next milestone. This gets a call because it signals either the org is not executing or the CFO is not tracking closely. Neither answer is good.
  3. The reforecast that has no bridge. Nothing generates a mid-week follow-up call faster than a new forecast that does not reconcile to the prior one. Sponsors do this math themselves and if the answer does not walk cleanly, they call.

Appendix strategy

The appendix is where you park everything the operating partner might drill into: department-level P&L, headcount detail by function, cohort revenue tables, customer concentration analysis, capex detail, tax provisioning. Nobody reads it in the meeting. It exists so that when the operating partner emails you Thursday afternoon asking “what does our top 10 customer concentration look like now vs a year ago,” the answer is “page A-14 of the deck.”

The appendix should be twice as long as the main deck. That is fine. What matters is that everything in it is real, tied to the same close, and clearly labeled. Do not put draft numbers or “for discussion” content in the appendix. If it is in the deck, it ships as a number the board can rely on.

Format conventions that make a deck feel professional

  • One number format across the whole deck. Pick $000s or $M and hold it. Do not switch mid-deck.
  • Every page footer has period, page number, and “prepared by finance” so any single page can be pulled out and still make sense.
  • No stock photos. No pull quotes. No “our values” slides. Save those for the all-hands.
  • Variance columns always in the same position, always same sign convention. Overs are positive, unders are negative, no exceptions.
  • If a number ties to something in the QoE or the model, show the tie. If it does not, note the reason.

Cadence and delivery mechanics

Standard sponsor cadence in the lower and middle market is monthly board deck by business day 15, quarterly deep dive with a longer package, and an annual budget review in Q4. The monthly package sits in Dropbox or a similar shared folder. The board deck itself goes out 48 hours before the meeting, not the morning of. A sponsor who is reading the deck in the taxi on the way to the meeting is a sponsor who did not prepare, and that is your fault for sending it late.

Push back on this.

Every operator’s situation is a little different. If you run this differently, disagree with the methodology, or think we got something wrong, tell us. We publish the best counter-approaches on our Reader Contributions page, credited or anonymous, your call. Email hello@thepragmaticcfo.com.

FAQ

How many KPIs is too many on the dashboard?

More than 15 and the eye glazes. Fewer than 8 and it feels thin. The right answer is usually 10 to 12, chosen because they actually drive the business, not because they are easy to pull. If a KPI is on the page but nobody in the room can define why it moved, cut it.

Should I include a subjective “commentary” section on the P&L page?

Yes, but keep it to three bullets max, and only for material variances. Commentary that just describes the number (“revenue was up 4 percent”) is filler. Commentary that explains why (“revenue was up 4 percent driven by a $300K prior-quarter deferral catching up in April”) is signal.

Do I need a separate deck for the audit committee?

In lower-middle-market PE, usually not. The audit committee gets a short section within the main board package covering controls, audit status, and any accounting policy changes. Only formalize a separate deck if the sponsor asks or if a major event (restatement, material weakness, transaction) demands it.

How much detail on people and org?

Enough that the board can see headcount tracking to plan, open roles being filled on pace, and any key departures called out. Do not put comp bands on the page. Do not name every open req. See the AI-native finance team job descriptions for how to define the roles cleanly before you get to headcount tracking.

Should the forecast on page 8 match the LRP the sponsor built at deal close?

No, and pretending it does is worse than being honest. The right approach is to show the current forecast and a one-line reconciliation to the deal-close LRP: “Full-year forecast is $2.1M below the LRP on EBITDA, driven by delayed price increase (Q3 vs planned Q1) and slower ramp of the third distribution center.” Own the delta. Sponsors respect honesty more than they respect a fake tie-out.

Related reading

Sources

  • Bain & Company, Global Private Equity Report 2026, on board reporting norms and value-creation plans
  • PitchBook US PE Middle Market Report Q1 2026, on cadence and monthly package expectations
  • Grant Thornton PE Value Creation Survey 2026, on KPI selection across portfolio companies
  • Alvarez & Marsal Private Equity Performance Study 2026, on reforecasting discipline and covenant tracking

Written by The Pragmatic CFO. 15+ years running P&Ls and building finance teams across portfolio companies.

Running restaurants? See the operator version: Multi-unit restaurant consolidated P&L at Restaurant Bottom Line.