The Monthly Management Pack: One Set of Numbers the Board Can Trust
Most board packs are assembled by hand in the four days before the meeting, from numbers that took three people a week to reconcile. What belongs in a monthly pack, why one certified definition beats four accurate spreadsheets, and how to get the assembly down to an hour.
The week before a board meeting has a recognisable shape in most Kenyan organizations. Somebody pulls figures out of the accounting system, somebody else compiles operational numbers from a different place, the two do not agree, a day goes into establishing which is right, and the pack goes out the night before with a slide explaining a variance that turned out to be a definition difference.
The board then spends the first twenty minutes of the meeting on that discrepancy instead of on the business. This happens monthly, everywhere, and it is not a competence problem. It is what you get when the same question has several answers and none of them is authoritative.
One definition, certified, boring
The fix is unglamorous: for each number in the pack, one saved definition that everybody uses, agreed once and then left alone. Not a spreadsheet that gets re-derived monthly — a definition with a name, an owner and a status that says it has been reviewed and is fit to be quoted.
Report definitions in AWRA OpsHub carry an owner, a description, a visibility setting and a certification status with a named certification owner and notes. That combination is what turns a report from something somebody built into something the organization stands behind. When a director asks "is this the same revenue figure we used in March", the answer is a status on the definition rather than a recollection.
Certification is a governance act, not a feature
Marking a definition certified means somebody senior has read what it actually computes and agreed that it is the organization's answer to that question. Doing that for eight numbers takes an afternoon, once. Not doing it means every month contains a small argument about which figure is the real one.
What belongs in the pack
Board packs suffer from generosity. Everything anybody has ever asked for accumulates, the pack reaches forty pages, and directors read the first three and the last one. A useful pack is short and each page earns its place by supporting a decision the board actually makes.
| Section | The question it answers | The trap |
|---|---|---|
| Cash position and short-term forecast | Can we meet obligations for the next 8–12 weeks? | Reporting the bank balance instead of the position after committed payments |
| Revenue against plan | Are we selling what we said we would? | Changing the definition of revenue between months without saying so |
| Receivables ageing | How much of our reported revenue is still a promise? | A total with no ageing bands, which hides the part that will not arrive |
| Payables and commitments | What have we already agreed to spend? | Showing invoices only, so open purchase orders are invisible |
| Gross margin by line or segment | Where does the money actually come from? | A blended figure that describes nothing you sell |
| Two or three operational measures | Is the engine healthy? | Twenty measures, which is the same as none |
| Exceptions and decisions requested | What do you need us to decide? | Leaving this out, which turns a board into an audience |
The last row is the one most packs omit and the one that determines whether the meeting is useful. A pack that ends with three specific decisions requested — with the options and a recommendation — produces a different meeting from one that ends with a summary.
A pack that ends with three specific decisions and a recommendation produces a board meeting. A pack that ends with a summary produces an audience.
The same number in two places
When the finance report and the operations report disagree, the cause is almost never an error. It is that they were asked slightly different questions and both answered correctly.
-
Date basis
Invoice date, delivery date or payment date. A month's revenue can legitimately differ by a large margin depending on which one is used, and the difference is largest in exactly the months you most want to explain.
-
Inclusion of tax
Gross or net of VAT. Obvious once said, and responsible for an enormous share of "why do these not match" conversations.
-
Treatment of returns and credit notes
Deducted in the month of the original sale or the month of the credit. Both defensible; only one can be yours.
-
Scope
All branches, or trading branches only. Including or excluding intercompany. The scope is usually implicit in whoever built the report, which is why it changes when they leave.
Write these four choices down in the definition's description. That single paragraph, attached to the report rather than living in the analyst's head, prevents more board-meeting confusion than any dashboard.
Assembly, and getting it down to an hour
Once definitions are stable, the pack becomes a distribution problem rather than an analysis problem. Reports can be scheduled with a cadence, a set of formats and a recipient list built from email addresses, named users or roles — so the underlying figures land in the right inboxes before anybody starts writing commentary.
Where the four days actually go
Illustrative but recognisable. Certified definitions and scheduled delivery remove most of the first two lines, which is where nearly two-thirds of the effort sits. What they cannot remove is the commentary — and that is the part worth having more time for.
One caution on automation: a pack that assembles itself and is never read is worse than a manual one, because the manual assembly at least forced somebody to look at the numbers. Keep a person between the report and the board, and let their time go into interpretation rather than extraction.
What we do and do not do
What AWRA OpsHub does today
- Saved report definitions with an owner, description, visibility and dataset, so a number has one agreed source.
- A certification status with a named certification owner and notes, so "is this the official figure" has an answer on the record.
- Scheduled delivery with cadence, formats and recipients specified as addresses, users or roles.
- Exports in multiple formats, recorded with the actor, the format and the run behind them.
- Dashboard pins, so the small number of standing figures live in one place between meetings.
- Report runs retained, so the version of a number issued last month can be revisited.
What it does not do
- No board pack document assembly. Nothing compiles reports, commentary and cover pages into a single formatted document — you assemble the pack.
- No narrative or commentary generation. The interpretation is yours, which is the part the board is paying for anyway.
- No statutory financial statements. Management reporting and a signed set of accounts are different products; the second belongs to your accountant.
- No consolidation with eliminations across entities. Group-level statutory consolidation is an accounting exercise, not a report definition.
The first line disappoints people, so plan for it: the realistic target is that every number in the pack arrives correct and on time without manual extraction, and a person spends their saved days writing what the numbers mean.
Making it stick
- Agree the pack contents with the board once, in writing, and resist additions unless something is removed.
- Certify each definition, and record the four definitional choices — date basis, tax, returns, scope — in its description.
- Schedule the underlying reports to arrive a week before the meeting, not the night before.
- Keep last month's figures beside this month's. A number without a comparison is decoration.
- End every pack with the decisions requested. If there are none, the pack could have been an email.
Our take
Certify eight definitions in one afternoon, write the date basis and scope into each description, and schedule them to land a week before the meeting. That removes roughly two-thirds of the assembly effort and the entire opening argument about which number is right — leaving the person who writes the pack free to do the only part that was ever worth their time.
See Reports & BI Studio
Saved definitions with owners and certification, scheduled delivery to users and roles, exports in multiple formats and dashboard pins for the standing figures.
Explore reportingFrequently asked questions
Why do our finance and operations reports disagree?
Almost always because they answer slightly different questions, not because one is wrong. The usual four culprits are date basis (invoice, delivery or payment), whether figures are gross or net of tax, how returns and credit notes are dated, and scope — which branches or entities are included. Write those four choices into the report definition's description and the disagreement stops recurring, because the difference becomes visible instead of mysterious.
What does certifying a report actually do?
It records that a named person has reviewed what the definition computes and agreed it is the organization's answer to that question, with notes explaining any judgement involved. It changes nothing technically and a great deal organizationally: "is this the same revenue figure we used in March" becomes a status on the record rather than an argument. Certifying the eight numbers in your management pack takes an afternoon once.
Can the system produce the board pack itself?
No — there is no document assembly that combines reports, commentary and cover pages into a formatted pack. What it removes is the extraction and reconciliation work: certified definitions delivered on a schedule to the right recipients in the formats you need. The assembly and the commentary stay with a person, which is the correct division of labour, since the commentary is the part the board is actually paying for.
How long should a board pack be?
Short enough to be read in full. Cash position, revenue against plan, receivables ageing, payables and commitments, margin by line, two or three operational measures, and the decisions you are asking for. Everything else is an appendix. Packs grow because nobody ever removes anything — the discipline is agreeing the contents once and requiring that an addition displaces something.
Should the pack be automated end to end?
The extraction, yes. The reading, no. A pack that assembles and distributes itself with nobody looking at the numbers is worse than a manual one, because the manual version at least forced somebody to notice the anomaly before the board did. Automate to the point where a person receives correct figures early enough to think about them, and stop there.
