A bill for an ordinance approving a proposed Amendatory Agreement between the City and County of Denver and Regional Transportation District, for eligibility determination, application processing, and services related to the RTD LiVE Program.
Official status: Passed
Prime sponsors
Sponsor information is on the official bill page (linked below).
Progress (from the official record)
Official summary
Official text — shown in English exactly as published by the official source. The official text controls.
Amends a Revenue Intergovernmental Agreement with Regional Transportation District (RTD) to expand the services provided by Denver Human Services for eligibility determination, application processing, and services related to the RTD LiVE Program. No change to the capacity or term, citywide (SOCSV-202474273/SOCSV-202684832-01). The last regularly scheduled Council meeting within the 30-day review period is on 8-31-2026. The Committee approved filing this item at its meeting on 8-5-2026.
Status timeline
| Date | Location | Action |
|---|---|---|
| 08/05/2026 | Health and Safety | A motion offered that Council Bill 26-1125 be approved by consent en bloc, carried by the following vote: |
| 08/17/2026 | City Council | Council Bill 26-1125 was ordered published. |
| 08/24/2026 | City Council | A motion offered by Council member Sawyer, duly seconded by Council member Flynn, that Council Bill 26-1125 be placed upon final consideration and do pass en bloc, carried by the following vote: |
| 08/24/2026 | Council President | signed |
| 08/25/2026 | Mayor | signed |
Full text
- 26-1125_Filed_Bill_Regional_Transportation_District version (official PDF), 08/25/2026
- 26-1125 For an ordinance approving a proposed Amendatory Agreement between the version (official PDF), 08/25/2026
Official record
City and County of Denver — Legistar (denver.legistar.com)
Source: City and County of Denver — Legistar (denver.legistar.com) · 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
ca9f6e21d95d8a82ff742792c0587b8d80dcf99ef59b113118872c30beea079e
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.