Adjust Experience Modification Factor in Workers' Compensation
Concerning the adjustment of an employer's experience modification factor in workers' compensation.
Official status: Became Law
Prime sponsors
- Marc Snyder (Senate) — Prime Sponsor
- Marc Catlin (Senate) — Prime Sponsor
- Tisha Mauro (House) — Prime Sponsor
- Chris Richardson (House) — Prime Sponsor
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 creates a process for employers and licensed insurance producers to update an employer's experience modification factor when: An open claim is reported by an insurance carrier to the rating bureau with a higher open claim amount than the amount after the claim was closed; and The lower claim amount would reduce an employer's experience modification factor at least .05 compared to the previously released experience modification factor or from above 1.0 to 1.0 or below. The employer must notify the insurance carrier between the time the claim is reported to a rating bureau and 31 days after the employer's rating effective date. The insurance carrier is required to credit the employer for a premium change resulting from the revised experience modification factor. (Note: This summary applies to this bill as enacted.)
Status timeline
| Date | Location | Action |
|---|---|---|
| 04/21/2026 | Senate | Introduced In Senate - Assigned to Business, Labor, & Technology |
| 04/30/2026 | Senate | Senate Committee on Business, Labor, & Technology Refer Unamended - Consent Calendar to Senate Committee of the Whole |
| 05/01/2026 | Senate | Senate Second Reading Special Order - Passed - No Amendments |
| 05/04/2026 | Senate | Senate Third Reading Passed - No Amendments |
| 05/04/2026 | House | Introduced In House - Assigned to Business Affairs & Labor |
| 05/06/2026 | House | House Committee on Business Affairs & Labor Refer Unamended to House Committee of the Whole |
| 05/07/2026 | House | House Second Reading Special Order - Passed - No Amendments |
| 05/08/2026 | House | House Third Reading Laid Over Daily - No Amendments |
| 05/09/2026 | House | House Third Reading Passed - No Amendments |
| 05/21/2026 | Senate | Signed by the President of the Senate |
| 05/21/2026 | House | Signed by the Speaker of the House |
| 05/21/2026 | Governor | Sent to the Governor |
| 06/02/2026 | Governor | Governor Signed |
Recorded votes
- 05/06/2026 — House Business Affairs & Labor: “Refer Senate Bill 26-175 to the Committee of the Whole.” — the motion passed on a vote of 13–0.
- 04/30/2026 — Senate Business, Labor, & Technology: “Refer Senate Bill 26-175 to the Committee of the Whole and with a recommendation that it be placed on the consent calendar.” — the motion passed on a vote of 5–0.
Full text
- Signed Act version (official PDF), 06/03/2026
- Final Act version (official PDF), 05/20/2026
- Rerevised version (official PDF), 05/09/2026
- Revised version (official PDF), 05/07/2026
- Reengrossed version (official PDF), 05/04/2026
- Engrossed version (official PDF), 05/01/2026
- Introduced version (official PDF), 04/21/2026
Official record
View SB26-175 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
1c4b4a6093bdf2b2e09e8dfb268ea178832e4307ab761c272c798128cee2ddeb
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.
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.
