Hospital Visitor Parking Decks: What Robot Patrols Must Cover

Does a hospital visitor deck need different robot planning?

Yes. A hospital visitor parking deck is not a shopping center garage with a hospital sign on it. Traffic follows visiting hours and shift changes, families arrive at odd hours after bad news, and an emergency lane may run beside the same stalls where a parent is buckling a child into a car seat.

For a facility team, a security patrol robot can extend the reach of a small guard force across a large deck. It does that well only when its route, camera set and escalation rules are written around hospital operations, and those rules are agreed before any contract is signed.

How much crime happens in hospital parking structures?

Parking structures carry real risk. According to Healthcare Facilities Today, citing FBI reports, parking structures and lots are the third most common site of murders and assaults in the US. In 2017, 378 of 5,542 homicides took place in a parking lot or garage.

The same trade article describes a nurse killed in a garage attached to a Wisconsin hospital. Staff described the garages as poorly lit and usually without security staff. A patrol program that ignores lighting and staffing gaps is planning for the wrong deck.

How do late-night arrivals and emergency lanes change the route?

Late-night arrivals are the pattern that separates a hospital deck from a commercial one. A lone visitor walking from a car at 2 a.m. is most exposed at stairwells, elevator lobbies and lower levels, so those points belong on the route's most frequent pass.

Emergency lanes need a rule that outranks the patrol. The route should yield to ambulance and fire apparatus access, and the provider should explain how a robot clears a lane or holds position when an emergency vehicle approaches. Ask whether that hold is automatic or triggered by staff.

Map those lanes as no-go or hold zones, then test the route at the hours when the deck is busiest, not only during a midday site walk.

What should the patrol route and charging cycle cover?

Route length and battery life set the real coverage. A trade article on parking lot security robots, undated and partly vendor-influenced, says patrol routes often run 3,000 to 4,000 feet and sometimes more than a mile. It also says robots patrol about two hours between 15 to 20 minute charges. Measure a multi-level deck against those figures, not against its floor area.

Physical fit matters as much. Robotomated's buyer guide says the Knightscope K5 stands about 5 feet tall, weighs about 400 pounds, needs relatively flat paved surfaces, cannot climb curbs above 3 inches, and needs a charging station with cellular or WiFi connectivity on site. Each of those constraints shapes where the charger sits and which ramps the route can cross.

Which camera, sensor and privacy terms matter?

Vendors advertise a long list of sensors. Knightscope's product page for the K5 lists 360 degree HD video, thermal imaging, plate recognition and public address. A Securenh vendor blog lists thermal imaging, motion detection, plate recognition and 360 degree video among garage robot sensors. Those are capabilities, not a promise of coverage.

Privacy is the term teams most often skip. Public criticism summarized on Wikipedia says the K5 can take pictures and video without notification. EPIC's Jeramie Scott argued that automated surveillance and plate recognition in public makes everyone a suspect. A hospital privacy office should set retention periods, access rules and signage before the first patrol.

How should alerts escalate, and who verifies them?

Escalation is where pilots earn trust or lose it. Daxbot's website says its command team verifies alerts before anything goes to security personnel or a provider, and that route, schedule and escalation rules are set during planning. Ask whether a person sees every alert or only the ones a sensor flags as serious.

Salem, Oregon tested Daxbot robots in a parking garage in early 2026. The stated goal was deterrence, with a prerecorded trespass warning, minor incidents going to a security company and dangerous ones going to police. As of the Salem Reporter article in February 2026, officials reported no calls to security or police. That reflects an early trial, not proven results.

Montgomery County, Maryland shows the downside. According to Bethesda Magazine in January 2026, the county scrapped a pilot of a Knightscope Parker robot in its Silver Spring garage and said the robot was not a fit. Officials said most garage incidents were minor, such as property damage, theft and loitering. The article also cites controversy over past safety incidents and a 2016 mall incident that injured a toddler. A pilot that ends this way is a warning to write success measures before the robot arrives.

What questions should you put to a security robot provider?

Use these as a scoring sheet. Ask for written answers, and count any vague reply as an open gap.

• Which levels, stairwells and lanes are excluded from patrol, and who approves changes to that map?
• How long is one patrol loop on our deck's actual length, and where does the charging dock sit relative to the route?
• Does the robot yield to ambulances and fire apparatus, and is that hold automatic or staff-triggered?
• Which cameras, thermal sensors and plate readers are on by default, and which need written hospital approval?
• How long is footage and plate data kept, who can access it, and where is it stored?
• What notice do visitors receive before recording begins, and who designs the signage?
• Who verifies each alert before security or police are called, and during which hours is that person on duty?
• What is the written escalation path for a minor incident, a dangerous one and a medical emergency?

Where does an integrator fit the deck plan?

Service Robot Co. is a full-service commercial robot integrator for US businesses. We are OEM-neutral, so we select robots across manufacturers for the job. Customers take a robot on a 3-year lease with one fixed payment quoted after a site assessment. We then deploy, integrate, train and service each unit through a nationwide US engineer network, so one partner answers for the whole lifecycle.

For a hospital deck, that matters because the questions above touch facilities, security and IT at once: charging power, network connectivity, camera settings and the emergency lane map. Platforms such as the Knightscope K5 and Daxbot's Dax differ in route fit, curb tolerance and escalation design, as of the vendor pages we reviewed. The hospital's security team still keeps the final rules.