Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Development Code topic
No spam. Unsubscribe anytime.
Belmont launches two‑phase Land Development Code update with public outreach, consultant says
Summary
At a special joint meeting, Belmont City Council and the Planning & Zoning Board heard a consultant outline a two‑phase update to the city's Land Development Code, including an August Planpalooza, stakeholder interviews and an adoption target of about August 2027.
At a special joint meeting, the Belmont City Council and Planning & Zoning Board heard Friese Nichols outline a two‑phase project to update the city’s Land Development Code (LDC), with a diagnostic/code‑audit phase followed by a drafting phase that will include map updates and multiple opportunities for public input.
Alexis Garcia, assistant project manager with Friese Nichols, told the council the project began in June and that the team is aiming "for adoption in about August 2027." She said Phase 1 will produce a code audit documenting issues and community feedback; Phase 2 will focus on drafting updated code modules and a revised zoning map, and will include additional public review and a final public hearing before adoption.
The consultant described an outreach plan that includes an online survey to be launched soon, targeted stakeholder interviews, listening sessions and a Planpalooza scheduled for August 20. Staff said residents can submit written feedback anonymously or provide contact information for follow‑up and that materials will be posted on the project website and linked through the city’s channels.
City staff and board members emphasized coordination with other planning efforts so feedback gathered for the LDC can inform downtown small area planning and other long‑range projects. Staff also said they will work with consultants to notify HOAs, environmental groups and other stakeholders so the engagement reaches a range of community voices.
The consultant said the diagnostic will identify recurring exceptions or variances that may signal sections of code ripe for change, and that one outcome of the diagnostic will be a code‑audit report summarizing recommendations and community feedback to guide drafting.
Procedural notes: the body approved a motion to set the special meeting agenda at the start of the session and later approved a motion to adjourn. No formal code amendment or policy action was taken at the meeting; the discussion was explicitly presented as an early, facilitated conversation to gather direction and priorities for drafting.
