Henderson's Data Center Moratorium Hearing - July 21, 2026. What promises were made? What promises will be kept?

In the hearing the genuinely new commitments were relatively narrow, automatically requiring development agreements for data centers, expressly adding that requirement to the code, applying it immediately and promising broader data-center standards later. Ok, so treat them like they did Lakemoor at Three Kids Mine. That would do nothing to protect the public, as Three Kids Mine demonstrated that a Development Agreement does nothing to protect the public from a City Council and Mayor who function as surrogates for developers. So what else?

Most of the other assurances were repackaged descriptions of authority and procedures Henderson already possessed or responsibilities it should already have been carrying out. The city should therefore not portray the entire list as reform. The true test will be whether Henderson adopts mandatory, measurable and publicly enforceable standards that materially restrict harmful development, require developers to bear their full costs and result in projects being rejected when they cannot protect the public.

The only real reform that can protect the public is to vote for leaders who will represent them, and not data centers and developers. And that is something Mayor Romero and the Council will fight to their last breath to stop.

Accountability Checklist:

First the New Commitments or Potential Reforms:

These are the items that appear to represent a new policy direction, a new code requirement or a potentially meaningful change specifically related to data centers.

1. Automatically require every data center to undergo a negotiated development agreement. Existing code already allowed the council to require development agreements for large, complex or unusual projects. The new commitment was to make the requirement automatic for every data center rather than discretionary.

2. Amend the development code to expressly require development agreements for data centers. Staff committed to introducing the initial amendment on August 4, 2026, with a hearing identified for August 18. This is a specific, measurable commitment that can be checked against the agendas, staff reports, ordinance language and final council action.

3. Immediately apply the development-agreement requirement before the amendment is enacted. The city attorney said existing code already gave the city enough authority to require a development agreement for any data-center application arriving immediately. The authority itself was not new. The commitment to use it automatically for data centers was new.

4. Develop broader data-center-specific code standards. Officials said the initial amendment would not be the end of the process. Staff would continue developing standards addressing energy, water, heat, noise, residential compatibility, infrastructure, decommissioning and other impacts. This would be a genuine reform if the standards are actually drafted, publicly reviewed and enacted. At the meeting, no such substantive standards were adopted and no firm completion date was given.

5. Create a defined framework showing applicants and residents what will be required. Mayor Romero directed staff to make clear: "Exactly what will be expected of them and what the process would be.” A written framework specifying required studies, standards, mitigation, infrastructure obligations and grounds for denial would be a meaningful improvement over purely discretionary negotiations.

6. Use the entire impact list as interim direction for development agreements. Staff said the concerns identified during the hearing could immediately guide negotiations, even before broader code standards were adopted. These included energy demand, grid impacts, ratepayer costs, water, air quality, heat, noise, vibration, environmental effects, residential proximity, infrastructure costs, waste and decommissioning.

7. Continue adding requirements based on public testimony, expert advice and further research. Staff said the list would continue to evolve as the city learned more and consulted the public and experts. This is potentially new only if it results in a transparent and documented process. No formal working group, meeting schedule or reporting requirement was created.

8. Potentially place the burden of proof on the developer. The city attorney said a development agreement: “Shifts the burden completely to the developer” to prove that staff and public concerns have been satisfied. This could be an important reform if the burden, evidence requirements and consequences of insufficient proof are clearly written into the process.

9. Conduct independent city research in addition to reviewing developer submissions. A councilmember said the city would undertake its own: “Independent research and investigation into the impact.” This would be meaningful if it involves truly independent experts, transparent methodologies and public access to the underlying information.

10. Consider standards stringent enough to discourage unsuitable projects. A councilmember suggested that requirements could become so strict that some developers might decide not to locate in Henderson. This would represent a meaningful change only if the city adopts measurable standards and is willing to deny projects that cannot meet them.

Existing Powers, Existing Procedures or Duties That Should Already Be Performed. These items were presented as safeguards, but they largely describe existing authority, standard land-use procedures or basic responsibilities that competent city staff should already fulfill. But do they? Not so much!

1. Require technical studies and operational information. Development agreements already allow the city to require detailed studies, operating information, mitigation, infrastructure improvements, performance standards and public-safety protections. Applying those powers to data centers may be new, but the authority itself is not.

2. Evaluate foreseeable project impacts. Reviewing energy use, water demand, noise, heat, air quality, compatibility, infrastructure and public-safety impacts is already the fundamental purpose of land-use and development review. Merely listing these issues is not reform unless the city adopts mandatory studies, thresholds and enforceable limits.

3. Question and verify developer claims. Staff should already critically review applicant information rather than accepting it at face value. Verification is a basic professional duty, not a new public protection.

4. Conduct research before approving an unfamiliar, high-impact use. Researching new technologies and comparing standards used by other jurisdictions should already be part of responsible planning. The city should not take special credit for performing the due diligence residents already pay it to perform.

5. Use contractual enforcement remedies. The city attorney explained that development agreements already create contractual remedies in addition to normal regulatory enforcement. That is an existing feature of development agreements, not a new reform created at this hearing.

6. Negotiate funding for infrastructure and public services. Staff said previous development agreements had already obtained funding for fire, police, parks and infrastructure. This is existing authority and existing practice. The unresolved issue is whether developers are required to pay their full attributable costs.

7. Send applications through the Development Agreement Advisory Committee. Staff described this as part of the existing development-agreement process. It is not a new safeguard unless the committee’s work becomes more transparent and accessible to residents.

8. Hold Planning Commission and City Council public hearings. Public hearings are already part of the land-use and development-agreement process. Mayor Romero’s promise of multiple hearings therefore largely described an existing legal procedure.

9. Publish agendas, staff reports and backup materials. Making application materials available through public meeting records is already a normal administrative and legal responsibility. A meaningful reform would require disclosure much earlier in the negotiation process, not simply shortly before a hearing.

10. Allow residents to submit comments and speak at hearings. Residents already possess this right. Saying residents will “have a voice” does not create a new protection unless the city demonstrates how that input changes proposed agreements or decisions.

11. Consult residents, businesses, unions and experts. Listening to affected groups is an expected part of major public decision-making. No formal consultation process, schedule or reporting requirement was adopted at the meeting.

12. Tailor conditions to a specific site and proposal. Project-specific negotiation is already one of the defining characteristics of a development agreement. It is not a new reform.

13. Adjust requirements as technology and circumstances change. Updating planning codes and conditions as new information becomes available is an ordinary legislative responsibility. It becomes meaningful only if there are mandatory review dates and public reporting.

14. Retain the authority to reject an application. The council already has the power to approve or deny qualifying land-use applications. Mayor Romero’s statement that the city could “say no” described an existing power, not a newly created safeguard.

15. Require public-safety, compatibility and mitigation measures. These are already standard subjects that may be addressed through land-use conditions and development agreements.

16. Require Planning Commission review before City Council action. This was described as part of the existing process, not a procedural reform adopted in response to the data-center controversy.

17. Make decisions based on sufficient facts and data. Elected officials and staff should already refuse to approve major projects without adequate evidence. Presenting fact-based decision-making as a new commitment risks taking credit for a basic duty of government.