AUTHORIZING SUPPLEMENTAL APPROPRIATIONS TO THE 2026 REVISED ANNUAL BUDGET IN THE AMOUNT OF $150,000 IN RECOGNITION OF GRANTS RECEIVED FROM THE COLORADO DEPARTMENT OF LOCAL AFFAIRS
Official status: Adopted
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/09/2026 | City Council | Introduced and read on first reading |
| 03/12/2026 | Published by title in the Denver Post and in full on the City of Lakewood website | |
| 03/23/2026 | City Council | Public hearing held |
| 03/23/2026 | City Council | Read, finally passed and adopted |
| 04/03/2026 | Signed by the Mayor |
Recorded votes
- 03/23/2026 — City Council: “Final passage” — the motion passed on a vote of 9–0.
Full text
Official record
City of Lakewood — City Clerk ordinance library (lakewoodco.gov)
Source: City of Lakewood — City Clerk ordinance library (lakewoodco.gov) · 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
07e86cc6f39394e3c026360e139cbb55896669534d783adc5a46b66b8632e70b
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.