Riverton staff outlines phased, data-driven traffic-calming program

Matt, a public works engineer, opened the council's work-session presentation with an overview of a new, written traffic-calming standard operating procedure and a three-phase approach for resident requests. "Our traffic calming program is not something new," Matt said, describing the goal of "data driven equity" and the use of objective benchmarks such as crash history and the 85th-percentile speed to guide priorities. He told the council that a typical trigger to consider physical measures is 8 miles per hour above the posted speed at the 85th percentile.

Council members asked for clarity about what qualifies as a formal request and whether accident counts factor into prioritization; Matt said the program accepts a standard form covering any right-of-way issue (speeding, crossings, trip hazards, stop-sign timing) and that accident-prone stretches should be elevated into capital project consideration. He committed to putting phase timelines on each request and to publishing a monthly spreadsheet summarizing new incoming requests, active studies and closed items so council members can refer residents to a single source. "So you kind of see where they're at," a public works staffer added when describing the tracking sheet.