Launching the Fall Data Review System — Before the First Data Review, the Board Needs to Know What It Is Looking At
August 11, 2027
In July, the board redesigned the fall data review system. The spring data review cycle was reviewed. The fall metric set was designed. The data format was selected. The fall data review schedule was confirmed. The decision-recording protocol was designed.
That was the design phase. Design is necessary. Design is not sufficient.
Now it is August. The system needs to be launched. Launching means the board confirms every component is operational before the first fall data review, likely in October.
What a launched data review system looks like
A launched data review system has six confirmable components. If any component is not confirmed, the system is designed but not operational.
One: The metric set is finalized and shared with the superintendent.
The board designed the fall metric set in July — the specific metrics that tell the board whether progress is being made against the goals adopted in January. Finalize it in August and share it with the superintendent in writing. The superintendent needs to know, in advance, what data the board expects at each data review. If the board has not communicated the metric set, the superintendent prepares data based on assumptions — and assumptions about what a board wants are often wrong.
The metric set should include, for each metric: the name, data source, baseline value, target value, and data frequency. Five elements make it a governance instrument. Just the name makes it a wish list.
Two: The data format is confirmed with the data provider.
The board selected a data format in July — one-page scorecard, dashboard, or data packet. Confirm it in August with the person or team responsible for producing it.
A one-page scorecard requires different preparation than a dashboard or a data packet. If the board selected a dashboard but the data team is preparing a data packet, the board will receive the right data in the wrong format. And the wrong format reduces the board’s ability to make decisions.
Three: The data review schedule is on the governance calendar.
The fall data review schedule was confirmed in July — October and January as the minimum, quarterly if possible. Those dates need to be on the board’s published governance calendar by the end of August.
If the dates are not on the calendar, they will be displaced by other priorities. School districts are busy. Schedules fill up. A data review date not on the calendar by August will not be on the calendar in October.
Four: The data review preparation responsibilities are assigned.
Every data review requires preparation work: the data packet, the board packet, the facilitation design, and the decision-recording format. Assign those responsibilities to specific people by the end of August. Not “the superintendent will prepare the data” — that is vague. Specific people. Specific dates. Specific deliverables.
Five: The decision-recording protocol is tested.
The board designed a decision-recording protocol in July — the format for documenting what the board decides after reviewing data. Test it in August, ideally using Q2 data the board has already reviewed.
A protocol that looks good on paper may not work in practice. The format may be too detailed, or not detailed enough. August is the time to discover those issues — not October, when the first real data review requires a functioning protocol.
Six: The board’s data literacy is assessed.
Most boards adopt data review systems more sophisticated than their current data literacy level. The board’s ability to interpret, question, and make decisions from the data depends on where the board is right now.
Assess your data literacy in August with an honest conversation. Does every board member understand how to read the one-page scorecard? Does everyone know what each metric measures, where the data comes from, and what the targets mean? Does every board member feel confident asking questions about the data during a public meeting?
If the answer to any of these is no, schedule a 60-minute training session before the first data review.
What this prevents
The most common reason boards stop doing data reviews after the first one is not that the data reviews lack value. It is that the board was not prepared. The data was in a format the board could not read. The metric set was unclear. The preparation was incomplete. The meeting ran long.
The board that launches the data review system in August — confirms every component, assigns every responsibility, tests every protocol — enters the fall knowing the first data review will work. And a first data review that works becomes a habit. A first data review that does not work becomes a reason to stop doing data reviews.
Your free CTA: Reply to this email with the keyword DataLaunch and I’ll send you the Fall Data Review System Launch Checklist — a complete instrument covering the six confirmable components with specific verification steps, the superintendent communication template, and the board data literacy assessment guide.
Your paid CTA: I offer a Data Review System Launch Consultation — a ninety-minute session with the board president and superintendent covering the metric set confirmation, the data format verification, the preparation responsibility assignment, and the decision-recording protocol test. Reply to this email for pricing and availability.
This continues the August Summer Governance Completion & September Preparation arc. Friday’s piece covers the budget guidance document finalization — the draft that the board needs to complete before the October budget guidance conversation with the superintendent.
Backlinks: The data review system design was covered in the Jul 23 piece, “Preparing the Fall Data Review System — The Infrastructure Work That Makes Progress Monitoring Possible.” The metric set design connects to the goal-setting framework established in the January 2027 arc and the fall goal-setting foundation work covered in the Jul 14 piece. The decision-recording protocol builds on the spring data review practices from the February and March data review pieces. The data literacy assessment connects to the board training agenda from the Jul 9 piece. The accountability framework connects to the ESB Progress Monitoring domain.