Policy vs. Practice: Where Governance Actually Breaks Down
Every district and every independent school has a policy manual sitting somewhere. A binder, or more likely a shared drive folder these days, with a section nobody has reread since it was written. Buried in there is the board’s actual governing document: how decisions are supposed to get made, who talks to whom, what channel a concern is supposed to travel through before it lands on a meeting agenda.
Almost none of that is what actually runs the board on a Tuesday night.
Policy describes intent. Practice is what happens when a vote splits and nobody saw it coming. It’s a parent calling a board member’s cell phone instead of going through the front office. It’s a superintendent who needs an answer before the next scheduled meeting, not two weeks from now. The distance between the written version and the lived version is where most governance conflict actually starts. Not in the manual. In the gap.
Nobody sits down and decides to ignore policy. That’s not how it happens. A board handles one urgent situation outside the normal channel because the normal channel was too slow that week. It works out fine. So it happens again. Eventually the workaround is just how things get done, and six months later, nobody in the room could tell you which version, written or practiced, is actually real.
Communication tends to go first. The manual says concerns route through the president or the superintendent’s office. In practice, board members take the calls and answer the emails directly, form an opinion before the full board even discusses it, and sometimes commit to a position they didn’t mean to commit to. That’s not really a policy failure. The policy was just never the thing actually running the room.
Decision authority goes next, usually under pressure. Written policy is normally pretty specific about what needs a board vote and what belongs to administration. Then a decision comes up that can’t wait for the next meeting, so the superintendent makes the call. The board doesn’t push back because the outcome turns out fine. It happens again the next time something’s urgent. Then one day it doesn’t turn out fine, and suddenly everyone’s arguing about who actually had the authority to decide in the first place.
And follow-through. Most boards have decent language about how disagreements should get handled: through the president, respectfully, no personal attacks in open session. What almost no manual says is what happens when somebody breaks that norm. So practice fills in the blank, differently every time. One instance gets addressed. The next one, somehow, doesn’t.
None of that makes the manual useless. It just means a policy manual is a record of what the board intended, not a description of what the board actually does. Mixing those up is where a lot of the trouble starts.
Fixing it doesn’t take a rewrite. It takes an honest look, before September gets moving, at where the written version and the practiced version have quietly split apart. Then a decision: does practice need to catch up to policy, or does policy need to catch up to what the board has actually learned works. Either answer is fine. Not asking the question is what causes the friction.
If you already know where your board’s policy and practice have drifted, that’s worth a real conversation before the year picks up speed.

