Continue Microgrid Community Resilience Grant Program
Concerning continuing the microgrids for community resilience grant program.
Official status: Became Law
Prime sponsors
- Larry Don Suckla (House) — Prime Sponsor
- Katie Stewart (House) — Prime Sponsor
- Dylan Roberts (Senate) — Prime Sponsor
- Cleave Simpson (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.
The microgrids for community resilience grant program (grant program) in the division of local government in the department of local affairs provides grants for cooperative electric associations and municipally owned utilities to purchase microgrid resources for eligible rural communities located within their service territories. Under current law, the grant program is set to repeal on September 1, 2026. The act continues the grant program indefinitely by removing the repeal date. (Note: This summary applies to this bill as enacted.)
Status timeline
| Date | Location | Action |
|---|---|---|
| 01/14/2026 | House | Introduced In House - Assigned to Energy & Environment |
| 02/05/2026 | House | House Committee on Energy & Environment Refer Unamended to Appropriations |
| 02/27/2026 | House | House Committee on Appropriations Refer Unamended to House Committee of the Whole |
| 02/27/2026 | House | House Second Reading Special Order - Passed - No Amendments |
| 03/02/2026 | House | House Third Reading Passed - No Amendments |
| 03/05/2026 | Senate | Introduced In Senate - Assigned to Transportation & Energy |
| 03/25/2026 | Senate | Senate Committee on Transportation & Energy Refer Unamended to Appropriations |
| 04/22/2026 | Senate | Senate Committee on Appropriations Refer Unamended - Consent Calendar to Senate Committee of the Whole |
| 04/22/2026 | Senate | Senate Second Reading Special Order - Passed - No Amendments |
| 04/23/2026 | Senate | Senate Third Reading Passed - No Amendments |
| 05/28/2026 | House | Signed by the Speaker of the House |
| 05/28/2026 | Senate | Signed by the President of the Senate |
| 05/28/2026 | Governor | Sent to the Governor |
| 05/29/2026 | Governor | Governor Signed |
Recorded votes
- 04/22/2026 — Senate Appropriations: “Refer House Bill 26-1051 to the Committee of the Whole and with a recommendation that it be placed on the consent calendar.” — the motion passed on a vote of 7–0.
- 03/25/2026 — Senate Transportation & Energy: “Refer House Bill 26-1051 to the Committee on Appropriations.” — the motion passed on a vote of 8–0.
- 02/27/2026 — House Appropriations: “Refer House Bill 26-1051 to the Committee of the Whole.” — the motion passed on a vote of 10–1.
- 02/05/2026 — House Energy & Environment: “Refer House Bill 26-1051 to the Committee on Appropriations.” — the motion passed on a vote of 12–0.
Full text
- Signed Act version (official PDF), 06/01/2026
- Final Act version (official PDF), 05/27/2026
- Rerevised version (official PDF), 04/23/2026
- Revised version (official PDF), 04/22/2026
- Reengrossed version (official PDF), 03/02/2026
- Engrossed version (official PDF), 02/27/2026
- Introduced version (official PDF), 01/14/2026
Official record
View HB26-1051 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
6bc62efc4480aa688f864fb87103b3e7ef893930d4f2e2ab39f71172281b6824
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.