Declaring an Emergency

Flock arrived in Toledo for free. In February 2022, the police department installed 25 automated license-plate readers as a no-cost, one-year pilot — cameras that log every passing plate, and where and when it passed. The pilot became permanent, the vendor became the incumbent, and the price stopped being zero.

By late 2024, the city was paying, and it paid the ordinary way: it took bids. In December, the council approved a 3-year, $150,000 expansion — 20 more readers and Flock’s cloud software — through a competitive process the ordinance documents in plain terms: Flock was “the lowest and best bidder.” Eleven months later, the council bought far more and bid nothing. In November 2025, ordinance O-512-25 authorized a fresh 3-year Flock agreement worth $846,000 — about $282,000 a year, roughly five and a half times the 2024 deal — and waived the competitive-bid requirements of Toledo Municipal Code Chapter 187 outright. The justification on the record was that Flock’s “Vehicle Fingerprint” technology was proprietary, available from no one else.

The city had bid that same vendor the year before. Whatever made Flock a sole source in 2025 did not stop the police department from running a competitive process in 2024, when the check was smaller. The larger the contract grew, the less competition it invited.

Both ordinances closed with the same phrase: each “declared an emergency.” So did the amendments that followed in 2026 — further continuations of the portable readers in May, then June. An emergency declaration makes an ordinance effective immediately; paired with a bid waiver, it lets a sole-source vendor renew without a rival ever quoting a price. The result is a network of more than 100 Flock cameras reading plates across Toledo.

An emergency declaration is not, by itself, unusual in Toledo. Of the 552 ordinances the council introduced from January 2024 through mid-2026, 520 — better than nineteen in twenty — carried the same language. On that record, the phrase reads less like an alarm than like a routine: a way to skip a layer of procedural waiting. Whether the clause was ever meant to be used this liberally is a question for another piece. The point here is narrower. Declaring an emergency is ordinary in Toledo. Waiving competitive bids is not — only about one ordinance in twelve did so over the same period. On the Flock renewal, the council reached for the rarer instrument, on the larger sum, for an already-contested surveillance system, having competitively bid the very same vendor a year earlier.

None of this turns on whether the cameras solve crimes. It turns on a narrower question that competitive bidding exists to answer out loud: is a no-bid renewal the best the city can do — and how would anyone know, when the city tested the market once, then chose not to again?

The pattern repeated in June. On June 22, 2026, running into the small hours of the next day, the council passed ordinance O-286-26 by 8–4, extending 4 portable license-plate readers that feed the police department’s Real Time Crime Center. The portable units are the mobile cousins of the fixed cameras: they can be moved, aimed, and parked. Most of the council saw a working crime tool. Four members did not.

The four who voted no were Nick Komives, Dr. Brittany Jones, Theresa Gadus, and Erin Kramer. Their objection was not that plate-readers are useless. Gadus had earlier filed a referral pressing the administration on the unanswered basics — how long Flock keeps the plate data, whether other agencies can query it, and, as her referral put it, whether they need a warrant. On June 22, 2026, those questions were still open when the vote was called.

The majority did not treat those questions as trivial; it treated them as a separate problem. Council member Sam Melden, who voted yes, drew the distinction plainly from the dais: there were “two issues in front of us” — how to resource police with the tools to do their job, and how to govern residents’ data when a private company handles it. His answer was to fund the tool now and build the data rules elsewhere, through an RFP process and a citywide data-governance policy the council had promised in January but not yet delivered.

Others made the case on public safety. Council member Adam Martinez pointed to local crimes the cameras had helped investigate and argued the council could hold both thoughts at once: “I do hear what the residents are saying — this is not falling on deaf ears,” he said, before proposing a working committee to audit how the data is accessed. “I just don’t think ignoring or voting down this contract is the way to do that.” Council member George Sarantou stressed the leash — “this is a one-year contract, and we need to do our due diligence to oversee” it — and Council President Vanice S. Williams was blunter: “I will not vote to take tools away from police.”

The disagreement, then, was less about whether the data questions mattered than about sequence: whether to withhold the contract until the rules existed, or approve it and write the rules later. The council chose later.

What made the June meeting unusual was who showed up to defend the deal. Not a police commander or a city lawyer, but Flock’s own senior director of public affairs, Trevor Chandler, who came to the council’s microphone to answer members directly. A vendor arguing its own contract on the public record is worth watching, because it puts the company’s promises where a court, or a voter, can later find them.

The sharpest moment came when a council member pressed Chandler on Flock’s own fine print. On February 16, 2026, the company had rewritten four of its standard terms and conditions, and one of them concerned selling data. By the council member’s account, the old terms flatly promised the company would not sell — and that sentence, she said, was gone. Chandler’s reply: “Our terms and conditions still fully prohibit the selling of any data.”

Both things can be read from the same tape. The prohibition on selling data may well survive in the condensed terms, as Chandler said. And a promise is easier to trust when it is written plainly than when a company explains that deleting it made the document “simpler.” That is precisely the sort of detail a competitive procurement, or a negotiated data-retention clause in the contract itself, is built to pin down before the money moves — not after, at a microphone, at midnight.

Toledo is buying in as other cities sell out. In February 2026, NPR reported that more than 30 American cities had moved to cancel their Flock contracts, driven largely by evidence that plate data could be reached by federal agencies, including for immigration enforcement. In Ohio, both Dayton and Cleveland ended their Flock deals. Federal data-sharing is the specific worry that Gadus’s retention-and-access questions were aimed at — and the specific worry Chandler came to Toledo to answer.

A plate-reader that helps find a stolen car and a plate-reader that quietly builds a map of everyone’s movements are the same device; what separates them is the rulebook around it — retention limits and query logs, warrant requirements, an audited contract. Toledo voted for the device and left the rulebook for later. You can watch the council work through it, session by session, in Hamlet’s archive of Toledo meetings. (Toledo’s police drone program is a separate initiative, and not part of this contract.)