AN ORDINANCE AMENDING THE 2026 BUDGET OF THE CITY OF COMMERCE CITY, COLORADO BY THE RECOGNITION OF FUNDING FROM THE URBAN RENEWAL AUTHORITY, FEDERAL FORFEITURE FUND, CAPITAL EXPENDITURES FUND, AND GENERAL FUND IN THE TOTAL AMOUNT OF $608,900 FOR USE ON THE FLOCK EXPANSION PROJECT AND THE AUTHORIZATION OF THE EXPENDITURE THEREOF
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.
The official page for this measure does not publish a summary. Its full text is linked below.
Status timeline
| Date | Location | Action |
|---|---|---|
| 03/02/2026 | City Council | A motion was made by Council Member Teter, seconded by Council Member Dukes, that Ordinance 2756 be introduced by council as seated and approved on first reading. VOTE: |
| 04/06/2026 | City Council | A motion was made by Council Member Dukes, seconded by Council Member Teter, that this Ordinance be approved on second & final reading. VOTE: |
Full text
Official record
City of Commerce City — Legistar (commerce.legistar.com)
Source: City of Commerce City — Legistar (commerce.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
34438c9965606d3728d6b44432d244f81b6cdc8c7ffbdb8ffa424c661dd5944a
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.