The Board’s Escalation Protocol — when a data review triggers more than a decision
October 18, 2027
Data reviews produce decisions.
Your board built the three-decision protocol from the October 4 post. Accept trajectory. Direct change. Request more information.
Most of those decisions are routine. The board documents the decision, the superintendent executes, and the board tracks progress at the next review.
Some decisions are not routine.
Here is the escalation protocol every board needs — the framework for distinguishing between a governance decision the board can make in a meeting and a situation that requires a special session, a closed session, or an immediate superintendent directive.
Three-level escalation framework (Level 1, 2, 3)
Level 1: routine governance. The data reveals a gap the board can address through normal governance channels. The board makes a decision during the meeting. The superintendent has 30 to 60 days to respond. The decision is documented in the meeting minutes. No special action required. Most data review decisions should be Level 1. If your board is escalating everything, your protocol is broken.
Level 2: elevated concern. The data reveals a pattern that cannot be addressed through a routine decision. Examples: a goal area has been flat or declining for three consecutive data reviews. A budget misalignment exceeds 10 percent of the goal area’s allocation. A staffing or programmatic issue has been flagged by multiple board members across multiple meetings. Level 2 triggers a written board directive, a shorter return-to-board timeline (14 to 30 days), and a closed session discussion if personnel or legal matters are involved.
Level 3: crisis. The data reveals an imminent threat to student safety, fiscal solvency, or legal compliance. Examples: a facilities report showing a structural safety hazard. A financial audit showing material noncompliance. A student outcome data point that indicates systemic failure in a protected class. Level 3 triggers an immediate special session, legal counsel notification, and a written directive to the superintendent with a 48-hour response window.
Every board needs these three levels defined in policy before the escalation happens. You cannot design a protocol in the middle of a crisis.
When October data review triggers escalation
October’s data review is the first real look at fall trajectory. It is the most likely point in the calendar for Level 2 or Level 3 escalation.
Here is why. The September launch set expectations. October reveals whether those expectations are being met. If the board adopted an ambitious goal in August and the October data shows no movement, that is not a routine finding. That is an elevated concern.
Three specific triggers to watch for in October.
Trigger one: the flatline. A goal area shows zero or negative growth from the baseline established in August. This is a Level 2 escalation. The board needs a specific plan from the superintendent within 30 days.
Trigger two: the budget-disconnect. The October budget alignment exercise reveals that a flatlined goal area is fully or over-funded. This is a Level 2 escalation with a financial component. The board needs both a strategy plan and a budget adjustment proposal.
Trigger three: the demographic disparity. The data reveals a significant gap in outcomes for a specific student subgroup. If the gap is large enough to suggest systemic issues, this may be a Level 3 escalation. Legal counsel should be consulted immediately.
Boards that recognize these triggers in October have time to respond. Boards that treat every data point as routine wait until the January self-evaluation to discover the problem has compounded.
Board president’s escalation authority
The board president holds the escalation trigger.
Here is the authority every board president needs. The president can determine, in consultation with the superintendent and legal counsel, whether a data review finding rises to Level 2 or Level 3. The president can call a special session for Level 3 escalations without a full board vote, provided that notice requirements are met.
Here is the accountability that accompanies that authority. The president must document the escalation decision in writing within 24 hours. The written escalation notice includes: the data finding that triggered the escalation, the level assigned, the rationale, and the next steps. The full board receives the notice and can override the president’s level assignment by majority vote at the next regular meeting.
This balance of authority and accountability ensures that escalation happens quickly when it needs to but is never unilateral.
Boards that do not define the president’s escalation authority create two risks. Risk one: the president escalates everything and the board becomes crisis-driven. Risk two: the president escalates nothing and the board misses problems until they become emergencies.
Communication protocols during escalation
Escalation changes how the board communicates.
Level 1 communication is standard. Decisions are in the meeting minutes. The superintendent reports back at the next regular data review. No special communication needed.
Level 2 communication requires a written board directive. The directive is approved by the board at a regular meeting or via written consent. It is sent to the superintendent within 48 hours. The superintendent acknowledges receipt in writing and provides the timeline for response. The board president designates one board member as the communication point of contact for the duration of the escalation.
Level 3 communication requires an immediate special session. The session is called within 72 hours of the trigger. Legal counsel attends. Closed session is used only for the specific personnel or legal matters that require it — not as a blanket. The board issues a public statement only after legal counsel reviews. No individual board member communicates about the escalation without board authorization.
The worst communication pattern in an escalation is individual board members speaking publicly without coordination. That pattern undermines the superintendent’s authority, creates legal exposure, and erodes public trust. The protocol prevents it by requiring a single point of contact and a coordinated message.
Define your communication protocol before you need it. Your board will need it.
Your free CTA: Reply to this email with the keyword Escalate and I will send you the Escalation Protocol Template — a one-page reference with the three-level framework, trigger definitions, president’s authority scope, and communication protocol. Use it to adopt your board’s escalation policy before the next data review.
Your paid CTA: I offer an Escalation Protocol Design Session — a ninety-minute virtual session where I facilitate your board through defining the three-level framework, drafting the escalation policy language, and building the communication protocols. Your board leaves with a written escalation policy ready for adoption. Reply to this email for pricing and availability.
This is post 3 of 12 in “The Governance Operating Cycle: Fall Execution” arc running October through December 2027. The October sub-arc (Data in Motion) covers data review, budget alignment, escalation protocol, and progress monitoring cadence. The November sub-arc (Goal Alignment and Superintendent Partnership) covers mid-year accountability check, goal writing, superintendent check-in, and the Thanksgiving governance reset. The December sub-arc (Year-End Governance and 2028 Preparation) covers the organizational meeting, year-end review, goal adoption prep, and the 2028 lookahead. Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece builds on the three-decision protocol introduced in the October 4 post (“The October Data Review in Practice”) and the budget alignment triggers identified in the October 11 post (“Data Meets Dollars”). It connects forward to the Progress Monitoring Cadence post on October 25, which establishes the follow-through discipline that prevents routine issues from escalating. It anchors in the Governance Team domain of the ESB Framework — specifically the board president’s role in managing board process and communication.
Note to RedTeamer: This piece is part of the Fall 2027 governance arc (Oct-Dec). Voice fidelity target: newsletter/TESBM register — AJ’s instructional, direct-address cadence with short declarative openings, “Here is what” patterns, and coaching authority. Verify CTA keyword uniqueness across the full arc (keywords: OctInPractice, BudgetAlign, Escalate, Cadence, MidYear, ACTSgoals, SuptCheck, ThanksgivingReset, OrgMeeting, YearEndReview, JanGoals, 2028Priorities).