A robot's reach rating is not its usable workspace

Maximum reach answers a narrower question

A robot's published maximum reach is a characteristic of a robot model under the manufacturer's stated conditions. It does not establish that the configured tool can reach every required position and orientation, follow the required path or clear the workcell without a collision.

The buying question is therefore not simply whether a point falls inside a catalogue radius. It is whether the exact robot, mounting, tool, workpiece and cell can complete every material task pose and motion while respecting joint, clearance, process and safety constraints.

Describe task poses, not dots on a drawing

Two targets at the same distance from the robot base can present different problems when the tool orientation, approach direction or surrounding geometry changes. A reach requirement should preserve those differences instead of reducing the work to a single farthest-point measurement.

• State the tool-centre-point position and orientation for each pickup, process, inspection, hand-off and placement state.
• Define the coordinate frame, tolerance and permitted alternatives so that 'reachable' has an inspectable meaning.
• Include approach, process, exit and recovery paths rather than checking only the final target.
• Cover representative object variants, machine states, fixture positions and tool states that materially change access.
• Separate confirmed geometry from estimates, allowances and unknowns, with an owner and source date for each input.

Model the complete configured geometry

ISO 10218-2:2025 covers integration of industrial robot applications and cells, including design, integration and commissioning. Its public scope supports treating the application as an integrated system, but it does not provide a public universal reach-calculation method or verify a particular layout.

• Identify the exact robot and controller variant, software version, mounting orientation, base location and pedestal, rail or other positioning equipment.
• Model the full end effector, adapters, hoses, cables, sensors and held object—not only a tool-centre-point marker.
• Use controlled revisions of fixtures, machines, conveyors, guarding, posts, doors and other nearby structures.
• Represent restricted and safety-related zones separately from ordinary collision geometry and record who owns each boundary.
• Include payload and tool data as configuration inputs, while keeping mass, inertia and process-capability questions in their own evidence checks.

Check the complete motion and robot configuration

Universal Robots distinguishes a recommended reach region from a larger maximum working area and says some positions near the outer limit restrict tool orientation. Its guidance also describes inner-workspace and wrist-alignment singularities that can make poses or motion problematic. These are first-party explanations for UR kinematics, not independently verified rules for every robot arm.

The practical requirement is to check every relevant pose and path for joint travel, joint configuration changes, singularities, self-collision, cell collision and near misses. A reachable endpoint does not rescue an impossible approach, an obstructed wrist motion or a recovery path that leaves the allowed space.

Require inspectable simulation evidence

FANUC says ROBOGUIDE can evaluate reach, payload, motion paths and cycle time using a workcell with the selected robot and controller, tooling, fixtures, safety zones, conveyors and parts. ABB's RobotStudio manual documents reachability, collision and user-configured near-miss checks. These are manufacturer descriptions of their software and recommended workflows; neither independently assures that a buyer's cell will perform as simulated.

• Record the software, robot and controller versions, source CAD revisions, frames, tool data, target definitions, path types and configuration assumptions.
• Retain unreachable targets, joint-limit warnings, collision and near-miss results, exceptions and unresolved risks—not only favourable screenshots.
• Define a project-specific clearance rule and its owner; do not infer a universal margin from a simulation tool's default settings.
• Make the model and result reviewable by the buyer or qualified integrator, including changes made to obtain a pass.
• Keep reachability, collision checking, cycle estimation, safety design and compliance as distinct conclusions with distinct evidence.

Confirm the installed cell

Before acceptance, freeze the robot, controller, software, mounting, tool, load, fixtures, target frames, programs, zones and measurement method. Confirm calibration and frames, then exercise representative approach, process, exit and recovery motions using the installed geometry and agreed object variants.

Record actual clearances, warnings, stops, interventions, deviations and any target or path altered after simulation. A successful digital check remains design evidence; installed-cell evidence is needed for the installed configuration and does not by itself establish production capability or application safety.

Reopen the decision when geometry changes

• Review affected poses and paths after a change to the robot, base, mounting, tool, adapter, cable routing, object, fixture, machine, guarding or restricted zone.
• Recheck the evidence after controller, software, program, frame, calibration or motion-setting changes that can alter the result.
• Preserve the earlier model and acceptance record as evidence for the old configuration rather than silently carrying its conclusion forward.
• Route unresolved reach, clearance, safety or process questions to the responsible engineering, integration and safety owners.

Keep every claim inside its evidence boundary

ISO is authoritative for the published scope and status cited here. Universal Robots, FANUC and ABB are authoritative for their own published product guidance and software claims; those statements remain manufacturer evidence until the proposed configuration is reviewed and tested under the buyer's conditions.

RobotAtom records task poses, configuration, assumptions, source dates, evidence type, unknowns and required validation. It does not certify reachability, cell safety, integration quality, process capability or regulatory compliance. Qualified engineering, integration and safety owners must decide what applies and whether the evidence is sufficient for the actual application.