Planning commission reviews Emigration Canyon site-development draft, pressing for stronger bonding and clearer standards

Acting Chair Andrew Wallace convened the Emigration Canyon Planning Commission on Dec. 12 and introduced staff and the working draft of the canyon’s site-development standards, referred to in the meeting as the FCOS draft. Commissioners spent the bulk of the meeting probing technical sections on slope protection and bonding, foundation walls used for slope retention, private-access road definitions, trails and tree protections.

Why it matters: commissioners said recent local grading and slope-stabilization problems showed gaps between the code on paper and field practice. Several members urged clearer language that would require applicants to secure the same suite of permits and post a single engineering bond that covers retaining structures, slope stabilization and revegetation before grading begins. That change, they said, would reduce the chance that contractors start excavation without completing mitigation work and leave properties unstable.

Discussion and staff response: staff summarized conversations with the county’s engineering and stormwater teams, which said they now require additional permitting elements be in place before grading is allowed and are bundling those items into an initial engineering bond. Commissioners asked whether that practice should be codified in the FCOS ordinance or whether the problem is enforcement of existing requirements. Several members asked staff to bring the grading/stormwater supervisor (Alex Rudowski) and the county engineer (referred to as Tolan in the meeting) to the next meeting so the commission can hear how bonds are calculated, who approves them, and how enforcement and inspections are handled.

Foundation walls and retaining walls: commissioners debated whether foundation walls that extend outside a building should be treated as retaining walls. Staff proposed language that would permit foundation-wall extensions so long as they "shall comply with" the retaining-wall requirements rather than creating a loophole that would allow excessive excavation (for example, converting a basement into a walkout by building an outsized foundation/retaining wall). Several commissioners favored the approach of allowing the extension but requiring compliance with the retaining-wall subsection.

Private access roads and driveways: engineering staff told the commission that anything within a public right-of-way or on public property must meet roadway standards; in contrast, a private driveway generally is treated less stringently. The draft treats long driveways (greater than 50 feet) or driveways that provide access to multiple units as "private access roads," which may trigger higher engineering standards. Commissioners raised equity and cost concerns for small property owners who would face expensive roadway upgrades for modest improvements (for example, adding a detached garage). Several members suggested deferring to fire-authority approval in marginal cases and requested that staff clarify whether "private access road" is a necessary separate term or whether existing "private roadway" language will suffice.

Trails, density bonuses and the master plan: the draft proposes a trails-related incentive: up to a 25% density bonus applied to the portion of a site lying on slopes greater than 30% if a developer dedicates trail land or easements that are "beyond what would be roughly proportional to the demand" generated by the development. Commissioners asked staff to split the paragraph into numbered subsections, provide a diagram showing sending/receiving areas, and identify objective metrics (for example, linear feet of trail per dwelling equivalent) to determine when a dedication qualifies as "beyond" proportional demand. Staff flagged that the city’s trails master plan (2007) is out of date and said they would consult Parks & Recreation on level-of-service metrics for trails.

Tree and vegetation protection and fire code references: the draft contains provisions to preserve the canyon’s vegetation, limit removal outside clearance and require revegetation and replacement for removed significant trees. Commissioners noted ambiguous references to a "Utah Wildland Urban Interface Code" and the "International Wildland Urban Interface Code (IWUIC, 2021)." Staff agreed to confirm which WUI edition Unified Fire Authority and Salt Lake County currently use and to correct the code citation before the ordinance is finalized. The commission also asked staff to check whether agricultural/forestry uses such as tree farms or commercial apiaries remain permitted in current FR zoning and to remove obsolete clauses if those uses were intentionally removed.

Next steps: staff will (1) invite engineering and stormwater supervisors (including Alex Rudowski and Tolan) to explain bonding, permitting and enforcement; (2) check the county/fire authority’s adopted WUI standard and correct the citation; (3) verify current FR-zone permitted uses related to agriculture and silviculture; and (4) tidy ordinance language (breaking long paragraphs into numbered subsections and swapping phrases such as "subject to" for stronger mandates like "shall comply with"). The commission left the draft open for revision and scheduled further review at a subsequent meeting.

The commission did not take votes on any substantive ordinance changes at this meeting; the only votes recorded were procedural (approving minutes and the 2025 meeting schedule).