HB26-1341 · Bill · 2026 Regular Session · Colorado

Colorado Agricultural Development Authority Bond Allocation Service Period

Concerning a modification to the service period during which the Colorado agricultural development authority may allocate its portion of the private activity bond state ceiling allocation.

Official status: Became Law

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 state private activity bond program funds privately developed projects by allowing the state and its political subdivisions to issue tax-exempt private activity bonds. The federal internal revenue code limits the total amount of tax-exempt private activity bonds that a state and its political subdivisions may issue each year by imposing a private activity bond ceiling (state ceiling). Existing law specifies a formula to allocate the ability to issue tax-exempt private activity bonds up to the state ceiling and initially allocates 50% of these bonds among several state issuing authorities through direct allocations as determined by the department of local affairs (department). On September 15 each year, with a few exceptions, each state issuing authority is required to relinquish unused portions of its direct allocation which is then further allocated pursuant to law. The Colorado agricultural development authority is one of the state issuing authorities to which the department may allocate a portion of the state ceiling. The act changes the date on which the Colorado agricultural development authority is required to relinquish the unused portion of its direct allocation from September 15 to November 15 each year. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1341, oldest first
DateLocationAction
03/27/2026HouseIntroduced In House - Assigned to Agriculture, Water & Natural Resources + Finance
04/13/2026HouseHouse Committee on Agriculture, Water & Natural Resources Refer Unamended to Finance
04/20/2026HouseHouse Committee on Finance Refer Unamended to House Committee of the Whole
04/23/2026HouseHouse Second Reading Laid Over Daily - No Amendments
04/27/2026HouseHouse Second Reading Special Order - Passed - No Amendments
04/28/2026HouseHouse Third Reading Passed - No Amendments
04/30/2026SenateIntroduced In Senate - Assigned to Finance
05/05/2026SenateSenate Committee on Finance Refer Unamended - Consent Calendar to Senate Committee of the Whole
05/06/2026SenateSenate Second Reading Special Order - Passed - No Amendments
05/07/2026SenateSenate Third Reading Passed - No Amendments
06/03/2026HouseSigned by the Speaker of the House
06/03/2026SenateSigned by the President of the Senate
06/03/2026GovernorSent to the Governor
06/04/2026GovernorGovernor Signed

Recorded votes

Full text

Official record

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

dae5542f75f3b2bc61ba5c79b2ad55ef0728d786f2546de7c009be763eb895d0

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-10-28 · 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.