A board report that gets read is short, opens with a one-page summary, puts the same handful of numbers in the same place every month, and gives every number a source the board could check if they wanted to. Six to ten pages is the right length for most UK SMEs. The template below is the one I'd start from, and the second half of this post is about the more interesting problem: making the pack build itself so the finance team gets their week back.
The nice thing about board reporting is that the board already knows what it wants. It wants to know whether the business is on plan, what's changed since last time, what's coming that needs a decision, and whether anything is quietly going wrong. A good pack answers those four questions in that order and then stops.
What should a board report contain?
Here's the structure, with what each section is for and where the numbers usually come from. Treat the page counts as a ceiling, not a target.
| Section | The question it answers | Pages | Usual source |
|---|---|---|---|
| Summary | Are we on plan, and what needs a decision today? | 1 | Written by the MD or FD, numbers pulled from the sections below |
| Financials | Revenue, gross margin, overheads, EBITDA, cash: actual vs budget vs last year | 2 | Accounting system (Xero, Sage, QuickBooks, Business Central) |
| Cash and forecast | Where cash is now and where it lands in 13 weeks | 1 | Bank plus the cash flow forecast |
| Sales and pipeline | Orders, bookings, pipeline coverage, top customers | 1 | CRM and the sales ledger |
| Operations | Delivery, service, stock, utilisation, whichever two or three numbers describe the engine | 1 | Operational systems, sometimes spreadsheets |
| People | Headcount, vacancies, leavers, anything the board would want to know before it becomes a surprise | 0.5 | HR system or payroll |
| Risks and decisions | The two or three things that need the board, with a recommendation | 1 | Written |
| Appendix | Full P&L, balance sheet, anything a director might dig into | As needed | Accounting system |
Three habits make this template work rather than just exist.
Same numbers, same place, every month. The value of a board pack compounds when directors can find the gross margin without hunting for it. If the layout changes every month, every meeting starts with orientation instead of discussion. Fix the layout and let the numbers do the talking.
Actual, budget, last year, on every financial line. A number on its own is trivia. A number next to what you expected and what happened last year is information. The variance column is where the conversation lives, so give it room.
One page the chair can read in five minutes. Some directors will read the whole pack. Most will read page one carefully and skim the rest, and that's fine, that's what page one is for. Write it last, once the numbers are in, and write it as sentences, not bullet points: "Revenue was 4% ahead of budget, driven by two large orders in the Midlands region; margin held; cash is £40k lower than forecast because of a delayed customer payment that landed on the 3rd."
How long should a board report be?
Six to ten pages for the main pack. The appendix can be as long as it needs to be, because nobody is expected to read it cover to cover; it exists so a director can go and look.
The instinct is always to add. A director asks a good question, and the answer becomes a permanent page. Twelve months later the pack is 40 pages and the summary has been pushed to page three. A good discipline is a yearly cull: anything that hasn't prompted a question or a decision in six months moves to the appendix, and if nobody notices, it goes.
What makes the numbers trustworthy?
Every number in the pack should be traceable to a system without a human in between. That's the whole test. If revenue on page two comes from the accounting system, and the board asks why it differs from the sales figure on page four, you want the answer to be "different definition, here's both" rather than "somebody copied it across on Tuesday".
This matters more than layout, more than charts, more than anything. I've written before about how six reports end up with six different numbers and the pattern in board packs is the same: the moment a number is retyped, it stops being a fact and starts being an opinion about a fact.
Practical version: keep a one-line note against each section saying where the figures come from and who owns them. When the pack becomes automated (next section), that note becomes the data model, but even in a spreadsheet it's worth writing down.
How do you stop rebuilding the board report every month?
Most board packs are rebuilt by hand. Somebody exports from the accounts system, pastes into the master workbook, fixes the rows that came out wrong, updates the charts, writes the commentary, and turns it into a PDF. Two or three days a month, often from the most expensive person in finance, and it lands the night before the meeting because it can't land earlier.
The better version separates the two jobs the pack is doing. The numbers are a data job. The commentary is a thinking job. Automate the first so the second gets more time.
In Power BI, that looks like this. The accounting system, the CRM and whatever holds the operational numbers get connected once, modelled once, with the definitions of revenue, margin and pipeline written down in one place. The pack becomes a set of report pages laid out exactly like the template above. Scheduled refresh runs overnight, so on the first working day of the month the financial pages are already right. Whoever writes the summary opens the pack, reads what happened, and writes about it, instead of building it.
A few things worth knowing about that setup:
- The pack can still be a PDF. Power BI will export a page set to PDF, or email a subscription every month at a set time. Directors who like paper still get paper. The difference is that the paper came from a system.
- Budget lives in the model too. Budget and forecast are just another table. Once they're in, the actual vs budget vs last year columns are automatic, on every line, every month.
- The commentary stays human. Nobody wants a board summary written by a formula. The point is to give the person writing it a finished set of numbers on day one rather than day four.
- Licensing is modest. Microsoft's published UK price for Power BI Pro is £10.80 per user per month as of September 2026, paid yearly. A board of five plus a finance team of three is under £90 a month.
This is the kind of build I do as a fixed-price Reporting Sprint: up to three source systems modelled into one system, eight report pages, a reconciliation pack that proves the numbers match the source, and a runbook so your own team owns it afterwards. Board packs are a common shape for it, precisely because the pack already has a fixed structure and a monthly rhythm, which is what automation likes.
What should the summary page say?
The summary page is the only page that has to be written fresh each month, so it deserves a shape of its own. Mine has four paragraphs:
- Performance. Two or three sentences on revenue, margin and cash against plan. Numbers in the sentences, not in a separate table.
- What changed. The one or two things that explain the variances. A big order, a lost customer, a price increase that landed, a hire that didn't.
- What's coming. The next quarter in three sentences. Pipeline, known risks, anything seasonal.
- Decisions needed. Numbered, with a recommendation each. If there are none this month, say so in one line; an empty decisions section is good news, not a gap.
Written this way, the summary takes an hour, and a director who reads only that page can still contribute to every discussion in the meeting.
Common questions
What is a board report?
A board report (or board pack) is the set of documents sent to a company's directors before a board meeting. For an SME it usually combines the month's financial results, cash position, sales and operational performance, a short summary from the MD or FD, and any decisions the board is being asked to make. It's the evidence base for the meeting, circulated in advance so the meeting itself can be about discussion rather than reading.
How far in advance should the board pack be sent?
A week before the meeting is the standard most boards aim for, and three working days is the practical minimum. Directors need time to read it and come with questions. If the pack routinely lands the night before, that is almost always a data-preparation bottleneck, not a writing one, and it's the strongest sign that the numbers part of the pack should be automated.
Should the board report include a full P&L and balance sheet?
Yes, but in the appendix. The main pack should carry the headline financials with variance columns; the full statements sit behind them for directors who want to dig in. Putting the full P&L on page two buries the story in the detail.
Can the board report be a Power BI report rather than a PDF?
It can be both. Power BI can publish the pack as interactive pages for directors who want to click into a number, and export or email the same pages as a PDF on a schedule for those who prefer to read. Most boards I've seen settle on the PDF as the formal record and the live version for anyone who wants to explore between meetings.
How much does it cost to automate a board pack?
It depends on how many systems feed it and how clean their data is. As a guide, my fixed-price Reporting Sprint at £9,500 covers up to three sources modelled into one system with eight report pages, which is more than a board pack needs. A pack fed by one accounting system and a budget spreadsheet is a smaller job. The cost guide has the wider range of prices for this kind of work in the UK.
What KPIs should be in a board report?
The ones that describe whether the business is on plan: revenue, gross margin, overheads, EBITDA and cash for nearly every business, then two or three operational numbers specific to yours (utilisation for a services firm, stock turn for a distributor, occupancy for a venue). Ten to fifteen numbers is plenty. If the board can't hold them in their head, there are too many.
How do you keep the board report consistent month to month?
Fix the layout and the definitions and change them deliberately, not by accident. A written definition for each number (what counts as revenue, when an order becomes a sale) stops the figures drifting when a different person prepares the pack. Once the pack is automated those definitions live in the data model, which is the most reliable way of all to keep them consistent.