RogataEvery bill, laid before the people.

HB26-1025 · Bill · 2026 Regular Session · Colorado

Exempt Auctioneers Charitable Solicitation Requirements

Concerning an exemption for auctioneers from certain requirements of the "Colorado Charitable Solicitations Act".

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.

As defined in the 'Colorado Charitable Solicitations Act', a 'paid solicitor' is a person that, for monetary compensation, performs a service in which contributions are solicited in Colorado for a charitable purpose or for the benefit of a charitable organization. The act excludes from the definition of 'paid solicitor' an auctioneer who provides auctioneer services to a charitable organization. As a result, the auctioneer is exempted from the requirements of the 'Colorado Charitable Solicitations Act' for paid solicitors. The exemption applies regardless of whether the auctioneer is contracted or paid to provide their auctioneer services to the charitable organization or is volunteering their auctioneer services to the charitable organization without compensation. However, for the exemption to apply, an auctioneer who provides auctioneer services to a charitable organization may not directly receive or handle contributions or charitable funding on behalf of the charitable organization for which the auctioneer is contracted or volunteering. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1025, oldest first
DateLocationAction
01/14/2026HouseIntroduced In House - Assigned to Agriculture, Water & Natural Resources
02/09/2026HouseHouse Committee on Agriculture, Water & Natural Resources Refer Amended to House Committee of the Whole
02/12/2026HouseHouse Second Reading Laid Over Daily - No Amendments
02/17/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
02/18/2026HouseHouse Third Reading Passed - No Amendments
02/20/2026SenateIntroduced In Senate - Assigned to Business, Labor, & Technology
03/05/2026SenateSenate Committee on Business, Labor, & Technology Refer Unamended - Consent Calendar to Senate Committee of the Whole
03/09/2026SenateSenate Second Reading Passed - No Amendments
03/10/2026SenateSenate Third Reading Passed - No Amendments
03/18/2026HouseSigned by the Speaker of the House
03/19/2026SenateSigned by the President of the Senate
03/19/2026GovernorSent to the Governor
03/27/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (1 proposed amendment)

Amendments proposed to HB26-1025, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.001Committee amendment — Agriculture, Water & Natural Resources (House)02/09/2026PassedView official document

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

Full text

Official record

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

73afa772424342a076b2d2cbf18fd444f49c0b54bd772dc98e9ada699bbf1362

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.