Board members are volunteers with fiduciary responsibility. They cannot fulfill that responsibility without information, and they cannot absorb information that is not organized for them.
Here is what nonprofit board reporting should include, how often, and in what format.
Why board reporting matters beyond compliance
Board reporting is a legal requirement in most states, boards are required to exercise oversight, and they cannot exercise oversight without regular financial and programmatic information. But the real reason to do board reporting well is not compliance. It is governance.
A board that receives organized, timely information makes better decisions. A board that receives information in a disorganized way, late, or not at all becomes either a rubber stamp (approving things without real oversight) or a bottleneck (withholding approval because they do not have enough information to say yes).
Neither outcome serves the organization.
How often to report
Your bylaws set the minimum, usually four board meetings per year. The question is what happens between meetings.
Most organizations send board members a brief written report before each meeting, so meeting time can be spent on discussion and decisions rather than information delivery. Some organizations also send a brief monthly update, a page or less, between meetings to keep board members informed without requiring a meeting.
The frequency that works is the frequency your board will actually read and respond to. Start with four times a year. Add more if your board wants it.
What to include in every board report
Financial summary. Year-to-date income and expenses against budget. Include the percentage of the fiscal year elapsed so board members can interpret the numbers in context. Flag any line that is materially over or under budget.
Cash position. How much cash does the organization have? How many months of operating expenses does that represent? This number matters more than any other for a small nonprofit.
Program update. Brief status on each major program: what is happening, whether it is on track, any significant issues. Keep this concise, a paragraph per program is enough if the program is healthy.
Grant status. Which grants are active? What reports are upcoming? Are there any compliance concerns? Board members do not need granular detail, but they should know the status of the organization's funding portfolio.
Key decisions needed. What does the board need to approve, discuss, or decide at this meeting? Flag these explicitly so board members can prepare.
Upcoming deadlines. Any material deadlines in the next 60 days, regulatory filings, grant reports, insurance renewals, that the board should be aware of.
Format matters
Board members are busy. A 40-page board packet that takes two hours to read will not be read. A four-page summary that covers the essentials will be read and will produce better discussion.
Aim for a board report that can be read in 15 minutes. Put the financial detail in an appendix for board members who want it. Put the critical information on the first two pages.
The relationship between board reporting and staff burden
Board reports require staff time to prepare. At a small organization, that time is not trivial, assembling financial data, writing program updates, and coordinating with department heads can take a full day or more per report cycle.
The investment is worth making. But it is worth designing the reporting system so that the information collection is continuous rather than a scramble before each meeting. Program data collected weekly is easier to report than program data reconstructed monthly from memory.