Budget Implementation Check-In — The Board’s Role After July 1
July 19, 2028
The budget your board adopted in April went into effect on July 1. That was nineteen days ago.
Here is the question I want every board member to ask today: Do you know whether the budget is being implemented the way the board intended when it voted to adopt it?
If your answer is no, you are not alone. Most boards do not have a budget implementation check-in process. The board adopts the budget in the spring, the fiscal year starts in July, and the next time the board looks at the budget in detail is the mid-year review in January or February — six to seven months after the fiscal year began.
That six-to-seven-month gap is where budget misalignment lives. Positions that were supposed to be funded but were not. Allocations that were redirected during summer administrative transitions. Contractual commitments that were entered into after the budget was adopted. Grant-funded positions that were approved but never filled.
A board that has completed a full governance cycle does not wait six months to check. It checks in July.
Why July matters
July is the first month of the new fiscal year. It is also the month when the most budget activity happens without direct board oversight.
Here is what happens in July at most school districts. The administrative team begins the year under the new budget. Summer programming, extended school year, and operational preparations are underway. Staff who were hired under the spring hiring cycle are being onboarded. Vendors are being contracted. Purchase orders from the previous fiscal year are being closed out. New purchase orders for the new fiscal year are being opened.
Most of these activities are routine. None of them is individually problematic. But collectively, they create a month where budget decisions are being made by staff without a board check-in point — and those decisions can drift from the board’s adopted budget assumptions without anyone noticing until the drift is large enough to matter.
A July budget implementation check-in catches the drift in July, not in January.
What the board should check
The July check-in is not a full budget review. It is a targeted assessment of three things.
One: Did the budget adoption assumptions hold?
Your board made specific assumptions when it adopted the April budget. Those assumptions include staffing levels, enrollment projections, grant funding expectations, state revenue estimates, and cost assumptions for contracted services.
The check-in question: Are the assumptions that the board used to adopt the budget still valid three weeks into the fiscal year?
If enrollment came in lower than projected, that affects revenue. If a grant was not renewed, that affects program funding. If a contracted service increased its rate over the summer, that affects the cost side. The board should know which assumptions held and which changed before the changes compound.
Two: Are the budget alignment adjustments from the spring crosswalk showing up in the actual allocations?
Your board conducted a budget crosswalk in February. It identified allocations that were aligned to student outcome goals and allocations that were not. The April budget adoption incorporated adjustments based on those crosswalk findings.
The check-in question: Did the crosswalk adjustments actually get implemented in the line-item budget that went into effect on July 1?
In Aldine, Texas, the board adopted a crosswalk-adjusted budget in April, but the administrative team implemented the previous year’s budget by default because the line-item adjustments had not been entered into the financial system. The board voted on a budget that did not match the budget being executed. The July check-in catches that mismatch.
Three: Are there any July decisions that create a budget variance the board should know about?
July is when summer administrative transitions happen. A department head who left in June may have been replaced by an interim who does not know the budget assumptions. A purchasing hold that was in place during the spring may have been lifted without board knowledge. A state funding notification that arrived after the budget was adopted may have changed the revenue picture.
The check-in question: What decisions were made in July that created a variance from the adopted budget?
The summer check-in protocol
I recommend a specific protocol for the July budget implementation check-in. It takes approximately thirty minutes and happens in a board work session or a finance committee meeting before the end of July.
Step one: Request the July budget-to-actual report. The CFO or finance director provides a July budget-to-actual report showing the adopted budget, the actual expenditures through the end of July, and the variance for each major budget category. The report should also include a narrative describing any assumptions that changed since the April adoption.
Step two: Compare the adopted budget to the financial system. The board or finance committee confirms that the budget the board adopted in April matches the budget in the financial system. This is a one-line verification that takes five minutes and catches the most common implementation error.
Step three: Review summer commitments. The board reviews any contractual commitments, hiring decisions, or programmatic changes that were made between the April adoption and the July start — particularly those that create obligations against the new fiscal year’s budget.
Step four: Identify variances that need board action. Any variance that exceeds a threshold the board establishes in advance — I recommend five percent of the line item or ten thousand dollars, whichever is lower — is flagged for board discussion and potential action at the first fall board meeting.
What the board gains
A July check-in is not about micro-managing the budget. It is about ensuring that the budget the board adopted is the budget being executed.
Here is what the board gains. If the check-in finds that the adoption assumptions held, the crosswalk adjustments were implemented, and no material variances exist, the board enters the fall cycle confident that the budget is on track. If the check-in finds problems, the board catches them in July — three weeks into the fiscal year, not six months later.
A board that catches a budget misalignment in July has July through September to address it before the first Progress Monitoring cycle. A board that catches the same misalignment in January has already lost half the fiscal year.
The difference is the check-in.
Subscribe at effectiveschoolboards.com to continue the series.
Your free CTA: Reply to this email with the keyword BudgetWatch and I will send you the Summer Budget Implementation Check-In Template — the post-adoption monitoring dashboard with July expenditure tracking, goal-aligned allocation review, and summer hiring and contract approval oversight checklist. Use it to conduct the board’s first budget implementation check of the new fiscal year.
Your paid CTA: I offer a Budget Implementation Review Session — a forty-five minute virtual session with the board’s finance committee chair and the CFO to review the first month of budget implementation against the April adoption assumptions. We will identify any July variances that need board attention before August. Reply to this email for pricing and availability.
This piece is 3 of 13 in the Summer 2028 Governance Renewal arc — a thirteen-piece series running July 5 through September 27, 2028. It follows the July 12 piece on post-evaluation implementation (Post-Evaluation Implementation) and continues the Transition & Renewal sub-arc (Jul 5–26). Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece extends the budget alignment work from the Spring 2028 Governance Execution Cycle — the February budget crosswalk (view the February budget review), the April budget adoption (view the April 18 piece), and the Mid-Year Resource Alignment (view the May 9 piece). The July check-in is the first monitoring point of the new fiscal year. Subscribe at effectiveschoolboards.com to continue the series.