Delivery robots and the complete trip to the recipient

What a delivery system includes

Starship describes robots that carry food, groceries and other supplies using cameras, radar and additional sensing for navigation. Its robot and FAQ pages describe the delivery service and human support around it. Treat manufacturer-wide autonomy claims separately from a measured completion rate on a particular route. [1] [2]

A route brief should state the departure point, the recipient's access point and the boundaries of the service area. It should also identify who loads the order and what happens when the recipient is unavailable. Indoor reception, outdoor pavement and stairs are different access conditions.

Define completion at the recipient

For an illustrative campus route, the robot stops outside a residence. The recipient still needs to receive a notification, identify the order and collect it. A service that ends at the entrance should not be described as delivery to every room.

Record each stage separately. Loading delays belong to dispatch, route interruptions belong to travel, and a missed collection belongs to the handoff. Combining them into one autonomous-driving score prevents the service team from finding the cause of a late order.

Scroll sideways for all columns.

Use a round trip to estimate service capacity

Imagine a robot taking 12 minutes outbound, four minutes for collection and ten minutes to return or reposition. Add four minutes for loading. The assumed cycle is 30 minutes, giving two deliveries per hour when it carries one order per trip.

A four-robot group would therefore give eight deliveries per hour under this simplified model. Shared queues, charging and uneven demand can reduce that output. Multiple orders on one trip require a different model because each stop adds time.

The numbers are illustrative. They are not Starship performance claims, a staffing forecast or proof that a public route is approved.

Evaluate the pavement as shared space

A field trial should include the actual approved route and its pedestrian access requirements. Record where the robot stops, whether people can pass and how staff handle a blocked path. Include wheelchair and mobility-aid access in the site's review.

Avoid describing a city or campus as covered solely because the service operates somewhere within it. Service boundaries, permitted routes and collection points need their own current information. Rules and operating permissions depend on jurisdiction.

Report delivered orders and unresolved exceptions

In an illustrative set of 100 accepted orders, 92 are collected at the planned point, three require a different handoff and five are returned. Report all three outcomes. A count of 95 completed trips would obscure that only 92 finished in the planned way.

Keep human assistance, food or goods handling requirements and time at the destination with the result. The service can then be compared with its intended promise to the customer, rather than with an unrelated measure of distance traveled.