A BILL FOR AN ORDINANCE APPROVING A FIFTH AMENDMENT TO AN INTERGOVERNMENTAL AGREEMENT BETWEEN THE CITY OF ENGLEWOOD AND THE URBAN DRAINAGE AND FLOOD CONTROL DISTRICT D/B/A MILE HIGH FLOOD DISTRICT REGARDING FINAL DESIGN, RIGHT-OF-WAY ACQUISITION, AND CONSTRUCTION OF DRAINAGE AND FLOOD CONTROL IMPROVEMENTS FOR THE SOUTH ENGLEWOOD BASIN PROJECT.
Official status: Second Reading
Prime sponsors
- Prange — Introduced by
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 |
|---|---|---|
| 04/06/2026 | City Council | First Reading — approved on the consent agenda (block motion carried; draft minutes) |
| 04/20/2026 | City Council | Second Reading — motion carried (draft minutes) |
Recorded votes
- 04/20/2026 — City Council: “CB 32 - Mile High Flood District Reimbursement” — the motion passed on a vote of 7–0.
Full text
Official record
City of Englewood — City Council meeting packets, CivicWeb (englewoodgov.civicweb.net)
Source: City of Englewood — City Council meeting packets, CivicWeb (englewoodgov.civicweb.net) · 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
f01e4aa5f300d46165b2a4bc15f083f189c181732e60be160d34facca21c70de
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.