RogataEvery bill, laid before the people.

SB26-012 · Bill · 2026 Regular Session · Colorado

Compensable Losses for Tribal Members

Concerning compensable losses under the "Colorado Crime Victim Compensation Act" for enrolled members of a federally recognized tribe.

Official status: Became Law

3 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 allows persons who are indigenous to receive compensation for traditional Native American healing ceremonies and practices and related expenses under the 'Colorado Crime Victim Compensation Act', which includes: Traditional counseling and healing from an elder or spiritual healer; Traditional ceremonial practices; Ceremonial burials, including clothing for the deceased, meals, and other related expenses; Child care during burial ceremonies; Reimbursement for honoraria provided in connection with ceremonial services; and Reasonable travel expenses related to the traditional Native American healing ceremonies and practices. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on SB26-012, oldest first
DateLocationAction
01/14/2026SenateIntroduced In Senate - Assigned to Judiciary
02/04/2026SenateSenate Committee on Judiciary Refer Unamended - Consent Calendar to Senate Committee of the Whole
02/09/2026SenateSenate Second Reading Passed - No Amendments
02/10/2026SenateSenate Third Reading Passed - No Amendments
02/11/2026HouseIntroduced In House - Assigned to Judiciary
03/04/2026HouseHouse Committee on Judiciary Refer Amended to House Committee of the Whole
03/09/2026HouseHouse Second Reading Laid Over Daily - No Amendments
04/30/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee, Floor
05/01/2026HouseHouse Third Reading Laid Over Daily - No Amendments
05/04/2026HouseHouse Third Reading Passed with Amendments - Floor
05/07/2026SenateSenate Considered House Amendments - Result was to Concur - Repass
05/21/2026SenateSigned by the President of the Senate
05/21/2026HouseSigned by the Speaker of the House
05/21/2026GovernorSent to the Governor
05/29/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (3 proposed amendments)

Amendments proposed to SB26-012, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.003Committee amendment — Judiciary (House)03/04/2026PassedView official document
L.007
Sponsor: Representative Velasco		Floor amendment — Second Reading (House)04/30/2026PassedView official document
L.009
Sponsor: Representative Velasco		Floor amendment — Third Reading (House)05/04/2026PassedView official document

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

Full text

Official record

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

d84ed9ca8578dcce63c8a28b53d0b43ab4d841d60d2a5a90f6139545cd0eb898

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.