A resolution approving a proposed Amendatory Agreement between the City and County of Denver and Mission Critical Partners, LLC to provide project management services to support computer-aided dispatch (CAD), records management system (RMS), and mobile data systems (MDS) to support emergency call taking and dispatch systems Denver 9-1-1 communications and the Denver International Airport, 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.
Amends an agreement with Mission Critical Partners, LLC by adding $378,907.00 for a new total of $660,000.26 and adding 24 months for a new end date of 12-31-2029 to provide project management services to support computer-aided dispatch (CAD), records management system (RMS), and mobile data systems (MDS) to support emergency call taking and dispatch systems Denver 9-1-1 communications and the Denver International Airport, citywide (SAFTY-202265618-00/SAFTY-202582711-01). The last regularly scheduled Council meeting within the 30-day review period is on 3-9-2026. The Committee approved filing this item at its meeting on 2-4-2026.
Status timeline
| Date | Location | Action |
|---|---|---|
| 02/04/2026 | Health and Safety | A motion offered by Council member Sawyer, duly seconded by Vice Chair Flynn, that Council Resolutions 26-0023 and 26-0024 be approved for filing in a block, carried by the following vote: |
| 02/17/2026 | City Council | A motion offered by Council member Watson, duly seconded by Council member Alvidrez, that Council Resolution 26-0024 be adopted en bloc, carried by the following vote: |
| 02/17/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
324fa030044cec5d5e15fbf7075cdc995b18c51d3d6f40f24cdbcdaecd0971a6
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.