On the difference between board reporting and management reporting

Most groups discover the difference between board reporting and management reporting at the worst possible moment, which is the first board meeting after a quarter has gone wrong. The board pack and the executive committee deck are the same deck, with a different cover sheet. The chair asks a question the executive committee already debated three weeks earlier, and the management team, who have moved on, find themselves explaining a problem they thought was last quarter's business.

This is a structural mistake, not a writing mistake. Board reporting and management reporting are different products built from the same data.

Management reporting is about operating decisions. It runs at the cadence of the business. Weekly for sales pipeline, monthly for the management accounts, quarterly for the full review. The audience is people who can intervene on Tuesday. The format follows the work. A finance team's monthly close pack, an operations dashboard, a heat map of open incidents. These are management reports because they exist to support someone changing something this week or this month.

Board reporting is about oversight. It runs at a slower cadence, which is the board's own meeting cycle. The audience is people who cannot, and should not, intervene at the executive layer. They are watching for the trajectory and the boundaries. The format follows the question 'should we be doing this at all, and is the executive team capable of doing it well?'

When the two are confused, both suffer. Management ends up with a stack of governance overhead that slows operating decisions and tells them nothing new. The board ends up with too much operating detail and not enough trajectory, and reaches for operating questions instead of governance ones. The result is a board that interferes badly and a management team that resents the interference.

The cleanest way I have found to separate them is to write each one for a different question. The management report answers 'what should we change.' The board report answers 'are we still doing what we said we would.' If a section does not answer one of those two questions, it belongs in neither pack. It belongs in someone's working file.

The corollary is that the board pack should be shorter. Most board packs are too long because they have absorbed the management pack. The discipline is to take the management pack as input, summarise it for the trajectory question, and leave the rest behind. The board does not need the operating cadence. It needs to know whether the operating cadence is sound.

There is one exception, which is the moment the board needs to know something has gone wrong. At that point the line between the two packs sometimes has to dissolve. A material incident, a regulatory letter, a senior departure. These belong in the board pack at the time they happen, not at the next quarterly cycle. The exception is what makes the rule worth keeping. If everything looks like an exception, the cadence has stopped working, and the board is operating on rumour and email rather than reporting.