Why You Can't Just “Vote Them Out”: The Patchwork Problem of Fighting Local Government
If you've never had to fight your own city government, there's a piece of advice you'll hear constantly from well-meaning people who also haven't done it: "Just vote them out" or "Just recall them" or "Just sue them."
I've done all three, or tried to. Here's what nobody tells you going in: there is no single playbook. Not because the problem is complicated — the problem is depressingly simple — but because the system you're fighting is different in almost every single town in America.
There Is No "Local Government." There Are Thousands of Them.
Pennsylvania has boroughs. Wisconsin has towns, villages, and cities, each with different powers. Oklahoma only has towns and cities. Every state hands out different authority to its municipalities, every city charter draws its own lines around what the council can and can't do without a public vote, and every governing body is structured a little differently — different numbers of council members, different ward maps, different rules for special meetings, different thresholds for a recall.
It took me weeks — closer to months — just to fully understand our own city's charter, our council's structure, and the process by which decisions actually get made in Sand Springs. And once I understood it, that knowledge didn't transfer anywhere else. A resident in Ohio fighting a similar fight is looking at a completely different rulebook. A resident in Pennsylvania is looking at a different rulebook still.
That's the first, and maybe the biggest, reason there's no single tactic that reliably works against "wayward" local governments: no organization, no matter how dedicated, can be a deep expert in thousands of different sets of rules at once. The fight has to be relearned, from scratch, in every single town.
The System Isn't Broken. It's Working Exactly As Designed — Just Not For You.
Here's the part that genuinely shocked me once I understood it: local governments and the officials who run them are protected by statute, both as a municipality and as individuals, from most of the consequences of even a clear-cut violation of the law. If a city breaks its own ordinances, breaks state statute, or runs roughshod over its own charter, the primary check on that behavior is the very citizens who pay the taxes that fund the city — who then have to raise money, out of pocket, to sue the government they already fund, on the off chance a court agrees with them. And even when citizens win, there's rarely any punitive consequence for the municipality. No real disincentive. The city gets to act first, and it's on the residents to catch up, with their own money, in a fight most communities simply don't have the resources to sustain.
Now layer this on top: in many annexation and zoning fights, the people most affected by a decision — landowners just outside the city limits, for instance — don't get a legal vote in the city elections that produced the officials who made that decision. We tried to prove that shouldn't matter by building a coalition of city residents and outside neighbors during our recall effort. It still wasn't enough to overcome a charter that appeared deliberately engineered to make a successful recall nearly impossible.
None of this is an accident of poor design. It's the predictable result of a system built with almost no meaningful accountability built in — and that's precisely why "just vote them out" or "just recall them" sounds like sound advice and, in practice, so rarely works.
What "No Active Effort to Encourage Participation" Actually Looks Like
The room where it happens — usually with almost no one in it. When notice goes out at the last legal minute, empty seats are the point, not the accident.
This isn't abstract. Here's what it looks like on the ground, and it's a pattern that repeats itself in council chambers across the country, not just around data centers — around zoning changes, ordinance passage, budgets, appropriations, anything a council would rather not have a packed room asking questions about:
•
Meeting notices posted at the last legally permissible minute — sometimes for special meetings scheduled specifically because they know a topic is contentious.
•
Minimal supplemental documentation attached to agenda items that involve real money and real consequences.
•
Public comment capped at three minutes per person, regardless of the complexity of what's being decided.
•
No audio or video recording of meetings, and no transcription — meaning there's no record of what was actually said, only what someone chose to write down afterward.
•
Minutes that are functionally a copy of the original agenda with a roll call and a vote tally bolted on — no record of discussion, no record of who said what, no record of concerns raised and dismissed.
•
Liberal use of executive session to move substantive conversations behind closed doors, sometimes in ways that may not hold up to legal scrutiny once the process is actually examined — something we may find out more about as discovery proceeds in our own litigation.
Add it up and you get a governing process that could not be less transparent if it were deliberately designed to keep citizens out. In our case — the fight over Project Spring, a proposed hyperscale data center here in Sand Springs, Oklahoma — every one of these patterns showed up. But I want to be clear: this isn't a story about one data center in one Oklahoma town. This is one example out of what is likely thousands of similar situations playing out in city halls across the country, on issues that have nothing to do with data centers at all.
So What Actually Works?
Given all of that, is there anything a community can do? Yes — but it rarely looks like a single silver-bullet tactic. It looks like combining several imperfect tools at once: open records requests to get the paper trail the minutes won't give you, organized and funded legal action when the law has actually been broken, sustained public pressure and turnout at every single meeting, and — critically — knowing far enough in advance that a decision is coming that you actually have time to mount a response, instead of getting two weeks' notice against a proposal that took developers eight months to prepare.
That last piece — the information gap — is the one piece of this puzzle that technology can actually help close. It's also the specific gap MuniWatch was built to close: watching the agendas and minutes so residents find out about the next contentious vote in real time, not eighteen months after the fact.
We're not naive enough to think a notification service fixes a system with this little built-in accountability. That takes real legislative reform — the kind that returns local government to the original American ideal: of the people, by the people, and for the people, with citizens' eyes wide open instead of blindfolded by design. That's a fight MuniWatch intends to be part of as we grow. But step one, for any community, is simply knowing what your government is doing before it's already done.