Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Public Safety It topic
No spam. Unsubscribe anytime.
Regional public-safety software project delayed to Feb. 2026; officials cite configuration, added features
Summary
Washoe County, Reno and Sparks officials said the joint Hexagon computer-aided dispatch and records management rollout will be delayed from September 2025 to Feb. 23, 2026 to finish configuration, testing and integrated features including AI agents and third‑party integrations.
City of Reno public-safety dispatch director Cody Schadl told the Washoe County Board of County Commissioners on Aug. 19 that the region's joint Hexagon computer-aided dispatch (CAD) and records management system would not meet its previously announced Sept. 9, 2025 go‑live date and is now targeting Feb. 23, 2026.
Schadl, the project coordinator for the multi‑agency effort that includes Reno, Sparks, Washoe County and REMSA, said staff have completed hardware and are about 95% through configuration. The project has added integrations with a wide range of systems used by fire, law enforcement and emergency medical services and has established a governance agreement to manage ongoing operations.
"Unfortunately, I'm here to tell you we're not gonna hit that mark," Schadl said of the September timeline. He and staff said the delay was intended to allow for expanded testing, training and the addition of new functionality — including a set of vendor‑supported artificial‑intelligence tools the team said can surface commonalities between incidents across agencies to speed investigations and operational response.
Schadl said the project has completed a geographically separate disaster‑recovery site and had configured dozens of third‑party integrations — examples included automatic transfer of fire staffing data from Telestaff into the CAD to avoid manual updates. He said the team would begin intensive user training after current functional testing concludes in October and then roll into a training and reliability period before the February go‑live date.
Commissioners and chiefs asked about post‑go‑live policy changes such as boundary drops and unrestricted automatic aid for fire agencies. Schadl said such changes would likely be implemented after go‑live through the system's change‑management process: "It wouldn't delay go live... we would probably schedule those to be done after go live." He said the product and governance structure were designed to accommodate future changes without rebuilding the system from scratch.
Schadl told the board the project remained within its approved budget and that the vendor had provided additional resources and discounted pricing in some areas to reduce the operational burden of the schedule shift.
Ending: Officials said the project will continue testing and training through late 2025 and into early 2026, with a new target go‑live date of Feb. 23, 2026. County staff said they will return to the board with updates as the project completes testing and transitions to training and reliability phases.
