The management pack that actually gets read.

There is a particular silence that happens about four minutes into a board meeting, when everybody is looking at page seven and nobody has a question. It is usually read as agreement. It is almost never agreement. It is a room full of people who cannot find, in twenty-two pages of accurate tables, the thing they are supposed to decide.

Why packs stop being read

A management pack is usually built by extension. Someone asks for a figure, it is added, and it is never removed. Over three or four years the document accretes until it is a complete description of the business and a useless guide to running it.

The underlying problem is that it was designed to report rather than to ask. Reporting is a compliance instinct: record what happened, accurately, in case someone queries it. Asking is a management instinct: here is what happened, here is what it means, here is what we should do, and here is the decision we need from you today.

Everything below follows from that distinction.

1. Lead with the decisions

Page one is not a profit and loss statement. Page one is a short list of the decisions the board is being asked to make this month, each with a recommendation attached and a note of what happens if it is deferred.

This feels presumptuous the first time it is done. It is not: a board that disagrees with a recommendation now has something specific to disagree with, which is a far more productive meeting than one where a group stares at a table hoping the issue will identify itself.

Three to five decisions is normal. If there are none, say so explicitly. “No decisions required this month” is genuinely useful information and takes one line.

2. Report forward, not only back

Actuals describe a month that is over. Nobody can influence it. The reason a monthly pack exists is to change what happens in the months that have not occurred yet, and most packs devote ninety per cent of their pages to the one that has.

A reasonable balance is roughly a third looking back and two thirds looking forward: the reforecast, the pipeline, the cash view, and the assumptions that have changed since last month. That last item is underrated. A forecast is a set of assumptions; when one of them changes, that is the news.

3. Explain variance in sentences, not columns

A variance column tells you a number differed from budget. It does not tell you whether that matters, whether it will persist, or whether anybody is doing anything about it. Those are the three things a reader actually wants, and all three fit in a sentence.

The useful form is consistent:

• What happened: gross margin was 2.4 points below budget.
• Why: two large orders shipped at agreed discounts negotiated in March.
• Whether it persists: no, both were one-off and the pricing policy is unchanged.
• What is being done: nothing required, but discount authority above 8% now needs sign-off.

Four short clauses replace a column of numbers nobody could interpret. Apply it only to variances that are material. Explaining a small one implies it mattered.

4. Cut it to six pages, and put the rest in an appendix

The instinct to include everything comes from a fear of being asked something you cannot answer. That fear is real, and the solution is an appendix rather than a longer pack.

Six pages that are read beat twenty-two that are skimmed, every time. Keep the detail, which is not wasted and which someone will eventually want, but move it behind the decisions so that the document a director opens on the train is the one that matters.

A practical test: if a non-executive read only pages one to six, would they be able to participate properly in the meeting? If not, something on page eleven belongs at the front.

5. Put cash before profit

Profit is an opinion; cash is a fact. That is a well-worn line and it is well worn because it keeps being true. Businesses very rarely fail because they were unprofitable this month. They fail because they ran out of money, frequently while trading profitably on paper.

Put the cash position and the forward cash view before the profit and loss. A thirteen-week view is the practical horizon for operational decisions; a twelve-month view belongs alongside the reforecast. Show both, and show the assumptions behind the receipts. A forecast that assumes customers pay to terms is a forecast about a business you may not have.

6. Publish the delivery date, and then keep it

A pack that arrives on a different date each month is a pack that arrives late, because the reader has no expectation to compare it against. Publish a date, and hold it. The tenth working day after month end is achievable for most businesses.

Where holding it means the pack is slightly less complete, that is almost always the right trade. A pack that is ninety-five per cent right on the tenth working day is worth considerably more than one that is perfect on the twenty-fifth, because by the twenty-fifth the month it describes is nearly two months old.

Timeliness is a feature of management information. Accuracy is a feature of statutory accounts. Confusing the two is how a business ends up with reporting that is beyond reproach and no use.

Where to start

Do not redesign the whole pack in one month. It will not survive contact with a close, and a half-finished redesign is worse than the original.

1. Next month: add a decisions page at the front. Change nothing else. This alone changes the meeting.
2. The month after: move cash ahead of profit and add a thirteen-week view.
3. The month after that: move everything nobody referred to in two meetings into an appendix.
4. Then: replace variance columns with variance sentences, on material items only.
5. Finally: agree a publication date and defend it.

Five months, one change at a time, and each change survives because it was allowed to bed in before the next one arrived. That is a slower schedule than most people want and a faster one than most redesigns actually achieve.

This piece describes the reporting approach we use with clients on financial management engagements. It is general guidance rather than advice on your particular circumstances. Every business has some feature that makes one of these six wrong for it, and finding that feature is what the first two weeks of an engagement are for.