Data centers are coming, and local governments have a job to do.
That job is not to roll out the red carpet without asking questions. It is also not to stack regulations like hay bales in a windstorm until nobody can figure out how to build anything.
Aurora is about to find out whether it can strike that balance.
The Aurora City Council has directed city management to update development standards for data centers. The first round of discussion will focus on two significant issues: banning evaporative cooling systems and changing where data centers may be located.
Those may sound like technical details. They are not. They affect water, neighboring property owners, infrastructure, economic development and the long-term tax base of the community.
That means the public deserves more than a fashionable answer. It deserves a workable one.
Start with water.
Colorado does not have water to waste, and local governments have every right to examine whether a proposed development places unreasonable demands on a limited resource. Stewardship matters. If a cooling system creates a significant burden on Aurora’s water supply, city leaders should be able to explain that burden clearly and adopt standards that address it.
But “ban it” should not become government’s automatic setting.
A blanket mandate is easy to announce. The harder work is showing the public the numbers behind it, identifying the actual impact and explaining why a broad prohibition is better than performance standards, conservation requirements or some other approach.
Good policy survives those questions.
Then there is zoning.
Data centers are large facilities with real infrastructure demands. Their location matters. Nobody should pretend otherwise. Compatibility with surrounding properties matters too, especially when residential neighborhoods or other sensitive uses are nearby.
Aurora is considering changes to where these facilities may be located, along with questions about buffers between data centers and residential areas. That is exactly the kind of discussion a city council should have.
But again, the standard needs to be clear.
If a data center does not belong next to a neighborhood, define the impact you are trying to prevent. Noise? Traffic? Utility infrastructure? Building scale? Emergency access? Whatever the concern is, name it and build a rule around the measurable problem.
That is better government than starting with the conclusion that a particular industry is undesirable and working backward until the zoning code produces the desired political result.
Development comes with tradeoffs.
It can create jobs. It can expand the tax base. It can bring private investment and new infrastructure demands at the same time. Responsible leaders have to consider all of it.
You do not protect residents by pretending development has no consequences. You also do not protect residents by making new investment so unpredictable that employers decide it is easier to build somewhere else.
The accountable parties here are Aurora’s City Council and city management.
They should show residents the proposed standards. Show the evidence supporting those standards. Explain what problem each regulation is intended to solve. Then explain how the rules will be applied consistently to the next applicant and the one after that.
That last part matters.
Businesses can work with tough rules when the rules are understandable and predictable. What is much harder to work with is a moving target where standards change depending on the political temperature of the room.
Colorado needs responsible stewardship of water and land. We need reliable infrastructure. We need communities where homeowners are not surprised by incompatible development next door.
We also need jobs, investment and a tax base capable of paying for the services residents expect.
Those interests are not mutually exclusive unless government makes them so.
Aurora has an opportunity to build a framework that protects residents and resources while still telling responsible businesses that the city is open for business. That requires more work than issuing blanket mandates, but that is what governing is supposed to be.
Put the facts on the table. Define the impacts. Write rules people can understand. Apply them consistently.
Then measure the results in months and dollars, not slogans.
That is stewardship without political theater, and it is a much better foundation for public policy.
Source: Denver Gazette
