Key takeaways
- Exception work is any human step the robot did not finish without help.
- Blocked routes and failed handoffs look like small delays but stack across shifts.
- Remapping after layout changes should count as exception labor in ROI models.
- A simple ticket taxonomy makes hidden minutes visible to finance.
- Maintenance included rental still needs exception logging to judge fit.
What are robot exceptions in plain language?
Most ROI decks count autonomous hours and call the project a win. On the floor, staff still free stuck wheels, finish corners, reboot after network blips, and escort units through crowded doors.
The direct answer: a robot exception is any task a human completes because the robot stopped, skipped, or needed a rescue. Those minutes are labor. They rarely appear in the spreadsheet that justified the purchase.
If you cannot name your top five exception types, you cannot know whether robot rental monthly is cheaper than the shifts it replaced.
Why do blocked routes dominate exception time?
A pallet left in an AMR lane for ten minutes can trigger three human touches: move the pallet, reset the robot, and explain the delay to the next shift.
Cleaning robots hit chairs, caution tape, and pop up displays that were not on yesterday's map. Each stop sends a porter or lead with a key fob.
Delivery robots lose more time to elevator holds than to motor faults. The exception is waiting, not repairing.
How do failed handoffs show up in labor?
Handoffs fail when the robot arrives but the human receiver is not ready, the bin is full, or the badge reader rejects the cart.
Kitchen and housekeeping teams often absorb those minutes as part of the job instead of logging them against the robot program.
Professional service robot fleets keep growing, with IFR reporting more than 205,000 professional units registered in 2023. More sites mean more handoff variance unless someone tracks it.
When does remapping count as exception labor?
Layout changes after a remodel, a seasonal display, or a new dock door are normal. The robot treats them as exceptions until someone updates the map.
Integrator remapping is billable work for many contracts. Internal labor for escorting mappers through live floors is also real cost.
Budget remapping hours the same way you budget deep cleaning after a flood. It is not a failure, but it is not free autonomy either.
What about manual finishing after a run?
Autonomous scrubbers may leave edges, low obstacles, or tight restrooms for human staff. That finishing work is exception labor if the robot was sold as full coverage.
Compare finished square footage to promised square footage, not to machine runtime alone.
Spot checks with photos beat arguments about whether the robot did enough.
- Log missed zones with photo and ticket ID.
- Record minutes to mop edges after each run.
- Note chemical changes that force manual prep.
- Track repeat misses on the same corner.
How should night crews log rescues?
Give night staff a single exception form on paper or in the work order system. Fields: robot ID, location, exception type, minutes spent, root cause.
Rescue drills belong in training, but unplanned rescues belong in the log. Remote triage that ends with a human visit still counts.
Review logs weekly with operations and finance. Patterns beat anecdotes.
How do you monetize exception minutes?
Multiply logged minutes by fully loaded hourly cost for the role that performed the rescue. Use the same burden rate you use for janitorial or warehouse labor studies.
Divide monthly exception labor by completed tasks or scrubbed area to get a hidden cost per unit of work.
Compare that figure to robot rental monthly and maintenance included fees. Surprises usually live in the numerator, not the invoice.
Which KPIs expose exception drift?
Track exceptions per hundred autonomous hours, not only faults per month.
Watch mean time to human recovery after a stop command.
Measure repeat exceptions on the same map segment after a remap claim.
Compare exception rates between buildings in the same chain. Shared playbooks reduce variance.
How do contracts and SLAs hide exceptions?
Uptime clauses can ignore minutes spent finishing floors or resetting carts as long as the motor spun.
Ask vendors how they define a completed task versus a completed run.
Robot leasing for business should attach an exception appendix with who logs data and who reviews it monthly.
Pilot programs should publish exception totals beside autonomous hours in the final readout. Otherwise leadership approves scale up on incomplete math.
What belongs in a simple exception taxonomy?
Start with six codes: blocked path, failed handoff, remap required, manual finish, network or software reset, and safety stop with human clear.
Add subcodes only after thirty days of data. Too many codes on day one kills compliance.
Align codes with the fleet portal fault names where possible so logs and telemetry reconcile.
Where does Service Robot Co. fit exception tracking?
We build exception logging into handoff training and monthly reviews, not as an afterthought once ROI looks soft.
Deployment, mapping, and nationwide service sit with the same partner that signs the taxonomy appendix. A free site assessment can list the exception types your layout will trigger before go live.
