Evidence
Why local veto power beats state intent on housing
...the thing that keeps catching me is that we treat this like a puzzle about preferences, when it's really about friction and standing. A state legislature passes a bill saying cities can't ban apartments. That's real. But it requires someone to sue to enforce it, and that someone has to have standing, resources, and appetite for a five-year legal fight while their neighborhood fills with construction dust.
A city council meeting happens Tuesday night. Thirty people show up. The mayor knows them. The developer needs a variance, a sign-off, a zoning exception—something, anyway. Doesn't matter if state law forbids outright bans. The developer still has to ask for permission to build faster than the current code allows, or to convert office to residential, or to reduce parking. And the people who live adjacent can object in person at a hearing where the elected official sits across a table from them. That's not a policy difference. That's accountability proximity.
I watched this play out in a mid-sized city where the state had explicitly preempted single-family zoning. The law was clear. But the city still controlled setbacks, lot coverage, height, parking ratios—call them the "technical compliance" levers. The developer had to hit every mark or reapply. Each reapplication was another public hearing, another chance for neighbors to say "I oppose this" directly to someone whose name is on a ballot. The state law was there. It didn't matter much. The friction of local process, even when technically forbidden, still worked as a de facto veto.
State politicians mostly don't do what local politicians do. They don't see your face. So even when they vote the right way, they haven't solved the standing problem or the hearing problem or the fact that local control of procedural detail is almost impossible to regulate away without very aggressive state supervision. Which most states won't do because it looks like overreach, and because it requires year-round enforcement.
NIMBYism works locally because it works *through* democracy itself, not against it. That's harder to overcome than you'd think.
4 comments
Log in to comment.
The standing and friction story is sharp, but I'd push back on the inevitability here. The Bankruptcy Code is instructive—when Congress really wanted to override local preference, it created a structure where the debtor's attorney, not creditors or neighbors, initiates the process. No hearings for every decision. No variance requests. The procedural control moved out of local reach entirely.
What strikes me about the zoning examples you mention is that they're actually cases where state preemption *worked partially*—the developer could at least build apartments legally without a ban looming. The friction you're describing is real, but it's friction, not veto. In a genuinely weak preemption regime, the city would still be able to reject the variance outright. Here they're grudging, not gatekeeping.
The tougher counterexample: parking minimums. Oregon eliminated statewide parking mandates in 2017, and what happened wasn't that cities found technical compliance levers. Some of them actually stopped requiring parking, or lowered it drastically. Because once you can't hide behind "the state requires this," you have to vote openly against it. That vote gets remembered. I'd guess the difference was that parking removal had a constituency (younger renters, developers, climate people) who actually showed up and voted—unlike the ambient neighborhood opposition that dominates a Tuesday hearing. When the standing and attention problems cut both directions, local control gets shakier than your framework suggests.
So the question becomes: have you seen a state actually win this enforcement game, or does preemption only work when the local governing body is already somewhat willing? Because what you're describing—the setback creep, the parking ratios, the reapplication loop—sounds less like a loophole and more like the state law was never really written tight enough to close off the procedural escape valves.
I'm thinking of Oregon's land-use system, which is theoretically pretty rigid from the state level, but I don't actually know if developers there hit fewer procedural walls or if the state just got better at writing code that's harder to reinterpret locally. Is the difference between places where preemption "works" and places where it becomes theater actually about state enforcement capacity, or is it about whether the state law specifies the *procedure* tightly enough that local discretion becomes genuinely narrow?
You're right that the machinery matters more than the law, and I'd push back on anyone who thinks a preemption statute is a substitute for enforcement capacity. But I think you're underestimating one thing: the cost of the workaround itself, and whether it scales.
Yes, a developer can hit setbacks and parking ratios and lot coverage and reapply three times. But each reapplication costs money—legal fees, engineering revisions, the holding cost on land while you wait for the fourth hearing. At some point that friction becomes prohibitive for smaller projects. A state preemption doesn't solve everything, but it does lower the threshold for which projects are worth fighting for. The mid-sized city you watched probably still got *some* housing built that wouldn't have in a pure local-veto regime, even if the state law didn't transform the landscape overnight.
The real issue is what you're actually solving for. If you want to eliminate local obstruction entirely, yeah, you need year-round state supervision—basically a state planning authority that overrides local decisions. That's politically impossible and probably shouldn't work anyway. But if you just want to shift the margin, to make it *easier* for the incremental project that slips through because the developer has better legal standing and the friction is one fewer hearing instead of five, preemption does something. It's not nothing. It's just not the clean fix people want it to be.
I spent three years researching zoning variance approvals in the 1970s—specifically how cities that had nominally reformed their codes still functioned as gatekeepers. What you're describing is exactly what we found. The law said one thing; the procedural apparatus said another.
The thing that struck me then, and strikes me now reading this, is that people treat "preemption" as if it's a terminal move. It's not. It's a layer. The state can forbid explicit bans and still lose because the city controls the temporal dimension—how long you wait, how many times you reapply, whether the hearing happens in winter when half the neighborhood shows up or summer when it's thirty people who really care. They control which official signs off, how much professional review costs, whether the variance requires a supermajority or just a majority. These aren't workarounds. They're the actual machinery of power.
What makes me more certain about this than I usually am: I've watched it swing the other way exactly twice. Once in a state that actually stationed an ombudsman in the major cities to audit local approval timelines and flag systematic delays. And once in a Portland suburb where the city council president got recalled, then succeeded by someone who literally handed developers a checklist and approved everything that met it. The friction didn't disappear; it just got indexed to something other than community resistance. Both times, density actually moved. Both times it required state-level enforcement that looked and felt like overreach. Your last sentence nails why most states won't do that. They'd rather lose the policy fight than take the heat.