Ord 2776 · Ordinance · 2026 · City of Commerce City · City Council

AN ORDINANCE AMENDING THE 2026 BUDGET OF THE CITY OF COMMERCE CITY, COLORADO BY AUTHORIZING THE TRANSFER OF OPIOID SETTLEMENT FUNDS FROM THE GENERAL FUND TO THE URBAN RENEWAL AUTHORITY IN THE AMOUNT OF $40,000 FOR THE BRIDGE HOUSE’S READY TO WORK PROGRAM 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

Every recorded action on Ord 2776, oldest first
DateLocationAction
04/20/2026City Councilintroduced by council as seated and approved on first reading
05/04/2026City Councilapproved on second & final reading

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

9e9560d0d8cdc071442b0584de321db2a12a99c15bb308ac3ba81b670d82df88

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 of Commerce City — Legistar (commerce.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.