Board Reporting Pack Builder

Board Reporting Pack Builder

When to use

Use whenever monthly, quarterly, or annual financials need to become a board-ready pack, especially replacing a pack organized around accounting structure (a data dump following the chart of accounts) rather than around what the board actually needs to know and decide.

What it does

Structures the board pack around decisions and variance first, financial detail second: a KPI and headline summary, a variance-against-plan section that draws directly on variance-bridge-analyzer and margin-decomposition style findings, an outlook section, and only then the supporting financial statement detail — so a board member gets the answer in the first two pages and the supporting evidence after, rather than having to derive the answer themselves from a financial statement.

Method

1. Open with a KPI and headline summary, not the income statement. The three to five numbers that matter most this period, each with a one-line read (on track, ahead, behind, and why) — this is what a time-constrained board member reads first and sometimes only.
2. Lead the variance section with the story, not just the numbers. Pull from variance-bridge-analyzer (price/volume/mix) and margin-decomposition (mix/rate) findings if they exist, so the board gets the actual driver behind a miss or beat, not just the dollar amount.
3. Include a forward outlook section explicitly, not just a look backward — what the rolling forecast or scenario plan currently shows, and what, if anything, has changed since the last pack.
4. Flag anything requiring a board decision or awareness clearly, separated from routine reporting — a covenant headroom warning, a cash runway concern, a capital allocation decision — these shouldn't be buried in a financial statement footnote when they need explicit board attention.
5. Put the full financial statements (P&L, balance sheet, cash flow) after the narrative sections, as supporting detail for anyone who wants to verify the story, not as the pack's opening act.
6. Keep the narrative sections readable in the time a board actually has — most board members spend minutes, not hours, with the pack before the meeting; a narrative that takes fifteen minutes to read defeats its own purpose.
7. Keep the structure consistent period to period (the same discipline as recurring-report-builder), so board members build familiarity with where to find what, rather than re-learning the pack's layout every cycle.

Inputs

• Current period financials and KPIs
• Variance findings against plan (from variance-bridge-analyzer, margin-decomposition, or equivalent analysis)
• Current forecast or outlook
• Any items requiring explicit board decision or awareness (covenant status, cash position, capital allocation asks)

Output format

KPI and headline summary (3-5 metrics with one-line reads); variance narrative with named drivers; forward outlook section; explicit decision/awareness items called out separately; full financial statements as supporting detail after the narrative sections.

Example

A board pack that used to open with a 40-line income statement now opens with five headline KPIs (revenue on track, gross margin down 2pts driven by a mix shift toward a lower-margin segment, cash runway at 14 months, one covenant showing 12% headroom worth watching), followed by the detailed variance and financial statements for anyone who wants to dig in. A board member with five minutes before the meeting gets the actual state of the business; a board member who wants to verify it can still find every number behind the summary.

Common pitfalls

• Opening the pack with a full income statement instead of a KPI and headline summary, forcing every reader to derive the story themselves.
• Reporting variance as a dollar figure with no driver behind it, when that driver analysis likely already exists from variance-bridge-analyzer or margin-decomposition.
• Burying a genuine decision item (a covenant warning, a cash concern) inside routine financial detail instead of calling it out explicitly for board attention.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Natan-Mohart
• Source: Natan-Mohart/24-finance-skills-for-claude
• License: MIT

Install and usage instructions live in the source repository linked above.