Summit County engineers ask Snyderville Basin commissioners to vet consolidated engineering standards; propose 25‑year design for drainage pipes

Summit County engineering staff on Wednesday sought feedback from the Snyderville Basin Planning Commission on a comprehensive rewrite of the county’s engineering standards intended to unify technical design rules now scattered across multiple code sections.

Steve Dennis of the Summit County engineering department told the commission the draft moves technical design criteria out of various development‑code sections and into a single chapter (Title 12) so engineers and reviewers can find standards in one place.

The rewrite centers on three changes: switching road classification from a development‑centric scheme to engineering classifications (arterial, collector, major local, minor local) that determine widths, right‑of‑way and shoulder requirements; reclassifying driveway and access standards to distinguish fire‑access routes from lower‑duty accesses and to allow narrower, engineered solutions where fire‑truck access is not required; and increasing the design standard for underground conveyance (catch basins and pipes) from a 10‑year storm event to a 25‑year event while retaining long‑term retention/detention sizing at the 100‑year event.

"We’ve written a pretty comprehensive rewrite of the code here, with the goal of unifying the standards," Dennis said. ‘‘We thought it prudent to up that to 25 [years] given what we’ve seen recently — higher runoff and more intense storms.’’

Commissioners pressed staff on the practical impacts. Dennis said site‑by‑site results will vary: some parking‑lot drainage runs might require larger pipe diameters — potentially increasing materials costs — but engineers can mitigate impacts through design choices such as multiple smaller ponds or distributed conveyance rather than one large pipe and pond.

Several commissioners asked that staff return with a short, plain‑language summary and a clear flag on every change that is substantive (numeric or design) versus changes that are purely relocations into the consolidated chapter. "It’d be helpful to know whether something was moved only or if any of the numbers changed," Commissioner John Kucera said.

Staff also noted where policy and engineering overlap. Parking siting, minimum counts and setback dimensions remain in the development code (Title 10); Title 12 will house technical parking design (grades, slopes, widths, drainage). For floodplain mapping, staff agreed to add introductory plain‑language text explaining where special flood hazard areas are located and pointing readers to FEMA maps on file.

Staff said the outreach is iterative: they will incorporate commissioner comments, other planning‑area commission feedback and input from service providers and return in several weeks with a clean draft ordinance language and a summary that highlights substantive edits. A formal recommendation to council is expected after that follow‑up.

The work session was informational only; the commission did not take a final vote on the draft engineering chapter. The next step is for staff to produce the summarized, clean draft and present it for the commission’s recommendation to the county council.