Key takeaways
- VA early robot results were mixed, and delivery, pharmacy and cleaning robots carried most of the early use.
- An idle robot costs staff time and route space even when the deployment count looks strong.
- Response time to a stalled unit matters more than the number of units on paper.
- Name a lead for every event class and every shift before any fleet expansion.
- Log idle minutes and staff chase minutes, not just completed trips.
Why do idle robots cost more than the headline suggests?
A deployment count tells you how many robots arrived, not how many minutes they worked. The cost of an idle unit shows up in staff time, delayed trips and a route blocked by a machine waiting for someone to free it.
That gap is the main lesson from the Veterans Affairs experience in early 2026. Results were mixed, and much of the trouble sat in the response system around the robots: who notices a stalled unit, who walks to it and how long that takes.
Treat the headline as the start of your cost model, not the end of it.
What did the March 2026 VA report actually find?
A March 2026 report in Nextgov, republished from FCW, described VA early robot use as having mixed success, though excitement remained. According to the Nextgov text, 37 uses were delivery robots, 35 were for pharmaceutical mixing and packaging, and 31 were for facility cleaning. Delivery, pharmacy and cleaning robots formed the core of the early footprint.
Follow-up visits to some facilities found mixed benefits, even though hospital staff showed strong excitement. Pulse, which summarized the same story, described deployments as mostly delivery, pharmacy and cleaning robots, and reported that many robots sit idle or need staff to chase them.
Why do robots end up waiting on people?
A stalled unit still takes up a route, a charging slot and a staff member's attention, even though it delivers nothing. Staff who must chase a robot down are pulled away from patient work to do a machine's job, and none of that appears in a unit count.
The sources I could check do not give a count of idle units, so the idle finding is qualitative. Do not turn it into a percentage in an internal memo without your own log data.
The problem is older than this report. According to the background section of the 2026 Nextgov article, a 2016 VA inspector general finding on the Madison, Wisconsin facility said robots acquired in 2012 were removed from the hospital floor after efforts to make them work in hallway traffic failed. The robots could get stuck near each other and block staff and patients.
What separates the strongest case from the rest?
Pulse cites the Houston VA Medical Center as the strongest case. It was a purpose-built site, and its staff were trained to maintain the robots, which reduced reliance on outside vendors.
That is the pattern to copy. When a stalled unit can be cleared, diagnosed or swapped by people already on site, the response clock starts in minutes rather than in the time it takes a vendor to arrive. A facility without that capacity should plan for more idle hours, not fewer.
What does the VA procurement trail signal?
A VA VISN 1 sources-sought notice dated March 30, 2026 sought autonomous mobile robots for delivery of medications, specimens and supplies. A later solicitation for the same VISN 1 robot delivery system BPA listed a June 4, 2026 deadline, and it now shows as closed in the search results I used.
Government notices name the tasks an agency wants automated, which makes them a useful model for your own requirements. Write requirements by task and response standard, the way the notice names medications, specimens and supplies, rather than by a single brand or a headline unit count.
What belongs on a pre-expansion checklist for response times, dispatch and reporting?
Use the VA findings as a gate. The checklist below asks what the current fleet can prove before a single unit is added.
If your team cannot answer each line for the robots already running, another unit will multiply the same gaps rather than close them.
- Set a response target for each event class: stalled unit, low battery, blocked corridor and full failure, each with a named lead.
- Name who dispatches a person to a stuck unit on every shift, including nights and weekends, and confirm that person can reach the unit within your target.
- Train a small group of on-site staff to clear jams and reset units without waiting on a vendor call.
- Confirm remote triage can diagnose a fault before anyone walks to the robot.
- Log idle minutes and staff chase minutes for every unit each day, not only completed trips.
- Agree a spare unit rule so one stalled robot does not stop an entire delivery route, and set a threshold that pauses expansion when idle time rises.
How should a pilot be phased before the fleet grows?
Start with one zone and one task, then measure response time, idle minutes and staff chase minutes over a set period before adding units. A go or no-go decision should rest on logs, not on how a robot performed during a demo.
Service Robot Co. is a full-service commercial robot integrator for US businesses. We are OEM-neutral: we pick the right robots across manufacturers, then finance, deploy, integrate, train and service every unit through a nationwide US engineer network, so one vendor covers the whole lifecycle.
Robots reach a customer through a 3-year lease with one fixed lease payment quoted after a site assessment. We map the site, provide go live support, and can start with one leased unit, with spare unit coverage and on-site dispatch aimed at the response gaps described above.
Frequently asked questions
Want a robot working for you?
Tell us the job and the site. We will recommend the robot, quote the lease, and keep it serviced.
Sources
Service Robot Co. is not affiliated with, sponsored by, or endorsed by the companies mentioned in this article.