HB26-1272 · Bill · 2026 Regular Session · Colorado

Extreme Temperatures Worker Protections

Concerning protections for workers necessitated by climate change, and, in connection therewith, making an appropriation.

Official status: Became Law

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 requires the division of labor standards and statistics (division) in the department of labor and employment (CDLE), on or before January 15, 2027, to begin collecting data concerning temperature-related injury or illness or temperature-related emergencies at worksites and to: Develop a platform on CDLE's website where users can provide information about occurrences of temperature-related injury or illness or temperature-related emergencies; Obtain from the department of public health and environment (CDPHE) data that CDPHE has collected through its syndromic surveillance program regarding occurrences of heat-related injury or illness or heat-related emergencies; and Collect similar data from the division of workers' compensation and the Center for Improving Value in Health Care. On or before July 1, 2028, the act requires the division to develop a model temperature-related injury and illness prevention plan (TRIIPP) that thereafter must be made available on CDLE's website. Additionally, the act requires the division to review and update the model TRIIPP at least every 5 years and grants the division authority to adopt rules necessary to implement the act. $76,651 is appropriated from the general fund to the department for use by the division. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1272, oldest first
DateLocationAction
02/19/2026HouseIntroduced In House - Assigned to Health & Human Services
03/18/2026HouseHouse Committee on Health & Human Services Refer Amended to Appropriations
05/04/2026HouseHouse Committee on Appropriations Refer Amended to House Committee of the Whole
05/04/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
05/05/2026HouseHouse Third Reading Passed - No Amendments
05/05/2026SenateIntroduced In Senate - Assigned to State, Veterans, & Military Affairs
05/07/2026SenateSenate Committee on State, Veterans, & Military Affairs Refer Unamended to Appropriations
05/11/2026SenateSenate Committee on Appropriations Refer Amended to Senate Committee of the Whole
05/11/2026SenateSenate Second Reading Special Order - Passed with Amendments - Committee
05/13/2026SenateSenate Third Reading Laid Over Daily - No Amendments
05/13/2026SenateSenate Third Reading Passed - No Amendments
05/13/2026HouseHouse Considered Senate Amendments - Result was to Concur - Repass
06/03/2026HouseSigned by the Speaker of the House
06/03/2026SenateSigned by the President of the Senate
06/03/2026GovernorSent to the Governor
06/04/2026GovernorGovernor Signed

Recorded votes

Full text

Official record

View HB26-1272 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

2f9b8b1d35a5f2ace2976e6982991b9dcc870df916ba484d4591ebd4f46eb87a

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-10-28 · 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.