Meta description: Cleveland City Council passed a police license-plate-reader contract 9-6 on July 15, the closest vote of the night. No dissenter explained why.
Cleveland City Council met for 71 minutes on July 15, 2026. In that time, members took roll call, sat through a moment of silence, recited the Pledge of Allegiance, heard a formal warning about meeting disruptions, processed dozens of condolence and congratulatory resolutions, and voted on more than 60 pieces of legislation. Almost none of it took more than a few seconds per item.
Then, buried in the second half of the meeting, seven votes broke from the council’s usual unanimity. The most contested of the night: a 9-6 vote authorizing a contract with Flock Group for automatic license plate readers for the Cleveland Division of Police. Six members said no. Not one of them said why, at least not on the record.
“Mark me as a no.” No explanation required. That’s the pattern across all seven contested votes on July 15, and it’s the story of this meeting.
How Cleveland City Council passes 60 items in 71 minutes
If you’ve never watched a full city council meeting, the pace can be disorienting. Cleveland City Council, like most municipal legislatures, relies heavily on a consent calendar: a bundle of ordinances and resolutions introduced, and often passed, in the same session, with no individual discussion.
The mechanic is simple. The clerk reads a long list of ordinance and resolution numbers into the record, one after another, often just a title and a departmental sponsor. Then a council member moves “that the rules be suspended and the legislation just read be placed on final passage.” Under normal council procedure, legislation has to sit through multiple readings before a vote. Suspending the rules skips that wait and sends the whole batch straight to a vote in one motion.
The roll is called once. If nobody objects, everything in the batch passes together, and the clerk simply reports the tally: “on all others, 15 yeas.”
This isn’t unusual or improper. It’s how most city councils handle high-volume, low-controversy business: purchasing agreements, personnel contracts, easement approvals, liquor license transfers, alley vacations, oaths of office. Cleveland’s July 15 meeting alone included cooperative purchasing agreements for laptops and Cisco hardware, water main repair contracts, three subdivision plats, eight liquor license transfer notices, and roughly 20 condolence resolutions read by name.
That process matters for one reason: when a council member wants to break from the pack, they have to say so out loud, in real time, as the item is being read, before the vote is gaveled through with everyone else. That’s exactly what happened seven times on July 15. Because the default mode of this meeting is unanimous and silent, those seven moments are the story, starting with the closest one.
The centerpiece: Cleveland City Council license plate readers pass 9-6
The most contested vote of the night was Ordinance 683, authorizing the Director of Public Safety to contract with Flock Group for the acquisition, renewal, and maintenance of an automatic license plate reader system for the police department. It passed, but narrowly: 9 yeas, 6 nays, the closest vote of the meeting.
As the item was read, six members asked in quick succession to be recorded as “no” votes.
“Council President, could you please mark me as a no on Ordinance 683, 2026?”
That request, or some near-verbatim version of it, was repeated by member after member in the span of about 30 seconds. Council Member Shaw and Council Member Austin-Davis are both named clearly in the record asking to be marked no on 683. At least four other members also asked to be recorded as dissenting votes on the same item, though the meeting recording doesn’t reliably identify all of them by name. The whisper-generated transcript produces inconsistent speaker labels around this stretch (at one point naming both a “Councilman Harsh” and a “Councilwoman Harsh” seconds apart, though the roll call lists only one member surnamed Harsh), so this piece reports only the two names that are unambiguous in the source.
What should give any resident pause is this: not one of the six dissenting members stated a reason for their vote on the record. Each simply asked the council president to note them as a “no.” There was no floor debate, no back-and-forth about surveillance concerns, data retention, or vendor selection, at least none captured in this recording. The contract passed, and the meeting moved on within seconds.
Automatic license plate readers like Flock’s are part of a live national debate: police departments credit them with solving crimes and recovering stolen cars; civil liberties groups warn about surveillance scope, data sharing, and how long the data sticks around. Whatever the six dissenting council members’ concerns were, Cleveland residents don’t get to hear them from this meeting.
A data-center moratorium, a suburban settlement, and TIF financing
Ordinance 683 wasn’t the only close vote. Six other items broke from the night’s near-total unanimity:
- Ordinance 556 — a moratorium on zoning permits, certificates of occupancy, and other permits for data centers in Cleveland, covering permits issued by the Department of Public Utilities as well. It passed 14-1. Council Member Starr asked to be marked as the lone “no.”
- Ordinance 664 — a first amendment to a settlement agreement between Brook Park and Cleveland relating to the International Exposition Center and the Emerald Park Joint Economic Development Zone (a shared tax and revenue arrangement between the two municipalities), plus establishing a special revenue fund. It passed 12-3.
- Ordinance 666 — a public-improvement authorization to design, construct, and renovate parts of Cleveland City Hall and Public Auditorium. It passed 14-1.
- Ordinances 686, 695, and 696 — three linked votes authorizing the city to acquire and reconvey property, and to enter tax-increment-financing (TIF) agreements, in support of a downtown development project. Each passed 13-2. (The transcript names one entity involved as the “Heller Keller Cone Project,” a name that doesn’t check out against any known Cleveland development and is very likely a transcription error. This piece describes it only as a downtown TIF-financed development project until the real name can be confirmed.)
As with Ordinance 683, no dissenting member on any of these items explained their vote. Council members simply asked to be marked no as each item was read, and the votes were tallied without discussion.
One more item belongs in this account, even though it doesn’t involve license plate readers: Ordinance 757, approving a collective bargaining agreement with the union representing theatrical stage employees and amending a salary schedule, passed 14-1 in the meeting’s first half. Again, no rationale was given.
A resolution opposing a state bill, with limited detail
The meeting’s one unanimous political statement came in Resolution 883, sponsored by Council Member Starr, opposing the implementation of Ohio House Bill 492. It passed 15-0, with no recorded dissent.
The resolution itself states its concerns: potential impacts on civil liberties, community trust, racial equity, and the relationship between Cleveland residents and law enforcement. It urges the Ohio General Assembly to review the bill’s implementation and consider amendments providing “additional protections against unnecessary escalation, discriminatory enforcement, and violations of constitutional rights.”
What the resolution does not do, and what this meeting’s recording does not supply, is describe what House Bill 492 actually does. Fifteen votes against a bill, and zero sentences in this meeting explaining what’s in it. Residents who want to understand the underlying state legislation will need to look beyond this meeting. Cleveland’s council registered its objection and the grounds for it. The bill’s actual provisions were never read into this record.
What the meeting didn’t include
Two things are missing from this meeting, and both matter.
First, there was no public comment segment in this recording. Residents did not have an opportunity, at least not one captured here, to weigh in on the license plate readers contract, the data-center moratorium, or anything else before the vote.
Second, and related: no council member who voted “no” on any of the seven contested items gave a reason on the record. Not on the Flock Group contract. Not on the data-center moratorium. Not on the Brook Park settlement. Not on the TIF financing votes. Members stated their votes; they did not explain them.
That’s not necessarily a scandal. Council members may have discussed their reasoning in committee, in ward meetings, or with constituents directly, none of which shows up in a floor recording. But for a resident trying to understand why their representative voted a certain way on a police surveillance contract, the public record from this meeting alone doesn’t answer that question. That absence of explanation is itself a transparency story, separate from how anyone feels about the underlying policy.
One other figure from this meeting deserves a correction before it circulates any further. The clerk’s reading of a loan acceptance from the Ohio Water Development Authority was recorded as “$26,311,637,000,” roughly $26.3 billion. That figure is almost certainly a transcription artifact. The realistic scale for this kind of municipal utility loan is approximately $26.3 million ($26,311,637). This is a reconstructed figure based on the likely intended number, not an independently verified one. Anyone citing this loan amount should confirm it against the underlying ordinance file rather than the meeting audio.
Seven votes, seventy minutes, no explanations
Most of what Cleveland City Council did on July 15 was uncontested and, frankly, unremarkable: purchasing agreements, personnel contracts, easements, plat approvals. That’s normal, and it’s not evidence of anything except a functioning bureaucracy processing its routine business.
But underneath that volume, seven votes tell a different story. A police department got new surveillance technology over the objection of six council members. A fast-growing, land-hungry industry hit a moratorium. A neighboring suburb got a settlement. A downtown project got its financing. All of it decided in roll calls that lasted seconds, with no public comment and no stated rationale from anyone in the minority.
If you want to know why your council member voted the way they did on the license-plate-reader contract, this meeting’s public record won’t tell you. That’s exactly the gap Citizen Portal exists to help you close.
Follow your city council on Citizen Portal to see what’s coming up for a vote before it’s already decided.