CALLING FOR A COORDINATED SPECIAL MUNICIPAL ELECTION TO BE HELD ON NOVEMBER 3, 2026, TO SUBMIT TO A VOTE OF THE REGISTERED ELECTORS OF THE CITY OF LAKEWOOD, COLORADO, A BALLOT QUESTION FOR THE PURPOSE OF AUTHORIZING VOTER-APPROVED AMENDMENTS TO THE CITY'S HOME RULE CHARTER TO REPLACE THE LANGUAGE ESTABLISHING TIME FRAMES FOR HOLDING REGULAR OR SPECIAL ELECTIONS AS ESTABLISHED WITHIN SECTION 13.1(d) REGARDING INITIATIVE PROCEDURES AND SECTION 13.2(e) REGARDING REFERENDUM PROCEDURES, AND ADOPTING THE BALLOT TITLE THEREFOR
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 |
|---|---|---|
| 08/10/2026 | City Council | Finally passed and adopted |
Recorded votes
- 08/10/2026 — City Council: “Final passage” — the motion passed on a vote of 11–0.
Full text
Official record
City of Lakewood — City Clerk ordinance index (lakewoodco.gov)
Source: City of Lakewood — City Clerk ordinance index (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
e21cb45db0a5c87437a821fb3241e81a6753b36f18f7becfa7c236533b8fad53
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.