Choose a task with a real operational reason
Start by observing the work. Identify repetitive trips, predictable routines, bottlenecks and points where staff are already waiting. Describe the task in plain terms: what is moved or handled, between which locations, how often, under what conditions and what counts as completion? Also record exceptions. If a task changes constantly or relies on human judgement, automation may be a poor fit.
Selection should compare documented capability with actual conditions. A demonstration in an empty room cannot establish suitability for a fully occupied restaurant. Ask for the operating boundaries, supported surfaces, payload details, sensor and connectivity requirements, accessibility considerations and limitations in writing. A site visit or pilot should involve the people who do the work.
Check the property and its interfaces
Map routes, turning space, thresholds, floor surfaces, guest traffic, restricted areas and charging locations. Consider doors, elevators, access controls, kitchen systems and network coverage. If a workflow crosses floors, establish how the elevator connection is supported and authorized. Do not assume that any device can operate doors or lifts without compatible equipment and an agreed safety procedure.
Network and system integration deserve a clear owner. Find out what connection is required, which services exchange information, what happens if connectivity drops and how software updates are managed. Limit access appropriately and request privacy and security documentation. Understand whether sensors capture images, audio, location or other data, where it is processed, who can access it and how long it is retained.
Train the team and communicate with guests
Staff training should cover safe operation, stopping and restarting, exceptions, cleaning, charging, maintenance escalation and guest questions. It should also name who owns the task on each shift. A robot that nobody is assigned to monitor is less an autonomous colleague than a surprisingly expensive mystery.
Tell guests what to expect in clear, modest language. Explain when a robot is operating, how they can pass or ask for help, and which staff member can assist. Consider accessible routes, audible or visual alerts, turning space and the consequences of a unit stopping in a busy area. Test with people who use the space in different ways.
Plan safety, support and upkeep
Work with the supplier and relevant local professionals to review risks, operating procedures and the equipment's safety documentation. Define permitted areas, supervision, emergency response, housekeeping around the charging station and how incidents or near misses are reported. Do not rely on a generic feature list as a substitute for a property-specific risk assessment.
Maintenance planning should describe preventive service, support hours, response arrangements, replacement parts, software updates, consumables and downtime. Confirm what the site team may safely clean or inspect and what must be handled by qualified service personnel. Retain an alternative workflow so guest service continues if the unit is unavailable.
Consider the total cost of ownership
Purchase price or lease payments are only one part of the cost. Include installation, integration, staff training, maintenance, consumables, charging, software fees where applicable, downtime, replacement parts and ongoing support. The balance depends on the agreement and the site. Ask vendors to state inclusions, exclusions, renewal terms and service assumptions; do not rely on a single headline figure.
Compare vendor proposals using documented capabilities, compatibility with your site, service availability, maintenance arrangements, warranty terms, privacy and safety documentation, and realistic pilot results. Check which tasks are excluded and whether the supplier can support your location. Avoid accepting unsubstantiated efficiency or return-on-investment promises.
A practical implementation checklist
Assess: Document the task, current steps, exceptions and people affected. Select: Match a system to the route, workload and intended use. Integrate: Confirm doors, elevators, network, layout, charging and data flows. Train: Assign owners and teach routine and exception handling. Review: Track interruptions, maintenance, staff effort, guest feedback and all operating costs against a baseline.
Keep the pilot bounded and agree in advance what would justify continuing, changing or stopping it. A compact hotel in Helsinki and a large property in Singapore will encounter different access, traffic and service patterns. Use evidence from your own operating environment. The point is not to prove that robotics always works; it is to find out whether a specific tool supports a specific job without making the rest of the operation harder.