Your October Data Review Is the Board’s Most Important Trust-Building Act — Here Is How
October 12, 2027
Last week, the October-December Governance Execution Plan landed in your inbox. It gave you the month-by-month framework — October’s first full data review and community progress report, November’s governance health check, December’s year-end reset.
That plan was about what to do. This piece is about why community trust depends on how you do it.
Here is what I have learned coaching boards through fifteen October data reviews.
The board that runs the data review in public, publishes the decisions in plain language, and tells the community what the board saw and what the board decided — that board is building trust with every data point.
The board that runs the data review in a work session, publishes the minutes three weeks later, and expects the community to infer what happened — that board is losing trust with every cycle.
October is the month where the gap between these two approaches becomes visible. And the boards that close that gap are the boards that enter November with community credibility, not community suspicion.
The data review has two audiences, and most boards only serve one
Most boards treat the October data review as an internal governance event. The board receives the data packet. The board reviews the data. The board makes decisions. The board moves to the next agenda item.
That is half the work.
The October data review has two audiences. The first audience is the board itself — the board needs the data to govern. The second audience is the community — the community needs to see the board using data to govern.
I have watched boards in districts like Council Bluffs (IA) handle both audiences well. Their October data review produces two outputs: the board’s internal decision record (the goals, the trajectory, the decisions, the action items) and a community-facing progress report that translates the data review into what the community needs to know.
The internal decision record is for the board. It is detailed. It names specific goals, specific data points, specific decisions, specific deadlines.
The community-facing progress report is for everyone else. It is clear. It names the goals, summarizes the data, states the board’s decisions, and explains what the community should expect next.
Two outputs. One data review. One set of decisions. Two different audiences.
Most boards produce one output — the agenda item that the community cannot follow unless they already understand governance terminology and have been following the district’s goal-setting process for the last year.
That is not a communication failure. It is a governance failure. If the board cannot explain what it decided and why, the board has not fully governed.
What the community sees when the board runs the data review in public
Here is what the community sees when the board runs the data review as a public governance act.
The board president opens the data review section by naming the goals. “We adopted three goals for this school year. Goal one is third-grade reading proficiency. Goal two is eighth-grade math proficiency. Goal three is chronic absenteeism. Here is the data for each goal.”
The superintendent presents the data in the format the board agreed to in September. One page per goal. Three questions per goal: what does the data show, what is driving the trajectory, what adjustments are planned.
The board asks questions in public. The board president keeps the discussion focused on understanding the data, not judging the superintendent.
The board makes decisions in public. “For goal one, we accept the current trajectory and confirm the superintendent’s planned adjustments. For goal two, we direct a change — additional literacy intervention in the second-grade pipeline, to be implemented by November 15. For goal three, we request additional information on the attendance intervention pilot before making a decision.”
The board secretary records the decisions. The decisions appear in the meeting minutes, linked to the specific goals.
The board president closes the data review by telling the community what happens next. “The decisions from tonight’s data review will be published on the district website by Friday. The superintendent will report on the directed changes at the November board meeting. Additional information on goal three will be presented by November 1. The community can submit questions about the data review to board@district.org.”
That sequence — name the goals, see the data, ask questions, make decisions, tell the community what happens next — takes forty-five minutes. And it builds more trust in forty-five minutes than a year of generic board newsletters.
The community progress report is the board’s second output
The community progress report is not a press release. It is not a newsletter article summarizing what the board discussed. It is a governance document that tells the community exactly what the board saw and what the board decided.
Here is what a strong community progress report looks like.
A one-page document — the board’s name at the top, the date of the data review, the three goals the board is monitoring. For each goal: the goal statement, the current data point, whether the goal is on track, watch, or off track, and the board’s decision.
That is it. No narrative. No spin. No framing. Just the data and the decisions.
The community does not need the board to interpret the data for them. The community needs the board to be transparent with the data. There is a difference. Interpretation is a press release. Transparency is a governance document.
I have seen boards in districts like Wichita (KS) add one more element to their progress report. They include the comparison data from the previous year. “Third-grade reading proficiency is at 62 percent. Last year at this time, it was at 58 percent. The goal is 70 percent by May.” The comparison frame gives the community context. Context builds trust. Without context, the data point stands alone and the community fills in the context themselves — usually with the worst-case assumption.
The boards that build trust in October are the boards that survive November
November is when the governance year gets hard. Budget pressure builds. The community’s patience with slow progress runs thin. The midyear enrollment data arrives, often with unwelcome surprises.
The boards that enter November with community trust built during the October data review can handle those pressures. The community has seen the board govern. The community knows the board is watching the data. The community knows the board is making decisions based on what the data shows.
The boards that enter November with no community trust built — because they ran the data review as an internal event and published nothing the community could understand — spend November defending their governance rather than governing.
I have seen this pattern play out in district after district. The board that publishes a community progress report after the October data review enters November with a reservoir of trust. The board that does not enters November with a deficit of trust.
The deficit shows up at the November board meeting. The community shows up with questions the board could have answered in October. The board spends the meeting explaining what it did, rather than discussing what it will do next. The meeting runs long. The board members get defensive. The superintendent gets caught in the middle.
A one-page community progress report, published within a week of the October data review, prevents that November meeting from happening.
Who should prepare the community progress report
I recommend the board president draft the community progress report, working with the superintendent to verify the data points. The superintendent provides the data. The board president owns the board’s message.
The report should be published within one week of the data review. If the board’s October data review is on a Tuesday, the report is published by the following Tuesday.
The report goes on the district website, linked from the board’s page. It goes to the local media if the district has education reporters. It is read into the record at the next board meeting as a follow-up item.
The board president reads the report at the opening of the next board meeting: “At our October 12 meeting, we reviewed the data for the three goals we adopted in January. Here is what the data showed and here is what we decided. The full report is on the website.”
That takes three minutes. And it tells everyone in the room — the community members, the staff, the reporters, the superintendent — that this board governs in public.
Your free CTA: Reply to this email with the keyword FallExec and I will send you the Fall Governance Execution Kit — the community progress report template (one-page format with the goal data, trajectory status, board decision, and comparison frame), the October data review decision documentation template, and the board president script for the public data review section. Use it to build trust starting with your October meeting.
Your paid CTA: I offer a fall community engagement coaching session — a sixty-minute virtual session with your board president and communication lead to build your community progress report, practice the public data review facilitation, and plan the November follow-up. Reply to this email for pricing and availability.
This is piece two of the October-December Fall Governance Execution arc — the first execution-phase newsletter after the October 5 arc plan. The arc continues: the board’s escalation protocol when the October data reveals a systemic problem (October 19), and the progress monitoring cadence that keeps data alive between board meetings (October 26). Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece executes the Community Progress Report component of the October work described in the October 5 arc kickoff (October data review + community progress report). The one-page progress report format extends the transparency framework from the September 21 October data review preparation piece. The board president’s public facilitation role builds on the September 21 piece’s board president protocol and the August 11 superintendent alignment meeting. The concept of the data review as a public governance act — with two audiences and two outputs — is rooted in the Governance Team domain of the ESB framework. The community trust reservoir framework connects forward to the November 9 governance health check piece, where the board evaluates the health of its community relationships. Subscribe at effectiveschoolboards.com to continue the series.