HB26-1373 · Bill · 2026 Regular Session · Colorado

Subsidy Limits in Assistance Programs for Children

Concerning reducing monthly subsidy reimbursement percentages for child welfare services provider contracts, and, in connection therewith, reducing an appropriation.

Official status: Became Law

1 proposed amendment

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 specifies monthly subsidy payment reimbursement limits for the adoption assistance program and the relative guardianship assistance program that apply to contracts that take effect July 1, 2026, or later, and prohibits reimbursement for services other than nonreoccuring adoption expenses. The act requires the state department of human services to create a standardized notice for families that describes the reimbursement change. The act requires the county departments of human or social services to provide the notice by June 15, 2026, to families currently receiving services. The act reduces the state fiscal year 2025-26 appropriation to the department of human services for adoption and relative guardianship assistance made in the long bill as follows: From the general fund, by $2,199,750; and From cash funds, by $407,295. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1373, oldest first
DateLocationAction
04/02/2026HouseIntroduced In House - Assigned to Appropriations
04/07/2026HouseHouse Committee on Appropriations Refer Unamended 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 - No Amendments
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 Concur - Repass
05/22/2026HouseSigned by the Speaker of the House
05/22/2026SenateSigned by the President of the Senate
05/22/2026GovernorSent to the Governor
05/27/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (1 proposed amendment)

Amendments proposed to HB26-1373, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.001
Sponsor: Senators Lindstedt & Bright
Floor amendment — Second Reading (Senate)04/15/2026PassedView official document

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Full text

Official record

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

f57cbd80637821f9bfce500b727e29074c4c904c795f3126a2904c671cac4e01

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.