September Data Review Preparation — Setting Up October’s First Data Review
September 6, 2028
Your last data review was probably in May or June. Your next one is October. That is a four-month gap — and in that gap, data systems drift, indicators go stale, and new board members remain data-illiterate without anyone noticing until they are sitting in the October review unable to interpret the dashboard.
I have watched boards walk into October data reviews blind. The data is late. The format changed over the summer. The new board members have never seen a trend line. And no one realized any of this was a problem until the superintendent said, “Here are the numbers,” and half the board did not know what to ask.
September is not the month to wait for October to arrive. September is the month to set October up.
Here is what the board should be doing right now. This is what effective Progress Monitoring looks like before the data arrives — the preparation work that makes the October review actionable rather than performative. Boards that skip these September steps do not fail in October because the data was wrong. They fail because they never asked the right questions in September.
1. Run the data system readiness check
Before October’s data review can produce actionable information, the data must exist in a usable form. Do not assume it does. Districts change their student information systems, switch assessment vendors, and lose institutional knowledge over the summer. Ask the superintendent’s team these four questions:
- Which data systems are we pulling from this fall — and are they all operational?
- Who is responsible for extracting and formatting the data for the board?
- Has the board dashboard been updated with current-year enrollment and staffing data?
- What is the verification process — who checks the numbers before the board sees them?
If the answers are vague, the October review will be vague. The data system readiness check is not an IT exercise. It is a governance discipline. If the board does not know where the data comes from, the board cannot trust the data when it arrives.
2. Set up the year-over-year comparison structure
The single most useful thing a board can do in September is align the fall indicators with the spring baselines.
Here is what I see boards get wrong: they carry every spring indicator into the fall without asking which ones still matter. Some indicators answered their question in the spring — you know the trend, you acted on it, you do not need to track it in October exactly the same way. Other indicators need to be replaced because the intervention changed over the summer.
Walk through each spring indicator from your May and June data reviews. For each one, ask:
- Does this indicator still measure progress toward our current goals?
- Does the baseline established in spring give us a fair comparison point for fall?
- Should this indicator be carried forward, replaced, or retired?
The answer does not have to be complicated. It just has to be intentional. A year-over-year comparison structure set up in September will tell you in October whether your summer and early-fall actions moved the needle.
Once the comparison structure is in place, the board applies the three-decision framework to each indicator: maintain, adjust, or escalate. Maintain means the indicator is working as designed and stays in its current form. Adjust means the threshold or calculation method needs refinement before the fall cycle. Escalate means the indicator revealed a structural issue — a goal that is not being measured correctly at all — that requires the board’s attention at the governance level. This framework is the discipline that separates boards that act on data from boards that just look at it. I have watched boards sit through an entire October data review without making a single decision because they had no framework for what to do with what they saw. Do not be that board.
3. Run the indicator refresh protocol
This is the companion to the year-over-year check. Some indicators carry over. Some do not. Some need recalibration because the data source changed, the population shifted, or the goal itself was refined over the summer.
The indicator refresh protocol has three steps:
- Verify source data. Confirm that the denominator, the time window, and the calculation method match the spring baseline. A changed calculation produces a false comparison. If the state changed its assessment between spring and fall, that matters — and you need to know about it now, not in October.
- Update thresholds. If your spring data review revealed that a threshold was too high or too low to be useful, adjust it before October. Do not waste an October meeting debating a threshold you already know is wrong.
- Add fall-specific indicators. There are indicators you only care about in the fall — enrollment stability, early attendance patterns, fall benchmark assessment results. Add them to the dashboard now so October is the first look, not a scramble to create them the night before.
4. Prepare the board’s data literacy
This is the one most boards skip, and it is the one that matters most.
I worked with a board — let me call it Springfield MO’s experience, because the pattern shows up everywhere I coach — that spent its entire September data literacy session learning how to read a scatter plot from a generic online tutorial. The session was well-intentioned, but it was useless. The board members could define “correlation coefficient” by the end of the training. They could not look at their own district’s third-grade reading trend line and say whether the slope was meaningful. The preparation has to be specific to your district’s actual dashboard. Not generic data training. Your data, your indicators, your thresholds.
El Paso TX demonstrated the opposite approach. The board president asked the superintendent’s team for a one-page data literacy guide specific to the board’s fall dashboard — what each indicator measures, how the trend line is calculated, what the threshold means, and what range of outcomes would trigger a maintain, adjust, or escalate decision. The board reviewed that guide in a thirty-minute working session before the September regular meeting. When the October data review arrived, every board member could read the dashboard and ask informed questions. That is the standard.
If you have new board members who joined after the spring data review cycle, they have never seen the board’s data dashboard. They do not know how to read the trend lines. They do not know what is a meaningful change versus random variation in the context of your district. And they will not ask in the October meeting. They will sit quietly and hope no one notices.
September is the time for a board data literacy session. It does not have to be formal. Thirty minutes before a regular meeting, or a voluntary workshop. But the content must be specific to your board’s actual dashboard. Do not train them on abstract data concepts. Train them on your district’s literacy data, your attendance data, your discipline data — the actual indicators they will see in October.
The goal is not to make board members data analysts. The goal is to make them informed consumers of the district’s data. Those are different things, and the distinction matters.
The tie that binds
These four steps share something important: none of them requires a board meeting to execute. The board president and data committee chair can run the readiness check with the superintendent’s team. The indicator refresh can happen in a thirty-minute working session. The data literacy session can be scheduled as a board development hour.
What it does require is intention. October will arrive whether you prepare for it or not. The question is whether you will walk into that room knowing your data systems are live, your indicators are aligned, your comparisons are valid, and your board can read the numbers.
Do not wait until October to discover what you should have verified in September.
Subscribe at effectiveschoolboards.com to continue the series.
Your free CTA: Reply to this email with the keyword OctPrep and I will send you the Data Review Preparation Toolkit — the data system readiness checklist with indicator refresh protocol, the year-over-year comparison template with baseline alignment from spring 2028, the board data literacy self-assessment, and the October data review agenda planner. Use it to prepare your board for the first fall data review.
Your paid CTA: I offer a Data Review Readiness Audit — a virtual session with the board president and the data committee chair to assess the board’s data system readiness, identify any indicator gaps from the spring cycle, and design the October data review agenda and board preparation materials. Reply to this email for pricing and availability.
This piece opens the Fall Launch Preparation sub-arc (Sep 6–27), the third of three sub-arcs in the Summer 2028 Governance Renewal arc. The August Organizational Reset sub-arc established the board’s committee structure (Governance Calendar Construction, Board Committee Renewal), partnership framework (Superintendent Partnership Refresh), and closing readiness (August Board Work Session). This sub-arc prepares the specific governance practices the board will execute in the fall. Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece inherits from the Spring 2028 data review cycle — the May 23 end-of-year data review prep (view the May 23 piece) and the Q2 Progress Monitoring Check-In (view the May 2 piece). The September preparation ensures the October 2028 data review advances from the spring cycle’s baseline. Subscribe at effectiveschoolboards.com to continue the series.