April’s Arc Sets Up May’s Q3 Data Review — Here’s What Your Board Built This Month
April 28, 2027
April is the most compressed governance month on the calendar. Budget adoption, public hearing, mid-year check-in — three governance-defining events in four weeks, each one building on the last, each one carrying consequences into the next. A board that navigates April well has locked the spring governance cycle. A board that treats April as a series of disconnected procedural requirements will spend May and June catching up.
This piece names what your board built this month and what it means for May.
What the budget adoption produced
The budget adoption (Apr 5) was not the end of the budget process. It was the beginning of the monitoring cycle. Your board entered the adoption vote with preparation — the final budget document review, the March alignment reconciliation, the public hearing testimony summary, the monitoring calendar confirmation, and draft motions for all three outcomes.
The adoption outcome — whether the board adopted as presented, adopted with conditions, or delayed adoption — determined the monitoring framework for the fiscal year.
If your board adopted with conditions, the conditions are now the first items on the monitoring calendar. The superintendent knows what to report, when to report it, and what variance threshold triggers board discussion. The board that set conditions at adoption and tracks them in the monitoring cycle governs the budget. The board that adopted with conditions and never followed up on them adopted the budget but did not govern it.
What the public hearing produced
The public hearing (Apr 12) was not a procedural requirement. It was the board’s most visible community accountability event of the spring. Your board entered the hearing with preparation — the seven-day preparation cycle, the hearing simulation, the spokesperson designation, the opening and closing statements.
The hearing outcome — whether the board validated the budget’s alignment story, surfaced specific concerns requiring board action, or revealed material misalignment — determined the board’s community accountability posture for the rest of the spring.
If the hearing surfaced specific concerns, those concerns are now documented in the testimony summary and assigned to the appropriate follow-through track. The board’s response to community testimony — the 24-hour follow-up communication, the testimony summary document, the adoption vote reference — closed the accountability loop that the hearing opened.
What the mid-year check-in produced
The mid-year check-in (Apr 19) was the governance event that connected data to dollars. Your board ran the four-phase Focused Monitoring Cycle — data presentation, pattern identification, root cause analysis, and outcome and direction. For each adopted goal, the board recorded one of three outcomes: on track, on track with conditions, or off track.
The mid-year outcome produced three deliverables that carry into the Q3 data review.
The goal-by-goal outcome record. Every goal has a recorded assessment with the data that supports it. The Q3 review starts from this record, not from scratch.
The budget alignment update. The investment-to-outcome connection is documented. The board knows which funding allocations produced results and which didn’t.
The governance health assessment. The five-indicator review produced a clear picture of where the board’s governance practice is strong and where it needs reinforcement.
What May’s Q3 data review requires
The Q3 data review — typically late May or early June — is the third full data review of the governance year. It follows the Q1 review (February) and whatever Q2 review the board completed at the mid-year check-in (April).
The Q3 review is significant for three reasons.
Reason one: It’s the last data review before the year-end governance report. The data the board sees in Q3 determines what the year-end report will say. If the board skips Q3 or runs a shortened version, the year-end report will lack the comparative data it needs to show the full year’s progress. The board that plans the Q3 review now — before the spring calendar fills the remaining meeting slots — holds the Q3 review. The board that waits until May to plan the Q3 review will find that the superintendent evaluation, the community reporting timeline, and the budget preparation for the next cycle have already consumed the available time.
Reason two: It provides the year-to-date trend line. The Q3 review should show the year-to-date trend for each adopted goal: Q1 data point, Q2 data point, and Q3 data point. The trend line tells the board whether the direction of change is consistent or inconsistent. A goal that improved from Q1 to Q2 but plateaued in Q3 needs a different governance response than a goal that has steadily improved across all three reviews. Without the Q3 data point, the board is governing with two data points — and two data points do not constitute a trend.
Reason three: It informs the next budget cycle. The Q3 review is the first data point that the next budget cycle uses. The board that knows in Q3 that a goal is off track — and knows why — can begin budgeting for the adjustments before the next budget development cycle starts. The board that waits until the year-end report in June to discover the goal is off track has lost the window for proactive budget planning.
Three specific actions for the Q3 review
The Q3 review requires three specific preparations that go beyond the standard data review structure. These should be completed in May, before the Q3 review meeting.
Action one: Year-to-date trend analysis. The superintendent should prepare a year-to-date trend analysis for each adopted goal. The analysis shows the Q1, Q2, and Q3 data points on a single visual. The board’s role is to identify trends, not to produce the analysis — but the board must request it now, in April, so the superintendent has time to prepare it.
Action two: Resource-to-outcome reconciliation. The budget alignment update from the mid-year check-in should be extended to include the Q3 data. The board needs to see: the investment number, the Q1 outcome, the Q2 outcome, the Q3 outcome, and the board’s assessment of whether the investment-to-outcome ratio is improving, stable, or declining. This reconciliation is the most data-intensive part of the Q3 review — and the most valuable.
Action three: Year-end governance report planning. The Q3 review is the moment to set the timeline and scope for the year-end governance report. The board president or designated board member should confirm the report’s due date, the data it will require, and the person responsible for assembling it. The board that plans the year-end report in April and uses the Q3 review to fill the data sections will produce a comprehensive report in June. The board that starts the year-end report in June will produce a hasty report in July.
What happens when the April arc is done
The board that completed the April arc — budget adoption preparation, public hearing execution, mid-year check-in, and this capstone — has done what most boards don’t: connected the full spring governance cycle into a coherent arc.
Management, processes, and outcomes are linked. The board’s decisions from the adoption, the community’s voice from the hearing, and the data from the check-in are all documented in a single governance record. The board enters May with a clear picture of where goals stand, what the community cares about, and what the monitoring calendar requires.
The board that skipped any element of the April arc — the one that adopted without conditions, held the hearing without follow-through, or ran the mid-year check-in without recording outcomes — enters May with gaps. The data is partial. The community’s concerns are undocumented. The monitoring calendar is unconfirmed. The board will spend May and June closing gaps instead of governing.
The choice is not between a productive spring and an unproductive spring. The choice is between governing through May and June with the infrastructure the April arc built — or governing reactively because the arc was never completed.
Your board built the infrastructure this month. May is where it proves itself.
Your free CTA: Reply to this email with the keyword AprilArc and I’ll send you the Spring Governance Arc Summary — a one-page assessment that connects your April outcomes to the Q3 data review preparation, with the year-to-date trend analysis template, the resource-to-outcome reconciliation worksheet, and the year-end report timeline.
Your paid CTA: I offer a Spring Governance Cycle Coaching Package — three sessions covering the budget adoption preparation, the public hearing execution, and the mid-year check-in facilitation. I also offer a Q3 Data Review Preparation session for boards that want structured support entering the final monitoring review of the spring cycle. Reply to this email for pricing and availability.
This closes the April arc: budget adoption preparation, public hearing board role, mid-year check-in data review structure, and the arc capstone into May’s Q3 data review. The May arc continues the Governance to Impact theme with the Q3 data review, the year-end governance report preparation, and the spring governance closeout. Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This capstone ties together the full April arc — budget adoption preparation (Apr 5), public hearing board role (Apr 12), and mid-year check-in data review structure (Apr 19). The Q3 data review preparation extends the Q3 cadence lock-in piece (Mar 31) from the March governance continuity arc. The year-end governance report connects to the community progress report framework (Mar 8) and the board self-assessment (Feb 24). The January governance roadmap (Jan 27) established the full spring calendar that this arc executes. The budget alignment review (Mar 1) and the goal adoption (Jan 11) provide the foundations that April’s work built upon.