Skip to content
LandmAIn
Back to Resources

Policy & Community

Aurora’s Data Center Moratorium Vote Moves to October 26: What It Means for Trident

Aurora’s moratorium vote moved to October 26. Learn what the proposed pause could cover, where Trident stands and which questions residents should ask.

October 26 update: Vantage has put its alternative-site evaluation in writing. Read the October 26 Trident search update. The new article reflects the record before the October 26 council meeting.

October 24 update: Arapahoe commissioners have directed staff to draft a permitting pathway; no ordinance has been adopted. Our new developer and broker analysis covers the October 19 direction, October 22 Trident reporting and refreshed industrial profiles. The article below preserves its original publication context.

Aurora’s proposed data center moratorium vote has moved to October 26. CBS Colorado’s October 19 update.

The proposed pause would stop acceptance of new applications while the city develops regulations, without a specified end date. City officials told the Sentinel it would likely leave Trident’s already-accepted application unaffected. Vantage says it is evaluating alternatives while continuing work on the current site; no relocation decision has been made. Sentinel’s October 19 report.

Those distinctions matter for neighbors trying to understand what the council can decide next. A pause on new applications, a permanent change to development standards and a decision on an existing project have different purposes and procedures.

This article explains the record reviewed October 19, 2026. It treats the moratorium as proposed and identifies questions residents can use to evaluate the next city documents.

What changed on October 19?

Mayor Mike Coffman canceled the special meeting because two council members who support the moratorium could not attend. Lawmakers instead intend to consider it at the October 26 meeting. The cancellation changed the immediate timetable without resolving the proposal. Sentinel’s meeting update.

For residents, the practical next step is to review the posted agenda and the actual measure when available. Check for amendments, the proposed effective date and the application categories it covers. Meeting dates and proposal language can change before a vote.

Issue Status in the record reviewed October 19
Special moratorium meetingCanceled; consideration intended for October 26
New application pauseProposed, with no fixed end date in the reported proposal
Trident applicationContinues through a separate development process
Alternative Trident locationUnder evaluation; no relocation decision announced
Permanent development standardsRemain a separate policy question

Use the city’s council-meeting page to locate current meeting information. A meeting announcement tells you when a decision may occur. The adopted text and vote record tell you what changed.

Where does the Trident application stand?

The Sentinel’s October 13 coverage describes Vantage’s approximately 860,000-square-foot proposal on East 48th Avenue as being in the Airport District. It reports that data centers are allowed there as a use by right, with administrative review. The project was undergoing a fourth review round, with a submission expected October 26 and timing dependent on a community meeting. Trident review reporting.

A use allowed by right still needs the applicable reviews and permits. The term describes the land-use route. It does not, by itself, tell a resident which approvals have been issued, which conditions remain or when construction can begin.

When checking the project, ask for the current site-plan version and the decision record for each approval stage. A revised plan can change the information neighbors need to review. Keep the date and document title with any map or figure circulated publicly.

Our earlier Trident campus overview provides background. For current application documents, use Aurora’s development portal and search for Trident.

Why a new moratorium may leave an existing application moving

A moratorium can be written to cover particular applications, activities or submission dates. Its reach depends on the adopted language and how that language applies to a project’s procedural position.

Residents should ask the city to publish a clear explanation of the proposed scope. Which applications would be affected? Which would continue? What is the relevant cutoff? What actions could an existing applicant still take during the pause?

These questions deserve direct answers before residents assume a vote will decide Trident’s future. An application pause may give the city time to write standards while leaving an existing case subject to another process.

The same care applies to exemptions. Ask for the stated basis and the documents supporting it. An explanation tied to a specific application date or approval is more useful than a general statement that projects are protected.

How the proposed pause relates to other zoning changes

The city has also pursued changes to where data centers are allowed. The Sentinel reported an initial October vote on a zoning restriction, with another vote needed before it takes effect. Its reporting says that change would leave Trident’s Airport District location outside the restriction. October zoning coverage.

Treat each measure as a separate item. Track its number, purpose, stage and effective date. A zoning amendment can alter future eligibility in selected districts. A moratorium can pause a defined set of applications. Project review determines whether a particular proposal meets the standards that apply to it.

Identify the rule that changed and the properties or applications it covers. Residents can then assess its effect on the project near them.

Residential separation needs a defined measurement

Aurora’s setback discussion predates the latest moratorium proposal. Axios reported in September that council members were considering a 350-foot separation while debating permanent standards, with uncertainty about which projects eventual rules would cover. Axios’s setback reporting.

For the next draft, ask where the distance begins and ends. Does it apply to the building, outdoor equipment or the full site? Does it reference an existing home, a residential property line or land already approved for housing?

A readable map should accompany those definitions. It should identify nearby homes, proposed equipment and the boundaries used in the measurement. Residents should be able to reproduce the basic comparison without guessing which feature the city intended.

LandmAIn’s position is that separation deserves attention early in site selection. It gives a project team room to examine layout options before a design becomes difficult to change. The appropriate distance still requires consideration of the actual equipment, setting and applicable standards.

What residents should ask about noise

Request the project’s acoustic analysis and the assumptions behind it. Useful questions include the location of measurement points, the operating conditions evaluated and whether the analysis covers the proposed full buildout.

Ask how ordinary operation differs from generator testing or an outage. A single predicted sound figure may describe only one condition. The supporting documents should explain what was modeled and where residents can find the results.

Then ask how compliance will be checked after the facility begins operating. Identify the responsible agency, complaint process, testing method and available corrective measures. Those details make an operating standard meaningful to both the operator and neighboring households.

These are requests for project-specific evidence. They should not be replaced with measurements from an unrelated facility whose equipment and surroundings may differ.

What residents should ask about water and electricity

Colorado Legislative Council Staff’s review explains that cooling approaches vary and that data centers’ environmental effects depend on their design and resource use. It also identifies important gaps in available reporting. Legislative research memorandum.

For a proposed Aurora facility, request a water budget with annual and peak demand, the source of supply and the phase covered. Ask for initial filling and recurring use to be stated separately. Include domestic use, landscaping and fire protection in the questions.

For electricity, ask what the serving utility has confirmed. Identify the requested initial load, ultimate load, required upgrades and assumed service date. Request a clear distinction between an estimate, a study result and a contractual commitment.

Responsibility for infrastructure costs also deserves a specific answer. Ask which costs are allocated through the utility’s service terms and which public infrastructure commitments appear in the development documents. A broad promise of economic benefit does not explain that allocation.

LandmAIn’s power-tariff explainer describes why those terms matter to Colorado projects. It should be read alongside the current utility and regulatory documents for the actual proposal.

Air permits and economic benefits need their own records

For generator emissions, EPA directs Colorado readers to the state Air Pollution Control Division, which handles Clean Air Act permitting outside Indian Country. Its guide links to permit status and public-notice resources. EPA’s permitting guide.

Ask which permits apply, which have been requested and what operating conditions they evaluate. A land-use meeting may not answer every air-permitting question. Directing comments to the relevant record helps the responsible agency address them.

Economic claims need comparable detail. Request separate estimates for construction employment and ongoing positions. Ask which tax revenues go to which public bodies, over what period and after which incentives or public costs.

The legislature’s research distinguishes temporary construction activity from continuing operations and discusses the different fiscal effects of incentives. That distinction is useful when evaluating local projections. Legislative Council Staff memorandum.

How Aurora compares with nearby policy decisions

Brighton’s one-year moratorium proposal passed first reading October 6 and was scheduled for second reading October 20. Brighton’s notice. Littleton was scheduled to consider a six-month proposal on October 20, with a second reading planned for November 3. Denver Gazette’s Littleton report.

Check the effective date, geographic reach and terms of each city’s action. The proposed pauses have separate review schedules and scopes.

Unincorporated Arapahoe County starts from a different position, with no current standalone data center pathway. Our Arapahoe County explainer examines its three policy options. Readers following eastern metro development should keep that county process separate from Aurora’s municipal decisions.

What would make the next decision useful?

A useful council record would state the moratorium’s scope, the work to be completed during the pause and how residents can participate. If there is no fixed end date, ask what milestones will demonstrate progress and what action would end the restriction.

For Trident, look for a current application status, revised documents, a confirmed community-meeting notice and a clear account of remaining decisions. Alternative-location discussions should be tracked as discussions until the developer announces a decision and submits the relevant documents.

LandmAIn’s guide to Aurora public input offers additional context for reviewing a proposal. The strongest public comments identify the location, cite the document and ask for a decision or missing piece of evidence. That approach gives the city and applicant a concrete issue to answer as the October 26 meeting approaches.