How Long a Hospital Delivery Robot Rollout Takes

The short answer for facility teams

Plan on roughly eight to twelve weeks for a typical hospital delivery deployment, and read that figure as a vendor estimate. Relay Robotics says a typical hospital deployment, including integration hardware work, floor mapping and staff training, takes about 8 to 12 weeks, with onsite installation generally taking one to two weeks. That description comes from a search summary of Relay's September 30, 2026 press release about its HCA Florida JFK deployment. A trade outlet covering BayCare's expansion cites roughly 12 weeks for the same kind of work.

The window is a starting point, not a promise. Most of the calendar goes to work outside the robot itself: approvals, door and elevator access, fire system connections and the floor map. The sections below show how a facilities team can test the estimate against its own building before anyone agrees to a go live date.

What BayCare's Winter Haven expansion added

On June 3, 2026, Relay Robotics and BayCare Health System announced two more delivery robots for the Winter Haven hospitals in Florida. Their work is lab specimen transport and medication and supply runs. The expansion adds to a BayCare fleet that began in 2025 at St. Anthony's in St. Petersburg with two robots, Beaker and Hygeia.

Trade write ups differ on which new robot went to which hospital, so check the split on Relay's own page before you quote it. Relay's case study reports that the robot Stork completed 18 deliveries in her first two days. That is a company reported figure over a short window, so read it as an early signal, not a measured result.

This was an add on at a campus that already runs robots. Public summaries do not say how much of the integration work carried over from the first units, and that is the question to put to any vendor adding robots to a live site.

Where the eight to twelve weeks comes from

Relay says integration drives the schedule. Its HCA Florida JFK deployment meant connecting with elevators, secure doors, fire systems and hospital IT at once. Each of those belongs to a different department, and each approval can wait on the one before it.

The estimates also disagree because they count different things. Relay's figure covers integration, floor mapping and training, with onsite installation as one part of the total. A search summary of a Robozaps listing for Savioke Relay gives an estimated lead time of six weeks. A marketing summary on a robot comparison page describes quick installation in days instead of weeks. Those are not the same measurement, so compare them only after you know where each clock starts and stops.

Walking the building before the first meeting

Start with a route list, not a robot list. Write every pickup and drop point, the elevator bank each route uses and every door that needs badge or secure access. A route that crosses two elevator banks and three secured doors is a different project from one that stays on a single floor, even when both carry the same specimens.

Floor mapping records corridors, doors and fixed obstacles as they stand on the day of mapping. Ask how the map gets updated when a wing closes for renovation, because a map drawn before construction starts goes stale quickly. Also note the hours when corridors fill up. A robot that waits in a crowded lobby adds minutes to every run, and a vendor timeline rarely captures them.

Training staff and reaching go live

Training decides whether the start holds. Nurses, transport staff and environmental services teams each need a short set of rules: how a unit is loaded, what happens when the robot stops, who clears a jam at a door and who calls the service line. Name one lead per floor and make that person the first call, before anyone contacts the vendor.

Go live goes better when the first runs are short and repeated. Relay's case study projects roughly 150 nursing hours saved across the campuses. That is a company projection, not a measured result, so record your own nursing walking hours before the rollout and compare them after a few weeks of real traffic.

Questions to put to any timeline

Before you accept a week count, put these questions to the vendor in writing.

• Does the figure run from contract to go live, or only from onsite installation to go live?
• Which integrations sit with your IT team and which sit with the vendor?
• How many weeks depend on approvals from elevator and door contractors?
• How much of the work carries over when units are added to a live site?
• What does the first 30 days after go live look like, and what triggers a pause?

Where a lease fits in the schedule

Service Robot Co. (servicerobotco.com) is an OEM neutral integrator. We choose the robot for the route rather than the catalog, lease it through financing on a three year lease, and deploy, integrate, train and service every unit under RoboCare, our service plan, backed by regional service engineers in every state we service. The site assessment is where the route list, elevator count and door list above get written down.

You receive one fixed lease payment quoted after that site assessment. Because the quote is built from your floors, elevators and staffing hours, the week count reflects your building rather than a generic estimate. Relay and Savioke appear in this article only because their public material covers this timeline.