What should a good board monitoring report look like?

Most board reports are written by staff to inform the board — dense documents filled with program updates, financial tables, and narrative summaries of activity. A monitoring report is different. It's written to answer a specific question: is the organization in compliance with the board's policies? That shift in purpose changes the format, length, and structure of what gets produced.

A good monitoring report is organized around the board's policies, not around staff activities. Each section corresponds to a specific board policy — an outcome goal or an executive constraint — and addresses one question: is the organization meeting this policy's expectations? The CEO interprets the policy, presents data relevant to that interpretation, and renders a judgment: compliant, not compliant, or partially compliant with explanation. The board's job is then to decide whether it agrees with that interpretation and that data.

Length matters more than most boards realize. A monitoring report that runs 40 pages is not more useful than one that runs 8 pages — it's less useful, because board members can't absorb it, and critical information drowns in volume. A well-designed monitoring report covers each policy in one to three pages. If an outcome goal requires more explanation, that's a sign the goal may need to be clarified, not that the report should grow.

The Four Required Elements of Each Section

Each policy section in the report must contain exactly four things: the Goal or Guardrail being monitored, the data the CEO is using to evaluate performance, the CEO's interpretation of what that data means, and — when performance is below target or at risk — the evidence of the underlying problem and the plan to address it. That's it. The board doesn't need a history of the program, staff biographies, or a list of activities. It needs to know what the standard is, what the evidence shows, how the CEO reads it, and what happens next if something is off track.

What a Monitoring Report Is Not

A monitoring report is not a newsletter, a program update, or a staff achievement summary. Those have their place — but they belong in supplementary materials, not in the monitoring report itself. When boards conflate the two, they end up with a document that feels comprehensive but doesn't actually answer the governance questions that matter. The monitoring report should answer the question "are we doing what we said we'd do?" Everything else is context that may or may not be relevant to that question.

One practical tip: the monitoring report works best when the CEO submits it to the board a few days before the meeting, not the day before. Board members need time to review it, identify questions, and come to the meeting prepared to engage — not read. If the report is distributed at the meeting itself, the monitoring conversation becomes a reading exercise rather than a governance conversation.

Getting the format right

1. Structure the report around your board's policies, not staff functions. Each section header should name the specific End or Guardrail being reported on — not a department, program, or topic.
2. Within each section, include all four required elements in order: the policy being monitored, the data the CEO is using, the CEO's interpretation of that data, and — if performance is below target — the evidence of the problem and the plan to address it.
3. Cap each policy section at one to three pages. If a section is growing longer, the End or Guardrail probably needs to be clarified — not the report expanded.
4. Send the report to board members at least three days before the meeting. This is non-negotiable: monitoring requires preparation, not sight-reading.
5. Keep program updates, staff achievements, and narrative summaries out of the monitoring report itself. If those belong anywhere, they belong in a separate supplementary packet — clearly labeled as context, not governance.