The compliance gap between a demo and a deployment
The distance from “it works on stage” to “it is legal on your floor”.
The first 30 days after a robot lands on site
Commissioning, staff and exceptions — the month that sets the ROI.
The first month after a robot arrives decides more about the year’s numbers than the twelve that follow it.
The month that decides the year
Commissioning, staff training and the discovery of every edge case a site’s floor plan produces all happen inside the first thirty days — and each one either gets resolved quickly or becomes a recurring drag on uptime for the rest of the contract.
A slow first month rarely announces itself as a crisis. It shows up later as a payback period that keeps slipping, one small unresolved exception at a time.
“The pilot ends the day staff stop asking whether the robot will be there tomorrow.”
A robot’s first exceptions are rarely about the machine — they are about everything around it.
Staff, exceptions, edge cases
Staff need to trust a new routine before they stop working around it, and that trust is built in week one or not at all. Edge cases — a doorway the robot cannot judge, a shift change it was not scheduled for — surface fast on a real floor and slowly in a demo.
Each exception resolved in month one saves a repeat of the same call in month six. Each one left unresolved becomes the reason staff quietly route around the robot instead of relying on it.
WHAT TO TAKE AWAY
Commissioning, staff training and edge-case discovery all happen in the first thirty days — plan for it.
An unresolved exception in week one becomes a recurring drag on uptime by month three.
Staff trust is built early or not at all — a slow first month is rarely recovered quietly.
The real milestone is not the install date. It is the point staff stop treating the robot as new.
The line between a pilot and a standing part of operations is crossed in the first month, not decided in advance.
From install to standing order
A site that treats month one as a structured commissioning period — with a named contact, a punch list and a scheduled review — crosses into standing operation with far less friction than one that treats the install as the finish line.
By the end of the month, the honest question is not whether the robot works. It is whether the site has stopped noticing it as new.
EDITORIAL RULE
Sourced or silent. Every figure on this page carries an attributed, dated source. Where we could not source a number, we left it out rather than estimate it.
SOURCES
- 01Site commissioning logs2025–2026
- 02Operator interviewsEurope · Q1 2026
- 03Manufacturer service SLAs2026
- 04N.O.N. Humanoid vetting notesFactory audits · 2026
A QUESTION
One person answers — from the first email to the room.
EMAIL
WECHAT
nh_alliance
LINKEDIN
