RogataEvery bill, laid before the people.

HB26-1017 · Bill · 2026 Regular Session · Colorado

Criminal Restitution Prohibited for Insurers

Concerning prohibiting an insurer from receiving restitution through the criminal restitution process.

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.

For the purpose of criminal restitution, the act excludes from the definition of 'restitution' losses for which a victim may be compensated through a private insurance policy, except for worker's compensation insurance. Current law defines a 'victim' as any person who has suffered losses because of a contractual relationship, including an insurance company. The act excludes a person from the definition of 'victim' because of a contractual relationship but clarifies that an insurance company is a 'victim' if the insurance company is a victim of a scheme to defraud the insurance company or when the insurance company's property is damaged or stolen through a criminal act. The act authorizes the court to award a victim restitution for a deductible amount under the victim's insurance policy. The act does not prohibit an insurance company from filing a civil action or pursuing any other civil action against a defendant to recover losses the insurance company has suffered. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1017, oldest first
DateLocationAction
01/14/2026HouseIntroduced In House - Assigned to Judiciary
02/03/2026HouseHouse Committee on Judiciary Refer Unamended to House Committee of the Whole
02/06/2026HouseHouse Second Reading Laid Over Daily - No Amendments
02/24/2026HouseHouse Second Reading Special Order - Passed with Amendments - Floor
02/25/2026HouseHouse Third Reading Passed - No Amendments
03/02/2026SenateIntroduced In Senate - Assigned to Judiciary
03/09/2026SenateSenate Committee on Judiciary Refer Unamended to Senate Committee of the Whole
03/12/2026SenateSenate Second Reading Laid Over to 03/13/2026 - No Amendments
03/13/2026SenateSenate Second Reading Laid Over to 03/16/2026 - No Amendments
03/16/2026SenateSenate Second Reading Passed - No Amendments
03/17/2026SenateSenate Third Reading Passed - No Amendments
03/25/2026HouseSigned by the Speaker of the House
03/26/2026SenateSigned by the President of the Senate
03/26/2026GovernorSent to the Governor
04/02/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (1 proposed amendment)

Amendments proposed to HB26-1017, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.005
Sponsor: Representatives Espenoza and Zokaie		Floor amendment — Second Reading (House)02/24/2026PassedView official document

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

Full text

Official record

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

ed46b77c01a598fe8d6b0f3d850d3d7baba2598b8f21afb09b69bfbb6dbb2495

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.