An ordinance providing for the tax levy upon all taxable property in the City for municipal purposes.
Progress (from the official record)
What happened
The official record lists the status of ordinance-providing-for-the-tax-levy-upon-all-taxable as “Second Reading”. Its most recent recorded action was on 11/10/2026.
Rogata explainer · Based on official record
What changed
- Record updated New: Added to the dataset
Prime sponsors
Sponsor information is on the official bill page (linked below).
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 ordinance provides for the tax levy upon all taxable property in the City for municipal purposes. It levies a tax of 10.21 mills upon each dollar of the total valuation for assessment of all taxable property within the City, for the year 2026 to be collected in 2027, and directs the Finance Director to certify the levy to the Board of County Commissioners of Adams County. Its current status is Second Reading.
Status timeline
Every recorded action on ordinance-providing-for-the-tax-levy-upon-all-taxable, oldest first
Listed on the City Council agenda (Regular Meeting) — LEGISLATIVE PUBLIC HEARINGS
Listed on the City Council agenda (Regular Meeting) — CONSENT CALENDAR
Full text — side-by-side reader
Showing the latest official version: Council packet item document (2026-11-10) version (official PDF), 11/10/2026
Official text — shown in English exactly as published by the official source. The official text controls.
INTRODUCED BY:
Russell
AN ORDINANCE PROVIDING FOR THE TAX LEVY UPON ALL TAXABLE PROPERTY IN THE CITY FOR MUNICIPAL PURPOSES.
NOW, THEREFORE, BE IT ORDAINED BY THE CITY COUNCIL OF THE CITY OF THORNTON, COLORADO, AS FOLLOWS: 1.
There is hereby levied a tax of 10.21 mills upon each dollar of the total valuation for assessment of all taxable property within the limits of the City of Thornton, Colorado, for the year 2026 to be collected in 2027.
The Finance Director of the City is hereby authorized and directed to certify to the Board of County Commissioners of Adams County, Colorado, the levy described herein.
This ordinance shall take effect upon final passage.
INTRODUCED, READ, PASSED on first reading, ordered posted in full, and title ordered published by the City Council of the City of Thornton, Colorado, on October 27, 2026. PASSED AND ADOPTED on second and final reading on ______________, 2026. CITY OF THORNTON, COLORADO
Jan Kulmann, Mayor ATTEST:
Kristen N. Long, City Clerk THIS ORDINANCE IS ON FILE IN THE CITY CLERK’S OFFICE FOR PUBLIC INSPECTION. APPROVED AS TO LEGAL FORM:
Jessica Whitney, Interim City Attorney
Change history
Official record
City of Thornton — City Council agendas, PrimeGov/OneMeeting (thorntonco.primegov.com)
Source: City of Thornton — City Council agendas, PrimeGov/OneMeeting (thorntonco.primegov.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
c2c2afc58bc1c26528eb65c9f566bfe1f431201597332330d1985c4f8a7e1efc
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.
