Warrenville council hears data recommending 25 mph standard for local streets, sparking debate on safety and enforcement

A consultant presented findings to the Warrenville City Council on May 4 recommending a consistent 25 mile‑per‑hour speed limit for local roads and a traffic‑calming toolkit to guide responses to resident concerns and targeted interventions. The proposal would leave several higher‑speed arterials at their current limits (for example, Betavia Road at 35 mph and Galuchia Road at 30 mph) and recommends 35 mph for Williams Road to match adjacent segments.

The recommendation came from Rory Fancler Split, a certified planner with Kimley Horn, who described the study’s methods and data: "Based on the engineering study, a consistent 25 mile per hour speed limit is recommended for local roads in the city," she said, explaining the team used prevailing‑speed measures, crash history from IDOT and adjustment factors for parking and conflict points.

The study found that some streets posted at 20 mph actually have higher prevailing speeds than nearby 25 mph segments and that violation rates on several 20 mph streets exceed commonly used enforcement thresholds. Rory told the council that changing posted limits to 25 mph in those places would, in the consultants’ view, better align posted speeds with motorist behavior and could reduce enforcement burdens.

Council members pushed back. "If we change 20 to 25, everybody on that street is not going to be happy with that at all," Alderman Lockett said, arguing resident safety and street character should weigh heavily when considering changes. Lockett asked whether the city should instead invest more in enforcement and physical roadway changes to lower speeds.

Alderman Widner said narrow subdivisions with parked cars and many children should not be treated the same as wide, low‑conflict streets: "Raising the speed limit there just doesn't make any sense to me at all," Widner said. City staff and the consultant acknowledged that local context matters and that the toolkit is designed to be data‑driven rather than one‑size‑fits‑all.

Staff described the public process and schedule: a public comment period opens immediately and runs through May 26, the item will return to council for discussion on May 18, staff anticipates providing a recommendation on June 1, and any ordinance changes would be considered June 15. City staff also noted that engineering, education and enforcement must work together: posted sign changes alone generally do not change driver behavior without changes to roadway design or enforcement.

The presentation included specific pilot locations where the toolkit could be trialed (Riverside Avenue, Timber Drive, a segment south of Woodlawn, and the segment of Betavia Road west of Butterfield); recommended short‑term measures include temporary speed feedback signs and targeted enforcement, while longer‑term solutions might require roadway reconstruction.

The council did not take formal action on the study that night. Instead members asked staff to publicize the comment period, provide cost estimates for potential implementation measures and return with additional analysis at the May 18 meeting. The June schedule could produce ordinance language if the council directs that next month.