26-0923 · Bill · Series of 2026 · City and County of Denver · South Platte River Committee

A bill for an ordinance approving a proposed Intergovernmental Agreement between the City and County of Denver and Kroenke Sports and Entertainment Metropolitan District No. 2 and Kroenke Sports and Entertainment Metropolitan District No. 3, for designing, financing, and building the Wynkoop Crossing bridge over Speer Boulevard. The IGA provides for the future conveyance of easement(s) by the City to the Districts for the bridge landing area, in Council District 3.

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.

Approves a non-financial IGA with Kroenke Sports and Entertainment Metropolitan District No. 2 and Kroenke Sports and Entertainment Metropolitan District No. 3 for $0.00 and a contract term from the effective date to the anticipated completion date of the bridge, on or around April 29, 2029. The Districts are designing, financing, and building the Wynkoop Crossing bridge over Speer Boulevard. The IGA provides for the future conveyance of easement(s) by the City to the Districts for the bridge landing area, in Council District 3 (DOTI-202684460). The last regularly scheduled Council meeting within the 30-day review period is on 8-3-2026. The Committee approved filing this item at its meeting on 6-24-2026.

Status timeline

Every recorded action on 26-0923, oldest first
DateLocationAction
06/24/2026South Platte River CommitteeA motion offered by Council member Hinds, duly seconded by Council member Alvidrez, that Council Bill 26-0923 be postponed to a date certain, carried by the following vote:
07/01/2026South Platte River CommitteeCouncil Bill 26-0923 was approved by consent.
07/13/2026Council Bill 26-0923 was ordered published
07/13/2026City CouncilA motion offered by Council member Alvidrez, duly seconded by Council member Watson, that Council Bill 26-0923 be ordered published was followed by a motion offered by Council member Torres, duly seconded by Council member Hinds, that Council Bill 26-0923 be amended in the following particulars: "1. On page 1, line 12, strike “District 9” and replace with “District 3”.". The motion to amend carried by the following vote:
07/13/2026City CouncilA motion offered by Council member Alvidrez, duly seconded by Council member Hinds, that Council Bill 26-0923 be ordered published as amended, carried by the following vote:
07/20/2026City CouncilA motion offered by Council Pro-Tem Gonzales-Gutierrez, duly seconded by Council member Hinds, that Council Bill 26-0923 be placed upon final consideration and do pass en bloc, carried by the following vote:
07/20/2026Council Presidentsigned
07/22/2026Mayorsigned

Full text

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

85e80e8144aef62c1671e093ad88da6fa404b407fd61173ee16365bf37cef99b

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-10-28 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: City and County of Denver — Legistar (denver.legistar.com) · 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.