A County Garage Security Robot Pilot Ends Over Privacy and Cost

A busy garage, mostly small problems, and thin staffing

The county transportation department manages parking facilities that see heavy daily traffic. One of its largest garages has seven levels, 1,280 parking spaces and more than 9,000 customers each month. Most of what goes wrong there is minor, though the cumulative cost of small incidents is real.

Incidents were concentrated. The department reported that 71% of security incidents in its county-owned garages and lots happened in one downtown area, which made that garage a logical place to test something new. The stated goal was specific: create an additional visible presence of security in the parking facilities.

Staffing was tight. The department reported nearly 190 vacant positions, so simply adding people was not a quick answer. A patrol robot looked like a way to add presence without adding payroll.

• Property damage in the garage
• Theft from and around parked vehicles
• Loitering
• Violent crime, which the department described as less common than the minor incidents

A one-year pilot with a five-foot patrol robot

The department began a one-year pilot in June 2025 at the garage, using a five-foot, 420-pound patrol robot built by the robot supplier. The unit carried 360-degree cameras and lidar, and it could detect people and read license plates. It had no facial recognition and did not record audio.

The plan also set rules for data and alerts. The robot had lights and sirens that could be activated, along with a call button for county parking security. The department was the sole owner of recorded data, and the supplier could view footage only for servicing. Footage was kept for 30 days and shared with county police for investigations.

Several councilmembers said they did not know the pilot was underway until they saw television coverage of it on June 11. That gap in communication became part of the story, and it shaped how the public later judged the rollout.

• Single garage, single year, one defined pilot scope
• Department owns recorded data, with a 30-day retention period
• Footage shared with county police for investigations
• Call button linked to county parking security

What the pilot produced, and why it ended

The pilot ended in January 2026. The department said it would return the robot to the supplier and concentrate on stationary cameras, lighting and more trained security personnel in county garages. Public figures for the pilot cost ranged from $90,000 to about $100,000.

Operational concerns surfaced early. One councilmember said the robot moved so slowly that three cars backed up behind it. Others raised a possible liability question for vehicle damage, and one said they could not see the department's logo on the machine, so it did not clearly identify who was running it.

Privacy was the decisive problem. The department's director acknowledged strong concern about surveillance, with people feeling watched, tracked and monitored in public facilities. Public reaction was mixed, since some residents and officials felt the robot might add a sense of security. Others were deeply worried about monitoring. The council president said residents felt watched and that the rollout lacked transparency and community input.

The county turned toward fixed tools and people. It added 81 security cameras in the downtown core last year, bringing the total to 225 across three commercial centers, and uniformed security personnel now staff downtown garages around the clock. A law professor quoted in regional coverage called robots of this kind security theater, a measure that makes people feel better without adding real protection.

What owners should assess before a patrol robot pilot

Service Robot Co. is a vendor neutral robot integrator for US businesses. We select the right robot across manufacturers, then handle robot deployment and integration, training and service through a nationwide US engineer network. Robots reach customers through robot leasing for business: a 3-year lease with one fixed payment, quoted after a site assessment.

The lesson in this case is mostly non-technical. Before any security patrol robot arrives, an owner should settle who owns recorded data, how long footage is kept, who can access it, how the unit identifies itself, how it behaves in live traffic lanes, and who answers the call button. A site assessment is the right place to test those questions, along with route speed and lane layout.

A well scoped robot pilot program can still be useful. It gives an operator room to learn, but only if the community hears about it first and the operator plans for the reaction as carefully as for the machine.