← Back to all questions

When the superintendent says "that's operational" or "we can discuss that privately" in a public meeting, your move is simple: hold the question open until the policy basis is named. Say something like, "I understand that's your call. Can you point me to the board policy that gives you discretion on this?" This works because it does two things at once: it respects the superintendent's role while asserting your board's right to know. Either the superintendent shows you the policy (and now you have something concrete to discuss) or admits there is none (and the board's authority stands unchallenged). Either outcome advances governance, not conflict.

The board's authority flows from policy it has adopted, not from managerial expertise, so when a superintendent calls something "operational," they're making a claim about where your authority ends. You're entitled to test that claim publicly. "Operational" is not a shield, it's an assertion about the policy framework, and the board oversees the policy framework. What you're really asking, when you push back politely, is whether the superintendent is acting within board-adopted policy or exercising unchecked discretion. If the decision rests on a policy the board approved, the board can discuss it in public, and if it rests on a policy the board has not seen, the board needs to see it.

Most board members either back down (training the superintendent that public deflection works) or push back in a way that feels adversarial (poisoning the working relationship). The mistake is thinking you have to choose between being respectful and being effective, but you don't. The skill is asking a question the superintendent cannot answer without either affirming the board's role or revealing a gap. A question like "What does board policy say about the timeline for this decision?" forces the superintendent to produce the policy (and now you're having the right conversation) or admit there is none (and now the board knows it needs to fill that gap). Either way, you win.

Sometimes the superintendent is right, and some decisions genuinely are operational - hiring a specific teacher, choosing a vendor, managing a bus route. When that's the case, accept it, but the superintendent bears the burden of showing you why. The phrase "that's operational" should trigger a follow-up question, not silent acceptance. If the superintendent can cite the specific policy giving them authority, thank them and move on, and if they can't, you've identified a governance gap. The goal is not to win a battle - it's to make sure the line between policy and operations is actually drawn where the board has decided to draw it.

1. When the superintendent deflects, ask: "Can you point me to the board policy that gives the district discretion on this?" This forces them to either cite policy or admit none exists.
2. If they name a policy, ask a follow-up: "Does that policy give you flexibility on timing, or is there a board-adopted standard?" This clarifies whether they're operating within clear parameters.
3. If they say there's no policy, respond: "Should the board consider developing one?" This shifts the conversation from confrontation to governance improvement.
4. In your next board work session, review the list of policies the superintendent has called "operational" over the past six months. Identify patterns - if the same topic keeps being deflected, that's a signal the board needs to clarify its own policy.
5. Meet privately with the superintendent before the next meeting. Say: "I want to understand where you see the line between policy and operations. Can you walk me through three recent decisions and the policy basis for each?" This builds shared understanding without public confrontation.

The board that consistently asks "where is the policy?" trains the entire organization that governance matters are not optional. The superintendent who learns that every deflection will be met with a calm policy question will either start bringing policy forward or stop using "operational" as a shield. Over time, this simple habit transforms vague authority into actual oversight.