Executive summary
A board reporting pack is the document set directors receive before a meeting so they can govern the company: approve decisions, challenge strategy, and check that management is on track. The board reporting pack template below is built around one idea. The pack exists to support decisions and oversight, so the first page should say what the board is being asked to do, and everything after that should be evidence in a fixed, predictable order.
The common failure is a pack assembled as a copy of the management report with a cover page added. Directors, who see the company for a few hours a quarter, receive forty pages written for an operator who lives in the detail. They skim, ask about whichever page they happened to read, and the meeting is spent on the wrong things.
This guide gives you a structure that works for a mid-market company with a board of directors, an investor board, or an advisory board: a decisions page, a one-page narrative, a capped scorecard, financials with a bridge, cash and covenant headroom, the forecast, risks, and an appendix. It includes a pre-read calendar, a page-level template, an illustrative scorecard with the arithmetic shown, and the mistakes that turn a pack into a reading assignment.
When to use this
Use this template when:
- You are building a board pack for the first time, for example after a financing, an acquisition or a new sponsor.
- Directors say the pack is too long, arrives too late, or does not tell them what you need from them.
- The board pack, the lender package and the management pack disagree on the same figures.
- You are moving from ad hoc updates to a regular quarterly or monthly board rhythm.
- Your sponsor or investors have given you a reporting template and you want to check that it answers the questions your directors actually ask.
If your governance documents (articles, shareholder agreement, credit agreement) specify what must be delivered and when, those documents govern. Treat this template as the layout for the content and confirm obligations with your counsel. For the monthly cycle that produces the numbers, see the management reporting playbook.
Diagnostic questions
Answer these about your current pack, or about the pack you are about to build.
- What decisions does the board need to make at the next meeting, and are they stated on page one?
- Which directors are operators and which are investors, and what does each need from the pack?
- How many days before the meeting does the pack arrive? Is that date written in your governance calendar?
- Does the narrative page stand alone, so a director who reads only that page knows the position?
- How many pages are information that nobody has asked a question about in the last three meetings?
- Does every material miss versus plan have a cause, persistence, and an action with an owner?
- Are the scorecard definitions written down, and do they stay the same from meeting to meeting?
- Does the pack show cash, liquidity and covenant headroom in the same place every time?
- Do the figures tie to the last management pack and to any lender package?
- Is the full-year outlook shown with a bridge from the last version?
- Where are the risks, and does each carry an owner and a mitigation?
- Who reviews the pack before it is released, and who answers director questions after?
A "no" to question 1 is the most expensive. A board that does not know what it is being asked tends to default to reviewing the past.
Framework: three jobs, three tiers
A board pack does three jobs, and each job belongs on a different part of the page order.
| Job |
Question it answers |
Where it lives |
| Decide |
What does management need the board to approve or advise on? |
Page 1: decisions |
| Oversee |
Are we on plan, and if not, why and what is being done? |
Narrative, scorecard, financials, forecast |
| Assure |
Are the numbers reliable, the cash safe and the risks owned? |
Cash and covenants, risks, appendix |
Use three tiers of detail so each director can stop where their need ends:
- Page one and the narrative. Everything a director must know, on two pages.
- Scorecard and summary financials. The evidence, on a few pages with consistent layout.
- Appendix. Detailed schedules and supporting analysis, referenced but not expected to be read.
The discipline is that tier one can be wrong only if tier two is wrong. The headline is built from the scorecard, the scorecard from the statements, and the statements from the closed ledger.
The board pack template, page by page
| Page |
Title |
Contents |
Owner |
| 1 |
Decisions and asks |
Each item: the decision, the options, management's recommendation, the deadline |
CEO |
| 2 |
Narrative |
Result versus plan, the two or three drivers, what is persisting, what is changing |
CFO |
| 3 |
Scorecard |
Capped KPI table: plan, actual, prior period, status, comment |
FP&A lead |
| 4 |
P&L and EBITDA bridge |
Actual versus plan and prior year; bridge from plan to actual |
FP&A lead |
| 5 |
Cash and liquidity |
Cash balance, 13-week outlook, covenant headroom |
Treasury / Controller |
| 6 |
Working capital |
Receivables aging, inventory, payables, cash conversion trend |
Controller |
| 7 |
Forecast |
Full-year outlook, bridge from last version, key assumptions |
FP&A lead |
| 8 |
Strategic initiatives |
Each initiative: milestone, status, next gate, owner |
CEO / initiative owners |
| 9 |
Risks and opportunities |
Top risks with owner, mitigation, trigger |
CEO |
| 10 |
Actions from last meeting |
Each action: status, owner, date |
Company secretary / CFO |
| Appendix |
Statements, schedules, definitions |
Detail referenced from the pages above |
Controller |
Adjust the order to your board's priorities but keep it fixed once set. A director who knows page 5 is always cash will find it in seconds.
Page 1: decisions and asks
List each decision as a row, not a paragraph.
| Item |
Type (approve / advise / note) |
Options |
Management recommendation |
Needed by |
|
|
|
|
|
Include only items that need the board. If an item is for information, put it in the narrative or the appendix. A board that sees six asks on page one understands the meeting's purpose before turning the page.
Page 2: the narrative
One page, in the structure from variance analysis narrative: writing the why:
- Result versus plan in one sentence with the number.
- The largest drivers, with size, cause and persistence.
- What changed in the outlook since the last meeting, and why.
- What management is doing about the unfavorable items, with owners.
Write it so a director who reads only this page can ask a good question.
Page 3: the scorecard
Cap it. For each metric show the definition, the plan, the actual, the prior period and a status. Choose the metrics by the decisions the board makes, not by what is available. The method is in KPI design: choosing 12 metrics that run the company. If the board sees different metrics from the management team, explain why in one line.
Page 5: cash and covenant headroom
Directors carry risk for solvency and covenant breaches. Show:
- Opening cash, closing cash, and the main flows between them.
- Liquidity (cash plus undrawn committed availability, as defined in your credit agreement).
- The 13-week outlook and its low point. See the 13-week cash flow forecast template.
- Each financial covenant: definition as written in the agreement, current calculation, threshold, headroom. See covenant compliance and headroom tracking.
Covenant definitions are contractual. Use the definitions in your own agreements, have your lender documents reviewed by counsel or your adviser, and do not paraphrase them in the pack in a way that changes their meaning.
Page 9: risks and opportunities
| Risk |
Likelihood (H / M / L) |
Impact ($ or metric) |
Early signal |
Mitigation |
Owner |
Last reviewed |
|
|
|
|
|
|
|
Include opportunities as well.
Step-by-step: producing the pack
- Set the meeting date and the pre-read deadline at the start of the year for all meetings. Owner: CEO with the board chair. Output: governance calendar.
- Agree the agenda and the decisions list with the chair about three weeks before. Owner: CEO. Output: draft decisions page.
- Close the period and lock the numbers. Owner: Controller. Output: locked period.
- Run the variance register and the bridges. Owner: FP&A lead. Output: confirmed causes and persistence. See the management reporting playbook.
- Draft the narrative and page one. Owner: CFO and CEO. Output: two-page lead section.
- Assemble the scorecard, financials, cash and forecast pages. Owner: FP&A lead and Controller. Output: draft pack.
- Tie-out. Check every figure on pages one to seven against the locked ledger and against the management pack. Owner: Controller. Output: signed tie-out.
- CEO and CFO review. Challenge each sentence. Owner: CEO. Output: approved pack.
- Legal and confidentiality check. Confirm that distribution, privilege and any information-rights provisions are respected. Owner: General counsel or outside counsel. Output: cleared pack.
- Release through a secure channel by the pre-read deadline. Owner: Company secretary or CFO. Output: sent pack with a version stamp.
- Director questions before the meeting. Collect, answer in writing to all directors, and add recurring questions to the pack structure. Owner: CFO. Output: Q&A log.
- After the meeting, record decisions and actions within two working days. Owner: Company secretary. Output: updated action log.
Pre-read calendar
| Timing |
Step |
| Meeting minus 21 days |
Agenda and decisions list agreed with chair |
| Meeting minus 14 days |
Period closed and locked |
| Meeting minus 10 days |
Variance register and causes confirmed |
| Meeting minus 7 days |
Draft pack to CEO |
| Meeting minus 5 days |
Pack released to directors |
| Meeting plus 2 days |
Minutes drafts and action log issued |
These offsets are an example. Set yours from your governance documents, your close timing and what your directors have said they need. If the close finishes later than the schedule assumes, move the meeting or the period, do not release unreviewed numbers.
Worked example: a one-page scorecard
Illustrative. The figures are made up to show the layout and the arithmetic. They are not benchmarks.
A manufacturer's board scorecard for one month:
| Metric |
Plan |
Actual |
Variance |
Variance % |
Status |
| Revenue |
$4,000,000 |
$4,180,000 |
$180,000 |
4.5% |
Green |
| Gross margin % |
40.0% |
40.0% |
0.0 pts |
0.0% |
Green |
| EBITDA |
$500,000 |
$522,000 |
$22,000 |
4.4% |
Green |
| Operating expenses |
$1,100,000 |
$1,150,000 |
($50,000) |
(4.5%) |
Amber |
| Closing cash |
$1,500,000 |
$1,350,000 |
($150,000) |
(10.0%) |
Red |
Arithmetic: revenue variance is 4,180,000 minus 4,000,000 = 180,000, which is 180,000 ÷ 4,000,000 = 4.5%. Gross profit is $1,600,000 on plan and $1,672,000 actual, so gross margin is 1,600,000 ÷ 4,000,000 = 40.0% planned and 1,672,000 ÷ 4,180,000 = 40.0% actual. EBITDA is gross profit minus operating expenses: 1,600,000 minus 1,100,000 = 500,000 planned, and 1,672,000 minus 1,150,000 = 522,000 actual. Cash variance is 1,350,000 minus 1,500,000 = (150,000), or 150,000 ÷ 1,500,000 = 10.0% under plan.
Suppose the credit agreement sets a minimum liquidity covenant of $1,000,000 (an invented figure for this example only). With $1,350,000 of closing cash, headroom is 1,350,000 minus 1,000,000 = $350,000, or 350,000 ÷ 1,350,000 = 25.9% of the cash balance.
What the scorecard tells the board: the P&L is on plan and cash is not. A director reading the green EBITDA row without the red cash row would be misinformed. The narrative page has to explain the $150,000 cash gap (working capital, capital expenditure or financing timing) and the decision page has to say whether management wants anything from the board about it. The scorecard does not say why. That is the narrative's job, and the structure makes sure it is asked.
Status rules
Write the rules for status colors and apply them mechanically. For example, green is within the materiality rule, amber is outside it with a confirmed recovery plan, and red is outside it without one or a covenant or contractual consequence. The rule matters more than its thresholds. A status set by the author's mood is not information.
Metrics and KPIs for the pack itself
| Metric |
Formula |
Data source |
Target by method |
| Release lead time |
Meeting date minus pack release date |
Release log |
Governance document; otherwise the date directors say they need |
| Tie-out breaks |
Unexplained differences between pack and ledger |
Tie-out sheet |
Zero |
| Questions per pack |
Director questions received before the meeting |
Q&A log |
Trend downward as recurring questions move into the pack |
| Repeat questions |
Questions asked in more than one meeting |
Q&A log |
Zero; each repeat means a missing page |
| Action closure |
Actions closed by due date ÷ actions due |
Action log |
Your own trailing best |
Treat repeat questions as design feedback. If a director asks the same thing in three meetings, the pack lacks a page, or the page it has does not answer the question.
Common mistakes
- No decisions page. Without it the board defaults to commenting. Put asks first.
- Pasting the management pack. Directors need a smaller number of pages with the narrative on top, not the operating detail.
- Changing the layout every meeting. A fixed order lets directors build habits and lets you spot omissions.
- Hiding bad news in the appendix. A miss belongs on page two with an owner and a plan. Directors punish surprises more than they punish misses.
- Late release. A pack that arrives the night before is not read. If the numbers are not ready, say so and send the narrative with the status.
- Different numbers for different readers. A board pack that disagrees with the lender package invites a distraction you cannot afford. Build from one closed dataset. See lender reporting package.
- Treating covenants as a footnote. A covenant approaching its threshold is a board matter. Show headroom every time.
- Skipping the action log. The first item of every meeting should be last meeting's actions.
- Ignoring confidentiality and privilege. Pack contents may be sensitive, and some may be privileged or subject to specific information rights. Involve counsel on distribution.
AI prompt assistance
Supply the data yourself, and do not paste confidential board materials into tools your company has not approved. Check every output against the ledger and the governance documents.
1. Draft the decisions page.
Here are the five items management wants the board to consider, each with the options and our recommendation. Format them as a table with columns: item, type (approve, advise or note), options, management recommendation, needed by. Do not add options or reasons that are not in my notes. If an item is missing a deadline or a recommendation, list it as a gap.
Check: confirm every row against your own notes and flag the gaps to the CEO.
2. Anticipate director questions.
Here is the draft narrative and scorecard. Act as three directors: a PE investor, a lender representative and an independent operator. For each, list the five questions they are most likely to ask about this pack, and the pages where the answer is missing or weak.
Check: answer each question yourself from the data. Add the answers to the pack where more than one director would ask.
3. Reconcile pack figures.
I will paste the board pack scorecard and the last management pack. List every figure that appears in both, show whether they match, and list each mismatch with both values.
Check: resolve every mismatch at the source ledger, not in the prompt.
Implementation guide
| Phase |
Days |
Owner |
Exit criteria |
| Design |
1-30 |
CEO, CFO |
Page structure agreed with the chair; governance calendar set; scorecard metrics defined; decisions page format agreed |
| First pack |
31-60 |
CFO, FP&A lead |
One full pack produced to the calendar; tie-out signed; Q&A log started |
| Refine |
61-90 |
CEO, CFO |
Director feedback collected; repeat questions added to the structure; pack reconciles to management and lender packages |
In the first 30 days, ask the chair and each director one question: what would you want to be able to decide or check from this pack? Build the structure from the answers. In days 31 to 60, run the full process once even if the pack is imperfect, because the calendar problems appear only when you run it. In days 61 to 90, remove pages that drew no questions and add pages that drew repeated ones.
Governance: the CEO owns the content standard and the decisions page. The CFO owns the narrative and the numbers. The company secretary or equivalent owns distribution, minutes and the action log. Counsel advises on confidentiality, privilege and information rights.
Downloadable assets
The decisions table, page structure, risk register, pre-read calendar and scorecard layout above are designed to be copied into a document or spreadsheet. There is no calculator for this topic. For covenant headroom arithmetic, use the covenant headroom calculator.
Related resources
Frequently asked questions
What should be in a board reporting pack?
A board reporting pack should contain a decisions page, a one-page narrative, a capped KPI scorecard, a P&L with an EBITDA bridge, cash and covenant headroom, the full-year forecast, strategic initiatives, risks with owners, and an action log. Detailed schedules go in an appendix. Lead with what the board must decide.
How long should a board pack be?
A board pack should be as short as keeps the decisions and oversight intact, with the two lead pages readable on their own and the detail in an appendix. There is no correct page count. Use your own shortest past pack that did not generate repeat questions, and remove pages that drew no questions across several meetings.
How far ahead should the board pack be sent?
The pack should reach directors with enough time to read it and send questions, and the date should be set in your governance calendar. Your governing documents may specify a minimum notice period, so confirm with counsel. If the numbers are not final, send the narrative and status on time and note what is pending.
What is the difference between a board pack and a management report?
A management report serves operators running the business and carries operating detail. A board pack serves directors who decide and oversee, so it leads with decisions, a short narrative, and a capped scorecard. Both should tie to the same closed numbers, but the board version is a smaller, more selective view with decisions at the front.
Should the board pack include covenant compliance?
Yes, if the company has financial covenants, because directors are accountable for solvency and compliance. Show each covenant, its calculation, the threshold and the headroom, using the definitions in your credit agreement. Have your lender documents reviewed by counsel or an adviser, and do not paraphrase definitions in a way that changes their meaning.
How this works in a System of Performance
A board pack is only as good as the chain from decision to outcome behind it. In most companies the board's actions, the variance causes and the covenant calculations live in different files, so each meeting rebuilds context from memory. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. To see where your reporting chain is thinnest, bring it to us as a launch partner.