Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Transportation Fee topic
No spam. Unsubscribe anytime.
Boulder council approves Transportation Maintenance Fee after hours of debate; tabling motion fails
Summary
After lengthy debate over outreach, impacts and legal constraints, the Boulder City Council adopted Ordinance 8719 to create a Transportation Maintenance Fee intended to fund pavement, bridge and safety maintenance. A motion to table the ordinance failed 4–5; the ordinance passed 6–3.
The Boulder City Council on Oct. 23 adopted Ordinance 8719, establishing a Transportation Maintenance Fee intended to generate recurring revenue for maintaining the city’s pavement, bridges, sidewalks and safety assets. The ordinance passed following a second reading by a 6–3 roll‑call vote.
Councilmember Matt Benjamin, who moved to pull the ordinance from the consent agenda for separate discussion, urged more outreach before final approval. “I still support the transportation maintenance fee, and I think it’s the right thing for us to do,” Benjamin said, but asked that staff perform additional engagement with businesses and residents before implementation.
Why it matters: City staff and transport planners told the council the fee would provide sustained funding for maintenance that has lagged current needs. Chris Hagland, principal project manager, told council the fee’s full‑year revenue estimate would allow the city to address underfunded maintenance, noting pavement maintenance is a major share of the proposed program. Valerie Watson, deputy director of Transportation and Mobility, warned that current spending levels will not preserve pavement condition and that delays make maintenance more expensive.
What the debate covered: Council discussion focused on three fault lines: (1) whether additional community outreach should delay final approval; (2) the legal limits imposed by the Nexus study used to justify the fee; and (3) the near‑term budget and timing implications if the fee is postponed. Several council members said prior engagement existed but may have gone stale; others said some businesses and residents have not heard details and deserved more outreach.
Staff said delaying the ordinance would shift the implementation schedule. City staff told council that enabling approval at this stage is intended to allow staff to complete detailed implementation design and outreach, and that fee collection would not begin until later (staff noted July as an expected collection start pending final enabling ordinance and implementation steps).
The votes: Council voted down a motion to table/postpone consideration of Ordinance 8719 to Q1/Q2 2026 by a 4–5 margin. On the final adoption roll call, the ordinance passed 6–3. The meeting record shows Councilmembers Shuhard, Speer, Mayor Brockett, Mayor Pro Tem Folkertz and Marquis voted in favor of adoption; Councilmembers Wallach, Weiner and Adams voted no in the roll‑call for final passage.
What comes next: With adoption, staff will proceed to the implementation phase, including outreach to businesses about collection mechanisms, billing cadence and possible exemptions or discounts. Council and legal staff emphasized that substantive changes to fees that exceed the Nexus study would require additional legal study or an updated Nexus analysis.
The council moved on to subsequent agenda items after the vote; staff said they will return with implementation details and any recommended ordinance language adjustments if engagement suggests changes are needed.
