What Goes in a Board Reporting Pack (With a Monthly Template)

A board reporting pack is the standing package of financials, metrics and narrative a company sends its board ahead of each meeting, usually monthly for early-stage venture-backed companies and quarterly once a company is larger or has an active board that meets less often.

Its job is narrow: give directors enough of the real picture, in a consistent format, that the meeting itself can spend time on decisions rather than on getting everyone caught up. A pack that requires a director to ask "wait, what happened to gross margin last month" has already failed at that job, whatever else is in it.

Two audiences read the same pack differently. Investor-directors are checking the numbers against the plan they funded and against other companies in their portfolio. Independent or operating directors are usually reading for judgment calls: is the hiring plan realistic, is the sales pipeline believable, does the risk list match what they are hearing informally. A pack built only for one audience tends to under-serve the other, so both need to see the same core numbers plus the narrative context that makes those numbers legible.

The pack is also a discipline device for the company itself, not just an investor-relations artifact. Building the same five sections every month forces a monthly rhythm: close the books, review the KPIs, look at cash, look at the team plan, name the risks. Companies that skip board reporting between raises often find the muscle has atrophied by the time a real board is seated.

Every board pack starts with three statements, in board format rather than raw general-ledger export:

• Profit and loss (income statement), current month and year-to-date, against budget and against the same period last year where the company has history
• Balance sheet, focused on cash, receivables, payables and any debt, not a line-by-line asset schedule
• Cash flow statement or a simplified cash bridge showing beginning cash, cash from operations, cash from financing, and ending cash

Board format means summarized, not the chart of accounts. A P&L with 80 expense lines belongs in the accounting system, not the board deck; the board version rolls those up into 10 to 15 lines (revenue, cost of revenue, and expense categories like payroll, marketing, and software) with a note that supporting detail is available on request.

Budget-to-actual variance is the single most useful column on the page. A revenue number in isolation tells a director nothing about whether the company is on plan. The same number next to budget, with the percentage variance and a one-line reason for anything off by more than roughly 10%, tells them everything they need for that line.

Companies on accrual accounting should present accrual-basis statements; a cash-basis P&L understates real profitability for any business with meaningful receivables, payables or deferred revenue, and mixing bases between board packs from month to month makes trend lines meaningless. For SaaS companies specifically, deferred revenue and monthly recurring revenue recognition under ASC 606 change what "revenue" means on the P&L versus what showed up in the bank account that month, and the pack should be clear about which one it is showing.

The KPI page is where most board packs go wrong, usually by trying to show everything the company tracks internally instead of the handful that actually drive board-level decisions.

A workable KPI page holds to 4 to 8 metrics, chosen for the company's actual business model, tracked in the same format every month so a trend line means something after a few quarters:

• SaaS: MRR or ARR, net revenue retention, gross margin, CAC, LTV:CAC or payback period, logo and dollar churn
• Ecommerce: gross merchandise value, contribution margin per order, customer acquisition cost, repeat purchase rate
• Marketplace: gross transaction volume, take rate, supply-side and demand-side growth, liquidity (match rate)
• Services or agency: utilization rate, revenue per employee, gross margin per engagement, pipeline coverage

Each metric needs a definition line the first time it appears in a board deck, and that definition should not change quietly later. A company that redefines "active customer" or "churn" between quarters without flagging the change erodes trust fast, even if the new definition is more accurate, because the board can no longer compare period to period without asking which definition applies.

Resist the pressure to add a metric every time a new investor joins the round or a new director asks a one-off question. A KPI page that grows from 6 metrics to 20 over two years usually reflects unresolved disagreement about what actually matters, not better measurement. Park one-off questions in the narrative memo or an appendix instead of permanently expanding the tracked list.

For any company that has raised outside capital, cash and runway get their own page, separate from the balance sheet, because this is usually the first thing an investor-director actually looks at.

The minimum version: current cash balance, average monthly net burn over the trailing 3 months, and runway in months at that burn rate. The useful version adds a rolling 13-week cash flow forecast, or at least a forward 3 to 6 month projection, so the board sees where cash is headed, not just where it has been.

Burn rate should be shown both gross (total cash out) and net (cash out minus cash in from revenue), because a company growing revenue fast can have a shrinking net burn even while gross spending rises, and the two numbers tell different stories about the same business. Flag any one-time items, a large annual software renewal, a lump insurance payment, a legal settlement, so the trend line reflects ongoing burn rather than a lumpy actual.

A runway number without a stated assumption behind it invites the wrong question in the room. "14 months of runway" needs a one-line footnote: at current burn, no new hires, no revenue growth beyond plan. If the company is planning to add 4 sales reps next quarter, the runway page should show that scenario too, because the board's real question is usually "how much time do we have to hit the next milestone or raise again," and a static runway number that ignores a known upcoming spend answers a different question than the one being asked.

The hiring plan page connects the P&L to the org chart, which is where most of an early-stage company's spend actually lives.

A useful version shows current headcount by department (engineering, sales, marketing, G&A, and so on), planned hires for the next one to two quarters with target start dates and department, and the resulting change in payroll burn once those hires land, fully loaded for benefits and payroll taxes, not just base salary.

This page earns its place because hiring decisions are one of the few things a board can meaningfully weigh in on before the money is spent, unlike most other expenses, which are usually reported after the fact. A director reviewing a plan to add 3 engineers and 2 account executives next quarter can ask about the underlying assumption, is the pipeline ready for those account executives, is the roadmap actually blocked on engineering capacity, before the offers go out, not after.

Open roles and time-to-fill are worth a line if hiring has been a bottleneck; if hiring has not been a constraint, this section can stay short. The test for every line on this page is the same as everywhere else in the pack: does this change what the board would decide, or is it detail that belongs in an internal ops review instead.

The narrative page, usually one page, sometimes two, is where numbers turn into judgment. It should cover three things plainly: what went well this period, what did not, and what the board is specifically being asked to weigh in on or approve.

This is the section directors most often say they actually read closely, because it is where a founder demonstrates whether they understand their own business or are just reporting numbers someone else prepared. A risk section that only ever says "no major risks to report" for six straight quarters reads as either genuinely low-risk or, more often, as a founder who is not looking hard enough or is uncomfortable naming problems to their own board; either read is worse than naming a real, smaller risk honestly.

Good risk items are specific and time-bound: "our largest customer, 18% of ARR, is up for renewal in Q2 and has flagged pricing as a concern" is useful; "competitive pressure" alone is not. Good asks are specific too: "approve the $180K annual contract with [vendor]" or "input on whether to raise a bridge or extend runway through cuts" gives the board something concrete to act on, rather than a vague request for feedback.

This page is also where a founder should name a decision they already made and why, not just decisions still pending. Boards generally react better to "we decided X, here is why, flag it if you disagree" than to every operating decision being escalated as an open question, which slows the company down without actually improving the decision.

A practical, reusable outline that most early-stage companies can build from month one and keep through a Series B without a major redesign:

• Page 1: Cover and agenda. Meeting date, prior action items and their status, agenda for the meeting itself.
• Page 2: Executive summary / narrative memo. The one-page wins, risks, and asks section, written last, read first.
• Page 3: Financial summary. P&L and balance sheet, current month and YTD, against budget.
• Page 4: Cash and runway. Current cash, burn rate (gross and net), runway, and a forward cash view.
• Page 5: KPI dashboard. The 4 to 8 metrics that matter for this business model, trended over the last 6 to 12 months.
• Page 6: Headcount and hiring plan. Current headcount by department, planned hires, payroll impact.
• Page 7 (as needed): Fundraising or strategic update. Only when a raise, acquisition conversation, or major strategic decision is live.
• Appendix: supporting detail. Full P&L by account, cap table snapshot, customer concentration, anything a specific director is likely to probe.

Keep the core (pages 2 through 6) at 6 pages or fewer for a monthly pack; a quarterly board pack for a later-stage company can run longer because the meeting itself runs longer. The appendix can grow without limit since it is reference material, not required reading, but it should stay clearly separated from the pages the board is expected to read before the meeting starts.

The pack is only as good as how fast the underlying books close. A company that closes its books 15 or 20 business days after month end is sending board numbers that are already stale by the time anyone reads them, especially the cash and runway page.

A workable target for most venture-backed companies with a headcount under 50: books substantially closed within 5 to 10 business days of month end (reconciled bank and card accounts, invoices entered, accruals for anything material), board pack drafted within 2 to 3 days after that, and sent to the board 3 to 5 business days before the meeting itself.

Sending the pack the morning of the meeting, or worse, in the meeting, defeats the point of having one. Directors who receive a dense financial package minutes before a call either skim it during the meeting, which produces shallow questions, or ask to push real discussion to a follow-up, which slows the company down. A pack sent with a real review window lets directors come to the meeting with informed questions already in hand, which is the entire reason to build one in the first place.

Once the cadence is set, keep it. A board that can predict when the pack arrives and what it will contain spends less time each cycle re-orienting and more time on the parts that actually need judgment.

A handful of patterns show up repeatedly in board packs that do not land well, across company stage and sector:

• Changing the KPI list every quarter. Even switching to genuinely better metrics costs trend continuity; do it rarely and flag it clearly when it happens.
• Burying the narrative memo at the back. The wins-risks-asks page should lead the pack, not close it, since it is what most directors read first regardless of page order.
• Reporting cash-basis numbers without saying so. A cash-basis P&L that looks worse or better than the accrual reality, with no note explaining the basis, invites a director to draw the wrong conclusion.
• No variance commentary. A number next to a budget column with no explanation for a 20% miss makes the board do the analysis the finance function should have already done.
• Treating the appendix as optional prep. An appendix built the night before, after the core pages are done, is usually where the actual answer to a hard director question is missing when it matters.
• No prior-period comparison. A single month's snapshot with nothing to compare it against tells a director less than the same number next to last month and last year.

Each of these is a formatting and discipline problem, not a resourcing one; fixing them costs an afternoon of template work, not new headcount.