To Be, or Not to Be … Permitted
Imagine you’re opening a craft brewery in Salem. You meet with city planners, review zoning regulations, and receive guidance that your proposed business is permitted. You invest in architectural plans, engineering, financing, and months of preparation.
Then, halfway through the process, the City Council decides that modern breweries are fundamentally different from those contemplated when the city’s regulations were written. Brewing technology has evolved, production methods have changed, and business models barely resemble those of a decade ago.
So, the council adopts new interpretations of existing regulations — concluding that your brewery doesn’t actually qualify as a brewery. The city hasn’t amended its code and insists it hasn’t changed any rules. It has simply changed its interpretation of what a brewery is.
Or consider an outpatient medical center. Medical technology, procedures, and treatment models have changed dramatically over the past decade. Surgeries once requiring hospitalization are routinely performed in specialized outpatient facilities using equipment that barely existed when older zoning classifications were developed.
Could city officials revisit those classifications in each case and decide that a modern medical facility or brewery doesn’t qualify under regulations the applicant was previously told applied?
These are hypothetical examples, but they raise the same fundamental question:
How much confidence should a business place in government guidance if the government can later adopt a different interpretation of the same rules?
A Question of Confidence
That’s the larger issue raised by the Salem City Council’s Nov. 17 decision concerning data centers. By a 6–2 vote, the council adopted a resolution interpreting existing zoning regulations to exclude certain artificial intelligence and hyperscale data centers.

Salem City Council met virtually Nov. 17 to discuss a proposed code interpretation for data centers.
The decision could have significant consequences for a pending development application from Verrus, which had already spent months working with city staff and received guidance that its proposed use was permitted.
City Attorney Dan Atchison repeatedly emphasized that Council wasn’t changing the code. Instead, it was adopting its first formal interpretation of language written in 2014.
Supporters argued that modern computing facilities differ substantially from the data centers contemplated when the classification was originally established, from electrical demands to operating characteristics and infrastructure requirements.
Those distinctions deserve consideration. They may also justify updated development standards. In fact, Salem already has a Data Center Task Force reviewing potential requirements and a separate code amendment process underway.
So why was an immediate reinterpretation necessary while those prospective regulations were already being developed?Atchison explained that formal amendments could face appeals and take months to become final, while an interpretation of existing regulations could have more immediate significance.
That explains why the two approaches operate on different timelines, but it leaves an equally important question about what the city needed its interpretation to accomplish before those amendments became effective.
Immediate Consequences
The Verrus proposal is hardly a mystery. It was the development at the center of this controversy, and the city attorney had previously indicated the interpretation would apply to its pending application.
Councilor Deanna Gwyn questioned how the decision would affect a developer that had relied on earlier city guidance. Mayor Julie Hoy questioned whether council was interpreting existing regulations or effectively establishing new ones. Both voted no.
Councilor Irvin Brown also raised concerns about changing the position of an applicant already underway, although he ultimately supported the resolution.
Atchison acknowledged that city staff previously advised the developer that its proposed use was permitted but questioned whether that determination was based on a thorough analysis. He also cited a nondisclosure agreement between the applicant and city staff for why the City Council was not informed of the project earlier.
That explanation may address the chronology of council’s involvement. It doesn’t resolve the significance of the city’s earlier guidance or the consequences of adopting a different interpretation now.
And the public opposition makes the need for a clear explanation more important, not less.
Public Opposition
Residents raised legitimate concerns about electricity, water, environmental impacts, and infrastructure. Some opponents wanted the proposed development stopped altogether.
Council is entitled to hear those concerns and respond through the regulatory tools available to it. But public opposition to a particular project does not, by itself, resolve how government should treat an application already in progress.
That’s where a question about one development becomes a question about the reliability of the entire permitting process. Uncertainty is expensive, not just for developers but for consumers.
The Cost of Uncertainty
Businesses make investment decisions based on the rules they understand to be in place. When those expectations become uncertain, additional legal reviews, redesigns, financing delays, and unpredictable approval processes can make development substantially more expensive.
Those costs don’t necessarily stop with the developer.
A more expensive restaurant can result in higher menu prices. Higher development costs for childcare facilities can contribute to making the cost of daycare even more expensive. Delays and uncertainty surrounding medical facilities can add costs and make needed services more difficult to access for patients.
That’s not to say every expense gets passed directly to consumers, but unnecessary uncertainty makes investment riskier, and the facilities communities depend upon harder to finance.
This isn’t an argument against regulating development. Communities should establish clear and enforceable standards for water, electricity, infrastructure, and environmental protection.
Nor does preliminary staff guidance necessarily create a binding development approval.
But Oregon’s land-use system recognizes the value of predictable standards through what is commonly called the goalpost rule, generally requiring qualifying applications to be evaluated under the standards and criteria applicable when they were submitted.
Whether Salem’s interpretation violates that protection remains an unresolved legal question.
The broader question of public confidence does not depend entirely on the outcome of that legal dispute.
Demanding Answers
Salem’s elected officials frequently emphasize transparency, accountability, and the importance of public trust. Those principles should apply even when the development in question is deeply unpopular.
The city explained why it believes this is an interpretation rather than an amendment. It explained why the amendment process could take longer. And it explained why council learned about the proposal after staff had already been working with the applicant.
What deserves a more direct explanation is how those points fit together: What immediate result was the council seeking, how would it affect Verrus, and what responsibility does the city have for the guidance its staff previously provided?
These aren’t unreasonable questions. They’re the questions a transparent government should be willing to answer plainly.
As Oregon prepares for a broader debate over development standards in the 2027 legislative session, Salem offers a case study in why the way government applies its rules matters as much as the rules themselves.
Salem’s decision sets a precedent that future developers, employers, and investors will weigh as much as they consider how much confidence to place in the city’s permitting process. Today, it’s a data center. Tomorrow it could be a brewery, an outpatient medical center, or something the community broadly supports.
And the question for our community leaders should be the same regardless of whether we welcome or oppose the project.



















