A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF BRIGHTON, COLORADO, CONSIDERING APPROVAL OF THE BRIGHTON CROSSING FILING NO. 9 SUBDIVISION PLAN AND CONSIDERING ACCEPTANCE OF ALL PUBLIC LANDS AND FACILITIES ASSOCIATED WITH THE SUBDIVISION PLAN FOR AN APPROXIMATELY 9.095 ACRE PROPERTY, GENERALLY LOCATED TO THE NORTH OF EAST BRIDGE STREET, SOUTH OF ROYAL PINE STREET, EAST OF APACHE PLUME STREET AND WEST OF THE SPEER CANAL, MORE PARTICULARLY LOCATED IN THE SOUTHEAST QUARTER OF SECTION 2, TOWNSHIP 1 SOUTH, RANGE 66 WEST OF THE 6TH PRINCIPAL MERIDIAN, CITY OF BRIGHTON, COUNTY OF ADAMS, STATE OF COLORADO
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
| Date | Location | Action |
|---|---|---|
| 03/17/2026 | City Council | Listed on the City Council agenda — Public Hearings |
Full text
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
9c6e8dfb065549cde4babcf82260f2db1925aaf83897c179769000308c7bf164
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.