Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Planning Master Plan topic

No spam. Unsubscribe anytime.

City staff refreshes Reimagine Reno master plan for council; cautions against using it as strict code

2316744 · February 13, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Development services staff presented the 2017 Reimagine Reno master plan as a 20‑year vision and urged council and planners to treat it as guidance — not a regulatory checklist — while underlining the plan’s role in long‑range CIP, concurrency and prioritization.

City staff gave a high‑level refresher on the Reimagine Reno master plan, urging elected officials and commissioners to treat the document as a guiding vision rather than a set of regulatory requirements.

Angela Foos, assistant director of Development Services, told the council the current master plan — adopted in 2017 after roughly two and a half years of public outreach — is intended to guide policy, infrastructure planning and long‑term land use decisions over a 20‑year horizon. Foos emphasized that the plan uses “promote,” “encourage” and “should” rather than “shall,” and therefore is not a codebook: zoning and text amendments remain the forum for legally binding requirements.

Why it matters: Council members asked how the master plan should inform decisions when projects come forward. Foos said staff always compares applications to master‑plan goals and policies in staff reports, but the plan does not itself substitute for zoning or code requirements. The city attorney warned council that legislative zoning decisions are separate from quasi‑judicial reviews of specific project applications. The office also cautioned that arbitrary or inconsistent application of plan language in denials could carry legal risk, citing a Nevada Supreme Court decision referenced in staff remarks.

Council discussion centered on two themes: how planners and staff should present master‑plan connections in staff reports, and whether the council should convert certain plan goals into mandatory zoning or code standards (for example, sustainability measures such as EV charging or solar requirements). Several councilmembers requested wider outreach — including presentations to planning commissioners and neighborhood advisory boards — so stakeholders better understand how the plan is used in day‑to‑day decisions.

Foos summarized recent context changes since 2017 (Tesla and Switch expansions, Swan Lake flooding, COVID and housing pressures), saying the city’s priorities have shifted over time and the master plan must be viewed alongside strategic and budgetary decisions. She also urged caution in relying on the plan as a legal basis to deny projects without clear code authority.

Looking ahead: councilmembers asked staff to brief the planning commission on the plan’s intent and to consider policy work to translate priority goals into code where council desires binding standards.