The October Data Review Is Coming — Here Is What Your Board Needs to Have Ready
September 21, 2027
The September board meeting launched the fall governance cycle. The first readings happened. The fall calendar was confirmed. The board demonstrated that the summer work had produced a different kind of governance.
That was the launch. Now comes the first real governance test of the new year.
The October data review is the board’s first substantive governance event after the organizational meeting. It is where the board moves from structure to substance — from confirming how the board will operate to actually operating. It is where the board proves that its governance framework produces decisions, not just meetings.
Most boards walk into the October data review unprepared. Not because they are negligent. Because they spent September on the launch — the agenda structure, the first reading procedures, the calendar confirmation — and assumed the data review would take care of itself.
It will not. And the boards that treat the October data review as automatic are the boards that discover in October that they have data but no foundation to govern with it.
Here is what your board needs to have ready before the October data review.
The data review format must be decided before the data review, not during it
The biggest mistake boards make with the October data review is deciding the format in the meeting. The board arrives, the superintendent presents data in the format the superintendent always uses, and the board spends the meeting trying to figure out whether the format works instead of actually reviewing the data.
Decide the format in September. Here is what that means.
First, the board decides what data it wants to see. The board’s goals from the previous governance cycle — or the goals the board is preparing to adopt in January — define the data set. If the board’s priority goal is third-grade reading proficiency, the data review should start with third-grade reading proficiency data. If the board has multiple goals, the board decides on the primary metric for each goal and that metric appears first in every data review.
Second, the board decides the format. I recommend a one-page dashboard per goal. Not a thirty-page data packet. The board members should be able to look at the dashboard and answer three questions within sixty seconds: Where are we? Where are we supposed to be? Is the trajectory improving, flat, or declining?
Third, the board decides the comparison frame. The board should see the current data point, the previous data point from the same metric, the target for the governance year, and — if available — the same data point from the same period last year. Without the comparison frame, a single data point means nothing.
The board president and superintendent should agree on the format in writing before the last week of September. If the board president and superintendent cannot agree on the format, that means the board is not ready for the data review.
The data packet deadline must be set in September
The superintendent needs to know when the data needs to be ready. Setting the deadline two days before the board meeting is a recipe for rushed data, incomplete data, or no data at all.
I recommend a five-business-day rule. The superintendent delivers the data packet no later than five business days before the board meeting. That gives board members time to read the data before the meeting. That gives the board president time to prepare the data review facilitation. And that gives the superintendent time to answer clarifying questions before the meeting, so the meeting itself is focused on decisions, not clarification.
If the superintendent cannot meet the five-business-day deadline, the board should know that before the meeting. The board president should ask the superintendent in September: is there any data source that will not be available in time for the five-business-day deadline? If yes, the board adjusts the expectation. But the adjustment should be made in September, not discovered in October.
The board needs a data review protocol before it sees data
The October data review should follow a protocol. The protocol should be agreed upon in September and published to the full board.
Here is the protocol I recommend.
Section one — data presentation. The superintendent presents the data for each goal. The presentation follows the board-approved format. The superintendent answers three questions for each goal: What does the data show? What is driving the current trajectory? What adjustments are planned if the trajectory is not on track?
Section two — board discussion. The board asks questions about the data. The board president facilitates the discussion. The discussion is focused on understanding, not judging. The board’s job in the data review is to understand the data well enough to make a decision about what to do next. The board’s job is not to evaluate the superintendent during the data review. That evaluation happens in the February check-in and May midpoint.
Section three — board decision. For each goal, the board makes one of three decisions. Accept the current trajectory and confirm the superintendent’s planned adjustments. Direct a change to the trajectory — additional resources, different strategy, timeline adjustment. Request additional information before making a decision.
The board documents each decision in the meeting minutes. The decision is not a vague statement. It is a specific recorded action that can be reviewed at the next data review.
The board president’s role in the October data review
The September Launch Sequence piece covered what the board president does in the September meeting. The October data review requires a different kind of leadership from the board president.
In the October data review, the board president’s job is to keep the board focused on data, not anecdotes. Every board has a member who wants to talk about the student they heard about, the classroom they visited, the parent who called them. Those stories are information the board should use. But they are not substitutes for data. The board president’s job is to acknowledge the story and redirect to the data: “Thank you for sharing that. Let’s look at what the data says about this issue across the district.”
The board president’s job is to enforce the decision protocol. When the board has discussed the data for a goal, the board president asks for the decision. If the board is not ready to decide, the board president sets a timeframe for when the decision will be made. The board does not leave the data review without a recorded decision for each goal.
The board president’s job is to manage the time so the board covers every goal. I recommend the board president set a time budget for the data review section of the meeting. Thirty minutes for three goals. Ten minutes per goal — presentation, discussion, decision. If the board needs more time for a specific goal, the board president adjusts the budget from the remaining goals. But the board does not skip a goal because it ran out of time.
What to do if the board has not adopted new goals yet
Some boards will enter October without new goals for the current governance year. The September Launch Sequence covered boards that followed the full summer-to-fall transition arc. But not every board does. If your board has not adopted new goals, the October data review still matters.
The board reviews the data against the goals from the previous governance cycle. The data review serves two purposes: it maintains accountability for the previous goals while the board completes its goal-setting process, and it gives the board baseline data for the new goals.
The board president should be transparent about the situation at the start of the data review: “The board is in the process of adopting new goals for this governance year. Until those goals are adopted, we will review our progress against the goals from last year. The data we see today will also serve as baseline data for the goal-setting process.”
That honesty respects the governance process and keeps the board accountable. Boards that abandon accountability because they have not adopted new goals create a governance vacuum that the superintendent must fill.
The data review is the board’s primary accountability mechanism
The September board meeting launched the fall cycle. The October data review is where the board demonstrates that the cycle will be governed by data, not by habit. The board that walks into the October data review with an agreed format, a confirmed data packet deadline, a published protocol, and a board president who knows how to facilitate the review will produce decisions that drive student outcomes.
The board that walks into the October data review hoping the superintendent has prepared something useful will discover in October what the board should have decided in September.
The first governance test of the new year is coming. The boards that pass it are the boards that prepare for it.
Your free CTA: Reply to this email with the keyword OctReady and I’ll send you the October Data Review Preparation Kit — the board-approved data format template, the five-business-day data packet deadline checklist, the three-section data review protocol script for the board president, and the goal decision documentation template. Use it to turn your October data review from a presentation into a governance decision.
Your paid CTA: I offer an October Data Review Facilitation Session — a ninety-minute virtual session with your board president to design the data review format, confirm the data packet expectations with the superintendent, and prepare the board president for the facilitation role. The session produces a complete October data review plan before you leave the call. Reply to this email for pricing and availability.
This opens the late-September arc — the transition from the September launch to the fall operations cycle. The September Launch Sequence (September 1) covered the first board meeting and the summer-to-fall transition. This piece covers the next governance milestone: the October data review and what boards need to have ready before it. The next pieces cover the superintendent partnership in the fall operating rhythm (September 23) and the board’s self-evaluation preparation before the busy cycle begins (September 28 and 30). Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece extends the governance framework established in the September Launch Sequence (Sep 1 piece) — the board that launched its fall cycle in September now prepares for its first substantive governance event. The data review format protocol builds on the Progress Monitoring framework from the June fall calendar preparation piece (Jun 23 piece) and the August data infrastructure piece (Aug 18 piece). The five-business-day data packet rule carries forward the superintendent communication protocol from the August alignment meeting (Aug 11 piece). The three-decision protocol — accept trajectory, direct change, request information — follows the same decision-making structure the board used in the August policy discussion session (Aug 18 piece). The board president’s data review facilitation role continues the leadership framework established in the August alignment meeting (Aug 11 piece) and the September Launch Sequence (Sep 1 piece). The goal-setting bridge for boards without new goals connects to the July 28 piece on fall goal-setting groundwork and forward to the December goal-setting preparation session.
Note to RedTeamer: This piece is the first of four late-September newsletters (Sep 21, 23, 28, 30). It opens a mini-arc that bridges from the September launch to the fall operations cycle, covering Progress Monitoring (this piece), Superintendent Partnership (Sep 23), and the remaining ESB domains across Sep 28-30. Voice fidelity target: newsletter/TESBM register — AJ’s instructional, direct-address cadence with short declarative openings, “Here is what” patterns, and coaching authority.