Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use topic
No spam. Unsubscribe anytime.
Council signals desire to keep 100‑foot Provo River setback in code, ask staff to craft design‑corridor approach
Summary
City planners proposed options Sept. 23 to clarify the Provo River 100‑foot setback and related design guidance. Council members told staff they favor keeping a 100‑foot default setback in ordinance while creating clearer criteria for limited exceptions and adopting design‑corridor standards to encourage river‑facing development and public access.
Get email alerts on the Land Use topic
No spam. Unsubscribe anytime.
City planning staff asked the Provo City Council Sept. 23 for direction on the city’s Provo River setback and possible design standards after a series of code amendments in 2020–21 that added a 40‑foot maintenance easement exception. Policy analyst David Pyle told the council that the 100‑foot setback has been in city code since the 1980s, originally established after 1983 flood events, and that a 40‑foot maintenance easement was added later to protect Public Works’ ability to operate equipment in the corridor.
Pyle said the city’s River and Lakeshore plan recommends encouraging buildings to face the river, adding active uses such as small commercial spaces and restaurants near the river, and adopting design guidance that integrates new development with the river’s natural amenity. He outlined several alternatives: keep a hard 100‑foot setback in ordinance (variance only by formal variance process); keep the existing language but strengthen and clarify the criteria for administrative exceptions that permit development closer than 100 feet; or create a Provo River Design Corridor ordinance that would require specific design responses for developments that abut or front the river.
Council discussion focused on two themes. Several councilors said they would prefer a 100‑foot default setback codified in ordinance rather than leaving the shorter 40‑foot maintenance easement as a standing administrative alternative. Several members also expressed support for a design‑corridor process: a durable, codified set of criteria and design standards to guide when and where the council would approve development closer to the river in exchange for public benefits (for example, river‑facing commercial uses, trail connections, or flood‑safe building forms).
Councilors and staff examined why the 40‑foot exception exists in the code. Planning staff explained that the 40‑foot maintenance easement emerged in a 2021 code amendment tied to floodplain mapping and a shift in finished‑floor elevation requirements; planners said exceptions were intended to allow flexibility in limited cases and to ensure an operational corridor for river maintenance. Council members asked staff to research the original staff reports and the rationale for the 2021 change and to consult Public Works and floodplain engineers before returning with specific ordinance language.
City staff recommended a longer, staff‑led process to write design‑corridor standards and stronger written criteria for any exceptions to the setback; the council gave staff direction to prepare options and to return with draft ordinance language. Members asked staff to consider a process that would preserve public safety (flood risk), allow riverside amenities when safe and appropriate, and make the city’s rules clearer and less discretionary.
Why it matters: Provo River frontage is a high‑value corridor for recreation and private development. The council’s decision will shape how closely new buildings can be sited to the river, whether new development can include riverfront commercial uses, and how the city balances flood safety with urban design and public access.
What happens next: staff will research the 2020–21 amendments, coordinate with Public Works and floodplain staff, and draft proposed ordinance language for a design corridor and clearer exception criteria. The topic will return to council for further direction and potential code amendment.

