What your board actually needs to see every month

A board packet has an unusual job. It has to let people who do not work in the organization’s books, who see the numbers twelve times a year at most, and who are legally responsible for the organization’s finances, exercise real oversight in about twenty minutes of reading.

That is a hard brief, and it is why so many packets fail in one of two directions. Either they are a single summary page that nobody can ask a question about, or they are forty pages of exports that nobody opens.

The board’s job is oversight, not bookkeeping

This is the distinction that sorts out most packet arguments. A board member is not checking your work. They are trying to answer a small number of governance questions, and everything in the packet should serve one of them.

• Can we meet our obligations? Payroll, rent, and commitments already made, over a horizon long enough to do something about it.
• Are we where we said we would be? Against the budget the board itself approved.
• Is anything moving in a direction we should ask about? Trends, not single months.

If a page in the packet does not help answer one of those, it is probably there out of habit.

Cash comes first, not the income statement

Most packets open with the statement of activities because that is the order accounting software puts things in. For a board, cash is the more urgent question, and it should be at the front.

The useful version is not just the bank balance. It is the balance, minus what is already committed to restricted purposes, against what has to go out over the next few months. An organization can look comfortable and be three weeks from a problem, and that gap is exactly what a board is supposed to catch early.

Budget against actual, with the variances explained

The numbers matter less than the sentences next to them. A column of variances with no explanation transfers the analytical work to people who have the least context to do it, and what happens in practice is that nobody does it.

A short note on each meaningful variance changes the meeting. It moves the conversation from "why is this number different" to "given that this is why, what should we do," which is the conversation a board is actually for.

Explain the favorable variances too. An underspend on a program line is not good news by default. It usually means something did not happen.

What does not belong

A general ledger detail export. Every account in the chart of accounts, most with zero activity. Three decimal places. A dashboard with twelve metrics on it where only two get discussed.

All of these come from the same instinct, which is that including more is safer than including less. In oversight it is the opposite: the more there is to look at, the less likely anyone is to look at the thing that matters.

Detail should be available on request and not in the packet. That distinction is worth stating out loud once to the board, so nobody thinks information is being withheld.

When the news is bad

The instinct is to soften it, or to wait until there is a plan to present alongside it. Both are understandable and both make things worse.

A board that learns about a problem late has fewer options than one that learns early, and it also learns something about the reporting it has been getting. Bad news delivered plainly and early costs a difficult meeting. Bad news delivered late costs trust, and trust is the thing the whole reporting relationship runs on.

Consistency beats completeness

The single most valuable property of a board packet is that it looks the same every month. Same order, same format, same definitions.

When the format is stable, board members develop a reading habit and start noticing changes on their own. When it shifts every few months, every meeting starts over with orientation, and nobody builds the intuition that makes oversight work.

A mediocre packet delivered identically for two years is more useful than an excellent one that gets redesigned every quarter.