Skip to content
LandmAIn
Back to Resources

Policy & Community

Arapahoe County Data Center Rules: The Three Choices Before Commissioners

Arapahoe County is considering three paths for data center rules. Understand the current exclusion, the October 19 agenda and what could change for eastern land.

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.

Standalone data centers currently have no approval pathway in unincorporated Arapahoe County. The county’s October 19, 2026 study-session materials put three choices before commissioners: retain that position, explicitly prohibit the use, or develop rules allowing data centers under specified conditions.

That is a meaningful policy discussion. Its outcome could shape where facilities are considered, what neighbors can expect and what evidence applicants must provide. The published agenda does not establish that commissioners have selected a path or adopted a code amendment. Official agenda and staff report, item 26-516.

For residents, the immediate task is to understand the choices. For eastern landowners, the question is whether a future rule would accommodate a particular property and project. Both depend on details that remain open in the materials reviewed for this article.

Status reviewed October 19: no current standalone-use pathway; policy options under active consideration. The meeting record reviewed for publication did not contain finalized minutes or a recorded outcome for this item. County meeting record.

Why data centers currently cannot proceed as a standalone use

The county’s published account of its September data center tour states that current development regulations provide no pathway in unincorporated Arapahoe County. The tour was an educational step as officials considered future land-use policy. County announcement.

The October staff presentation explains the mechanism: the Land Development Code has neither a data center definition nor an entry in its permitted-use table. Staff distinguish a standalone facility from an accessory server room subordinate to an otherwise permitted use. Staff presentation.

This geographic scope matters. A property located within a municipality needs review under that government’s applicable rules. A county name on an address or a regional map does not identify the approval authority by itself.

If you are checking a nearby property, begin with its boundary and jurisdiction. Then identify the governing code and the proposed use. Those steps prevent confusion between a county policy discussion and a separate municipal application.

What the October 19 discussion was designed to decide

The agenda scheduled the data center item for 1:30 p.m. within the Board of County Commissioners study session. Staff asked for direction on potential Land Development Code changes and on a public-input process.

The choices have substantially different consequences:

Staff option Practical direction
Continue current policyKeep standalone data centers unpermitted without further code work on this item
Create an express prohibitionDefine the use and prohibit it in all zoning districts
Develop a regulated pathwayPrepare definitions, permitted or special-review districts, and use-specific standards

These are the alternatives in the county’s staff report. An instruction to prepare language would be a step toward a future decision. Residents and applicants would still need to examine the resulting draft and adoption record.

Watch for a specific direction, an assigned work program and a public process. A general expression of interest leaves more uncertainty than an instruction identifying which uses, locations and standards staff should evaluate.

What is in the county’s research packet?

The packet contains a board summary, a comparison of other jurisdictions, an air-quality permitting fact sheet and staff slides. The comparison matrix is dated October 12. It organizes examples by approval process, zoning, air quality, water, noise and energy. Data Center Jurisdiction Matrix.

The comparison matrix lists policy tools used or considered by other jurisdictions. Readers should check each jurisdiction’s own current ordinance before applying an example to a property. A summary may combine proposed rules, adopted provisions and broader descriptions of a process.

For Arapahoe residents, the most useful reading is across the policy questions: who makes the decision, which activities are covered, what evidence is required and how compliance would be checked. Copying another jurisdiction’s numerical threshold would still require a local explanation of why that threshold fits.

Noise: make the standard measurable

The staff presentation identifies setbacks, property-line sound limits and equipment screening as possible tools. It also identifies generators and cooling equipment among the sources officials are considering. These remain discussion topics in the presentation. County staff slides.

A useful future rule would tell a resident how a noise concern gets evaluated. It should identify where measurements are taken, which operating conditions are tested and who is responsible for corrective work. LandmAIn recommends including those provisions in the future rule.

Ask how the analysis would address the full campus. A proposal may add buildings or equipment over time. A study for the first phase should clearly identify its scope and the conditions that would trigger another review.

Setbacks also need a precise starting point. Distance from a property line, a building or a piece of outdoor equipment can describe different conditions. A clear definition gives applicants and neighbors the same basis for evaluating a plan.

Water: require a complete operating description

County staff identify provider documentation or adequate adjudicated rights as part of demonstrating water availability. They also raise cooling design as a potential subject for use-specific standards. Water discussion in the staff presentation.

Residents should ask a future applicant to describe annual demand, peak demand, initial filling and ongoing replenishment separately. The description should also cover domestic use, landscaping and fire protection. Put the figures in consistent units and identify the phase they describe.

A cooling-system label is a starting point for that conversation. The useful question is how the proposed system operates at this site and what the water provider has confirmed. Request the assumptions behind forecasts, including how the design responds during hot weather.

For a phased campus, ask which water commitments apply to the initial construction and which depend on later decisions. That helps the public understand whether a figure represents the first building or the eventual development.

Electricity and air quality involve additional authorities

The county presentation raises possible electrical-demand thresholds and different review paths for different project scales. No selected threshold is established in the record reviewed here. Staff presentation.

A county approval process should make utility evidence understandable to the public. Residents need to know what service has been evaluated, which upgrades are assumed and which commitments remain conditional. A letter’s actual terms matter more than its label.

Air permitting has its own authority. EPA identifies Colorado’s Air Pollution Control Division as the Clean Air Act permitting agency for the state outside Indian Country. EPA’s Colorado permitting guide.

If a future application includes generators, ask for the equipment inventory, operating assumptions and applicable permit record. Keep emergency operation, maintenance testing and any other proposed operation clearly described. County land-use review and state air review need to address their respective questions using a consistent project description.

What commissioners and candidates have actually said

An October 11 Colorado Politics questionnaire shows different views. Commissioner Jessica Campbell expressed skepticism about hyperscale sustainability while discussing possible conditions. Commissioner Leslie Summey emphasized community needs, ratepayer protection and closed-loop water use. Challenger Sonda “Sunny” Banka supported predictable development standards and evaluation of full buildout. Candidate questionnaire.

Banka’s development-compatible position should be attributed to her as a candidate. It should not be counted as a statement by Summey or as evidence of a current board majority.

The questionnaire helps explain the political discussion. The board’s direction and subsequent code language will establish the policy record. Residents should follow those documents alongside campaign statements, particularly where a candidate’s preferred standard has yet to appear in a draft.

Could eastern Arapahoe parcels become more attractive?

They could, if the county eventually permits the use and adopts standards that particular eastern properties can meet. Larger parcels may offer more flexibility for separation, equipment placement and future phases. Each parcel would need to satisfy the eventual rules. The county has yet to designate preferred development territory.

The same property may face difficult infrastructure questions. A distant location can require more work on access, fiber, water or electrical service. A transmission corridor nearby does not establish a service commitment for a data center.

Our position is that residential separation deserves early attention, alongside infrastructure and the actual approval process. A parcel should earn further investigation through evidence on all three. Moving east does not remove the need for that work.

For landowners, the next useful step is to establish current conditions and identify what a future rule would need to allow. The broker’s qualification checklist explains how to assemble that record without presenting a speculative use as an approved opportunity.

What residents should ask in a future public process

Focus comments on decisions the county can make and information the applicant can provide. Specific requests make it easier to evaluate whether the eventual code addresses the concern.

  • Which zoning districts would allow each type or scale of facility?
  • Which proposals would receive public hearings?
  • Would review cover the full campus and later expansion?
  • What noise, water and utility evidence would be public?
  • How would operating compliance be checked and enforced?
  • What happens when equipment or the approved operating plan changes?

Ask for maps alongside written standards. Maps can show how a proposed rule interacts with existing neighborhoods, approved housing and infrastructure. They also help reveal whether an apparently broad permission would apply to only a small set of suitable locations.

What to watch next

The next meaningful record is the commissioners’ direction, followed by any proposed code text and public-review schedule. A draft should make the permitted locations, approval process and operating standards identifiable. An adopted amendment would then need an effective date and a clear explanation of how applications proceed.

Nearby Aurora is dealing with its own proposed pause and an existing project application. Our Aurora moratorium and Trident explainer covers that separate municipal process. The distinction matters for readers following development across the eastern metro.

LandmAIn tracks the relationship between location evidence and development rules. You can explore our public screening demonstration or contact us about a specific property. For Arapahoe County today, the central fact remains the current lack of a standalone pathway. The October 19 materials make the possible directions clearer, while leaving the eventual policy to the county’s decision process.