HB26-1039 · Bill · 2026 Regular Session · Colorado

Adding Municipal Jails to County Jail Oversight Requirements

Concerning requirements for municipal jails.

Official status: Became Law

3 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 July 1, 2027, the act requires municipal jails to comply with existing jail data collection requirements, standards, and oversight. The act requires a keeper of a municipal jail to release a pregnant person charged with a violation of a municipal ordinance from custody if jail staff have a reasonable belief the person is in labor unless remaining in custody is necessary for the health or welfare of the person. If the pregnant person in labor is not released, the use of restraints is prohibited during the labor, delivery, and postpartum recovery, and the jail staff shall make a written record that the labor, delivery, and postpartum recovery occurred at the jail and record the reason the pregnant person was not released from custody. The act requires council members of a city that has a city jail to examine the jail's management and sufficiency at least once a year and allows the attorney general to conduct assessments of municipal jails to identify gaps and deficiencies based on the jail standards. The act adds a nonvoting member who represents a municipality to the jail standards advisory committee. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1039, oldest first
DateLocationAction
01/14/2026HouseIntroduced In House - Assigned to Judiciary
02/04/2026HouseHouse Committee on Judiciary Witness Testimony and/or Committee Discussion Only
02/24/2026HouseHouse Committee on Judiciary Refer Amended to House Committee of the Whole
02/27/2026HouseHouse Second Reading Laid Over Daily - No Amendments
03/02/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
03/03/2026HouseHouse Third Reading Passed - No Amendments
03/10/2026SenateIntroduced In Senate - Assigned to Judiciary
03/18/2026SenateSenate Committee on Judiciary Refer Unamended to Senate Committee of the Whole
03/23/2026SenateSenate Second Reading Passed - No Amendments
03/24/2026SenateSenate Third Reading Passed - No Amendments
04/16/2026HouseSigned by the Speaker of the House
04/16/2026SenateSigned by the President of the Senate
04/16/2026GovernorSent to the Governor
04/27/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (3 proposed amendments)

Amendments proposed to HB26-1039, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.003Committee amendment — Judiciary (House)02/24/2026PassedView official document
L.004Committee amendment — Judiciary (House)02/24/2026PassedView official document
L.006Committee amendment — Judiciary (House)02/24/2026PassedView official document

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

Full text

Official record

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

d85ef5ed92e2b11cba0895dc12ebafdf7901b4a28ce58b1d803e50a05f5d547e

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.