The October Data Review Season Is Here — Are You Governing from Data or from Anecdotes?

October 1, 2027


October is when the governance year begins in earnest.

September was the preparation. You set the data packet format. You confirmed the review schedule with your superintendent. You evaluated your board’s own governance effectiveness. You built the infrastructure that makes real governance possible.

Now October arrives. And with it, the first real test of whether your board will govern from data or from anecdotes.

I have watched dozens of boards face this test. And I can tell you with certainty: the boards that govern from data do not have better data than the boards that govern from anecdotes. They have a framework for what to do with it. They have a discipline for how to discuss it. And they have a protocol for making decisions from it instead of around it.

The boards that govern from anecdotes? They have the same data reports. But they do not have a framework. So the data sits in a binder, and the board governs from what someone remembers, what someone heard in the parking lot, or what the loudest speaker in public comment demanded.

October is the month you choose which kind of board you will be.

Three categories that define data-governing boards

The ESB framework for Progress Monitoring organizes data review into three categories. Every data point your board reviews this fall fits into one of them. And every board decision should connect to one of the three.

Here is the framework.

Category One: Accept Trajectory

The data shows progress toward the goal. Not perfection. But movement in the right direction at a pace that is likely to reach the target.

This is the easiest decision a board makes. But it is not a passive decision. Accepting trajectory means the board formally records: We reviewed the data. We accept the current trajectory. We will check again next month.

The board that does this is governing. The board that simply moves to the next agenda item without recording its data review decision is holding a meeting, not governing.

Category Two: Direct Change

The data shows a gap. Progress is stalled or moving in the wrong direction. The board needs to direct the superintendent to make an adjustment.

This is the most important decision a board makes during the fall governance cycle. Because directing change means the board is using its authority to intervene — not by micromanaging, but by setting a new expectation and a timeline for results.

I have watched boards struggle with this category. They see data that concerns them. They ask questions. They express frustration. But they never formally direct a change. They leave the meeting having discussed a problem without having decided a response. The superintendent leaves the meeting unsure what the board expects.

The board that directs change says: We reviewed the data. We do not accept the current trajectory. We direct the superintendent to present a revised plan by our next meeting. The plan must include a timeline, a resource commitment, and a measurable milestone.

That is governance. Not frustration. A decision.

Category Three: Request Information

The board does not have enough data to determine whether the trajectory is acceptable. The data is incomplete, the cohort is too small to be meaningful, or the question the board needs answered has not yet been asked.

Requesting information is not a sign of weakness. It is a sign of rigor. The board that requests more information before making a decision is not punting — it is ensuring that when it does decide, the decision is grounded in evidence.

The trap to avoid: requesting information repeatedly without ever reaching a decision. I have seen boards request five consecutive months of data on the same topic without ever directing a change or accepting a trajectory. That is not rigorous governance. That is decision avoidance dressed up as diligence.

Request information once. Maybe twice. Then make a decision.

The third-grade reading example

Let me give you a concrete example so this framework stops being abstract and becomes something your board can use at your next meeting.

Your board adopted a goal in January: increase third-grade reading proficiency from 48 percent to 55 percent by June 2028. It is October. Your superintendent presents the mid-year reading assessment data. Third-grade reading proficiency is at 49 percent. An improvement of one percentage point since the baseline.

What does the framework tell you to do?

If the board accepted this trajectory, it would be betting on a second-half acceleration that the data does not support. One percentage point in the first half of the year is unlikely to produce seven percentage points in the second half. Accepting trajectory would be a governance error disguised as patience.

The correct response is Category Two: direct change. The board says: We reviewed the reading data. We do not accept the current trajectory. We direct the superintendent to present a revised reading intervention plan at our November meeting. The plan must include the specific instructional changes, the schools targeted, the resources reallocated, and the measurable milestone we should expect by the February assessment.

That is a board governing from data. Not from hope. Not from the anecdote about a principal who said the third-grade team is working hard. From data that tells a clear story, combined with a framework that tells the board what to do about it.

Now imagine the alternative. A board without this framework. A board member says, “I visited Washington Elementary last week, and the third-grade teachers seem really dedicated. I think we are heading in the right direction.” Another board member says, “I got an email from a parent who said her child’s reading has improved dramatically.”

That board is governing from anecdotes. They are making decisions based on what someone saw or what someone heard, not on what the data shows. And the one percentage point gain that looked modest against the framework looks like good news when filtered through a personal story.

The framework protects you from yourself. It gives you something to set against the anecdote. Not because anecdotes are irrelevant — they provide context that data alone cannot. But because a board that governs from anecdotes alone will never know whether its decisions are producing results.

The baseline principle

Here is the principle every board needs before reviewing October data.

You cannot measure progress without a baseline.

It sounds obvious. And yet I have watched board after board review October data without knowing where the district started. They look at a number — the current reading proficiency, the current attendance rate, the current math score — and they debate whether it is good or bad without reference to where the district was six months ago.

The baseline principle solves this. Before your board reviews any data point, confirm: What was this number in January? What was the target? What is the current number?

Three numbers. That is all you need. A baseline, a target, and a current value. Every data point your board reviews should be presented in that format. If the superintendent brings you a data report that does not include all three numbers, send it back.

The baseline is what separates data governance from data review. Reviewing data without a baseline is reading a report. Reviewing data with a baseline is governing.

Your October agenda

Here is what I want your board’s first October meeting to include.

Add a standing agenda item: Progress Monitoring Review. Twenty minutes. No exceptions. No deferrals.

The superintendent presents three data points — one per adopted goal — with baseline, target, and current value for each. The board applies the three-category framework to each one: accept trajectory, direct change, or request information. The board secretary records the decision for each goal in the minutes.

Twenty minutes. Three decisions. One record of how your board governed in October.

The boards that do this consistently are the boards that walk into December with a governance record, not a wish list. They know exactly what they decided. They know exactly what they directed. They know exactly what they are watching.

The boards that skip this step are the boards that walk into December trying to remember what they discussed in October.

The data review season is here

October through December is the most consequential governance period of the year. The data arrives. The budget pressure builds. The calendar does not slow down.

Your board has two choices.

You can govern from data — with a framework, with a baseline, with a decision-making protocol that turns every data point into a governance action. You will leave every meeting knowing what you decided and why.

Or you can govern from anecdotes — with hope, with impressions, with whatever story happens to be the loudest in the room. You will leave every meeting feeling busy without knowing whether you moved anything forward.

The framework is here. The season is here. The choice is yours.


Your free CTA: Reply to this email with the keyword DataGovern and I will send you the October Data Review Protocol — a one-page meeting structure with the three-category decision framework, the baseline principle reminder, and a record template that turns twenty minutes of data review into a permanent governance record for every goal.

Your paid CTA: I offer a Data Review Facilitation session — a two-hour virtual work session where I facilitate your board’s first Progress Monitoring review, walk through the three-category framework with your actual data, and produce a written record of your board’s decisions. Reply to this email for pricing and availability.


This opens the October Governance Season arc — the fall execution phase that follows September’s Fall Operations Transition arc. September’s four pieces prepared you: the October data review format (Sep 21), the superintendent partnership protocols for fall (Sep 23), the goal clarity path for boards without adopted goals (Sep 28), and the board self-evaluation that gave you a governance baseline before the busy season (Sep 30). This arc continues with the October-December governance execution plan (Oct 5), the first full data review facilitation guide (Oct 12), and the community progress report (Oct 19). Subscribe at effectiveschoolboards.com to continue the series.

Backlinks: This arc builds on the Progress Monitoring framework from the ESB Framework (effectiveschoolboards.com/framework/). The three-category decision protocol extends the January-June 2027 Governance Roadmap (January 27, 2027) into the fall semester. The baseline principle draws on the data governance standards introduced in the August-September launch sequence. The board self-evaluation referenced in the footer was completed during the September Fall Operations Transition arc (Sep 30, SelfEvalNow keyword). The October community progress report continues the trust-building work from the October Community Engagement arc. Subscribe at effectiveschoolboards.com to continue the series.