SB26-093 · Bill · 2026 Regular Session · Colorado

Workers' Compensation Insurance Coverage Verification

Concerning ensuring compliance with workers' compensation insurance coverage requirements.

Official status: Became Law

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

The act requires that an applicant for a building permit or a construction permit for a project with a total construction cost of more than $1 million (permit) file with the permitting agency, prior to commencing work under the permit, a signed declaration under penalty of perjury verifying that any person working under the permit maintains valid workers' compensation insurance coverage for the duration of the permit. A person may file a complaint with the division of workers' compensation in the department of labor and employment alleging a person's workers' compensation insurance coverage is not in compliance with the state's workers' compensation laws. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on SB26-093, oldest first
DateLocationAction
02/10/2026SenateIntroduced In Senate - Assigned to Business, Labor, & Technology
03/05/2026SenateSenate Committee on Business, Labor, & Technology Refer Amended to Appropriations
04/24/2026SenateSenate Committee on Appropriations Refer Amended to Senate Committee of the Whole
04/28/2026SenateSenate Second Reading Passed with Amendments - Committee, Floor
04/29/2026SenateSenate Third Reading Passed - No Amendments
04/29/2026HouseIntroduced In House - Assigned to Business Affairs & Labor
05/06/2026HouseHouse Committee on Business Affairs & Labor Refer Amended to House Committee of the Whole
05/07/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
05/08/2026HouseHouse Third Reading Laid Over Daily - No Amendments
05/09/2026HouseHouse Third Reading Passed - No Amendments
05/13/2026SenateSenate Considered House Amendments - Result was to Concur - Repass
05/22/2026SenateSigned by the President of the Senate
05/22/2026HouseSigned by the Speaker of the House
05/22/2026GovernorSent to the Governor
05/29/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (5 proposed amendments)

Amendments proposed to SB26-093, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.002Committee amendment — Business, Labor, & Technology (Senate)03/05/2026PassedView official document
L.003Committee amendment — Business, Labor, & Technology (Senate)03/05/2026PassedView official document
L.004Committee amendment — Appropriations (Senate)04/24/2026PassedView official document
L.005
Sponsor: Senator Sullivan
Floor amendment — Second Reading (Senate)04/28/2026PassedView official document
L.006Committee amendment — Business Affairs & Labor (House)05/06/2026PassedView official document

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

Full text

Official record

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

d29a84e4853142fe9b75d620b724702763a4b4548ef8259db82ae2ab3436087a

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.