Citizen Portal
Sign In

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

Get email alerts on the Subdivision Ordinance topic

No spam. Unsubscribe anytime.

Eureka council advances overhaul of subdivision ordinance, schedules Dec. 17 public hearing

Eureka City Council · December 9, 2024
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

Councilors spent the bulk of their Dec. 9 meeting reviewing a proposed rewrite of the subdivision ordinance, pressing the consultant for clearer checklists and a two-step review process and scheduling a Dec. 17 public hearing to collect input and consider RFP awards.

Eureka's city council devoted most of its Dec. 9 meeting to a detailed review of a proposed rewrite of the city's subdivision ordinance, asking the consultant for clearer checklists, harmonized water-rights language and a clearer two-step review process before voting to set a public hearing for Dec. 17.

The council began by placing the subdivision ordinance first on the agenda because members expected lengthy discussion. A consultant-provided draft uses color-coded changes; councilors said they would proceed page by page and share marked-up copies so the group could focus on areas with substantive changes.

Why it matters: The ordinance establishes how the city handles pre-application meetings, applicant submittals, water-rights conveyance, required improvements and the handoff between planning review and final technical checks. Councilors said the document will affect developers, property owners and the city's long-term infrastructure and drainage responsibilities.

Key issues raised during review included who must attend pre-application meetings, whether the city should require potable water conveyance before final plat approval, and how the city defines the Land Use Authority (LUA) versus a Subdivision Review Committee (SRC). Multiple members argued for a two-phase review in which the LUA (the planning commission) performs preliminary vetting and the SRC (engineers, attorney and staff) performs final technical review.

Members flagged inconsistent water-rights language in the draft. One section cited "not less than 1.5 acre-feet per acre" while another referenced "one-third acre-foot per lot." Councilors asked staff and the consultant to harmonize those figures and to make explicit that the conveyed rights must be usable for municipal purposes prior to final plat approval.

On drainage and safety, one councilor urged raising the design standard from a 10-year, 24-hour storm to a higher standard; others said a 100-year standard would be considerably more expensive and may shift costs to developers and nearby property owners. The council also discussed curb-and-gutter, sidewalk timing for simple and minor subdivisions, driveway grades, and construction-on-slopes limits (the draft uses 25 percent in one place; members asked staff to verify consistency with other city code provisions).

Process changes and checklists were a recurring theme. Several councilors asked the Hanson consultant to provide an expanded flowchart and a concrete checklist tied to the flowchart so applicants and city staff know which office receives applications, which documents are required and the timing for reviews. Council members emphasized that city staff should not be left in ambiguous positions, and that the checklist should prevent applicants from assuming informal handoffs.

On administrative timelines, the draft calls for staff to send written notice within 15 calendar days of a complete application and for the LUA to act within 20 business days; the planning commission is required to forward recommendations within 30 days. Members asked staff to confirm whether those timelines align with the city's meeting cadence and to clarify calendar-day versus business-day language.

The council also questioned who is responsible for post-approval tasks such as updating the state's geospatial/911 database. The draft requires city staff to submit new subdivisions to the Utah Geospatial Resource Center within 30 days; councilors asked staff to confirm whether the county recorder performs that step and asked for the text to be revised if the county is the authority.

What the council decided: After the floor debate and a request for clarifications to be returned to the consultant, a council member moved to set a public hearing on Dec. 17 to consider the proposed ordinance and to include RFP awards for related professional services on the same agenda. The council added that staff should return a revised draft and the consultant's expanded checklist before the hearing.

Next steps: The planning commission will hold the Dec. 17 public hearing; council members said they will review any consultant revisions and the checklist before taking final action. Staff was asked to verify the county's role in GIS/911 updates, to harmonize water-rights language, and to research warranty and bonding periods and engineering thresholds recommended for the city's geography.

Quote: "We need a clear, black-and-white checklist — no gray area," a council member said during the discussion, calling for explicit intake and routing procedures so staff and applicants are not put in difficult positions.

Ending: The council scheduled the Dec. 17 public hearing and asked the consultant to return an expanded flowchart and checklist to address the council's questions before consideration.