Oshkosh Reversed Flock Safety Contract

Our Take

Credit to Respectsyoutech for surfacing this one, because it's a near-perfect case study in how these contracts get sold. A Flock representative reportedly told Oshkosh officials the system doesn't build heatmaps — then the police chief went and checked, and found that it does. That's not a rounding error. Heatmapping is exactly the kind of feature that turns a "license plate reader" into a movement-tracking tool, and it's the feature most likely to make elected officials pump the brakes if they understand what they're actually buying.

Whether that was a sales rep fumbling the technical details or something closer to a company trying to smooth over a sticky feature during a pitch, the result is the same: a town council that now has reason to question everything else they were told. Vendors pitching this gear to small-town councils are often the only technical voice in the room, and most municipal boards don't have the staff or expertise to independently verify claims about retention windows, data sharing, or analytics capabilities. Oshkosh happened to have a police chief willing to dig in. A lot of towns don't.

This is why local pushback matters more than most people assume — a single skeptical official asking the right question can unwind a contract that would've otherwise sailed through on a vendor's word. If you want to see whether cameras like these are already running in your area, check our camera map, and if your town is considering a Flock contract, our take-action page has guidance on the questions to ask before anyone signs anything.