A resolution approving a proposed Contract between the City and County of Denver and LOYA CONSTRUCTION, INC. for roto-mill and asphalt overlay in various locations, citywide.
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.
Approves a contract with LOYA CONSTRUCTION, INC. for $6,850,000.00 with a term of NTP + 180 days for roto-mill and asphalt overlay in various locations, citywide (DOTI-202683839). The last regularly scheduled Council meeting within the 30-day review period is on 10-26-2026. The Committee approved filing this item at its meeting on 9-23-2026.
Status timeline
| Date | Location | Action |
|---|---|---|
| 09/23/2026 | Transportation and Infrastructure | Council Resolution 26-1330 was approved by consent. |
| 10/05/2026 | City Council | A motion offered by Council member Alvidrez, duly seconded by Council member Flynn, that Council Resolution 26-1330 be adopted en bloc, carried by the following vote: |
| 10/05/2026 | Council President | signed |
Full text
Official record
City and County of Denver — Legistar (denver.legistar.com)
Source: City and County of Denver — Legistar (denver.legistar.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
680dc421b390c73f803479fecb426c8a4118fba9546256f537c521d78fa56d4a
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.