Why city procurement fails when vendors lie

When a vendor stands before your city council and misrepresents the technical capabilities of their surveillance hardware, the contract isn't just at risk—it’s already dead. The recent decision by the Oshkosh City Council to rescind its Flock Safety contract serves as a masterclass in why technical due diligence cannot be outsourced to the sales team. When a representative claims a system doesn't generate heat maps, but your own police department’s internal audit proves otherwise, you have a fundamental breach of trust that no amount of "minor nuance" can fix.

Most city officials treat vendor presentations as gospel, assuming that if a company is already operating in other jurisdictions, their claims are vetted. This is a dangerous assumption. In the world of automated license plate recognition (ALPR) and public safety tech, the gap between "marketing speak" and "system reality" is often where your legal liability lives. If you are responsible for municipal procurement, you need to stop asking vendors what their system does and start asking for a sandbox environment where your own IT staff can verify those claims.

Here is how you avoid becoming the next headline:

1. Demand a technical deep-dive with your own engineers, not just the sales rep.
2. Require a written, signed affidavit confirming specific data retention and tracking capabilities.
3. Run a pilot program that includes a "stress test" of the software’s reporting features.
4. Cross-reference vendor claims against independent privacy impact assessments from other cities.

This next part matters more than it looks: the vendor’s defense in Oshkosh—that they were just talking about "pattern of life" versus "point-in-time" data—is a classic deflection. If a system can visualize vehicle movement over 30 days, it is effectively creating a pattern of life, regardless of what the marketing brochure calls it. When you ignore these technical nuances, you aren't just buying a tool; you are buying a potential lawsuit.

If you are currently evaluating surveillance technology procurement for your municipality, you must treat every claim as a hypothesis that requires testing. Don't rely on the vendor to define their own limitations. If they refuse to let your technical team audit the software’s output, that is your signal to walk away. Transparency isn't a feature you add to a contract; it is the baseline requirement for any partnership involving public data.

The Oshkosh situation proves that even after a contract is signed, the relationship remains fragile. If you find yourself in a position where you have to choose between a "highly successful" tool and the integrity of your council’s decision-making process, the choice is clear. You cannot build public safety on a foundation of misinformation. How does your city verify vendor claims before signing off on new surveillance tech? Try this today and share what you find in the comments, or read our breakdown of data privacy in municipal contracts next.