The October Data Review — Running Progress Monitoring With Experience
October 10, 2028
Your board has done this before.
That sentence is the most important difference between Fall 2027 and Fall 2028. A year ago, the October data review was the board’s first time running the Progress Monitoring protocol. Board members were learning the three-decision framework. The board president was learning the facilitation role. The data request timeline was being built from scratch.
None of that is true this year. The board has run multiple data reviews. The protocol is familiar. The question has shifted — from how do we do this? to how do we do this better?
The October data review is not a learning experience. It is a performance experience. Here is what that looks like.
The five-business-day rule is now standard practice.
Last year, the board learned that the data packet needs to arrive five business days before the meeting. Some boards hit that timeline. Some did not. The ones that did made better decisions.
This year, there is no learning curve. The September preparation piece laid out the timeline. The data request went to the superintendent in September. The data packet arrives two weeks before the meeting — not five business days, but ten. The experienced board does not just meet the minimum timeline. It builds in a buffer so board members have time to review the data individually, formulate their questions, and arrive ready to decide.
If your board does not have the data packet in hand by October 3 — one full week before this meeting — something in the preparation system needs adjustment. The data request timing. The metric set confirmation. The superintendent partnership around data delivery. The September prep piece gave you the checklist. October is where you check whether it worked.
The three-decision protocol is practiced, not learned.
The maintain-adjust-escalate framework was new last fall. Board members had to think through each category during the meeting. The conversation was slower because the protocol itself required explanation.
This year, the protocol is second nature. The board spent time in September discussing what maintain, adjust, and escalate mean for each goal — not during the data review meeting, but before it. That advance discussion is what separates experienced boards from first-time boards. The experienced board arrives at the October meeting already knowing the decision categories for each goal. The meeting is not about learning the protocol. It is about applying the protocol to the data on the table.
The difference shows up in the meeting pace. First-time boards spend the first thirty minutes of a data review clarifying the decision framework. Experienced boards spend that thirty minutes examining the year-over-year comparison data. The same meeting time produces more decisions because less of it goes to process orientation.
Year-over-year comparison baselines change the conversation.
This is the single biggest advancement in Year Two board data review practice.
Last year, the board saw October data with no prior fall baseline to compare against. The board could see whether students were on track against the target, but it could not see whether students were improving relative to last fall. Those are different questions.
Fall 2028 gives the board its first year-over-year comparison. The October 2028 data sits next to October 2027 data for the same grade levels and the same metrics. This changes the conversation from are we on track? to are we making progress faster than last year?
Both questions matter. The first question tells you whether students are meeting the target. The second question tells you whether the system is accelerating. A board that answers only the first question knows where students are. A board that answers both questions knows whether the system is improving.
Here is how the year-over-year comparison should appear in the board packet. Column one: each goal metric with its 2027-28 fall baseline data. Column two: the 2028-29 fall data in the same format. Column three: the change — in percentage points or raw scores. Column four: the adopted target. The board reads left to right: where we were, where we are, how much we changed, where we need to go.
The year-over-year change column is the one that produces the sharpest questions. When a metric shows improvement, the board asks: what practices are driving that improvement and how do we protect them? When a metric shows stagnation or decline, the board asks: what changed between last fall and this fall that produced this outcome?
These questions require data that the board prepared in September. The September data review prep piece covered the year-over-year comparison setup. If the board followed that guidance, the October data packet includes this comparison. If it does not, the board has lost the primary advantage of Year Two: the ability to compare this fall against last fall.
The board president’s facilitation role is practiced.
Last year, the board president was learning how to facilitate a data review conversation. The role requires staying neutral on the data while keeping the conversation focused on decisions. That is harder than it sounds. Most board presidents are accustomed to facilitating meetings where they participate in the discussion. Data review requires a different posture: ask the question, let the superintendent answer, move the conversation toward a decision.
This year, the board president has practiced this role across multiple data review cycles. The board president knows the rhythm. Data presentation. Board member inquiry. Goal-by-goal decision conversation. Record the decision. Move to the next goal.
The experienced board president enters the October meeting with an advanced facilitation checklist. The checklist includes the time allocation for each goal, the trigger for escalating a decision to a special session, and the specific question the board president asks after each inquiry round: Are we prepared to make a decision on this goal?
That question is the most important facilitation tool in a data review. It forces the board to decide. Boards without an experienced board president spend the data review talking about data. Boards with an experienced board president spend the data review making decisions about data.
Board member inquiry questions are sharper.
First-time data review participants ask broad questions: Why is this metric where it is? Experienced participants ask specific questions: What intervention was in place for the students who started below benchmark and what was the dosage?
The difference is experience with the data system. A board member who has seen the October data review before knows which questions produce actionable answers and which questions produce discussions that could go anywhere.
Here is what the sharper inquiry looks like. For a literacy goal: instead of asking why third-grade reading scores are where they are, the experienced board member asks whether the year-over-year comparison shows the same cohort gaining, whether the tier-two intervention students are closing the gap at the expected rate, and whether the current trajectory puts the goal target within reach by the end of the year.
These questions produce specific answers. Specific answers produce specific decisions. Specific decisions change student outcomes.
The board member inquiry role assignment from the September preparation is what makes this possible. Board members did not arrive cold. They arrived with an assigned domain of focus, a data packet with year-over-year comparisons, and the advance preparation time to formulate their questions before the meeting. The experienced board member does not discover the data during the meeting. The experienced board member arrives having already discovered the data and prepared the questions.
The pre-meeting work takes less time and produces more.
Experienced boards spend less time preparing for data review because their systems are established. The data request timeline is routine. The metric set is confirmed during September, not debated during the meeting. The board member inquiry roles are assigned in advance. The year-over-year comparison template is filled in by the administration as a standing practice.
The September preparation piece estimated that boards should allocate four to six hours of individual preparation time before a data review. That estimate holds for first-time boards. For experienced boards, the preparation time should be two to three hours — half the time, because the systems are in place and the protocols are known.
But the two to three hours an experienced board member spends produces more than the four to six hours a first-time board member spent. The time goes to analyzing data and formulating decisions rather than learning processes and clarifying definitions. The experienced board member’s prep hour is worth more.
If a board member on your board is still spending four to six hours on data review preparation with a year of experience, something in the system is not working. Either the data packet format is inefficient, the metric set is too large, or the board member has not internalized the protocol enough to work faster. Any of those issues is worth an October conversation.
The meeting produces specific decisions.
The measure of an experienced board running a data review is not whether the conversation was good. It is whether the board produced specific decisions for each goal.
Experienced boards produce maintain decisions when the data shows the goal is on track. They produce adjust decisions when the data shows a specific intervention change is needed. They produce escalate decisions when the data shows the superintendent needs additional support or resources.
Each decision is recorded with the data that supported it and the rationale. The board produces a written record of the October data review decisions — one sentence per goal, naming the decision and the basis for it. That record becomes the baseline for the November goal trajectory check and the December year-end review.
First-time boards often leave a data review with impressions but no decisions. Experienced boards leave with decisions and a clear path to the next check-in.
What the board should do this week
The October data review meeting is this week. Here is what every board member should do.
First, confirm you received the data packet. If you have not, call the board president. The packet should contain the year-over-year comparison sheet and the metric-set confirmation from September. Review it with the year-over-year comparison as your primary focus.
Second, review your assigned inquiry domain. If you own the literacy indicators, look at every literacy metric with the year-over-year change highlighted. Formulate three specific questions per indicator — not questions about the data format, but questions about the student outcome the data represents.
Third, arrive prepared to decide. The board president will ask. The answer should be maintain, adjust, or escalate for each goal. If you cannot name your position on a goal before the meeting, you need to spend more time with the data.
Fourth, bring the September preparation checklist. Check each item: data request went out on time, metric set was confirmed, inquiry roles were assigned, maintain-adjust-escalate parameters were discussed in advance. If any item is incomplete, note it for the October governance check piece that follows on October 31.
Fifth, at the meeting, help the board president keep the conversation on track. When the conversation drifts from data to general discussion, ask the question: Are we ready to make a decision on this goal? The experienced board does not depend on the board president alone to maintain discipline. Every board member owns the meeting’s focus.
The board has done this before. That should not make the board comfortable. It should make the board faster, sharper, and more decisive. The October data review is the first public test of whether the Summer Renewal produced real change. The data on the table will answer that question — if the board is prepared to read it, question it, and decide on it.
Subscribe at effectiveschoolboards.com to continue the series.
Your free CTA: Reply to this email with the keyword OctData2 and I will send you the Year Two Data Review Advancement Toolkit — the experienced board data review facilitation guide, the year-over-year comparison template, and the board president’s advanced facilitation checklist for experienced boards. Use it to run your October data review as an experienced board, not a first-time board.
Your paid CTA: I offer a Fall Data Review Coaching Package — two virtual sessions (October and November) with the board president to support data review facilitation, budget connection, community report production, and governance accountability check. Reply to this email for pricing and availability.
This piece is 2 of 12 in the Fall 2028 Governance Execution arc. It follows the October 3 arc opener (Fall Governance Launch), which launched the board’s Year Two governance cycle after the Summer 2028 Governance Renewal arc. The October 17 piece will connect the data review findings to the budget outlook. Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece inherits from the September 6 data review preparation piece (September Data Review Preparation), the Spring 2028 data review cycle (Q2 Progress Monitoring Check-In), and the Progress Monitoring domain of the ESB Framework. Unlike the Fall 2027 data review instruction, this piece assumes the board has run the protocol before and is advancing its practice. The year-over-year comparison baselines introduced in this piece are the primary advancement from first-year monitoring to experienced governance. Subscribe at effectiveschoolboards.com to continue the series.