Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use Code topic
No spam. Unsubscribe anytime.
Fernley council tables major rewrite of adjacency rules and data-center standards for more work
Summary
Council moved to table proposed adjacency-code rewrites and a related data-center item after planners outlined new default lot-size, buffering and maintenance rules and councilmembers raised concerns about buffer funding, enforcement, noise and industrial hazards; items 5.3 and 5.4 were tabled for further staff work.
Get email alerts on the Land Use Code topic
No spam. Unsubscribe anytime.
Fernley’s City Council voted unanimously on April 15, 2026, to table proposed changes to adjacency standards (CA25012 / bill 377) and a related item so staff can respond to specific council concerns about buffer maintenance, enforcement, data-center noise and industrial-adjacency hazards.
Planning Director Michelle Rambo presented a comprehensive rewrite intended to clarify applicability and provide either a default lot-size transitional requirement (including half-acre boundary lots and rear-yard setback matching) or a 30-foot buffering alternative with required improvements and common ownership for maintenance. She said the rewrite replaced unclear, mixed requirements with clearer, either/or options.
Councilmembers raised multiple issues: Councilwoman Zaberski asked that larger adjacent lots require transitional lot-size matching rather than the buffering alternative; she and others asked how buffers will be maintained if an HOA dissolves or maintenance agreements fail. Council members also pushed staff to consult fire and hazardous-materials experts about industrial adjacency, and asked for clearer operational rules covering noise, outdoor dining and events where mixed use abuts housing.
On data centers, staff noted ongoing work on mitigations for noise and the “white elephant” question should a data center close, including options to require demolition or other remedies. Councilman Torres and others asked staff to return with data-center-specific mitigation language.
Given the range of substantive policy and implementation questions, the council voted to table items 5.3 and 5.4 until staff can return with revisions and additional analysis. Staff suggested a multiweek or multi-month follow-up timeline and asked to return when work is complete.
Next steps: planning staff will draft revisions to address buffer maintenance and enforcement, clarify when lot matching must be used, consult fire and hazardous-materials experts about industrial adjacency, and develop clearer data-center operational and decommissioning protections.

