Most companies above a certain size produce a monthly management reporting pack. Far fewer produce one that gets read. The failure mode is always the same: the pack grows page by page, quarter by quarter — a new table here, a requested breakdown there — until one day it's forty pages long, three weeks late, and the leadership team has quietly gone back to steering by bank balance and gut feeling.
The uncomfortable truth: a reporting pack that isn't read isn't a reporting problem. It's a design problem. The information is usually all there — buried.
This guide covers what actually belongs in a monthly pack, what should be cut, and the structural rules that separate a pack that drives decisions from a pack that gets filed.
In short: an effective management reporting pack runs 10–25 pages with an executive summary readable in five minutes or less, follows a fixed structure — summary first, performance second, risks last — and tracks five to ten KPIs, not thirty. It contains a financial core (profit and loss, balance sheet, cash flow), variance commentary that explains the gap rather than restating the table, and a forward-looking cash view. And it arrives by working day five of the month — a pack delivered in week three is describing history, not informing decisions.
Why most management reporting packs get skimmed, not read
When a pack buries key updates inside long paragraphs and scattered tables, readers skim — or miss the decision entirely. Research on board and management reporting consistently points to the same pattern in packs that actually get used: summary first, performance second, risks last. The reader gets the headline before the evidence, and the evidence before the caveats. Packs that fail usually invert this — thirty pages of evidence, with the headline left as an exercise for the reader.
A reporting pack has one job: to answer the leadership team's questions before the meeting starts. What changed? Is it a one-off? What does it mean for cash?
The one rule: a reporting pack is for decisions, not documentation
Every element in the pack should survive a single test: does this change what someone does this month? If a table exists because someone asked for it once in 2023, it goes. If a breakdown exists to prove the finance team did the work, it goes — the work is the foundation, not the content. What remains is the material a managing director actually acts on: performance against plan, the reasons behind the gaps, and what's coming at the business next.
The executive summary: five minutes, one page
The executive summary is the most important page in the pack — and the hardest to write, because it forces choices. The benchmark: readable in five minutes or less, ideally a single page a reader can scan top to bottom. It states what happened, why, and what management should focus on next — in sentences, not bullet-point fragments that outsource the interpretation to the reader. If the leadership team reads only this page, they should still walk into the month informed.
The financial core: profit and loss, balance sheet, cash flow
The non-negotiable backbone of any pack is the standard financial trio: a profit and loss statement against budget and prior year, a balance sheet, and a cash flow statement. This is deliberately boring — and that's the point. The financial core establishes trust through consistency: same format, same definitions, every single month. Readers who trust the core will engage with the commentary; readers who catch the core changing shape every quarter will trust none of it.
Variance analysis: explain the gap, not the table
Variance analysis is where most packs waste the most space. A table showing budget, actual and variance is data, not analysis — the reader can subtract. What earns its place is the sentence underneath: "Marketing is 12% over budget, driven by a one-off trade fair cost; the run-rate is on plan." One-off or structural, timing or trend — that's the analysis. A useful discipline: every variance above a defined threshold gets exactly one to three sentences of commentary. Below the threshold, silence. Selectivity is what makes the commentary readable.
KPIs: five to ten, not thirty
The research here is blunt: a leadership team staring at thirty KPIs isn't governing — it's auditing. The discipline of choosing five to ten metrics is the core of the exercise, because choosing them forces the question "what actually drives this business?" For most companies that's some mix of revenue momentum, margin, cash runway or conversion, and one or two operational drivers specific to the model. Everything else belongs in an operational dashboard someone owns — not in front of the leadership team every month. (How each KPI is defined matters as much as which ones you pick — definitions that shift between reports destroy credibility faster than bad numbers do.)
The cash flow view managing directors actually need
The statutory cash flow statement looks backward. What managing directors need alongside it is the forward view: where cash stands today, and where it will be in the coming weeks — ideally lifted directly from a rolling 13-week forecast. A pack that reports last month's cash movements but stays silent on next month's position answers the accountant's question and skips the managing director's one.
Monthly reporting cadence: day five, every month, same structure
Monthly reporting lives or dies on timing and consistency. The benchmark delivery is working day five — a pack that lands in week three describes history too old to act on, and the leadership meeting ends up run on ad-hoc numbers instead. Just as important: the structure doesn't change month to month. Same sections, same order, same definitions. The reader should know where everything is before opening the file — novelty in a reporting pack is a cost, not a feature.
What a working pack looks like
| Section | Question it answers | Length |
|---|---|---|
| Executive summary | What happened, why, what to focus on | 1 page, ≤5 minutes |
| KPI dashboard | Are the drivers of the business on track? | 1 page, 5–10 metrics |
| Profit and loss vs budget | Where are we against plan? | 1–2 pages |
| Variance commentary | Which gaps matter, and are they one-offs? | 1 page, threshold-based |
| Balance sheet | Is the financial position sound? | 1 page |
| Cash: actual + forward view | Where is cash now — and in 13 weeks? | 1–2 pages |
| Risks and outlook | What's coming that management should see early? | 1 page |
Total: roughly 8–10 pages for most small and mid-sized companies — comfortably inside the 10–25 page range the research supports, and far from the forty-page packs that stop being read. Appendices exist for anyone who wants the detail; the pack itself is the argument, not the archive.
Where an interim controller fits in
Designing a pack is a one-time exercise; producing it reliably by day five every month is a process. That's interim controller territory on both ends: building the structure once — sections, thresholds, KPI definitions agreed with the leadership team — and then wiring the monthly production into the close so the pack falls out of the process instead of being assembled by hand under deadline pressure. It draws on the same disciplines covered across this blog: a close fast enough to deliver by day five, KPI definitions that hold up, and a rolling cash forecast feeding the forward view. Most companies don't need a permanent hire for this — they need the pack designed properly once, produced through a few cycles, and handed over.
Conclusion
A management reporting pack earns its existence one way: by being read. That takes a fixed structure with the summary first, a financial core that never changes shape, commentary that explains rather than restates, five to ten KPIs instead of thirty, a forward cash view — and delivery by day five, every month, without exception. Cut everything that doesn't change a decision. What's left is shorter, sharper, and — for the first time in a while — actually read.
Does your monthly pack drive the leadership meeting — or get politely filed?
Let's build one that gets read. Book a call → or get in touch directly.
Frequently asked questions (FAQ)
What should a monthly management reporting pack include?
An executive summary readable in five minutes, a KPI dashboard with five to ten metrics, profit and loss against budget, threshold-based variance commentary, a balance sheet, cash actuals plus a forward-looking cash view, and a short risks-and-outlook section — roughly 8–10 pages for most small and mid-sized companies.
How long should a management reporting pack be?
Effective packs typically run 10–25 pages, with the executive summary readable in five minutes or less. For most smaller companies, 8–10 pages is enough. Length beyond that usually signals documentation rather than decision support — and is the most common reason packs stop being read.
How many KPIs should management track monthly?
Five to ten. A leadership team reviewing thirty KPIs is auditing, not governing. Additional operational metrics belong in function-specific dashboards owned by the responsible manager, not in the monthly leadership pack.
When should the monthly reporting pack be delivered?
By working day five of the following month. A pack delivered in week three describes history too old to act on. Hitting day five reliably usually requires a fast, well-structured month-end close rather than more reporting effort.
What's the difference between variance data and variance analysis?
A budget-versus-actual table is data — the reader can subtract. Analysis is the sentence underneath: whether the gap is a one-off or structural, timing or trend, and what it means for the rest of the year. Commentary should be reserved for variances above a defined threshold.