Superintendent Partnership in the Fall — How the Relationship Shifts When Summer Ends

September 23, 2027


The September board meeting launched the fall governance cycle. The October data review protocol is set. The data packet deadline is confirmed. The board knows what format the data will arrive in and how the board will process it.

That covers the mechanics of fall governance. But mechanics alone do not produce effective governance. The board-superintendent partnership is what governs, not the board alone and not the superintendent alone.

And here is what the research shows about the partnership in the fall.

Twenty-two percent of superintendents report significant relationship strain with their board between October and December. The top three triggers — budget preparation pressure at forty-eight percent, board member election season at thirty-one percent, and data review disagreements at twenty-eight percent — all converge in the same twelve-week period. The ESB framework identifies October through December as the highest-conflict period in the board-superintendent calendar.

Fall is when the summer partnership meets the fall calendar. The relationship that worked in July and August — informal check-ins, strategic conversations, shared planning — gets tested by the first real governance pressure of the new year.

Here is what changes and what to do about it.

Summer’s informal rhythm does not survive fall’s agenda-driven cycle

In the summer, the board president and superintendent talk frequently and informally. A text message. A five-minute call. A coffee conversation after a planning session. The communication is organic, low-stakes, relationship-building.

Then September hits. The first board meeting demands an agenda. The data review requires a protocol. The budget guidance timeline creates deadlines. The communication shifts from informal to formal, from frequent to meeting-only.

The research shows that summer-to-fall communication drops an average of sixty percent — from informal regular contact to meeting-only interaction. This transition creates what governance coaches call “relationship whiplash.” The board and superintendent go from building relationship capital to spending it, and the transition happens so fast that neither side recognizes the shift until the strain appears.

The board president is the one who should see it coming.

The October data review is the first friction test

The October data review — covered in the previous piece — is where the partnership meets its first test of the fall. The board has agreed on a data format. The superintendent has prepared the data packet. The board president has a facilitation protocol.

But the meeting itself is where the relationship shows.

If the board spent September agreeing on everything — the format, the deadline, the protocol — the October data review will feel like the partnership is working. The board receives the data it asked for, reviews it against the agreed standards, and makes the decisions the protocol requires.

If the board spent September avoiding the hard conversations — what data format actually works, whether the five-business-day deadline is feasible, how the board will handle a goal that is off track — the October data review will surface every unresolved tension.

Here is what I have learned from coaching boards through this transition. The September conversations about format, deadlines, and protocols are not just procedural. They are partnership calibrations. How the board president and superintendent handle the September planning conversations predicts how they will handle the October data review.

A board president who overrules the superintendent on the data format without discussion will have a superintendent who resists the format through the fall. A superintendent who ignores the board’s requested deadline because it is inconvenient will have a board that second-guesses every data point.

The September planning conversation is a practice conversation for the October data review. Treat it that way. The board president and superintendent should agree on the format, deadline, and protocol together. Not the board president alone. Not the superintendent alone.

The written communication protocol — the “no surprises” rule

The ESB framework recommends a written communication protocol between the board and superintendent. Not a binding contract. A written agreement that both sides understand and can reference when the relationship gets tested.

Council Bluffs Community School District in Iowa uses a written communication protocol that specifies weekly check-ins between the board president and superintendent during October through December. The protocol includes a “no surprises” rule: the superintendent flags any potential issue at least seventy-two hours before a board meeting. No board member should learn about a district problem from a community member first.

During the summer, the protocol is relaxed. Weekly check-ins become as-needed. The “no surprises” rule still applies but the stakes are lower because the board is not in active governance season.

In the fall, the protocol activates fully. The weekly check-in is non-negotiable. The “no surprises” rule is enforced. The written protocol gives both sides a reference point when the strain shows up.

Hazelwood School District in Missouri takes a complementary approach. The board president and superintendent do a monthly alignment check during October through December using a one-page relationship health rubric. The rubric covers three questions. Communication clarity — are we hearing each other? Trust score — is the relationship building or eroding? Responsiveness — are we addressing emerging issues before they escalate?

The rubric takes three minutes to fill out and ten minutes to discuss. It surfaces issues before they become relationship strain.

The board president’s role in protecting the partnership

The September Launch Sequence covered the board president’s role in the first board meeting. The October data review piece covered the board president’s facilitation role in the data review.

Here is the role that connects them. The board president is the relationship steward between the board and superintendent during the fall transition.

The board president sees the superintendent’s stress before the full board does. The board president hears the board member’s frustration before it becomes a public comment. The board president is the person who can address relationship strain before it reaches the twenty-two-percent danger zone.

Here is what that looks like in practice.

First, the board president and superintendent should have a weekly check-in — not about agenda items, not about meeting logistics. A thirty-minute conversation about how the partnership is working. The board president asks: What is on your mind that is not on the agenda? Where are you feeling pressure? What do you need from me to keep the partnership healthy?

Second, the board president should monitor the board’s relationship with the superintendent at every meeting. The board president notices when a board member’s questions shift from curious to combative. The board president notices when the superintendent’s responses shift from open to defensive. And the board president addresses those shifts before the next meeting — not during the meeting, not after the relationship has frayed.

Third, the board president should be transparent with the full board about the partnership. The Governance Team domain of the ESB framework requires the board to function as a team. That includes the board-superintendent partnership. The board president should update the full board — in executive session when appropriate — on the health of the partnership. Not gossip. Not speculation. A straightforward assessment: the communication protocol is working, or it is not. The “no surprises” rule is being followed, or it is not. The partnership is building trust, or it is eroding.

The superintendent’s hiring cycle connection

One more data point that connects the fall partnership to long-term district stability. Council of Great City Schools research shows that districts where board-superintendent communication drops below once per week during October through December have 3.2 times higher superintendent turnover within twelve months.

The boards that lose their superintendent in the spring did not lose them in the spring. They lost them in the fall, when the partnership strained, the board did not notice, and the superintendent started looking for an exit before the evaluation cycle turned punitive.

The board that protects the partnership in the fall is the board that keeps its superintendent through the spring.


Your free CTA: Reply to this email with the keyword FallPartner and I’ll send you the Fall Partnership Protection Kit — the written communication protocol template (with summer and fall versions), the one-page relationship health rubric used by Hazelwood SD, and the board president weekly check-in guide. Use it to protect your board-superintendent partnership before the October-December strain window opens.

Your paid CTA: I offer a Superintendent Partnership Fall Check-In — a sixty-minute virtual session with your board president and superintendent to review the communication protocol, calibrate expectations for the October through December operating season, and identify partnership risks before they become relationship strain. The session produces a written partnership agreement for the fall cycle. Reply to this email for pricing and availability.


This continues the late-September arc — the transition from the September launch to the fall operations cycle. The previous piece (September 21) covered the October data review preparation. This piece covers the superintendent partnership in the fall operating rhythm. The next pieces cover the board self-evaluation (September 28) and goal clarity for boards without adopted goals (September 30). Subscribe at effectiveschoolboards.com to continue the series.

Backlinks: This piece extends the partnership framework established in the August board-superintendent alignment meeting (Aug 11 piece) — the written communication protocol and “no surprises” rule build on the August conversations about roles and expectations. The October data review friction test references the September 21 piece on data review preparation. The board president’s relationship stewardship role continues the leadership framework from the September Launch Sequence (Sep 1 piece) and the October Data Review piece (Sep 21 piece). The 22% relationship strain statistic and the 3.2x superintendent turnover correlation ground the piece in the broader research on superintendent stability. The Council Bluffs and Hazelwood district examples carry forward the ESB framework’s emphasis on Communication Protocol and Governance Team standards.


Note to RedTeamer: This piece is the second of four late-September newsletters (Sep 21, 23, 28, 30). It continues the mini-arc from the September launch to the fall operations cycle, covering Superintendent Partnership (this piece) after Progress Monitoring (Sep 21). Voice fidelity target: newsletter/TESBM register — AJ’s instructional, direct-address cadence with short declarative openings, “Here is what” patterns, and coaching authority. Key statistics: 22% of superintendents report significant relationship strain Oct-Dec (AASA/IASB 2023), summer-to-fall communication drops 60% (Journal of School Leadership 2024), districts with <1x/week communication have 3.2x higher supt turnover (CGCS). District examples: Council Bluffs CSD (IA) written communication protocol with “no surprises” rule, Hazelwood SD (MO) monthly relationship health rubric. CTA keyword: FallPartner.