Homes and service work
Service robots and the work that remains around each task
Compare reception, delivery and cleaning systems through their handoffs, building access and remaining staff workload.
A service robot's job should be described as an outcome for a person or an operation. A visitor reaches the right desk, a meal reaches the collection point or a floor meets the agreed cleaning standard. A screen responding to a request or a vehicle completing a route does not settle that outcome.
IFR groups service robots by personal and professional use. Its definition covers several physical designs and degrees of autonomy. It also explains that medical robots form a separate category in the ISO vocabulary, even though its statistical reports may group them differently. [1]
Write down where the robot's responsibility ends
In an illustrative hotel delivery, a person prepares an order, loads a carrier and selects a destination. The carrier travels to a floor and notifies a recipient. Someone still needs to collect the order. Each transition can introduce a wait or an exception.
For reception, define what happens when a visitor's request cannot be resolved. For cleaning, define who handles an inaccessible corner or services the equipment. A complete specification names these handoffs rather than assuming that one robot performs every surrounding activity.
Scroll sideways for all columns.
| Task | A useful completion condition | Remaining work to measure |
|---|---|---|
| Reception and guidance | Visitor reaches the intended service or staff member | Unrecognized requests, language support and escalation |
| Indoor delivery | Correct item is accepted at the agreed point | Preparation, loading, access and collection |
| Floor cleaning | Required accessible area passes the agreed inspection | Preparation, edges, consumables and equipment care |
Doors and lifts belong in the workflow
A building route should be assessed with its ordinary access arrangements. An open corridor during a presentation leaves closed doors, access controls and lift queues untested. List which interfaces the supplier actually provides and which actions staff perform.
Use an approved test route and retain a timestamp for each wait. This can distinguish travel delays from access delays. It also prevents a building integration problem from being mistaken for an inability to navigate.
A service trial should preserve accessible passage for visitors and staff. Plan where a stopped machine can wait and who is responsible for recovering it. The robot's presence must be included in the site's own operating and risk review.
Calculate staff time across the complete service
Consider a hypothetical delivery that previously required eight minutes of staff work. With a robot, preparation and loading take two minutes, the handoff takes one and the averaged exception workload adds another minute. Remaining staff work is four minutes per delivery under those assumptions.
For 40 deliveries, the arithmetic difference is 160 minutes. This is not a staffing reduction forecast. It does not establish that the saved intervals occur together or can be reassigned to another job. Record when the work happens and what staff can actually do during the robot's travel.
Also record elapsed customer waiting time. A process may reduce staff walking while making a recipient wait longer. Both measures belong in the evaluation.
Keep the proposed function within its evidence
A product's speech interface should be tested separately from its physical task. A device acknowledging a cleaning request does not prove it cleaned the specified area. Ask for the task log or physical inspection that confirms the result.
For an initial trial, select a small set of ordinary requests and retain every outcome. Classify completion, staff handoff and unresolved requests without deleting the difficult cases from the denominator.
The specialist guides below examine homes, cleaning and restaurant transport in more detail. Their acceptance conditions differ because the physical work differs. A shared service-robot label should not be used as evidence that one system can take another's place.
Sources and scope
Sources were consulted for this revision. Manufacturer descriptions are identified in the text. Worked examples are illustrative calculations, not measurements from a TechniaHQRobot test.
- IFR service robot definitions and statistical scope
Personal and professional service categories, autonomy and the distinction between terminology and report groupings. Workflow examples here are illustrative.