HB26-1013 · Bill · 2026 Regular Session · Colorado

Ratio Utility Billing Systems

Concerning the use of a ratio utility billing system by a landlord to allocate utility charges to tenants.

Official status: Became Law

2 proposed amendments

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 authorizes landlords to use a ratio utility billing system to allocate utility charges for a residential premises to individual tenants. The landlord may charge tenants a utility bill using a ratio utility billing system if the landlord meets certain requirements, such as: The aggregate amount billed to all tenants does not exceed the amount charged by the utility provider for service to the entire residential premises; The landlord does not apply a fee or other charge to the tenant in addition to the actual charges from the utility; The utility costs for common areas or shared facilities are excluded from the charges to the tenant; and The landlord clearly discloses the method of allocation for the dwelling unit in the tenant's rental agreement. For residential premises constructed with permits applied for on or after July 1, 2027, utility service must be metered directly by the utility provider or by a submeter. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1013, oldest first
DateLocationAction
01/14/2026HouseIntroduced In House - Assigned to Business Affairs & Labor
02/04/2026HouseHouse Committee on Business Affairs & Labor Refer Unamended to House Committee of the Whole
02/06/2026HouseHouse Second Reading Laid Over Daily - No Amendments
02/17/2026HouseHouse Second Reading Special Order - Passed - No Amendments
02/18/2026HouseHouse Third Reading Passed - No Amendments
02/19/2026SenateIntroduced In Senate - Assigned to Business, Labor, & Technology
03/05/2026SenateSenate Committee on Business, Labor, & Technology Refer Amended - Consent Calendar to Senate Committee of the Whole
03/09/2026SenateSenate Second Reading Passed with Amendments - Committee
03/10/2026SenateSenate Third Reading Passed - No Amendments
03/11/2026HouseHouse Considered Senate Amendments - Result was to Laid Over Daily
03/12/2026HouseHouse Considered Senate Amendments - Result was to Concur - Repass
03/18/2026HouseSigned by the Speaker of the House
03/19/2026SenateSigned by the President of the Senate
03/19/2026GovernorSent to the Governor
03/26/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (2 proposed amendments)

Amendments proposed to HB26-1013, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.002
Sponsor: Representative Richardson
Floor amendment — Second Reading (House)02/17/2026LostView official document
L.004Committee amendment — Business, Labor, & Technology (Senate)03/05/2026PassedView official document

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

Full text

Official record

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

d3b9bd4d25f3f436432b42b291a2352b4ac6d14f13a861fad127f8232785e5d0

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.