Preparing the Fall Data Review System — The Infrastructure Work That Makes Progress Monitoring Possible
July 23, 2027
The spring data review cycle is complete. The board reviewed data in February, March, and May. The board made recorded decisions after each review. The board knows which data reviews produced productive governance conversations and which produced informational briefings.
Now the board has a choice. The board can repeat the same data review format in the fall — the same metric set, the same data format, the same meeting structure, the same decision-recording protocol — and hope for different results. Or the board can use the summer to redesign the data review system based on what it learned in the spring.
The second choice is the only choice that produces governance improvement. Summer is the only time the board has to step back from the cadence of data reviews and redesign the system. During the governance year, the board is executing the system. During the summer, the board improves it.
What to review from the spring data cycle
Before the board designs the fall system, the board needs to review the spring system. The review covers five questions:
Which metrics drove decisions and which were informational noise? Not every metric the board reviewed in the spring led to a governance decision. Some metrics prompted discussion, adjustment, and direction. Other metrics were received as information — the board noted the data point and moved on. The board should identify which metrics fell into each category. The metrics that drove decisions are the core of the fall data review system. The metrics that were informational noise should be reconsidered — either improved to drive decisions or removed to reduce cognitive load.
Did the data format facilitate or hinder productive discussion? The board received data in a specific format — a one-page scorecard, a multi-page data packet, a dashboard, a staff presentation. Did the format make it easy for the board to see the trajectory, compare actuals to targets, and identify areas needing attention? Or did the format require board members to search for key information? The board should identify what worked about the spring format and what needs to change.
Did the review cadence work? The board held data reviews in February, March, and May. Was that cadence sufficient? Did the intervals between reviews allow enough time for the data to change meaningfully? Did the intervals align with the board’s other governance events — budget reviews, evaluation check-ins, community engagement? The board should decide whether the fall cadence should be the same, more frequent, or less frequent.
Did every review produce a recorded decision? The board’s discipline in recording decisions is the single best indicator of whether data reviews are producing governance outcomes. If the board has a written record of each data review’s decisions, the board can verify that the decision-recording discipline is working. If the board doesn’t have a written record — or the records are inconsistent — the board needs to make decision recording a non-negotiable part of the fall system.
What did we learn about our own data review skills? The board self-assessment (Jun 21 piece) may have revealed specific data review skill gaps. Did the board struggle to interpret the data? Did board members have difficulty distinguishing trajectory from point-in-time data? Did the board lack confidence in making governance decisions based on the data? The board’s data review skill level should inform the training the board does this summer (Jul 9 piece) and the support the board builds into the fall system.
Designing the fall data review system
Once the spring review is complete, the board designs the fall system. The design covers four elements:
The metric set. The board decides which metrics to track in the fall. The metric set should be directly connected to the goals the board will adopt in January 2028 — or, if the board hasn’t adopted new goals yet, the metrics should be connected to the current goals that will carry forward. For each metric, the board defines: the specific data point, the target or trajectory, the data source, the reporting frequency, and the responsible party for preparing the data.
The data format. The board decides how the data will be presented. The best format is the one that makes the board’s governance decision the most obvious. A one-page scorecard with a stoplight indicator (green/yellow/red) and a trajectory line makes the decision obvious. A multi-page data packet with raw numbers and narrative explanation buries the decision. The board should choose the format that makes it easiest for the board to see what needs attention and decide what to do about it.
The review schedule. The board decides when the fall data reviews will happen. The fall calendar (Jun 23 piece) should already have the dates blocked. The board confirms: the October data review (the fall’s first review — typically done after the board’s goal-setting foundation work is complete), the January data review (aligned with the new goal adoption), and the March data review (before the budget alignment work intensifies). Some boards add a December check-in if the data demands it. The board decides the specific dates and confirms them with the superintendent.
The decision-recording protocol. The board decides how data review decisions will be recorded. The protocol should specify: who records the decisions (board clerk, designated board member, or superintendent’s designee), what gets recorded (the data reviewed, the board’s assessment, the decision made, the follow-up assigned, and the deadline), how the decisions are communicated to the full board and the superintendent, and how the decisions are followed up at the next data review.
What the board produces before September
The board’s data review system design should be documented and complete before the first September board meeting. The documentation should include: the metric set with definitions and targets for each metric, the data format template for the first fall data review, the fall data review schedule with specific dates, and the decision-recording protocol with templates.
The board that designs its fall data review system in July enters October’s first data review with clarity and confidence. The board that waits until September to think about the data review system enters the first data review with whatever format the superintendent prepares — and that format may or may not be designed to produce governance decisions.
Your free CTA: Reply to this email with the keyword DataFall and I’ll send you the Fall Data Review System Setup Guide — a complete resource with the spring data review retrospective worksheet, the metric set design template, the data format selection guide with examples (one-page scorecard, dashboard, data packet), the review schedule planner, and the decision-recording protocol template.
Your paid CTA: I offer a Data Review System Design Consultation — a ninety-minute call covering the spring retrospective, the fall metric set design, the data format selection, the review schedule confirmation, and the decision-recording protocol setup. Reply to this email for pricing and availability.
This continues the July Summer Governance Deepening & Fall Prep arc. Monday July 26’s piece covers fall budget cycle preparation — what the board prepares in July before the October budget guidance conversation. Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece builds on the entirety of the spring data review arc — the February first data review (Feb 3 piece), the March data review refinement, the May data review and governance closeout. The metric set design follows the goal-connectivity principle from the January goal adoption pieces. The one-page scorecard format was referenced throughout the spring cycle (Council Bluffs model from Feb 3 piece). The decision-recording protocol extends the recorded-decision discipline established in the February alignment arc. The review schedule connects to the fall governance calendar (Jun 23 piece). The data review skill assessment connects to the board self-assessment (Jun 21 piece) and the summer learning agenda (Jul 9 piece).