Moratorium, Shmoratorium. Was always a tactic to keep the public at bay

Henderson City Council — Data Center Moratorium Item (Agenda Item 78)

Research Memo — Regular Meeting, July 21, 2026

Re: Bill No. 3927 — Moratorium on Acceptance of Conditional Use Permit Applications for Data Center Use

Source: Exported meeting transcript, City Council Regular Meeting, 7/21/2026, 4:00 PM

1. Overview

Agenda Item 78 proposed a moratorium, recommended for adoption as Ordinance No. 4165, pausing the city's acceptance of Conditional Use Permit applications for data center development. The item was moved to the front of the agenda, following the consent agenda, so that all public comment on data centers could be consolidated into a single discussion. Staff presented an alternative to the moratorium during the same item: requiring all future data center proposals to proceed through the city's existing Negotiated Development Agreement (NDA) process. Council ultimately did not vote on the moratorium ordinance. It instead gave staff informal direction to pursue the development agreement path and to bring code amendments forward at a later date.

2. Staff Presentation and the Development Agreement Alternative

Community Development and Services Director Eddie Dichter opened by confirming there were no data center applications pending before the city in any form. Staff reported that, since April 2026, it had researched regulatory approaches used elsewhere, reviewed proposed standards from environmental and policy organizations including the Sierra Club, and coordinated with the Southwest Energy Efficiency Project (SWEAP) on emerging Northern Nevada practices.

Staff identified that Henderson Municipal Code Section 19.27.3 already authorizes the city to require development agreements for large, complex, or high-impact projects, and that Section 19.27.3(B) gives Council discretion to apply that requirement to other unique project types. Staff proposed a narrow code amendment adding data center projects explicitly to that list. Staff represented that this amendment could be introduced for first reading on August 4, 2026, and heard on August 18, 2026.

Staff outlined the evaluation criteria a development agreement would allow the city to negotiate on a project-specific basis: energy demand and grid impact, energy costs and rate-payer protections, water use, air quality, heat generation, noise and vibration, environmental impacts, proximity to residential areas, land use compatibility, public safety, infrastructure and service costs, waste management, and decommissioning or future reuse of the site.

3. Public Comment

Public comment ran for approximately two hours with dozens of speakers, the overwhelming majority in favor of the moratorium and asking that its length be extended from the proposed 180 days to a full 12 months. Recurring themes included:

● Water consumption in a drought-stressed region, citing the existing Google data center's reported use of roughly 352–400 million gallons annually and its status as the state's highest water-consuming data center.

● Electricity demand and grid strain, including NV Energy projections of a 47 percent increase in required capacity, planned methane gas generation to serve data center load, and risk to the state's 2030 renewable portfolio standard.

● Health effects associated with low-frequency noise, diesel backup generators, and heat island effects, with several speakers citing out-of-state examples (Northern Virginia, Cheyenne, Wyoming) and asthma and respiratory-illness data.

● Land use efficiency, with speakers arguing data centers generate comparatively few permanent jobs relative to the acreage consumed, versus housing, retail, or mixed-use development.

● Surveillance and data governance, connecting data center infrastructure to license plate reader networks and the absence of state law governing retention or sharing of that data.

● Timing relative to the 2027 state legislative session, with several speakers urging the city to hold any moratorium in place until the legislature acts on data center policy.

A smaller number of speakers, including at least one with direct industry experience, urged the city to consult technical experts before setting policy and noted variation across data center types and operators.

4. Council Deliberation

Each councilmember expressed sympathy with the concerns raised and framed the choice as between a moratorium and the development agreement mechanism, not as a choice to decline regulation. City Attorney Nicholas Baskoff advised that a moratorium is inherently temporary and typically defensible for only 12 to 18 months before permanent code changes are required, whereas the development agreement route is immediately available under existing code and functions as a more durable, contractually enforceable tool. Staff estimated a full development agreement negotiation, from application through Planning Commission and Council hearings, would take roughly six to nine months, a timeline comparable to the moratorium period under discussion.

Council coalesced around the development agreement approach on the stated rationale that it shifts the burden of proof to the developer, provides two public hearings per application (Planning Commission and City Council), and allows conditions to be negotiated and updated as technology changes, rather than fixed in a static ordinance.

5. Outcome and Commitments

● No vote was taken on Bill No. 3927 or Ordinance No. 4165. Council took no formal action on the moratorium.

● Council gave informal direction to staff to require a negotiated development agreement for any future data center application, using existing code authority effective immediately.

● Staff committed to introduce a development code amendment on August 4, 2026, to be heard August 18, 2026, formally adding data centers to the list of uses requiring a development agreement.

● Staff committed to continue compiling the list of required disclosures and studies raised by Council and the public, and to bring further code changes forward at an unspecified future date, at which point Council would take a vote to adopt them.

6. Conclusion

On its face, the outcome reads as responsive to two hours of public testimony: staff and Council repeatedly credited residents with shaping the criteria list, and the development agreement mechanism was presented as giving the public more process, not less, through its two-hearing structure. But the structural commitments made on July 21 are notably soft. No ordinance was adopted, no vote was taken, and no binding timeline exists for the promised code amendments beyond the August 4/18 introduction of language that itself only codifies the requirement to negotiate, not the substantive standards residents asked for. The list of protections, buffer distances, water and power conditions, backup generator standards, is still described as a working list staff will "continue to add to," with no date certain for adoption.

This pattern is worth measuring against the Three Kids Mine / Lakemoor Ventures development agreement, where the record shows a similar sequence: a process that ran for months while the substance of the deal was negotiated largely outside public view, followed by a final public hearing at which residents raised serious, specific objections, including health and environmental concerns, and Council nonetheless moved to approve the development agreement in short order after that testimony closed. In that case, the development agreement structure itself, the same mechanism now proposed as the safeguard for data centers, was the vehicle through which the substantive terms (the federal land conveyance to Pulte, the up-to-$550 million, 45-year property tax pledge) had already been effectively settled before the public had a meaningful opportunity to alter them.

The data center item leans on the same structural assumption: that negotiation-stage flexibility and a closing public hearing are an adequate substitute for enforceable standards adopted in advance. Absent a hard deadline for the substantive code changes, and absent any mechanism forcing the negotiated terms of a future data center development agreement to be shaped by public input before they reach a final hearing, rather than ratified after, the July 21 outcome is better read as a deferral than a resolution. The relevant test will be whether the code amendments staff described materialize on a fixed schedule with the specific protections residents requested (buffer distances, closed-loop water verification, rate-payer insulation, backup power standards) written into code, or whether, as with Three Kids Mine, the first real test of the process arrives only when a specific applicant is already at the table and residents are once again testifying against a deal that has substantially taken shape.