How to Prepare Board Reporting Packs

Board reporting is the discipline of giving directors the information they need to oversee the company, in a form they can absorb before the meeting and use in the room. It is a core part of business analytics for finance and operations. Directors typically meet for a few hours a quarter and have other commitments, so a pack that is late, long, inconsistent or buried in detail wastes their limited time and weakens governance. The finance leader is often the author of the pack, and the quality of the pack shapes the board's view of both the business and the management team. This guide explains how to prepare board reporting packs: what to include, how to schedule the work, how to explain the numbers to people who are not in the business every day, how to present covenants and risk with a worked headroom calculation and checked arithmetic and how to review the pack before it goes out. It follows the management reporting package and the monthly management report template, and leads to the financial reporting automation checklist and data warehouses for finance teams. Board numbers must reconcile to the plan in budgeting and forecasting.

What the board needs

Boards have three jobs: to oversee strategy, to oversee performance and risk and to ensure that management is accountable. The pack should therefore answer: Are we on track against the plan and the strategy? What are the main risks, and how are they being managed? Do we have the cash and covenants to carry out the plan? What decisions do you need from us? Directors rarely need transaction-level detail. They need a clear picture, trends, explanations of the large movements and early warning of problems.

Recommended contents

1. Cover note or CEO and CFO letter (one page). The headline message, the main developments, what changed since the last meeting and the decisions requested.
2. Agenda and decision items. Each item stating whether it is for information, discussion or decision, and the recommendation.
3. Financial summary. Income statement against budget, prior year and forecast, for the quarter and year to date; a short bridge from budget to actual profit; balance sheet summary.
4. Cash, liquidity and covenants. Cash balance, rolling cash forecast, debt facilities, covenant calculations and headroom.
5. KPI dashboard. Eight to twelve measures with trend, target and status, consistent from quarter to quarter.
6. Full-year outlook. Latest forecast versus budget, the key assumptions, upside and downside scenarios.
7. Strategic initiatives. Status of major projects, with milestones, spend against budget and benefits delivered.
8. Risks. The top five to ten risks, rated for likelihood and impact, with changes since the last meeting and mitigations.
9. Operational highlights. Customers, products, people and operations, in brief.
10. Appendices. Detailed schedules, minutes of the previous meeting, policy approvals, reconciliations and definitions.

Put the decisions first and the supporting information after. Keep the main body to a length that directors can read in an hour, with the rest in appendices.

A worked example: covenant headroom

Lenders often set covenants, such as a maximum ratio of net debt to EBITDA. The board needs to know not just whether the company complies, but how close it is. Suppose net debt is $4.5 million, trailing twelve-month EBITDA is $1.9 million and the covenant requires net debt to EBITDA of no more than 3.0 times (hypothetical).

• Current ratio: 4.5 / 1.9 = 2.37 times
• EBITDA needed to stay at 3.0 times with the same debt: 4.5 / 3.0 = $1.5 million
• EBITDA headroom: 1.9 - 1.5 = $0.4 million, which is 0.4 / 1.9 = 21 percent of current EBITDA
• Debt headroom at current EBITDA: 3.0 × 1.9 = $5.7 million allowed, so net debt could rise by 5.7 - 4.5 = $1.2 million

Check: 4.5 / 1.9 = 2.368; 4.5 / 3.0 = 1.5; (1.9 - 1.5) / 1.9 = 0.2105. The board should see this as a one-line statement: "We are at 2.37 times against a 3.0 times covenant; EBITDA can fall about 21 percent, or net debt rise $1.2 million, before a breach." Add a forward view: if the downside scenario reduces EBITDA by 15 percent to $1.615 million, the ratio is 4.5 / 1.615 = 2.79 times, still compliant but with less than a quarter of a turn of room. If the planned acquisition adds $2.0 million of debt without adding EBITDA, the ratio becomes 6.5 / 1.9 = 3.42 times, a breach. These are the numbers directors need when they approve a strategy.

Writing for non-executives

Directors are intelligent but busy and not close to day-to-day operations. Write for them.

• Define terms the first time, or use plain words.
• Lead with the conclusion, then the support.
• Explain movements, not only levels. "Gross margin fell 0.8 points because of mix toward lower-margin products" is useful. "Gross margin was 38.2 percent" is not.
• Be candid about bad news. Directors dislike surprises more than problems. Show what you are doing about issues.
• Be consistent. Use the same measures and layout each quarter, so that trends are visible. Where definitions change, say so and restate.
• Show ranges and uncertainty for forecasts.
• Separate facts from judgments.
• Avoid jargon and acronyms.

Timeline

Work back from the meeting date.

Agree the cut-off date for data with the board, and tell directors if figures are preliminary.

Consistency with other reports

The numbers in the board pack should tie to the management accounts, to the figures given to lenders and to any public or statutory reports. Build a reconciliation, and include a note of known differences, for example due to timing or accounting basis. A director who spots two different profit figures in the same pack will question everything else. Maintain a master list of key figures for the period, and draw all documents from it. See single source of truth.

Presenting risk

A risk page should be a living document, not a list copied from last year. For each major risk, show the description, the likelihood and impact rating, the trend since last time (up, down or stable), the owner, the mitigation in place and planned, and an early-warning indicator. Add new risks and remove those that have passed. Quantify where possible: "Loss of our largest customer, 14 percent of revenue, would reduce annual gross profit by about $1.1 million." Link the risk list to the scenarios in the forecast.

Final review checklist

1. Does the first page state the message and the decisions needed?
2. Do all numbers reconcile to the books and to each other?
3. Are definitions and layouts consistent with previous packs?
4. Is every variance explained, and every red KPI accompanied by an action?
5. Is the covenant position stated, with headroom?
6. Are forecasts labeled with their basis and date?
7. Are the risks current?
8. Is it free of typos and unexplained acronyms?
9. Has someone not involved in the preparation read it, and understood the message?
10. Is the length reasonable, with detail in appendices?

Common mistakes

1. Sending the pack late.
2. Too much detail in the main body.
3. Inconsistent numbers.
4. Burying bad news.
5. No clear decision requests.
6. Changing the format every quarter.
7. Forecasts with no stated assumptions.
8. Treating the pack as a data dump rather than a communication.

Scenarios in the board pack

Boards want to know how the plan behaves if things go differently. Present three cases rather than a single forecast: base, downside and upside, with the assumptions behind each. Using the covenant example above, suppose base EBITDA is $1.9 million, the downside is 15 percent lower and the upside is 10 percent higher. The downside EBITDA is 1.9 × 0.85 = $1.615 million, and net debt to EBITDA would be 4.5 / 1.615 = 2.79 times. The upside EBITDA is 1.9 × 1.10 = $2.09 million, and the ratio would be 4.5 / 2.09 = 2.15 times. The range of 2.15 to 2.79 times, against the 3.0 times covenant, tells the board that the company stays within its covenant in all three cases but has little room in the downside. Add what management would do in the downside, such as deferring capital spending or delaying hiring. Scenarios help directors discuss risk concretely.

Handling questions

Anticipate the questions directors will ask, and prepare short answers. Hold a pre-meeting with the chair or the audit committee chair if needed to flag sensitive items. Keep a log of questions raised in the meeting and answers promised, and circulate it with the minutes. If a director asks for information you do not have, say so and give a date. Do not guess in the room.

Confidentiality and security

Board packs contain sensitive information about performance, strategy, people and sometimes pending transactions. Use a secure board portal or encrypted distribution. Control who receives each section: some items are for directors only. Number the copies if printing. Set a retention rule for drafts and old packs, consistent with your legal advice. Remind directors not to forward the pack, and keep an audit trail of distribution.

FAQs

What should be in a board reporting pack?

A cover letter, agenda and decision items, financial summary, cash and covenant position, KPI dashboard, outlook, strategic initiatives, risks and appendices.

How long should a board pack be?

Short enough for directors to read the main body in about an hour, with supporting detail in appendices.

When should the board pack be sent?

Typically several days before the meeting, according to the board's rules. Agree the date with the chair.

How do I present bad news to the board?

Early, plainly and with the facts, the cause and the plan. Directors value candor and dislike surprises.

How do I make sure numbers are consistent?

Draw them all from one reconciled set of figures, and cross-check the pack against the management accounts and lender reports.