A good demonstration leaves you with a clearer understanding of the machine. Ask the organiser to show a task that matters to you, explain the operating method and keep a record of what happens. A short success clip can introduce a product; an observed session can answer buying questions.

Before the session

Name the task and an observable result. “Be useful in my home” is difficult to assess. “Move this bottle from the table to the tray without spilling it” can be observed. Confirm the exact robot edition, hardware accessories and software version, and whether that configuration is the one you would receive.

  • Ask which steps are autonomous, scripted or remotely operated.
  • Agree who will operate the machine and when they may intervene.
  • List required connectivity, markers, maps or preparation.
  • Ask whether the task uses released software or a development feature.
  • Agree the safe operating space and the manufacturer’s handling instructions.

Watch several attempts

Record the number of attempts, completed tasks, interventions, resets and the time each attempt takes. A failed attempt is useful information when you understand why it failed and how the operator recovered. Keep the denominator: three successes out of three attempts means something different from three selected successes out of twenty.

Ask the supplier to vary one ordinary condition within the agreed safe test: object position, a permitted obstacle or the wording of a command. Observe whether the system completes the task, asks for help or stops. Do not create surprise hazards or exceed the manufacturer’s operating instructions to make a point.

Separate the layers

A machine can understand a request but be unable to execute it. It can follow a route while choosing the wrong destination. It can perform a movement under teleoperation without having autonomous perception. Write down which layer the demonstration actually exercises.

The 9jaBots task benchmark illustrates the separation between interpreting a command and carrying it out. The navigation lab checks routes in a simplified grid. These teaching tools explain the distinction; their scores do not predict a physical robot’s performance.

After the session

Ask for the exact included capability list, setup requirements and the person responsible for support. A feature shown in a development build may have a different release schedule from the product you are offered. If a home robot uses remote assistance, discuss how sessions are authorised and how household information is handled.

Keep a simple record: date, configuration, task, operating mode, attempts, results, interventions and unresolved questions. This becomes a useful basis for a pilot acceptance plan or supplier comparison.

Apply it to an enquiry

Bring the task and your questions to 9jaRobotics. Demonstration arrangements depend on supplier and model availability. For permissioned human demonstrations you want to label yourself, open the task studio and keep the source video alongside its annotations.

Source context reviewed 10 September 2026: Unitree’s G1 capability and operating notes and 1X’s description of NEO autonomy and remote assistance. The checklist is an editorial evaluation method, not a product certification.

Bring people into the project

Use 9jaTesters to request collection, annotation, testing or human review. Describe the task, volume, location or languages, and acceptance criteria in your brief. For contributor opportunities, join the 9jaTesters workforce.