Acceptance — the list before the truck

Worked through at the device, by a person, with the device switched on. Not from memory and not from a build report.

Function

Check	Expected
Power on, hands off	our application appears, no desktop at any moment
Pull the plug during operation, plug back in	comes up again, no dialogue, no lost configuration
Every screen edge swiped	no system bar, no notifications
Application killed	restarts by itself
Drive a tour with two stops	reaches both, log clean
Emergency stop pressed	device stops, page shows it, release works
Charging run	finds the station, docks, charges
Language switch	all six surface languages, nothing falls out of the layout
Technician page over the network	reachable, password required
Sound and face	as configured, not the default image

Fleet, if the site has more than one device

Check	Expected
All devices report	members = number of devices, on every device
One master	the same serial number everywhere
Nobody on "alone"	—
Discarded packets	zero
Two devices to the same point	one waits or gives way; no contact

The acceptance rule is the CEO's and has no tolerance: the fleet test passes only if the robots do not collide with each other. "Almost" does not count.

Data hygiene before packing

Check	Expected
Map archive	only maps of the receiving customer
Tour history	test tours removed
Log	no other customer's name in it
Accounts	no internal account left on the device
Cloud assignment	correct customer node
Reset secret	in the password manager, tied to the serial number

Papers

Serial number, certificate expiry, customer node, fleet key set yes/no, software version, date, name of the technician. One page, and it stays with us — the customer gets the handover protocol, not our internal sheet.