Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Sometimes—but there is no blanket yes. A humanoid robot is suitable to work near people only when the specific robot, task, workspace and integrated safety measures have been assessed and validated for that use. Cameras, LiDAR, force control and a humanlike shape are not, by themselves, proof of safe collaboration.

What “safe to work alongside” actually depends on

Safety is a property of the complete application: the robot and its end effector, the work it performs, where people can enter, how the system detects hazards, how it responds, and the procedures used to operate and maintain it. A robot that may be appropriate in one layout or task may not be appropriate in another.

“Collaborative” does not simply mean humanoid, or that people may safely approach at any time. ISO describes collaborative operation in relation to the robot system and its operating conditions. ISO/TS 15066:2016 supplements ISO 10218-1 and ISO 10218-2 for collaborative industrial robot systems and their work environment. ISO says the specification was reviewed and confirmed in 2022 and remains current. Its scope does not automatically establish that every service or humanoid robot, or every use of one, is covered.

Standards and legal requirements are also different things. OSHA says there are currently no specific OSHA standards for the robotics industry; its robotics standards page lists consensus standards and guidance, and clarifies that national consensus standards are not OSHA regulations. In the United States, employers still need to address workplace hazards under the rules that apply to their operation. Which technical standard is relevant depends on the robot system, installation and intended use.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What sensors can—and cannot—tell you

Sensors can contribute to safety functions, such as detecting a person and triggering a slowdown or stop. But having a sensor is not the same as having a validated safety system. The important questions are whether the sensor and control path are suitable for the safety function, what area they actually cover, how quickly the system responds, how the robot stops, and what happens if a component fails or detection is blocked.

Technology or function Possible role What must be established
Camera, depth camera or LiDAR Perception or detection of people and objects; potentially an input to a safety function Whether the specific equipment and control system are suitable for the required safety function, plus detection coverage, response and failure behavior
Speed and separation monitoring (SSM) Monitors the distance between a person and robot and can slow or stop the robot as separation changes How the system detects people, the required separation, its response time and stopping behavior in the installed layout
Protective stop or monitored stop Brings the robot to a stop or monitors a stop under defined conditions Which conditions initiate the stop, how the stop is monitored, and how restart is controlled
Collision or low-obstacle sensor May detect certain contacts or obstacles, depending on its design and placement What it detects, what it does not detect, and whether its behavior is part of a validated safety function

Product feature lists illustrate why the distinction matters. Unitree lists a depth camera and 3D LiDAR for its G1. Its G1-D page lists LiDAR, depth cameras, physical collision sensors and low-obstacle detection sensors for the chassis configuration described there. Those specifications do not establish safety-rated performance or suitability for a particular shared workspace. Unitree also tells users to keep sufficient distance and use the robot carefully.

A sensor’s field of view, mounting position, occlusion, lighting or other operating conditions, and connection to the control system can affect what the complete application detects and how it reacts. Those characteristics need to be considered in the actual installation, rather than inferred from a product demonstration or the sensor name.

Why there is no universal “safe force” number

Power and force limiting (PFL) is one collaborative operating technique. It does not provide a single force threshold that makes every possible collision harmless. OSHA’s technical guidance says force, power and ergonomic parameters for force-limited robot systems are determined through risk assessment. Both transient contact and quasi-static contact—where a person may be pressed or trapped against an object—must be considered for the application.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The consequences of contact can change with the robot’s speed, the shape and stiffness of the robot or end effector, the body location struck, and whether nearby structures could trap a person. For that reason, a force value without the relevant body region, contact condition, measurement basis and tested configuration is not enough to judge a deployment. Do not treat a generic “safe force” figure as a guarantee.

SSM and PFL can be combined: a robot may operate faster while people are farther away and slow as they approach, with any potential contact remaining within the limits assessed for that application. That is a layered approach, not permission for unrestricted close contact.

Safeguards that belong in a deployment

The risk assessment should determine which safeguards are needed. Depending on the task and whether contact is expected, a system may combine:

  • Physical barriers, restricted zones or interlocked access to keep people out of hazardous areas.
  • Suitable, safety-related worker detection connected to validated control functions, such as safe speed, separation monitoring or protective stops.
  • Power and force limiting where the application has been assessed and validated for the relevant contacts.
  • End effectors and workpiece handling arrangements that account for sharp, rigid, heavy or otherwise hazardous contact surfaces.
  • Procedures for abnormal behavior, emergency response, maintenance and lockout of hazardous energy.
  • Training and supervision so workers understand operating boundaries, access controls and recovery procedures.

Warning lights and sounds can help communicate a robot’s state, but they supplement safeguards; they do not replace detection, guarding, stops or safe work procedures. OSHA’s Technical Manual discusses safety-related sensors and control logic, monitored and protective stops, and speed and separation monitoring as parts of robot safety. The right functions depend on the hazards and task.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What to request before people work beside a humanoid

Ask for evidence about the exact installed application, not just the robot model or a general product brochure. A useful review should cover:

  • The risk assessment for the actual task, layout and foreseeable ways people may approach or enter the work area.
  • The exact robot, software or firmware where relevant, end effector, payload and operating configuration being assessed.
  • Safety-function documentation, including limitations, detection coverage, response time, stopping behavior and how faults are handled.
  • Validation records for the safety functions and, if PFL is used, for force and pressure under the relevant contact conditions.
  • The design of guarding, restricted areas, interlocks and access control, along with how the system prevents an unsafe restart.
  • Instructions for maintenance, abnormal conditions, emergency response and recovery, plus worker training arrangements.

A claim that a robot meets or is “certified to” a standard should identify the model and configuration, the application and the relevant conformity assessment. ISO’s ISO 10218-1:2025 page describes safety requirements for industrial robots and points to ISO 10218-2:2025 for integration and applications. That industrial scope does not justify calling an unspecified humanoid deployment “ISO certified.”

What current evidence does—and does not—show

There is no named, broadly representative humanoid-worker injury-rate statistic or safety comparison established here. A May 27, 2026 announcement from Fraunhofer IPA describes an assessment program that includes functional-safety assessment and collision-force measurement with a force sensor. The stated test basis included a Unitree G1 EDU-4 with Dex3-1 hands and firmware 1.04. This is an example of configuration-specific testing work, not an injury-rate estimate or evidence that all humanoid robots have passed such an assessment.

For worker-safety information and ongoing research, NIOSH’s Center for Occupational Robotics Research focuses on people who use, wear or work near robots. Its work is relevant context, but it does not substitute for an assessment of the particular robot cell and task.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.