Digital Transformation · 3 November 2026
Flock Safety cameras: Virginia county removes defunct units itself
A Virginia county is removing dozens of Flock Safety camera units itself after the vendor stopped responding following contract cancellations, according to TechRadar.
What happened
A Virginia county has had to remove dozens of Flock Safety camera units after the surveillance-technology vendor stopped responding to the local government following contract cancellations. TechRadar reports that work crews are removing the devices, and its headline puts the number at 120 defunct cameras.
According to the reporting, the county is handling the removal itself rather than relying on the vendor. The coverage frames the situation as a company failing to fulfil its contractual obligations, with the public authority left to manage the physical clean-up of hardware it no longer operates.
The source material available for this briefing is limited to TechRadar's report and its headline, so the timing of the removals, the terms of the cancelled contracts and the vendor's own position are not established here.
Why it matters
This is a public-sector technology story about dependency. A municipality that buys networked devices as a service is tied to the vendor for software updates, data access, support and, eventually, decommissioning. When the supplier stops engaging, the government's ability to run, maintain or retire the service depends on contract terms and in-house capability that may never have been tested.
For leaders in digital transformation and GovTech, the implication is operational. A modernisation programme is not finished when hardware is installed. It needs an exit and continuity plan covering who owns the data, how the asset is removed, and what service continuity looks like if the supplier disappears. Residents are also affected, because the status of a public surveillance system changes overnight and the public-facing explanation falls to the local authority.
The Renascence take
Most coverage will treat this as a story about one vendor. The more useful lesson is about contract design. Public bodies often evaluate technology partners on features and price, then discover late in the lifecycle that the operating relationship is the product.
Every connected public service should be treated as a relationship with an exit path, not just a purchase. The behavioural trap is optimism bias: buyers assume a vendor will be there at renewal, so they underweight the cost of silence. A customer-obsessed operator writes decommissioning, data portability and communication obligations into the first contract, and rehearses them before they are needed. Trust is lost when people learn about a change from a work crew rather than from the government that authorised the system.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in Digital Transformation
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


