A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF BRIGHTON, COLORADO, LEVYING GENERAL PROPERTY TAXES FOR THE YEAR 2027, TO HELP DEFRAY THE COSTS OF GOVERNMENT FOR THE CITY OF BRIGHTON, COLORADO, AND SETTING THE MILL LEVY AT 6.650 MILLS FOR THE 2027 BUDGET YEAR
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-21 · Human review pending
This resolution levies general property taxes for the year 2027 and sets the mill levy at 6.650 mills for the 2027 budget year. It levies a tax of 6.650 mills upon each dollar of the total valuation of assessment for all taxable property within the City of Brighton, with property tax revenue of $6,711,156 stated as necessary for general operating purposes. The record lists no current status.
Status timeline
| Date | Location | Action |
|---|---|---|
| 11/10/2026 | City Council | Listed on the City Council agenda — Consolidated Items for Sequential Review |
Full text — side-by-side reader
Showing the latest official version: Legistar attachment: RESO 26- 2027 City Mill Levy version (official PDF), 2026-11-10
Official text — shown in English exactly as published by the official source. The official text controls.
RESOLUTION NO. 2026-90
A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF BRIGHTON, COLORADO, LEVYING GENERAL PROPERTY TAXES FOR THE YEAR 2027, TO HELP DEFRAY THE COSTS OF GOVERNMENT FOR THE CITY OF BRIGHTON, COLORADO, AND SETTING THE MILL LEVY AT 6.650 MILLS FOR THE 2027 BUDGET YEAR
WHEREAS, the City Council of the City of Brighton has adopted the 2027 Budget in accordance with the Local Government Budget Law; and
WHEREAS, the amount of money necessary to balance the budget for general operating purposes from property tax revenue is $6,711,156.
NOW, THEREFORE, BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF BRIGHTON, COLORADO AS FOLLOWS:
Section 1. That for the purposes of meeting all general operating expenses of the City of Brighton for the 2027 budget year, there is hereby levied a tax of 6.650 mills upon each dollar of the total valuation of assessment for all taxable property within the City of Brighton for the year 2027.
Section 2. The City Manager is hereby authorized and directed to immediately certify to the County Commissioners of both Adams County, Colorado and Weld County, Colorado the mill levies for the City of Brighton as hereinabove determined and set.
Section 3. This resolution is effective upon its adoption.
RESOLVED this 10th day of November 2026.
CITY OF BRIGHTON, COLORADO
GREGORY MILLS, Mayor
ATTEST:
NATALIE HOEL, City Clerk
APPROVED AS TO FORM:
JAMES GALLAGHER, Assistant City Attorney
Change history
Official record
City of Brighton — City Council agendas, CivicPlus Agenda Center (www.brightonco.gov)
Source: City of Brighton — City Council agendas, CivicPlus Agenda Center (www.brightonco.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
d5ce3c1e2941c18389e34748ffe9825b3fbe35c6f8903c67cfd4c134799a605d
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.
