Healthy School Meals for All State Education Fund
Concerning the use of state education fund money to fund the healthy school meals for all program.
Official status: Became Law
Prime sponsors
- Kyle Brown (House) — Prime Sponsor
- Emily Sirota (House) — Prime Sponsor
- Judy Amabile (Senate) — Prime Sponsor
- Jeff Bridges (Senate) — Prime Sponsor
Progress (from the official record)
Official summary
Official text — shown in English exactly as published by the official source. The official text controls.
During the 2023-24 and 2024-25 state fiscal years, the general assembly appropriated money from the state education fund for expenditures related to the healthy school meals for all program. The act directs the state treasurer to transfer $31,066,831 from the healthy school meals for all program cash fund (program fund) to the state education fund on July 1, 2026. Under current law, beginning on July 1, 2026, and on each July 1 thereafter, the state treasurer is required to transfer money from the state education fund to the program fund and to the healthy school meals for all program fund account (account) within the program fund. The act delays that requirement so that the treasurer is required to transfer money from the state education fund to the program fund and to the account beginning on July 1, 2028. In addition, the act repeals reporting requirements related to money in the program fund. (Note: This summary applies to this bill as enacted.)
Status timeline
| Date | Location | Action |
|---|---|---|
| 04/02/2026 | House | Introduced In House - Assigned to Appropriations |
| 04/06/2026 | House | House Committee on Appropriations Refer Unamended to House Committee of the Whole |
| 04/08/2026 | House | House Second Reading Special Order - Passed - No Amendments |
| 04/09/2026 | House | House Third Reading Laid Over Daily - No Amendments |
| 04/11/2026 | House | House Third Reading Passed - No Amendments |
| 04/13/2026 | Senate | Introduced In Senate - Assigned to Appropriations |
| 04/14/2026 | Senate | Senate Committee on Appropriations Refer Unamended to Senate Committee of the Whole |
| 04/15/2026 | Senate | Senate Second Reading Special Order - Passed - No Amendments |
| 04/16/2026 | Senate | Senate Third Reading Passed - No Amendments |
| 05/22/2026 | House | Signed by the Speaker of the House |
| 05/22/2026 | Senate | Signed by the President of the Senate |
| 05/22/2026 | Governor | Sent to the Governor |
| 05/27/2026 | Governor | Governor Signed |
Recorded votes
- 04/14/2026 — Senate Appropriations: “Refer House Bill 26-1351 to the Committee of the Whole.” — the motion passed on a vote of 7–0.
- 04/06/2026 — House Appropriations: “Refer House Bill 26-1351 to the Committee of the Whole.” — the motion passed on a vote of 9–2.
Full text
- Signed Act version (official PDF), 05/28/2026
- Final Act version (official PDF), 05/21/2026
- Rerevised version (official PDF), 04/16/2026
- Revised version (official PDF), 04/15/2026
- Reengrossed version (official PDF), 04/11/2026
- Engrossed version (official PDF), 04/08/2026
- Introduced version (official PDF), 04/02/2026
Official record
View HB26-1351 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
c5cc656079ff4a90f54151d50efbf6f87079a88b786bdc316f8d79e862d8d2bd
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.
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.
