Hospital Delivery Robot Setup: What the 8 to 12 Weeks Covers

What the vendor timeline says

According to Relay Robotics, a typical hospital delivery robot setup takes about 8 to 12 weeks, and the onsite installation generally takes 1 to 2 weeks. Those figures surfaced in June 2026 coverage of BayCare Health System adding two more Relay robots at Winter Haven Hospital, and they are the numbers facility leaders will hear first.

Treat them as a vendor claim, not a schedule. The 8 to 12 week range comes from a Relay press release tied to a different deployment, at HCA Florida JFK. RoboticsTomorrow's June 3, 2026 article on BayCare restates the scope as about 12 weeks total, given as a single figure. A facility can plan around that frame. It should not agree to a go live date on the strength of it.

Where the weeks go, phase by phase

Relay's description folds integration hardware work, floor mapping and staff training into the 8 to 12 week window, and reports the onsite installation separately at 1 to 2 weeks. The material checked does not say how many weeks each phase takes. That gap matters, because the longest phase is the one a nursing director has to staff around.

Each phase needs something from your building, so settle these questions before the calendar is set:

• Integration: the hardware and system connections the robot needs before it can move. Ask which hospital systems must be opened and who approves that access.
• Floor mapping: the survey of corridors, doors, elevators and charging spots. Ask who walks the route, how long the survey takes on your floors, and what triggers a remap.
• Staff training: the sessions for nurses, unit clerks and environmental services. Ask how many people are trained, on which shifts, and whether night staff are included.
• Onsite installation: the physical setup the vendor reports at one to two weeks. Ask which days the robot is out of service and what the unit does without it.

Elevators and doors set the real schedule

Relay says elevators are configured during installation, so the robot can call them and ride without staff help. Elevators and doors decide how much of a route a robot can actually run, which makes this claim worth testing on your own lifts rather than accepting it in general terms.

Swisslog's product page, which describes integration over WiFi or LTE with elevators and automated doors, shows that connection work is central to this category, though it gives no timeline. Ask your elevator contractor and facilities team to confirm controller access, after hours elevator behavior and wireless coverage in stairwells and back corridors before the clock starts.

What to confirm before agreeing to a schedule

A vendor timeline describes the vendor's side of the work. Your building adds conditions no press release can see: route length, the kind of load the first route carries, staff hours on the unit, and the approvals your IT and biomedical teams need. A route that moves meal tray transport is a different job from one that moves medication transport robot loads or specimens, and the schedule should name which one is being built.

Ask for a written phase schedule with a named owner for each phase, the floors and elevators included in scope, and the test that counts as live. Then ask what support runs after go live, not only during installation. A schedule that ends at handover leaves the first month to chance.

What the time savings claim does and does not show

Relay states an average of more than 150 hours saved a month across hospitals using its robots. One outlet cites more than 500 deliveries and 150 nursing hours a month at BayCare. Neither figure has been independently verified, so read them as what the vendor measured, not what your unit will see.

Set your own baseline before the first run. Count how often a nurse or runner leaves the unit for supplies, specimens or meals in a typical week, then measure again after the robot has run for a full month. That gives your facility a number it can defend in a budget meeting.

How BayCare's record reads

According to Baynews9, BayCare was testing two mobile robots at St. Anthony's Hospital in 2025. The June 2026 expansion added two robots, named Stork and Miles, at Winter Haven Hospital. Relay's BayCare case study lists four robots, Beaker, Hygeia, Stork and Miles, across three hospitals.

This review could not confirm the three hospital names from an independent source, so treat the three hospital count as the vendor's figure. A move from a test to a multi site fleet still shows something useful: each new site is another chance to measure how long setup really took and compare that against the weeks that were promised.

How Service Robot Co. approaches a first route

Service Robot Co. is an OEM neutral integrator, so we choose the robot for the route rather than for a manufacturer's catalog. We lease the robot through financing on a three year lease, and the lease quote is fixed after a site assessment that measures the route, elevators, doors and wireless coverage. A hospital delivery robot lease starts with those measurements, not with a brochure.

Deployment and integration, site assessment mapping, staff training and go live support sit with one team, and RoboCare keeps each unit serviced by regional service engineers in every state we service. For a facility that does not want to coordinate several vendors for one route, that is the practical case for one partner and one number.