Update Workers' Compensation Statutes Allow Electronic Filing
Concerning updates to the "Workers' Compensation Act of Colorado" necessitated by technology updates.
Official status: Became Law
Prime sponsors
- Janice Marchman (Senate) — Prime Sponsor
- Mark Baisley (Senate) — Prime Sponsor
- Brianna Titone (House) — Prime Sponsor
- Rebecca Keltie (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 makes various updates to language in the 'Workers' Compensation Act of Colorado' to align with technology changes in the division of workers' compensation in the department of labor and employment. These updates include changing current statutory language requiring mailing of documents to allow for electronic mailing or filing of the documents. The act also changes the fund into which an employer or employer's insurance carrier makes payments to the state for a compensable injury resulting in death of a minor without surviving parents from the subsequent injury fund to the Colorado uninsured employer fund. (Note: This summary applies to this bill as enacted.)
Status timeline
| Date | Location | Action |
|---|---|---|
| 05/01/2026 | Senate | Introduced In Senate - Assigned to Business, Labor, & Technology |
| 05/05/2026 | Senate | Senate Committee on Business, Labor, & Technology Refer Unamended - Consent Calendar to Senate Committee of the Whole |
| 05/06/2026 | Senate | Senate Second Reading Special Order - Passed - No Amendments |
| 05/07/2026 | Senate | Senate Third Reading Passed - No Amendments |
| 05/07/2026 | House | Introduced In House - Assigned to State, Civic, Military, & Veterans Affairs |
| 05/09/2026 | House | House Committee on State, Civic, Military, & Veterans Affairs Refer Unamended to House Committee of the Whole |
| 05/11/2026 | House | House Second Reading Special Order - Passed - No Amendments |
| 05/12/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/09/2026 — House State, Civic, Military, & Veterans Affairs: “Refer Senate Bill 26-186 to the Committee of the Whole.” — the motion passed on a vote of 11–0.
- 05/05/2026 — Senate Business, Labor, & Technology: “Refer Senate Bill 26-186 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/12/2026
- Revised version (official PDF), 05/11/2026
- Reengrossed version (official PDF), 05/07/2026
- Engrossed version (official PDF), 05/06/2026
- Introduced version (official PDF), 05/01/2026
Official record
View SB26-186 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
afadee740ffbcaa2516e1b7505739da55af63edba48a4d16f17991799888a8b3
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.
