HB26-1357 · Bill · 2026 Regular Session · Colorado

Phase-Out of Teacher Recruitment Education and Preparation Program

Concerning phasing out the teacher recruitment education and preparation program, and, in connection therewith, making and reducing an appropriation.

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 act repeals the teacher recruitment education and preparation program (TREP) after the 2026-27 budget year. The act repeals the teacher recruitment and preparation program and pathways in early technology early college high schools working group on July 1, 2027. On July 1, 2026, the act requires the state treasurer to transfer $799,200 from the electrifying school buses grant program cash fund to the state education fund. The general assembly declares that TREP may receive funding from the state education fund. For the 2026-27 state fiscal year, the act caps the amount that a district receives for a student participating in TREP under the school finance formulas at $7,104. The act increases the cash fund appropriation to the department of education for state share of districts' total program funding and decreases the cash fund appropriation for extended high school in the 2026-27 long bill in order to fund TREP for the 2026-27 state fiscal year. The amount of the changes is contingent on whether House Bill 26-1364, concerning the calculation of the consumer price index for the 2025 calendar year, becomes law. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1357, oldest first
DateLocationAction
04/02/2026HouseIntroduced In House - Assigned to Appropriations
04/07/2026HouseHouse Committee on Appropriations Refer Amended to House Committee of the Whole
04/08/2026HouseHouse Second Reading Special Order - Laid Over Daily - No Amendments
04/09/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee, Floor
04/10/2026HouseHouse Third Reading Laid Over Daily - No Amendments
04/11/2026HouseHouse Third Reading Passed - No Amendments
04/13/2026SenateIntroduced In Senate - Assigned to Appropriations
04/14/2026SenateSenate Committee on Appropriations Refer Unamended to Senate Committee of the Whole
04/15/2026SenateSenate Second Reading Special Order - Passed with Amendments - Floor
04/16/2026SenateSenate Third Reading Passed - No Amendments
04/17/2026HouseHouse Considered Senate Amendments - Result was to Not Concur - Request Conference Committee
04/27/2026SenateSenate Consideration of First Conference Committee Report result was to Adopt Committee Report - Repass
04/28/2026HouseHouse Consideration of First Conference Committee Report result was to Adopt Committee Report - Repass
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-1357 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

3ca3651ac5b168fc112dc1c9017781392966657a89c3b47f9d144283a6861204

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.