SB26-059 · Bill · 2026 Regular Session · Colorado

Multiple Elected Offices Prohibited for General Assembly

Concerning a prohibition on a member of the general assembly holding multiple elected offices.

Official status: Became Law

1 proposed amendment

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 with the first regular session of the seventy-sixth general assembly, the act prohibits a member of the general assembly from holding any other elected offices while serving as a member of the general assembly, with the following exceptions: The member of the general assembly holds a special district elected office; The member of the general assembly has less than one year remaining in their term in another elected office at the time they take the oath of office of the general assembly; The member of the general assembly has less than one year remaining in their term in the general assembly at the time they take the oath of office of another elected office; or The member of the general assembly is a senator who is in the middle of their term at the beginning of the first regular session of the seventy-sixth general assembly. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on SB26-059, oldest first
DateLocationAction
01/28/2026SenateIntroduced In Senate - Assigned to State, Veterans, & Military Affairs
02/24/2026SenateSenate Committee on State, Veterans, & Military Affairs Refer Amended - Consent Calendar to Senate Committee of the Whole
02/27/2026SenateSenate Second Reading Laid Over to 03/02/2026 - No Amendments
03/02/2026SenateSenate Second Reading Passed with Amendments - Committee
03/03/2026SenateSenate Third Reading Passed - No Amendments
03/03/2026HouseIntroduced In House - Assigned to State, Civic, Military, & Veterans Affairs
03/23/2026HouseHouse Committee on State, Civic, Military, & Veterans Affairs Refer Unamended to House Committee of the Whole
03/26/2026HouseHouse Second Reading Laid Over Daily - No Amendments
04/20/2026HouseHouse Second Reading Special Order - Passed - No Amendments
04/21/2026HouseHouse Third Reading Laid Over Daily - No Amendments
04/22/2026HouseHouse Third Reading Passed - No Amendments
04/27/2026SenateSigned by the President of the Senate
04/27/2026HouseSigned by the Speaker of the House
04/27/2026GovernorSent to the Governor
05/04/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (1 proposed amendment)

Amendments proposed to SB26-059, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.001Committee amendment — State, Veterans, & Military Affairs (Senate)02/24/2026PassedView official document

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

Full text

Official record

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

4e6c41df255b2804e756fc2a8e756cc6bcf1c7937ab5c96279f126c36341aebe

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.