A Resolution Repealing Resolution No. 42, Series of 2024 and Adopting A Revised City Fee Schedule
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.
Staff has proposed some formatting and clean-up language to the Village’s Fee Schedule. Staff has also proposed to reinstate fees for accident reports. These proposed fees ensure they are up to date, recover actual costs imposed on the City for completing a process or program, and are aligned with surrounding municipalities. <br id="isPasted"> <br> No new line items or fees were added to the City Clerk's Office, Community Development Department, Finance Department, Parks, Trails and Recreation Department, or Public Works Department in the proposed 2026 Schedule.
Status timeline
| Date | Location | Action |
|---|---|---|
| 06/01/2026 | City Council | Listed on the City Council agenda — Ordinances and Resolutions |
Full text
Official record
Source: City of Greenwood Village — City Council meetings, CivicClerk (greenwoodvillageco.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
45949536d638f8666737c4c6a3f57831e2cc1d5781da46a091446c7dd69c623c
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.