Standard 1: site readiness
The site should be mapped before launch so the rollout team knows where the robot can operate safely and where human intervention is still required.
- Confirm boundaries, access routes, and charging locations
- Identify slopes, obstacles, narrow passages, and high-traffic zones
- Document weather or surface conditions that change operating risk
- Decide which areas remain manual-only
Standard 2: operator onboarding
Operators should be trained on the workflow they will actually use, not just the product feature list.
- Review startup, shutdown, and daily checks
- Confirm how alerts, exception handling, and maintenance are reported
- Assign one named owner for support escalation
- Keep a short runbook that fits the team’s real operating rhythm
Standard 3: incident escalation
Every deployment needs a clear path for pausing, investigating, and resuming operations.
- Define who can pause the robot or fleet
- Define when human review is required
- Record the issue, time, site, and outcome
- Recheck the rollout plan before expanding to more areas
Launch rule
If the site cannot be described clearly enough for a human operator to manage it, it is not ready for autonomous rollout yet. The goal is controlled adoption, not unchecked automation.