RogataEvery bill, laid before the people.

HB26-1391 · Bill · 2026 Regular Session · Colorado

Safe Drinking Water in Child Care Centers & Schools

concerning the testing of drinking water, and 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.

In 2022, the general assembly enacted, and the governor subsequently signed into law, House Bill 22-1358 ('Concerning measures to eliminate the presence of lead in the drinking water of certain facilities where children are present, and, in connection therewith, making an appropriation'), which required child care centers, family child care homes, and each public school that serves any of grades preschool through eighth grade to: Test its drinking water sources by having a state-certified laboratory measure the lead content of water drawn from each drinking water source; and Satisfy other requirements concerning the provision of safe drinking water. House Bill 22-1358 also created the school and child care clean drinking water fund (fund) to help schools, child care centers, and family child care homes comply with House Bill 22-1358. House Bill 22-1358 included a repeal date of June 30, 2026, for its provisions. The act extends the provisions, with amendments, until June 30, 2029. The act also adds high schools (i.e., schools that serve grades 9 to 12) to the scope of House Bill 22-1358, which means that high schools may receive grants from the fund and must satisfy certain requirements on or before dates specified in the act. The act requires the department to adopt rules establishing how a child care center shall demonstrate compliance with the requirements concerning the testing for the presence of lead in drinking water. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1391, oldest first
DateLocationAction
04/02/2026HouseIntroduced In House - Assigned to Appropriations
04/06/2026HouseHouse Committee on Appropriations Refer Unamended to House Committee of the Whole
04/08/2026HouseHouse Second Reading Special Order - Laid Over Daily - No Amendments
04/09/2026HouseHouse Second Reading Special Order - Passed with Amendments - Floor
04/10/2026HouseHouse Third Reading Laid Over Daily - No Amendments
04/11/2026HouseHouse Third Reading Passed - No Amendments
04/13/2026SenateIntroduced In Senate - Assigned to Appropriations
04/14/2026SenateSenate Committee on Appropriations Refer Unamended - Consent Calendar to Senate Committee of the Whole
04/15/2026SenateSenate Second Reading Special Order - Passed - No Amendments
04/16/2026SenateSenate Third Reading Passed - No Amendments
05/26/2026HouseSigned by the Speaker of the House
05/26/2026SenateSigned by the President of the Senate
05/26/2026GovernorSent to the Governor
05/28/2026GovernorGovernor Signed

Recorded votes

Full text

Official record

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

16db4a590f5a5c769f66a60e6fc3f524956dc003be1d38940fcb3b7f435a6055

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.