Identity
Model, serial, configuration, software, accessories and labels.
Sample · adapt to the contract
Define what “tested” means before the robot is built.
This generic checklist is not sufficient for every robot or regulated application. A project-specific protocol should follow the signed specification and risk assessment.
Sample record · CRS-FAT-DEMOTemplate only
Condition
Assembly, finish, damage, connectors, wheels, joints and packaging.
Safety controls
Emergency stop, limits, alarms, manual modes and recovery.
Core function
Motion, charging, sensors, navigation or task sequence.
Interfaces
API, network, doors, elevators, fleet or tool integration.
Release
Deviations, correction, re-test, documents and packing evidence.
Release rule
Each check records unit identity, method, expected result, actual result, evidence link, deviation and disposition. A “pass” applies only to the tested scope and date.