Building-by-Building Operations Management Is Splitting Off From Delivery Robots

From making robots to operating them

On October 23, 2026, the Ministry of Land, Infrastructure and Transport, Korea’s national transport ministry, announced a regulatory overhaul plan for commercialising autonomous vehicles and mobile robots. The plan includes setting operating methods and responsibility boundaries for the places where robots actually move, such as apartment complexes, construction sites, car parks, and urban logistics facilities.

These are not yet finished rules. The government plans to develop rules for robot waiting, charging, and maintenance space; building access and elevator integration; accident liability; insurance; and spatial information.

For driverless autonomous vehicles, the government also plans to formalise operators that manage vehicle operations separately from the companies that make the vehicles. The direction is to recognise remote monitoring of vehicle status, passenger safety, accident response, and on-site dispatch as a single business.

Outdoor mobile robots already have a baseline. A combination of a robot and equipment used to manage it remotely must receive an operational safety certification before it can use pavements and crosswalks. It must weigh no more than 500 kilograms including its load, and its top speed must not exceed 15 kilometres per hour.

Operators must purchase liability insurance before operating. Minimum coverage is KRW 150 million per person for death and permanent disability, KRW 30 million per person for injury, and KRW 1 billion per accident for property damage. Robots must also display the company name and an emergency contact number, so a channel for handling accidents and complaints on site is needed from the start.

On-site operations that can be separated from the manufacturer

Some robot companies provide both the device and on-site operations. In some systems, manufacturers primarily manage robot status and driving records, while sharing fleet dashboards and operational data with customers.

Imagine 12 staff members managing a 1,200-unit apartment complex. The management office head tracks delivery-vehicle access, elevator inspections, resident complaints, and construction work across separate ledgers and group chats.

When delivery robots arrive, someone must first inspect the route between the main gate and each building entrance, then mark ramps, kerbs, children’s playgrounds, and rubbish collection times. Each time the robot company changes, the same information must be explained again. Operating hours and charging locations must be copied into documents and shared with the security office and the residents’ representative council.

When a robot stops, the work becomes even more fragmented. A security guard takes a photo and sends it to the management office. The management office calls the robot company. If a vehicle or facility has been scratched, the time and location must be explained again to the insurance contact. If there is no record of who moved the robot remotely and when, there is also less evidence for answering residents.

The service that can break out here is building-by-building operations management. It does not make robots. Instead, it manages permitted areas and times within a complex, resident notices, access approvals, charging-space allocation, fault reports, and connections to on-site dispatch in one place.

After this changes, the management office head opens a complex map and marks construction zones and restricted access times. The robot company checks those conditions before operating. If a stop or contact occurs, the robot number, time, location, photos, and contact history are collected in one case file. Each month, the team can review recurring faults and complaint locations, then repair a corner of a flower bed or change operating hours.

Some work clearly remains with people. Removing a fallen bicycle, meeting and explaining the situation to a concerned resident, and stopping robot operations during a water leak or fire must be handled by people on site. The role of this service is not to remove people. It is to reduce repeated handoffs of the same information among manufacturers, security offices, and management offices.

Elsewhere, operating rules and on-site services grew together

In the United Kingdom, Starship Technologies and Co-op operated grocery robot deliveries centred on Milton Keynes. Users selected from about 1,000 products in the app and paid delivery fees of about KRW 2,800 to KRW 4,600 depending on distance.

The service expanded into areas near Milton Keynes rather than ending as a demonstration at one store. These figures come from company announcements, but they show how repeatedly handling orders, loading, pavement travel, and customer handover within a compact local area can become a distinct service.

Los Angeles in the United States required pavement delivery robots to carry insurance, follow operating hours, avoid obstructing pedestrians, comply with neighbourhood-level fleet caps, and submit operating records. Under these permits, Serve Robotics accepted restaurant orders and used robots for short-distance deliveries, while an ordering platform handled customer intake and payments.

Serve began in Los Angeles and expanded to multiple cities. According to the company’s 2025 filing, it had delivered more than 100,000 orders from more than 2,500 restaurants and owned more than 2,000 robots. In this structure, Serve Robotics makes the robots and runs local operations, the ordering platform handles customer orders and payments, and the city permits operations.

Four small services to separate out

1. Robot access management for apartment complexes

• This service registers operating hours and entrances for each complex, then handles security-office approvals and resident notices in one place.
• It is for management office heads and outsourced property-management companies at apartment complexes with 500 or more units that are considering delivery robots.
• As operating standards are created for each apartment complex, there will be a role for managing on-site rules that must be followed regardless of manufacturer.
• The first screen shows a complex map with colour-coded zones for “operation permitted,” “time restricted,” and “entry prohibited.”

2. Pre-deployment site inspection service

• This service walks the routes robots would use and records kerbs, ramps, narrow passages, automatic doors, elevators, and charging locations to assess whether deployment is possible.
• It is for facilities teams at mixed-use shopping buildings or campus management teams introducing delivery or patrol robots for the first time.
• As place-specific standards and robot-friendly building standards emerge, inspection results based on the same checklist matter more than vague consultation.
• The first screen has an address field and four buttons to begin checks: “outdoor route,” “building access,” “charging,” and “accident response.”

3. Incident and complaint record bundle

• When a collision or obstruction complaint is received, this service creates one bundle containing the robot number, location, photos, contact history, and materials for insurance submission.
• It is for local delivery operators running roughly five to 30 robots without a dedicated incident manager.
• Insurance and the display of emergency contact information are already required, and liability boundaries are expected to become more specific, making cases harder to handle through call records alone.
• The first screen shows a “report new incident” button, plus the owner, next action, and deadline for cases currently being handled.

4. Charging and fault dispatch coordination

• This service receives reports of low batteries, stuck wheels, or lost connections, assigns a nearby on-site person to respond, and records parts replacements.
• It is for facilities-management companies at hospitals or large commercial facilities that use cleaning, patrol, and delivery robots from several manufacturers.
• As robot fleets grow, it becomes harder for manufacturer staff to visit every site directly, while charging and simple faults can be assigned locally.
• The first screen shows each building’s robot status as “operating,” “charging needed,” “stopped,” or “dispatch in progress,” with a button to contact the site.

What to check today

Call one apartment-complex management office that could potentially introduce delivery robots and ask questions for 20 minutes. Find out who handles entrance checks, resident notices, fault reports, and incident records when new equipment is introduced. If work passes through three or more people, or no single record remains, a building-by-building operations management service may be worth testing.

Why this matters where you are

The rules, insurance requirements, and local permits in this article are Korean, British, and Los Angeles examples, not universal requirements. You can check which local rules apply to robot access, insurance, operating records, and pedestrian access in your own market. You can also test whether buildings already pass robot-related work among several people without one shared record.