DESIGNATING THE PUBLIC PLACE FOR POSTING NOTICES OF PUBLIC MEETINGS DURING 2026 PURSUANT TO C.R.S. 24-6-402
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.
Plain-language explainer
Plain-language explainer — not the bill text
Written by AI from the official bill text · 2026-11-20 · Human review pending
This resolution designates the public place for posting notices of public meetings during 2026. It designates the lobby/atrium of the Lakewood Civic Center, 480 South Allison Parkway, and the City's official website (Lakewood.org) as the posting places. The record lists no current status.
Status timeline
| Date | Location | Action |
|---|---|---|
| 01/12/2026 | City Council | Listed on the City Council agenda (Regular Meeting) — Consent Agenda Ordinances On First Reading |
Full text — side-by-side reader
Showing the latest official version: Resolution R-2026-2 version (official PDF), 01/02/2026
Official text — shown in English exactly as published by the official source. The official text controls.
R-2026-2 A RESOLUTION DESIGNATING THE PUBLIC PLACE FOR POSTING NOTICES OF PUBLIC MEETINGS DURING 2026 PURSUANT TO C.R.S. 24-6-402
WHEREAS, C.R.S. 24-6-402(2)(c) requires the designation of a public place for posting notices of public meetings in order to meet the requirement of “full and timely” notice of meetings; and
WHEREAS, it is hereby determined that such public place for posting purposes shall be located within the lobby/atrium of the Lakewood Civic Center, 480 South Allison Parkway, and published on the City’s official website (Lakewood.org), the exact manner and means of posting to be implemented by the City Manager or designee, and such posting place shall be used for “local public bodies” as defined under C.R.S. 24-6402(2)(c).
NOW, THEREFORE, BE IT RESOLVED by the City Council of the City of Lakewood, Colorado, that:
SECTION 1. The lobby/atrium area within the Lakewood Civic Center, 480 South Allison Parkway, and the City’s official website (Lakewood.org), are hereby designated as the public places for the posting of notices of meetings in 2026, pursuant to C.R.S. 24-6-402(2)(c). The exact manner and means of said posting shall be implemented by the City Manager or designee. INTRODUCED, READ, AND ADOPTED by a vote of __ for and __ against at a hybrid regular meeting of the Lakewood City Council on January 12, 2026, at 7 o’clock p.m. at the Lakewood Civic Center, 480 S. Allison Parkway, Lakewood, Colorado.
Wendi Strom, Mayor ATTEST:
Jay Robb, City Clerk APPROVED AS TO FORM:
Alison McKenney Brown, City Attorney
Change history
Official record
City of Lakewood — City Council meetings, CivicClerk (lakewoodco.portal.civicclerk.com)
Source: City of Lakewood — City Council meetings, CivicClerk (lakewoodco.portal.civicclerk.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
5ca337f6cb2ce9275c0893333ad6fc9deacb99a02946dff4a4b8fbe56bf3f82e
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.
