SB26-152 · Bill · 2026 Regular Session · Colorado

Changes Automated Vehicle Identification System Usage

Concerning changes to the usage of automated vehicle identification systems.

Official status: Became Law

14 proposed amendments

Prime sponsors

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

The act makes changes to the use of automated vehicle identification systems (AVIS), including: Modifying the public notice requirements that the state, a county, a city and county, a municipality, or an agency responsible for placing a new AVIS must provide before utilizing the new AVIS; Making the registered owner of a motor vehicle responsible for all civil penalties associated with violations committed with the vehicle unless the vehicle was sold, leased, or stolen; Creating a procedure through which the registered owner of a motor vehicle may prove that the vehicle was sold, leased, or stolen at the time when a violation was detected by an AVIS and, thereby, under certain circumstances, relieving the registered owner from having to pay the civil penalty associated with the notice of violation; Requiring that, if a variable speed limit is in effect or a speed limit is otherwise temporarily lowered due to hazardous weather or other traffic conditions, the state, a county, a city and county, or a municipality may issue only a notice of violation and civil penalty for a speeding violation that exceeds the regular maximum posted speed limit for that location; Changing the penalty structure for different levels of speeding violations detected by an AVIS; Establishing that the compensation the state, a county, a city and county, or a municipality pays to a manufacturer or vendor of an AVIS must, in addition to other conditions, be a flat monthly fee or a flat hourly rate and not include any incentives, bonuses, or escalators related to the number of citations issued or the amount of revenue generated; and Beginning January 1, 2035, increasing the civil penalties associated with notices of violations issued for violations captured by an AVIS. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on SB26-152, oldest first
DateLocationAction
03/31/2026SenateIntroduced In Senate - Assigned to Transportation & Energy
04/29/2026SenateSenate Committee on Transportation & Energy Refer Amended to Senate Committee of the Whole
05/04/2026SenateSenate Second Reading Passed with Amendments - Committee, Floor
05/05/2026SenateSenate Third Reading Passed with Amendments - Floor
05/05/2026HouseIntroduced In House - Assigned to Transportation, Housing & Local Government
05/08/2026HouseHouse Committee on Transportation, Housing & Local Government Refer Amended to House Committee of the Whole
05/11/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee, Floor
05/12/2026HouseHouse Third Reading Passed - No Amendments
05/13/2026SenateSenate Considered House Amendments - Result was to Concur - Repass
05/26/2026SenateSigned by the President of the Senate
05/26/2026HouseSigned by the Speaker of the House
05/27/2026GovernorSent to the Governor
06/02/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (14 proposed amendments)

Amendments proposed to SB26-152, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.001Committee amendment — Transportation & Energy (Senate)04/29/2026PassedView official document
L.002Committee amendment — Transportation & Energy (Senate)04/29/2026PassedView official document
L.003Committee amendment — Transportation & Energy (Senate)04/29/2026PassedView official document
L.005Committee amendment — Transportation & Energy (Senate)04/29/2026PassedView official document
L.007
Sponsor: Senator Pelton B.
Floor amendment — Second Reading (Senate)05/04/2026PassedView official document
L.009
Sponsor: Senator Pelton B.
Floor amendment — Second Reading (Senate)05/04/2026PassedView official document
L.010
Sponsor: Senator Pelton B.
Floor amendment — Second Reading (Senate)05/04/2026PassedView official document
L.012
Sponsor: Senator Pelton B.
Floor amendment — Third Reading (Senate)05/05/2026PassedView official document
L.016Committee amendment — Transportation, Housing & Local Government (House)05/08/2026PassedView official document
L.017Committee amendment — Transportation, Housing & Local Government (House)05/08/2026PassedView official document
L.018Committee amendment — Transportation, Housing & Local Government (House)05/08/2026PassedView official document
L.019
Sponsor: Representative Willford
Floor amendment — Second Reading (House)05/11/2026PassedView official document
L.020
Sponsor: Representative Willford
Floor amendment — Second Reading (House)05/11/2026PassedView official document
L.023
Sponsor: Representative Willford
Floor amendment — Second Reading (House)05/11/2026PassedView official document

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Full text

Official record

View SB26-152 on leg.colorado.gov

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

3be86e86a688af3d8f05598623b70d65688527fbe1ce7ca143edd47a4e7a7efe

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-11-06 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.