Before a robot pilot begins, decide who owns the exclusions

A pilot price is not a complete delivery boundary

A provider proposal can name the robot, trial duration and price while leaving the hardest delivery questions unanswered. Who supplies the parts used in the trial? Who makes an upstream machine available? Is network access included? Who decides whether a changed product or operating condition calls for a new test? Write those answers into one versioned boundary record before treating price and timing as settled.

The record should name the configured system, included work, exclusions, operator inputs and authority to approve a change. It is an operational method, not a contract template or safety sign-off. Qualified legal, engineering and site-safety owners still need to review the actual project.

Begin with the complete application

For an industrial robot cell, list the robot, tool, guarding, conveyors, controls, utilities, data links and test environment. Another robot class will have a different system boundary. If a working element comes from the operator or another integrator, identify that party rather than leaving the interface implied.

ISO 10218-2:2025 covers integration of industrial robot applications and cells through design, commissioning, operation and maintenance. Its public scope does not assign the commercial responsibilities in a buyer's contract or certify a deployment. It does make one distinction useful here: a quote for a robot unit is not a complete integration plan. Safe Work Australia's plant-design guide likewise calls for design information, intended use, limits and conditions for safe commissioning to reach the end user. Its examples include production rate, cycle time, environment and interfaces. These are general plant materials; applicable law and standards depend on the site and application.

Treat an exclusion as an allocation question

An exclusion is useful only when it explains what is outside this provider's work, who will provide or decide it, and what happens if it is unavailable. 'Conveyor integration excluded' leaves a gap if the acceptance test needs that conveyor. 'Operator to supply samples' leaves a gap if no one has agreed which variants and quantities represent the work.

• Name the item or condition using the same terms as the work brief and proposal.
• Mark it included, excluded or unresolved; name the responsible organisation and decision owner.
• Set the date or event when the input is needed and the consequence if it is absent.
• Link the evidence that will close the item, including any changed acceptance test.

Record the operator inputs, not just provider deliverables

Depending on the task, the operator may need to supply access windows, floor space, power, network permissions, representative products, staff time or site approvals. Assign each input an owner and due date. Do not apply a universal checklist without checking the proposed configuration and work.

A commercial exclusion cannot remove a statutory safety duty. Safe Work Australia's plant risk code describes commissioning checks against specified requirements under actual site conditions. If an excluded interface is necessary for safe commissioning or for the agreed acceptance test, that boundary remains unresolved until the responsible parties address it. A completed row is not evidence that equipment is safe or suitable.

Decide how a change reaches the baseline

Pilots change shape. The operator adds another part type, the provider proposes a different gripper, or the site asks for a new shift pattern. Each could alter price, timing, interfaces, safety assumptions or the meaning of the original result. Give a proposed change an identifier linked to the original scope version. Record affected configuration and tests, expected cost and schedule effect, technical or safety review, approvers and decision date. Keep it open while those facts are unknown.

ISO 10007:2017 configuration-management guidance describes authorities, baselines, change control and status records. NASA's systems engineering handbook uses a propose, evaluate and approve sequence in its own programmes. These are useful process analogies, not a legal clause for a private robotics pilot. Australian Government contract guidance illustrates documented variation approvals and authorised delegates, but private parties need their own contractual advice; a written process cannot guarantee that every dispute is prevented.

A small example and the next decision

Suppose a hypothetical pick-and-place pilot covers one configured cell and three agreed product variants. The operator will provide products, utilities and access on named dates. An upstream conveyor interface is excluded pending a separate integrator scope. The boundary record should state whether the site test can proceed without it and what evidence would be missing.

Halfway through, the operator requests a fourth variant. The first result does not establish performance for that variant. The parties can record the engineering and safety effects, revise the test set and decide cost, timing and approval before extending the original promise. Ask for the versioned record before agreement and again before the test; distinguish a provider statement, buyer-witnessed result and unresolved exception.

RobotAtom's trust model records provider scope, assumptions, exclusions and operator inputs before a pilot and links acceptance to evidence. This method shows what a buyer can ask that record to contain. For cross-border diligence, use the separate overseas supplier assessment. None of these records replaces qualified site, safety or legal judgement.