Summary

  • Aurora City Council approved a data-centre standards resolution by 7–4 after rejecting a proposed six-month moratorium.
  • The policy direction includes prohibiting evaporative cooling and creating setbacks or buffers near residences.
  • The city manager has 35 days to return with recommended regulatory changes, so the vote is not yet a completed detailed ordinance.
  • The new direction is reported to apply to future development rather than the five data-centre projects already in development.
  • City information cited by Sentinel Colorado counts nine established data centres and five in development.
  • A statement that data centres generated more than $24 million in city revenue lacks a stated period, cost denominator or project breakdown.

The council chose movement without a pause

The rejected moratorium would have stopped new decisions for six months. The approved resolution instead lets the city continue processing development while staff translates policy instructions into rules.

That choice preserves near-term project momentum but concentrates risk in the drafting interval: applications can move while the scope and effective date of new controls remain unsettled.

The binding text still has to return

Council Member Curtis Gardner’s resolution establishes direction. The city manager’s 35-day assignment must produce recommended changes that can be read, amended and adopted. Until then, there is no complete code package to test against a specific design.

Readers should therefore distinguish the political decision from the later legal instrument. A resolution can command work without containing every enforceable threshold.

Water policy has a clear headline and missing mechanics

The reported direction would prohibit evaporative cooling, a significant choice in a water-constrained region. It does not yet disclose how hybrid systems, emergency operation, existing entitlements, measurement or enforcement will be handled.

A categorical phrase can become narrower or more technical in drafting. Project economics will depend on the exact definition and compliance date.

Buffers convert community concern into geometry

Setbacks or residential buffers move debate from general nuisance to measurable distance. Final text must still define the protected uses, the point from which distance is measured and whether noise, generators, substations and cooling equipment receive separate treatment.

Those details determine whether a buffer merely shifts a building or materially changes the usable site.

Existing and future projects are separate cohorts

Sentinel Colorado reports nine established facilities and five projects in development. The new direction is aimed at future development, not retroactive application to those five projects. “In development” also does not mean permitted, built or operating.

The baseline matters because grandfathering and application dates can shape more capacity than the rule’s headline language.

The revenue figure lacks a fiscal ledger

The city manager said data centres generated more than $24 million in revenue. The account does not specify the time period, recurring share, project contribution or infrastructure and service costs.

The figure therefore supports fiscal materiality, not net benefit. A meaningful comparison would place taxes and fees beside water, road, emergency-response and administrative obligations.

Independent confirmation has an evidence boundary

Denver7 corroborates the rejected moratorium and 35-day work period, but its page says the broadcast report was converted for the platform with AI assistance and editorially verified. It contributes no unique fact here.

The Sentinel account remains the factual basis for the vote, inventory and policy direction. That prevents a derivative production process from quietly adding unsupported detail.

Sources