Flock Safety cameras have become a familiar subject at city council meetings.
Residents ask who can search license plates, how long records are kept, which police departments can see them and what happens when cameras operated by one community become part of a much larger network.
Those are reasonable questions. Flock itself describes its product as a connected license-plate-reader network that captures plate numbers, vehicle images and characteristics, dates, times and camera locations.
But while attention has focused on cameras mounted on poles along roads and subdivision entrances, another large camera system has been spreading across the country.
This one moves.
It rides on school buses.
And the company behind one of the largest systems is increasingly describing those buses as something more than transportation.
BusPatrol says it now supports more than 400 school districts and more than 40,000 buses, protecting more than 2 million students. Its careers site says the company has installed more than 300,000 cameras.
The original purpose sounds straightforward: catch motorists who illegally pass stopped school buses.
But BusPatrol’s own marketing now describes school buses as a platform for something considerably broader.
First, the important difference from Flock
BusPatrol says its school-bus stop-arm enforcement system should not be confused with a conventional automated license-plate-reader network.
According to the company, its stop-arm cameras activate for potential violations when a school bus is stopped with its warning lights and stop arm deployed. Artificial intelligence helps identify possible violations, a human reviews the event and law enforcement ultimately decides whether the evidence justifies a citation.
BusPatrol says this system does not continuously scan license plates, does not create a searchable record of vehicle movements and does not permit police agencies to search footage from other communities.
The company also says government customers own their data and that footage that does not qualify for enforcement is deleted.
Those distinctions matter.
A school-bus camera documenting a car passing an extended stop arm is not doing the same thing as a fixed ALPR repeatedly recording vehicles as they travel through a community.
But that is no longer the entire BusPatrol story.
The school bus is becoming public-safety infrastructure
On another section of its website, BusPatrol makes a much broader pitch to law enforcement.
The company calls the school bus “America’s most trusted safety asset” and promotes connected buses as an additional layer of visibility for public-safety agencies.
Its platform advertises access to live and historical bus location and video, integration with real-time crime centers and 911/CAD systems, crash notifications and situational awareness for cases involving missing or endangered people.
BusPatrol says the buses can provide visibility near school zones and bus stops and help authorities identify where students are during emergencies.
The company describes the concept this way: school buses already travel millions of miles through communities, so connecting them to public-safety systems can extend camera coverage into places that previously lacked it.
That’s worth paying attention to.
The stop-arm enforcement system and BusPatrol’s broader public-safety platform are not necessarily the same product or governed by the same access rules. BusPatrol specifically says law enforcement does not have general searchable access to the stop-arm ticketing system.
But the company is simultaneously marketing live and historical bus video and location data as a public-safety resource.
For residents trying to understand the cameras operating in their communities, that distinction should be explained before a contract is approved — not discovered afterward.
Then there is the money
BusPatrol frequently markets its stop-arm program as requiring zero upfront cost.
Its current public-safety website is even more explicit: it calls the program “violator-funded” and says it is “fully funded through violator-paid fines.”
That doesn’t necessarily mean the vendor is paid the same way everywhere. State laws and individual contracts vary substantially.
But public records from other states show why the details matter.
A Bloomberg Businessweek investigation published through Type Investigations examined BusPatrol agreements around the country and found that many local governments were sending significant portions of citation proceeds to the company while also paying technology fees.
In Richmond, Virginia, for example, the contract examined by CBS 6 provided BusPatrol with 60% of gross citation revenue while the school district received 40%. Richmond’s portion was then subject to a $37,800 monthly technology fee. CBS 6 reported that during the 31 months it reviewed, Richmond actually generated a profit from the program in only 15 months.
BusPatrol has said financial structures are designed to allow it to recover its upfront investment and operating expenses and that in some programs operating costs can meet or exceed citation revenue.
Montgomery County issued $92 million in fines
The numbers become much larger in Montgomery County, Maryland.
Bloomberg and Type Investigations reported that more than 375,000 tickets representing $92 million in issued fines had been generated there.
Yet the investigation found little reduction in violations and no evidence of a decline in collisions near stopped school buses. An earlier Maryland audit similarly reported that it could not find evidence that the program had reduced collisions, improved public safety or decreased total violations.
That does not establish that school-bus cameras cannot improve safety.
Results differed considerably among the communities Bloomberg examined. Some experienced falling citation rates. Others did not. The investigation also found examples where enforcement was accompanied by education or infrastructure changes and violations fell more substantially.
BusPatrol says the vast majority of people receiving one of its citations do not become repeat offenders, and it argues that illegal passing of stopped buses remains a serious safety problem.
The important question for a government purchasing the system therefore isn’t simply whether the cameras can issue tickets.
It’s whether the program produces the outcome officials promised when they approved it.
Illinois has already put limits on this model
Illinois permits automated school-bus enforcement, but state law contains safeguards that appear designed to address some of the controversies familiar from the red-light-camera era.
A school board must approve the system and approve the vendor contract. The district must also enter an intergovernmental agreement with the municipality or county administering enforcement.
Illinois law specifically says vendor compensation must reflect the equipment or services provided and cannot be based on the number of citations issued or the revenue generated by the system.
Fine proceeds, however, are divided equally between the participating school district and the municipality or county administering the program.
That means the Richmond arrangement — where a vendor receives 60% of citation revenue — would not simply transfer into Illinois under the same terms.
But the Illinois structure still makes the contract important.
How much does the technology cost?
Is the program expected to support itself from citation proceeds?
How many events does the software flag?
How many are rejected before reaching police?
How many citations do officers reject?
How many drivers successfully contest them?
What happens to footage that never becomes a citation?
And, most importantly, do violations and dangerous incidents actually decline?
Those questions sound familiar because communities are already asking versions of them about Flock.
The conversation shouldn’t begin and end with Flock
It is easy to think of municipal surveillance as a collection of individual products.
A Flock camera here.
A school-bus camera there.
A real-time crime center downtown.
A traffic camera at an intersection.
But vendors increasingly sell these technologies as connected public-safety infrastructure.
BusPatrol’s current pitch demonstrates that evolution unusually clearly.
The company began with a compelling and narrow use case: record motorists who illegally drive past stopped school buses.
Today its website invites law-enforcement agencies to think much bigger — live bus video, historical video, bus-location information, real-time crime center integration and road coverage provided by a fleet that moves through neighborhoods every weekday.
And BusPatrol says its enforcement side can provide the revenue to help fund that broader public-safety mission.
None of that makes the technology inherently improper.
There are legitimate reasons to want evidence when someone drives around a school bus full of children. There are also legitimate emergency situations in which knowing where a bus is — or seeing its cameras — could help police find a missing child or respond to a crash.
But those benefits don’t eliminate the governance questions.
They make those questions more important.
Before a community turns hundreds of yellow buses into connected cameras, residents should know exactly what is being installed, when it records, who can see the footage, how long it is retained, whether the system can later be expanded, how the vendor gets paid and what evidence will be used to determine whether the program actually improves safety.
Flock may be the camera company everyone is talking about right now.
It isn’t the only camera network local government should be explaining.
How this story was made
CityNewsWire reviewed BusPatrol’s current school-bus safety, privacy, trust, careers and public-safety materials; Flock Safety’s current license-plate-reader policies; Illinois’ automated school-bus enforcement statute; Richmond’s BusPatrol contract terms as reported by CBS 6; and the April 2026 Bloomberg Businessweek/Type Investigations examination of BusPatrol programs and public records from communities across the country.
Company statements about technology, privacy, safety performance and program design are identified as company claims. Contract terms and program outcomes are distinguished from one jurisdiction to another because state law and local agreements differ.