SB26-141 · Bill · 2026 Regular Session · Colorado

Wildlife Collision Prevention

Concerning optional fees during motor vehicle registration that primarily support wildlife projects, and, in connection therewith, using the proceeds of a newly created optional fee to construct wildlife crossings and other transportation improvements and making an appropriation.

Official status: Became Law

4 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.

Beginning on January 1, 2027, the act authorizes an optional collision prevention fee (fee), which is collected at the time of registration of a passenger motor vehicle, light-weight truck, motorcycle, or recreational vehicle (motor vehicle). An individual may decline to pay the fee when registering a motor vehicle, and nonpayment of the fee does not affect the individual's ability to register the motor vehicle. In connection with imposing the fee, the statewide bridge and tunnel enterprise (enterprise) within the department of transportation (department) is required to collaborate with: The department of revenue and county clerks to develop language to notify individuals about the fee, including explicit language regarding the ability to decline to pay the fee and the fact that nonpayment of the fee will not affect an individual's ability to register a motor vehicle; and The department of revenue, the department, county clerks, the division of parks and wildlife, and other impacted stakeholders to conduct a public outreach campaign to educate the public about the fee and what benefits the fee will provide. The enterprise is required to initiate the public outreach campaign as soon as practicable and must develop and deliver customer-facing educational materials to county clerks on or before December 1, 2026. The fee amount is set at $5 and, beginning in state fiscal year 2028-29, the enterprise is allowed to adjust this fee amount upward for inflation. 75% of the revenue from the fee is credited to the newly created collision prevention fund (fund), which is continuously appropriated to the enterprise for use in the following ways: To fund wildlife safe passage projects, defined as one or more projects that reduce wildlife-vehicle collisions and improve habitat connectivity by providing wildlife road crossings; To provide matching money as required by federal grant programs relating to wildlife safe passage projects; To expend for administrative and personnel expenses related to those purposes; and To promote the fee and fund to maximize participation in the optional fee, in collaboration with the department of revenue, impacted stakeholders, and interested organizations. In determining which wildlife safe passage projects the enterprise will undertake, the enterprise is required to: Consult with the division of parks and wildlife (division) and the Colorado wildlife and transportation alliance; Consult with the tribal government if the project is on or adjacent to tribal land; Consult with relevant local governments with jurisdiction over the area of the proposed project and any relevant local organizations engaging in work to reduce vehicle collisions; Consider studies concerning the prioritization of wildlife within the state; Consider whether the wildlife safe passage project is related to a bridge or tunnel project undertaken by the enterprise; and In consultation with the division, consider opportunities for landowner agreements or additional conservation efforts that may be necessary to ensure the continued functionality of infrastructure associated with a proposed wildlife safe passage project. 25% of the revenue from the fee is credited to the wildlife cash fund and continuously appropriated to the division to provide services related to wildlife connectivity and wildlife crossing-related conservation efforts. The act also modifies the process for the keep Colorado wild pass fee, which is an existing optional fee paid at the time an individual registers a motor vehicle, to align with the process for the collision prevention fee by removing the presumption that an individual who declines to pay the keep Colorado wild pass fee is presumed to decline to pay that fee in subsequent years with respect to registration of the same motor vehicle. With this change, an individual must affirmatively opt out of the payment of both the keep Colorado wild pass fee and the collision prevention fee each year that the individual registers the motor vehicle. For the 2026-27 state fiscal year: $53,516 is appropriated from the DRIVES cash fund to the department of revenue for use by the division of motor vehicles; Of funds appropriated from the parks and outdoor recreation cash fund to the department of natural resources for use by the division, $778 is reappropriated to the department of revenue for use by the division of motor vehicles; and $19,940 is appropriated from the legal services cash fund, from revenue received from the department from the collision prevention fund, to the department of law to provide legal services for the department. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on SB26-141, oldest first
DateLocationAction
03/16/2026SenateIntroduced In Senate - Assigned to Transportation & Energy
03/25/2026SenateSenate Committee on Transportation & Energy Refer Amended to Finance
03/31/2026SenateSenate Committee on Finance Refer Amended to Appropriations
04/10/2026SenateSenate Committee on Appropriations Refer Amended to Senate Committee of the Whole
04/10/2026SenateSenate Second Reading Special Order - Passed with Amendments - Committee
04/13/2026SenateSenate Third Reading Passed - No Amendments
04/13/2026HouseIntroduced In House - Assigned to Finance
04/20/2026HouseHouse Committee on Finance Refer Unamended to Appropriations
05/01/2026HouseHouse Committee on Appropriations Refer Unamended to House Committee of the Whole
05/01/2026HouseHouse Second Reading Special Order - Passed - No Amendments
05/04/2026HouseHouse Third Reading Passed - No Amendments
05/20/2026SenateSigned by the President of the Senate
05/20/2026HouseSigned by the Speaker of the House
05/20/2026GovernorSent to the Governor
05/27/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (4 proposed amendments)

Amendments proposed to SB26-141, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.002Committee amendment — Transportation & Energy (Senate)03/25/2026PassedView official document
L.003Committee amendment — Finance (Senate)03/31/2026PassedView official document
L.004Committee amendment — Finance (Senate)03/31/2026PassedView official document
J.001Committee amendment — Appropriations (Senate)04/10/2026PassedView official document

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

Full text

Official record

View SB26-141 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

9e7253db6d6453ac588f93faa352ce6e3235fcc09186e37ca4bb42ba8814c0db

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.