Ordinance 8742 · Ordinance · 2026 · City of Boulder

vacating and authorizing the city manager to execute a deed of vacation for a portion of Colorado Avenue right-of-way located north of 1100 28th Street (LUR2025-00070)

Official status: Second Reading

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.

Status timeline

Every recorded action on Ordinance 8742, oldest first
DateLocationAction
03/05/2026City CouncilListed on the City Council agenda — Consent Agenda
04/02/2026City CouncilListed on the City Council agenda — Consent Agenda

Full text

Official record

City of Boulder — City Council meeting agendas, OneMeeting portal (bouldercolorado.primegov.com)

Source: City of Boulder — City Council meeting agendas, OneMeeting portal (bouldercolorado.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

06c992200d94c43df9c931bf2f37ab8836454cc8c014b092d1166fda396c3963

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.

Computed 2026-10-28 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: City of Boulder — City Council meeting agendas, OneMeeting portal (bouldercolorado.primegov.com) · Data as of

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.