land-use-strategies

The Quiet Approval Is the Expensive One

Tue, 21 Jul 2026 20:26:25 GMT

BP's Lightsource bp is moving its Big Bronco solar-and-storage project forward in Adams County, Colorado. The project totals roughly 300 megawatts of solar paired with 300 megawatts of battery storage and is backed by a reported $675 million in private investment. Public figures estimate $39 million in new local tax revenue and about 400 jobs at peak construction. By most accounts, it has been a smooth ride: willing landowners, a site that steers clear of sensitive areas, and little of the organized community opposition that stalls so many energy projects.

Read casually, it's just another big solar farm getting built. Read the way we read these things, it's a case study in how projects actually get approved.

“Uncontested” is not inherited

A project that looks this easy is almost never easy. “Uncontested” is not a condition a developer inherits; it's an outcome they manufacture. Every box Big Bronco quietly checks is a box where energy projects normally lose.

Private funding neutralizes the first and loudest attack in almost every energy fight: who's really paying for this. Careful siting, away from sensitive habitat, prime viewsheds, and the parcels neighbors care most about, removes the environmental coalition's easiest hook. Landowner buy-in kills the “outsiders imposing on our community” narrative that supplies most of the emotional fuel for NIMBY campaigns. And pre-committing real dollars to local schools and county services does something subtle but decisive: it creates a constituency with something to lose if the project dies.

Opposition organizes around grievance

After thirty years of this work, we can tell you what opposition actually needs to get off the ground: a grievance and a villain. A packed, hostile hearing room is rarely the start of a fight; it's the visible end of one that's been building for months. Remove the grievances early, and there's nothing for an opponent to organize around. No villain, no rallying cry, no email list.

There's a corollary that developers consistently underestimate: support is silent by default. The neighbors who are fine with your project, or even glad for the tax base and the jobs, have no reason to spend a Tuesday night at a public hearing. Opponents always do. So an unmanaged process doesn't produce neutral turnout; it produces a lopsided one, where the three loudest objectors sound like the entire community. Manufacturing a clean approval means giving your quiet supporters a reason and a way to be counted, so the public record reflects reality rather than just the anger in the room.

That's why the Big Bronco hearing looks boring. The real work happened long before it, off-camera, one conversation at a time, in living rooms and county offices. What looks like a lack of strategy is the strategy.

Don't learn the wrong lesson

There's a trap in a story this clean, and it's worth naming. It's tempting to conclude that “solar in rural and Front Range counties is easy now.” It isn't. Adams County and the surrounding counties are precisely where the next generation of land-use fights is heating up: farmland-preservation ordinances, glare and viewshed complaints, decommissioning-bond demands, and moratoria that land on a planning commission agenda with almost no warning.

Big Bronco is a template, not a guarantee. The developers who assume the next project will glide through as this one did are the same ones who skip the pre-work and end up in a packed hearing room, wondering what went wrong.

What a developer should actually do

If you're planning a solar, storage, or other energy project where local sentiment could decide your fate, treat the quiet approval as something you build, not something you hope for:

Map the grievance landscape before you file, not after. Know who is likely to object, and why, while you can still design around it.
Lock in landowner and adjacent-neighbor alignment early. The parcels next to your site often matter as much as the one you're leasing.
Pre-load the benefit story with a real constituency. Jobs, tax revenue, and school funding only protect you if the beneficiaries hear it from you before they hear the objections from someone else.
Site defensively. Distance from sensitive and highly visible land is almost always cheaper than fighting a coalition you could have avoided.
Show up in the community before there's a hearing to show up to. Relationships built under pressure are worth a fraction of the ones built early.

None of this is glamorous, and none of it makes the news. That's exactly the point. The quiet approval isn't the cheap outcome; it's the expensive one. You pay for it up front, in disciplined pre-entitlement work, rather than paying for it later through delay, litigation, and stranded capital.

The bottom line

Every project that never makes the headlines represents a fight won before it even started. If you're considering a site where community sentiment or local politics could make or break your timeline, that is the work we do. The best time to start is before anyone has a reason to oppose you.

Use It or Lose It: The Entitlement Risk You Can't Read Off the Permit

Tue, 07 Jul 2026 22:04:05 GMT

In Central Oregon, the Deschutes River lives two lives. The stretch through Bend looks healthy. A mile or two downstream, roughly ninety percent of it vanishes into pipes and canals. A recent investigation by OPB and ProPublica followed the water to determine where it goes and who benefits.

The answer is a study in leverage. One of the region's oldest and most powerful irrigation districts holds senior claims that allow it to divert about half the river's summer flow. But according to the reporting's satellite analysis of what plants actually absorb, only about one gallon in four of that diversion is consumed by crops. The rest keeps sprinklers turning over lawns and pasture on some of the least productive and most expensive land in Oregon. Forty miles downstream, a farmer with junior rights shut down a once-thriving potato business because the water never reached him.

The coverage frames this as a matter of fairness: haves and have-nots, a century-old law that turns the desert green for a few while others go dry. That's the right story for a newsroom. It's not the one a developer or project sponsor should walk away with.

The doctrine that does the real work

Western water runs on prior appropriation, "first in time, first in right." Whoever holds the oldest claim gets served first when supply runs short. That part is well known. What's less understood is the quieter doctrine underlying it, the one that actually governs whether you keep what you hold: beneficial use without waste.

To retain a water right, you must keep using the water in the manner your right specifies, without wasting it. Stop using it, and you can lose it. It is, in the most literal sense, use it or lose it.

Here is the part worth studying. Nobody has actually defined the standard. Oregon courts have almost never ruled anything "waste." One law professor quoted in the reporting compared the legal test to the old line about obscenity: you know it when you see it. In practice, the state almost never sees it. Involuntary cancellations of unused rights occurred in four of every five years. Meanwhile, the district has sent more than a thousand letters since 2020 telling landowners the opposite: irrigate that dry patch, or risk losing the right.

Set the fairness question aside and look at the machine. It says something about every entitlement that seems permanent.

A vague standard is not neutral risk

The intuitive read of an undefined standard is that it hangs over everyone equally; anyone could, in theory, be found wasteful. That is not how it works.

An undefined standard is enforced through discretion, and discretion follows power. The senior rights holders with the political weight to make reform untouchable are not the ones whose claims are canceled. Two state legislators told the reporter, on the record, that taking on this system would end their careers; one said flatly they'd "get crushed." When the people who benefit from a rule are also the ones who can end your political career for changing it, the standard doesn't apply everywhere. It points downhill, toward whoever has the least power to redefine it.

That is the first thing a vague standard does: it converts an ambiguous rule into a predictable one, just not on the terms written down. The rule on paper applies to everyone. The rule as enforced applies to the weak.

The right is a condition, not a possession

The second reframe is the useful one. The district's water right is not something it owns outright, the way you own a car. It is a continuing obligation to perform "use" under terms someone else can reinterpret. The moment it fails to meet the standard, the asset is exposed.

That structure covers far more than water. A conditional use permit with performance conditions. A development agreement with milestones and clawbacks. An incentive package tied to job counts or build-out dates. A variance granted on the assumption of a stated use. An air or discharge permit with operating parameters. In each case, winning approval doesn't hand you possession; it hands you a maintenance obligation, measured against a standard you don't control and judged by a party whose incentives may drift.

Approval feels like the finish line. It's closer to the terms of a lease you have to keep re-earning.

Ambiguity accrues to the incumbent

Put those together, and you get the third lesson, where the real money and the real risk both live. When a rule is undefined, the contest is never actually "what does the rule mean?" It's "who gets to decide what it means, and where do I sit relative to them?"

Incumbents love vague standards because they can define them in their own favor and direct them at challengers. Oregon's outcome is the perverse proof: a doctrine built to reward productive use now rewards visible use, sprinklers running to defend a claim, whether or not anything grows. Landowners told the reporter they have every incentive to use more water than they need and none to use less. They are not being irrational. They are reading the enforcement pattern correctly and acting on it. The stated purpose of the law, to develop rural economies and put water to productive use, has become fully detached from what the law now does, which is to protect the least productive land in the state.

That gap between what a regime says it's for and what it actually does is the single most important factor to price. Read the mission statement instead of the enforcement record, and you will misjudge the position every time.

What to do about it

For anyone holding or chasing an entitlement, the takeaways are concrete.

Underwrite the maintenance conditions as carefully as the approval itself. Before you celebrate a win, ask what ongoing performance the right assumes, on what standard, judged by whom, and how often that judgment is exercised.

Treat every undefined standard as a power question, not a legal one. Map who holds discretion over it and what their incentives are. "Nobody enforces this" is not the same as “this is safe.” It means the standard is dormant, and dormant standards wake up when the politics change.

Watch the pattern, not the text. Four cancellations in five years tell you more about your true exposure than the statute’s language does. If you're the incumbent, that pattern is your moat. If you're the challenger trying to pry water or approvals, or access loose, that pattern is what you actually have to move, and you don't move it by being right. You move it by changing what the decision costs the person with the discretion.

The through-line in most of what we do: winning approval is the start of the position, not the end of it. If you're holding or pursuing an entitlement whose value rests on a standard someone else gets to define, that's a conversation worth having before someone else defines it for you.

When Reform Outran the Vote: A 15-Unit Building Becomes Pittsburgh's Test Case

Thu, 02 Jul 2026 16:01:21 GMT

In Lawrenceville, a developer plans to build 15 apartments on a 3,300-square-foot lot on 49th Street, next to Stinky's Bar and across from the Locomotive Lofts. It's tiny by headline-making standards, yet it now faces a formal protest before Pittsburgh's Zoning Board of Adjustment, backed by a neighborhood attorney, a petition signed by more than 40 residents and businesses, and a 45-day decision clock. The trigger was not height or density, but the zoning administrator's decision to waive the parking requirement entirely, citing a reform ordinance the City Council has not yet passed.

That detail is the whole story, and almost everyone is stepping over it.

Here's what most people miss. On the surface, this is a parking fight: neighbors worry about cars, while the developer offers bike-share memberships instead of parking spaces. But parking is only the container. The reform package, which eliminates parking minimums, legalizes accessory dwelling units by right, and makes affordable housing incentive-based, won unanimous Planning Commission support in early June. It now returns to Council for a vote not expected until after the August recess. The administrator applied the logic of a proposed rule. The legislative branch has not acted; the administrative branch has.

For a developer, that gap is dangerous because it looks like a shortcut.

Administrative discretion is an attack surface, not a safe harbor. When an administrator grants an exception grounded in pending legislation, she makes a judgment call that a court can second-guess. That is what happened here. Opponents did not have to win the parking policy argument; they only had to show that the administrator exceeded the law in justifying this approval. A “by-right” approval feels certain. But when it depends on an unenacted rule, that certainty is provisional, and provisional entitlements invite litigation.

Parking was the only objection that could be raised about the project. The neighbors' grievance is broader than five spaces: the project arrived through an administrative exception that bypassed normal community development review. “We weren't consulted” is a real feeling, but not an appealable one. “The administrator misapplied the parking standard” is. The process complaint was poured into the one vessel carrying legal weight at the ZBA. The stated objection is rarely the whole objection; it is the one that has standing. Miss that, and you litigate parking counts while the real driver (a community that felt bypassed) hardens.

Reform didn't end the parking fight. It privatized it. Removing the requirement lifts the developer's obligation to provide parking. It does not remove the grievance. The street remains just as crowded. Reform shifts the burden from the code to the developer. Under the old regime, you built the required spaces, and the fight never started. Under the new one, you must persuade a skeptical room that bike-share and transit can substitute for cars, while “there is no parking” remains emotionally unbeatable and endlessly repeatable. The city changed the rule, not the street. That negotiation is now yours.

Approval was the midpoint, not the finish line. The exception opened a 45-day appeal window that may expire before Council votes on the ordinance. A zoning board could rule on the project before the new rule takes effect. Whatever the outcome, the developer now carries schedule risk, legal costs, and reputational friction into a neighborhood where it will operate for decades. The permit was not the destination but the ticket to the next phase of exposure.

So what should a project sponsor do?

First, treat “pending” as a red flag, not a green light. If an entitlement depends on an unenacted rule, price the timing risk honestly. An approval that outpaces legislation may be financeable on paper but fragile in practice. The cheapest and most durable paths are often different.

Second, don't let a procedural shortcut replace the political work. The exception was legally available but bypassed community review, a missing step opponents turned into a legitimacy argument. When the process does not require neighborhood engagement, that engagement is most valuable. A developer who convenes neighbors controls the narrative. One seen as avoiding them inherits a story it cannot rewrite.

Third, identify the real objection before building the record. If parking is the appealable proxy for a deeper grievance, answering only parking means fighting the wrong battle. Identify what the objection stands for and address it with the technical case. The proxy is litigated at the hearing; the real issue is resolved in the neighborhood. You need to win in both venues; only one runs on a 45-day clock.

None of this argues against parking reform, denser housing, or speed. Pittsburgh needs housing. Occupancy is above 90%, and small infill projects like this are what a healthy market should produce. The lesson is narrower and concerns sequencing: when the tools of approval move faster than the politics of approval, the developer inherits the gap. A 15-unit building in Lawrenceville is about to show an entire city what that gap costs. It is worth watching and planning for before you are the one being watched.

On Paper, It’s a Zoning Fight. In Practice, It’s Leverage.

Wed, 24 Jun 2026 16:10:48 GMT

What Arizona’s development battles reveal about the opposition every developer is about to face.

For years, the Phoenix metro has been shorthand for a builder-friendly market: fast permits, pro-growth councils, and room to move. That reputation is now colliding with a string of high-profile fights. An advocacy group called Worker Power, tied to a hospitality-workers union, has helped force major Valley projects onto the ballot, from a Glendale resort to a Scottsdale corporate headquarters to a Tempe sports-anchored entertainment district. In several of these cases, the city council had already said yes, sometimes unanimously, after a full public process. The approval didn’t end the fight. It started the next one.

It would be easy to file this under “community opposition is getting louder.” That read is true, but it misses what actually makes these fights different and why they're a preview rather than a one-off.

The overlooked issue

The objections on the record are rarely the grievance driving the fight.

In these Arizona cases, the stated concerns have been a rezoned parcel once used for park space, water discharge from a man-made beach, a tax-incentive amendment, and light and noise. Real issues, all litigable on their merits. But the developers and city officials on the receiving end have publicly described the group’s actual interest as something else entirely. Leverage to organize the project’s future workforce. The zoning fight, in their telling, isn’t about zoning. It’s the venue. The land-use process is simply the most powerful pressure point available, so that’s where an unrelated demand gets applied.

This is the part developers consistently get wrong. When you assume your opponent cares about the thing they’re objecting to, you respond by fixing it. You redesign the discharge plan. You adjust the lighting. You commission the traffic study. Months disappear. The opposition doesn’t soften because you spent that time solving a problem that was never the obstacle. You can’t satisfy a proxy by perfecting the thing it’s standing in for. The real ask is at a different table, and until you find that table, every concession you make is wasted motion.

The approval is no longer the finish line

The second shift is procedural, and it’s the one that should reset how every sponsor scopes a project timeline.

A favorable vote at the dais used to signal that the political risk was behind you. In an increasing number of jurisdictions, it now means you’ve cleared phase one. Direct-democracy tools such as referenda and initiatives allow an organized group to take a council’s decision and put it back before voters, even after unanimous approval and a clean public record.

In Scottsdale, opponents gathered tens of thousands of signatures to send a headquarters rezoning to a referendum. In Glendale, a petition drive collected enough signatures that the city ultimately repealed its own incentive action rather than fight an election. In Tempe, a project that had cleared its approvals was sent to the ballot and lost.

Notice what that does to your risk model. The hearing is no longer the moment of maximum exposure. It’s the opening move. Your real test may come weeks or months later, in a low-turnout special election, when your opponent has a motivated base, and you have only a press release. If you treated the council vote as the win and stood down your coalition, you would walk into that election with nothing built.

And here’s the uncomfortable irony for builder-friendly markets: the states with the strongest pro-business reputations in the West – Arizona, California, and Colorado – also tend to have the most robust ballot-initiative and referendum traditions in the country. The same civic machinery that makes a place feel open and participatory also hands organized opponents a second bite at every approval. “Business-friendly” and “procedurally exposed” are not opposites. In these markets, they’re the same trait viewed from two angles.

It’s worth saying plainly what this is and isn’t. This isn’t a story about one union, one party, or one coast. State legislatures and governors from both parties have intervened, sometimes to override these referendums, sometimes to defend them. That tells you the tactic doesn’t belong to a political side. It belongs to whoever learns it first. Treating it as a culture-war grievance is itself a strategic error: it hands your opponent the mobilization narrative they want and shrinks your own coalition to those who already agree with you. The disciplined response is clinical, not tribal.

What a developer or sponsor should actually do

If your project has a workforce footprint, a public incentive, or any concentrated stakeholder who wants something from you, assume the land-use process can be turned into leverage against you. Then prepare accordingly.

DIAGNOSE THE REAL ASK BEFORE THE FIRST HEARING. This is what opposition research is for. Map who benefits from the delay and who has an unrelated demand, such as a labor organization, a competitor, an adjacent owner, or a group seeking a policy concession. Identify the table where the actual fight lives. You cannot negotiate a settlement you haven’t located.

DON’T LITIGATE THE PROXY. When an objection is a stand-in, resolving it on the merits buys you nothing and costs you months. Address the genuine community concerns because it’s right and it builds your record, but don’t mistake that work for resolving the opposition.

SCOPE ENTITLEMENT AS A TWO-PHASE CAMPAIGN. Plan for a hearing phase and a possible ballot phase from day one. Know your jurisdiction’s referendum window, signature thresholds, and which actions (rezonings, development-agreement amendments, incentive votes) are most exposed. Sequence your approvals to minimize the surface area an opponent can put on a ballot.

BUILD A BASE YOU CAN ACTUALLY ACTIVATE. Genuine, visible community support, residents who will sign, testify, and turn out, is your only real defense in a referendum. That support has to exist before a petition drops, not be assembled in a panic after. Earned validators, a real coalition, and a turnout operation are entitlement infrastructure now, not campaign luxuries.

RETIRE THE WORD “SAFE.” A friendly council is necessary and no longer sufficient. The most pro-growth markets in the country are precisely where this playbook is being refined, because that’s where the procedural tools are richest. Plan as if your easiest market is your most exposed one.

The bottom line

The fight that decides your project increasingly isn’t the one on the agenda. It’s the one beneath it, and it may not be resolved until voters weigh in, long after the council says yes. Developers who keep treating entitlement as a permitting exercise will keep getting surprised. Those who treat it as a political campaign, with a real coalition and a plan for the ballot, are the ones still standing when the special election is over.

That’s the work we do. If your next project is in a market where approval might be the opening move rather than the closing one, it’s worth a conversation before the first hearing, not after the petition lands.

When “Just Tear It Down” Meets the Zoning Code

Mon, 15 Jun 2026 17:36:43 GMT

The Denver demolition debate isn’t really about wrecking balls. It’s about who bears the political risk of a vacant lot, and that’s a question developers must answer before the first permit.

A growing chorus of Denver real estate experts has settled on a blunt fix for the city’s emptiest office buildings: stop trying to save them and knock them down. With downtown office vacancy near 39%, and roughly 47% for the older Class C stock nobody wants, boosters argue that clearing prime land for something new is “a once-in-a-few-generation opportunity.” The Denver Business Journal even identified about a dozen buildings that match the profile demolition advocates describe: smaller floorplates, few amenities, high vacancy, and no historic protection.

Then the mayor’s own point person on downtown said no, and the reasons he gave are the whole story.

Here’s what most people miss

The demolition debate is framed as economics versus sentiment: hard-nosed developers who can do the math versus nostalgics “attached to keeping what was there forever.” That framing is a trap, and it’s the wrong one to walk into.

Because the city’s representative didn’t object on sentimental grounds, he objected on process and tax base grounds. Denver’s zoning doesn’t allow a cleared downtown lot to be used for surface parking. A demolished building reduces the property tax base during the gap between teardown and whatever comes next. A gap that can run for years. And the city has live leases and operating tenants in the very properties advocates want flattened. His conclusion: it’s “against the city’s best interest to see property torn down, because the buildings are worth more than a vacant lot that can’t even be used by zoning for parking.”

Read that again, because it’s the most important sentence in the entire debate. The thing that kills the teardown isn’t construction cost. It’s the code and the political incentives wired into it. A city official who watches the tax base dip on his watch, fields complaints from

displaced tenants, and stares at a fenced-off dirt lot on Denver’s marquee street for 36 months has every reason to slow-walk the whole idea. The economics may pencil for a developer. The politics actively punish the public official who has to sign off.

That gap, between what’s financially rational for a sponsor and what’s politically survivable for the decision-maker, is where land use projects live or die. It is the entire game.

The pattern we see again and again

We’ve spent 30 years on the entitlement side of fights exactly like this one, and the Denver story is running a script we know cold.

The “obviously good idea” attracts opposition precisely because it’s dramatic.

A conversion is quiet. A demolition is a spectacle, and spectacle organizes opposition. Preservation-minded residents, tenants facing relocation, neighbors bracing for months of dust and street closures, and the “why are we doing favors for developers” crowd don’t share a worldview, but a wrecking ball gives them a shared event to rally around. One side of this debate has already supplied the rallying cry: tearing down buildings is “not healthy for a city.” That line will show up on a flyer.

The decision-maker’s real calculation is rarely the one stated in the hearing.

Officials will talk tax base, zoning, and process – all legitimate. But underneath sits a simpler question: what happens to me if I say yes and it goes wrong? A half-built lot that stalls when financing dries up is a visible monument to a bad vote. Until a sponsor answers that personal-risk question for the official with a credible plan, a realistic timeline, and political cover, “no” is the safe default, and safe defaults win.

Existing tenants and leases are an opposition coalition that already exists.

You don’t have to wait for opponents to organize when the building is full of them. Every operating business in a teardown candidate is a sympathetic local story, a potential plaintiff, and a reason for a council member to hesitate. Smart sponsors map that coalition before they option the property, not after the application is filed.

Zoning that blocks the interim use quietly blocks the whole project.

The rule that a cleared lot can’t be surface parking sounds like a technicality. It isn’t. It means the land generates almost nothing during the dead zone between demolition and redevelopment, which weakens the financial case, lengthens the timeline, and widens the window for opposition and for a council to get cold feet. The interim-use question is a political question wearing a zoning costume.

What a developer or sponsor should actually do

If you’re looking at an underperforming office asset, in Denver or any downtown running the same play, the teardown-versus-convert decision is the easy part. Sequencing the politics is the hard part. A few moves that consistently matter:

Pressure-test the politics before the pro forma is final.

Know where the mayor’s office, the council member of record, and the downtown authority stand before you’re committed. In Denver, the mayor’s representative is already on record as opposed. That’s not a detail to discover at your hearing; it’s a starting condition that should shape your entire approach.

Solve the interim-use and timeline problem out loud.

The bottom line

Reframe the story from “demolition” to outcome.

The moment public money or public land enters the picture, and the Denver downtown authority is already “doling out millions” for conversions, you’ve created a populist target. Get ahead of it with a clear public-benefit case, or watch it get defined for you.

Neutralize the “subsidizing developers” line early.

Nobody rallies for a wrecking ball. People do rally for housing, for a safer block, for a downtown that’s alive after 6 p.m. If your project is described by its most disruptive phase, you’ve already lost the narrative. Lead with what replaces the building, not the act of removing it.

Identify the residents, employers, and civic groups who benefit from your project and give them a reason and a way to show up. An empty hearing room fills with opponents by default. A sponsor who has done the organizing changes who’s in the seats.

The official’s nightmare is a vacant lot that sits. Bring the answer to them: a phased plan, a financing structure that survives a downturn, an activation strategy for the gap, or a conversion alternative you can pivot to. Make the safe vote the one that says yes to you.

Build the coalition before the opposition does.

Denver’s experts are right that some of these buildings should probably come down. They’re also about to learn that “should” and “can” are separated by a public process that rewards caution and punishes the official who takes the leap. The demolition itself is boring, a floor-by-floor peel, no explosives. The real drama is the fight over whether it’s allowed to happen. That fight is winnable. But it’s won the way campaigns are won, by knowing the decision-makers’ real incentives, organizing support before opposition hardens, and giving the people who have to say yes a reason that protects them. That’s the work, and it starts long before anyone

files an application.

Land Use Strategies helps developers and project sponsors secure the public and political support required for entitlements. If you’re weighing a conversion, a teardown, or any project where local politics could be the deciding factor, we’re happy to talk through the terrain before you commit.

When the State Clears the Path, the Community Still Owns the Ground

Wed, 10 Jun 2026 23:07:14 GMT

Arizona’s Senate has advanced a bill that would let small modular nuclear reactors be sited next to data centers and on retired coal sites across the state’s rural counties without those counties’ zoning approval. The legislation strips local supervisors of the authority to use land use rules to block the plants, and it’s written to allow a reactor to go in right next to any business with round-the-clock power demand. That’s a near-perfect description of a data center. The bill now awaits a vote in the House.

Read at face value, this is an energy story: faster power for the computing boom. We read it as something else, an entitlement story, and a cautionary one .

Here’s what most people miss. Preemption doesn’t eliminate opposition. It relocates it.

When the state removes a local government’s authority over a project, the instinct in a boardroom is to treat the fight as over. The hard permit is gone; the path is clear; build. But in 30 years of moving contested projects through hostile rooms, we’ve watched the same pattern repeat: opposition that loses its official venue does not dissolve. It migrates into channels that are slower, more expensive, and far less open to negotiation than the hearing you just skipped.

That hearing, for all its friction, was actually the cheapest place to resolve a dispute. It had rules, a record, a decision-maker, and an end date. Take it away and the energy behind the opposition has to go somewhere. Historically, it goes to four places: the courts, where a lawsuit can stall a project for years on procedural grounds that have nothing to do with the merits; the ballot, where a referendum can put your project in front of the very voters you bypassed; the adjacent permits a state law can’t preempt, water, air, road access, grid interconnection, environmental review, each of which becomes a new pressure point; and the next election, where the statute you relied on can be amended or repealed by a legislature that reads the room differently a year later.

This is the gap between legality and legitimacy . A preemption bill can hand a developer the legal right to build. It cannot manufacture the community’s sense that the project is fair, safe, and theirs to weigh in on. And legitimacy, not legality, is what determines whether a 24/7 power plant or a sprawling data campus gets built on schedule, on budget, and without the project becoming a years-long referendum on the company behind it.

The tell is already in the record. The state’s county supervisors’ association didn’t argue against the technology or even against the economic case. Their concern was about process — that energy infrastructure has historically been sited in collaboration with the residents who live next to it and the local officials they elect. That’s not a political objection. It’s the oldest lesson in our business: people will accept a great deal if they feel they were heard, and resist almost anything if they feel they weren’t. Opposition is frequently rooted in lived local experience, not ignorance, which means you cannot “educate” your way past a felt grievance. You have to engage it directly, with real answers and real people, before the concrete is poured.

So what should a developer or project sponsor actually do?

First , treat a preemption win as the opening of your community engagement window, not the closing of it. The political capital you have is highest the moment the bill passes and lowest the moment a crane shows up unannounced. Spend it on relationships, not on speed.

Second , map the veto points that survive preemption. Removing county zoning authority does not remove the courthouse, the ballot box, the interconnection queue, or the air and water permits. Build a risk map of every approval, challenge, and decision-maker that still stands between you and operation, and resource the ones that can actually stop you.

Third , engage the local board even when you no longer legally have to. A county board that feels bypassed and humiliated becomes a permanent, motivated adversary with a long memory and a public microphone. A board that feels respected, invited in, briefed early, given a real role even within the limits of the new law, is the cheapest insurance you can buy. The statute may say you don’t need their vote. Your timeline still needs their goodwill.

Fourth , build the local coalition before you need it. The people who benefit from a project are almost always quieter than the people who fear it, and they stay quiet unless you organize them. A large data center can generate tens of millions of dollars a year in local property taxes, money that funds schools, fire, police, roads, and water systems. But a number in a press release persuades no one. Connect the benefit to the specific institutions residents care about, recruit the local employers and trades who gain from construction, and identify credible local validators who will speak before the opposition fills the silence.

Fifth , get ahead of the concrete fears with specifics, not gloss. In energy siting, the recurring anxieties are predictable: safety, waste, water draw, traffic, and the long shadow of past industrial harms in the region. Vague reassurance and glossy mailers read as spin and deepen distrust. Direct, technical, locally delivered answers from people the community recognizes are what move a skeptical room.

The opportunity here is real. The demand for reliable power to support the data infrastructure the country is racing to build is not going away, and the sponsors who can pair the right energy source with the right site will have a genuine advantage. But the advantage goes to the teams who understand that clearing the legal path is step one, not the finish line. The project still has to live in a community for decades. The companies that win are the ones who start earning that welcome long before they have to.

A legislative shortcut can solve a permitting problem. It can just as easily create a legitimacy problem that costs far more than the hearing it replaced. The smartest move available to any sponsor watching this bill is to plan for both — to win in the statehouse and win in the county .

That second campaign is the one we run.

If you’re developing energy or data center projects in a market where the politics are shifting and the community response is uncertain, let’s talk about what the path actually looks like on the ground.

Power Gets You a Site. Politics Gets You a Project.

Fri, 05 Jun 2026 16:16:31 GMT

THE LUS TAKE | DATA CENTERS

Across the country, data center developers are learning a hard lesson the rest of the land use world internalized decades ago: you can do everything right on paper and still lose at the podium. Communities from suburban Pennsylvania to the outskirts of Duluth are increasingly defeating data center proposals – not on engineering grounds, but on political ones.

One AI security project counted roughly $98 billion in projects blocked or delayed across 11 states in a single quarter, about two-thirds of the total it was tracking. Microsoft now lists “community opposition, local moratoriums, and hyper-local dissent” as an operational risk in its securities filings. The backlash has evolved from a local nuisance to a balance-sheet line item.

Here’s what most people in the industry miss. These projects aren’t dying because the numbers don’t work. In the Charlotte suburb of Matthews, North Carolina, a data center would have funded roughly half the city’s budget, and the developer brought environmentally friendly design features. It still got pulled before a vote, and the mayor said it would lose “999 to one against.”

A development team can show up with tax revenue, water-conservation commitments, and a willing power source, yet still walk away with nothing. When that keeps happening, the problem isn’t the project. It’s the approach to securing approval for it.

The fight is political, so treat it that way.

Data centers have quietly become the most contested land use in America. A 2026 Gallup poll found that about 70 percent of Americans oppose building a data center in their own neighborhood, a level of resistance higher than that for new nuclear plants. And unlike most land-use fights, this one crosses party lines.

On the left, the objection is environmental: water draw, emissions, and the diesel generators. On the right, it’s the tax abatements and the sense that a trillion-dollar company is receiving a public subsidy. Rising electric bills and grid strain unite both sides. That breadth is exactly what makes the opposition durable. A coalition that spans the political spectrum doesn’t fracture the way a single-issue group does.

What we see again and again in contested entitlements is that opposition isn’t a mood, it’s an organization. Residents who feel blindsided find each other online, order yard signs, learn to navigate the public-comment period, and file the records requests that surface in every internal email. In Hermantown, Minnesota, neighbors discovered that state, county, city, and utility officials had known about a massive proposed campus for roughly a year before the public did.

The substance of the project mattered less than the secrecy surrounding it. As one resident put it, the secrecy drove people crazy. Once a community feels it has been handled rather than consulted, no amount of late-stage generosity can buy back trust. Opposition doesn’t disband when you finally show up with a good offer. It hardens into a permanent process: appeals, lawsuits, moratoriums, and a council that knows a yes vote ends its career.

This is the trap many developers are walking into right now. The instinct is to lock up the scarce, valuable asset first – the power interconnection – and treat zoning and community sentiment as paperwork to clear later. One developer told the Associated Press that firms are now considering selling sites the moment they secure power, because they’ve realized the interconnection is worthless if the project can’t survive the room. That’s the whole point.

Secrecy doesn’t buy time. It builds the opposition. The site with power and no community support isn’t an asset. It’s a liability with a substation attached.

What a developer should actually do.

If you’re building data centers or any other energy-intensive, large-footprint facility, the engagement playbook can no longer be an afterthought bolted on after the application is filed. It has to be the spine of the development strategy from site selection onward. A few principles we’d apply to a project like this:

Engage before you need anything.

The most common mistake is treating community outreach as a box to check right before the hearing. By then, the opposition is already organized, and you’re playing defense on their terms. Real engagement starts before the rezoning petition exists, when you can still shape the conversation rather than react to it. Water utilities in the UK have been blunt about this: water is considered last when it should be at the forefront of early thinking. The same is true of community sentiment.

Do the opposition research on yourself.

Before you file, you should know exactly who will oppose this, why, and what they’ll say – the water, ratepayer, property-value, and noise arguments. Map the likely coalition the way a campaign maps the opposing electorate. You cannot address concerns you haven’t anticipated, and “their concerns are baseless” is not a strategy. It’s how you lose a room.

Make transparency a weapon, not a vulnerability.

The industry’s reflex toward non-disclosure agreements and unnamed “Fortune 50” clients is actively manufacturing the distrust that kills projects. When the only way residents learn what’s coming is through a public records request, you’ve handed your opponents the most powerful message they have. Get ahead of it. Disclose water and energy figures on your own terms and in your own framing before someone else frames them for you.

Build a coalition, don’t just rent a podium.

Winning the council isn’t the same as winning the community. Matthews proved that a unanimous-looking staff recommendation means nothing in the face of an overwhelmed inbox. You need real local validators: businesses that benefit, labor that builds it, ratepayer protections that neutralize the bill-increase argument, and community benefits that are specific and enforceable rather than vague and promised. Localize the upside, because right now the tax revenue lands in one jurisdiction while the water draw, the generators, and the higher utility bills spread across the whole region. That asymmetry is the opposition’s best talking point. Take it away from them.

Control the narrative before the records request does.

Every contested project tells a story. The only question is whether you’re telling it or your opponents are. The developers who lose these fights are the ones who let “secret deal with Big Tech” become the story while they stayed quiet and hoped the economics would speak for themselves. They never do.

None of this is unique to data centers. It’s the same discipline that decides contested housing, energy, and infrastructure entitlements everywhere, with earlier engagement, honest opposition research, a real coalition, and a narrative you actually drive. Data centers are simply the newest arena where developers are discovering that securing the land and the power is the easy part. Securing public and political permission to use them is the work.

At Land Use Strategies, we run pre-entitlement campaigns for exactly these situations – energy-intensive, high-opposition projects where local sentiment can decide the outcome before the engineering even gets a hearing. If you’re siting a data center or any large facility in a community that’s paying closer attention than it used to, it’s worth a conversation about how to win the room before the room organizes against you.

'Transparency Before Transformation': Why Lakewood's Backlash Should Worry Every Developer

Tue, 02 Jun 2026 19:39:24 GMT

This spring, Lakewood voters did something developers should not ignore: they repealed the city's first major zoning overhaul in more than a decade. The code update would have expanded housing types and affordability across the city. Voters rejected it outright.

Now the grassroots group behind that win, the Lakewood Citizens Alliance, is going a step further by filing for a November charter amendment that would permanently require more public notice and community engagement before any large-scale rezoning.

They call the principle "transparency before transformation."

Most of the coverage frames this as a housing fight or a win for community voice. From where we sit, it's something more instructive and more dangerous for the development community: it's proof that organized opposition, once it wins, doesn't go home. It hardens into a permanent process.

The city didn't lose on the merits. It lost on the politics.

By most technical measures, the repealed code was sound policy: more housing options, more affordability, the first modernization since 2012. None of that saved it. It was defeated because residents felt the change was happening to them rather than with them. When people believe a major decision about their neighborhood is being made over their heads, the proposal's technical quality becomes irrelevant.

They don't argue the zoning tables. They organize.

And here's the part developers often miss: that single defeat is now becoming durable infrastructure. The same coalition that killed the code is now rewriting the city charter so that every future legislative rezoning requires more notice, more hearings, and more friction. If it passes, the entitlement bar rises for every project that follows – including yours, even though you had nothing to do with the original fight. A community's anger over one decision becomes a structural cost you inherit at every subsequent hearing.

Notice the messaging discipline.

The Alliance has been explicit that it is not trying to stop growth or housing. Its frame centers on notice, trust, and "a greater voice." That is a sympathetic, almost impossible-to-attack position. In any campaign, the side with the simpler, more emotionally resonant message usually wins, and "we just want a say in what happens to our neighborhood" beats "this code update optimizes housing typologies" every time.

The city was selling policy. The opposition was selling trust. Trust won.

What this means if you're moving a project

A few hard lessons, particularly for anyone with residential or mixed-use work in a market like this:

You cannot outsource your political risk to city hall. When a jurisdiction mishandles the politics of a change, the backlash doesn't stay contained to that one decision. It reshapes the rules you'll have to operate under, and city staff won't carry your engagement for you.

"Transparency before transformation" is just a description of a well-run pre-entitlement campaign. Identify the stakeholders early, give them genuine notice and a real voice, and build visible support before the staff report drops, not after the opposition has already organized and framed the story.

Map the opposition before it maps you. In Lakewood, the pressure points were obvious in advance: traffic, infrastructure strain, neighborhood character, and protection of single-family areas. Those concerns were knowable. A project that anticipates them in both its design and its messaging is far harder to mobilize against.

Give decision-makers political cover. Lakewood's council now has direct proof that voters will reverse them. Every elected official in that region just learned that a "yes" on rezoning can be overturned at the ballot box. Your job is to make a "yes" vote the safe vote — by showing up to the hearing with organized, visible community support, not just a polished site plan.

The takeaway isn't that engagement is a nice-to-have. It's that in an environment where residents are willing to repeal an entire code and then amend the charter to lock in their leverage, community and political support is no longer the soft side of development. It's the difference between a project that gets built and one that becomes the next cautionary headline.

At Land Use Strategies, we treat entitlement like the political campaign it has become – building public and political support before opposition has the chance to define your project for you. If you're advancing a project in a market where the ground can shift this fast, it's worth a conversation.