RogataEvery bill, laid before the people.

HB26-1174 · Bill · 2026 Regular Session · Colorado

School Finance Mid-Year Adjustments

Concerning adjustments to school funding for the 2025-26 budget year, and, in connection therewith, 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.

Compared to what was anticipated when appropriations were established in the 2025 regular legislative session for the 2025-26 budget year, the general assembly finds that for the 2025-26 budget year the actual funded pupil count and the at-risk pupil count are lower than anticipated; the local share of total program funding is higher than anticipated; and therefore, the general assembly intends to decrease the state share of districts' total program funding by $103,472,508 for the 2025-26 budget year. Under current law, there are 2 total program formulas to finance public schools, commonly referred to as the old formula and the new formula. For the 2025-26 budget year, a district's total program is the greater of: The district's total program amount for the 2024-25 budget year; or The amount calculated for the 2025-26 budget year under the old formula plus an amount equal to 15% of the difference between the amounts calculated between the old formula and the new formula. The act clarifies that for the 2025-26 budget year, if the calculation under the new formula is less than the calculation under the old formula, then that district's total program for the 2025-26 budget year is the greater of: The district's total program amount for the 2024-25 budget year; or The amount calculated for the 2025-26 budget year under the old formula. The act reduces appropriations to the department of education for the 2025-26 budget year by $103,472,508. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1174, oldest first
DateLocationAction
02/06/2026HouseIntroduced In House - Assigned to Appropriations
02/10/2026HouseHouse Committee on Appropriations Refer Unamended to House Committee of the Whole
02/11/2026HouseHouse Second Reading Special Order - Passed - No Amendments
02/12/2026HouseHouse Third Reading Passed - No Amendments
02/17/2026SenateIntroduced In Senate - Assigned to Appropriations
02/18/2026SenateSenate Committee on Appropriations Refer Unamended - Consent Calendar to Senate Committee of the Whole
02/19/2026SenateSenate Second Reading Special Order - Passed - No Amendments
02/20/2026SenateSenate Third Reading Passed - No Amendments
03/16/2026HouseSigned by the Speaker of the House
03/17/2026SenateSigned by the President of the Senate
03/17/2026GovernorSent to the Governor
03/26/2026GovernorGovernor Signed

Recorded votes

Full text

Official record

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

4ff7dfc555421f5b1df0bef8076d76661a2f0d62c7ec98919d9f59038c740ab3

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.