@ReeceBaker0471 I tried that in a discussion. Several people read the same restart line differently. So yes, we've handed over an instruction that doesn't agree with itself.

Rewrite that line around the visible condition, permitted next step and when to call for help. Have the responsible integrator check it, then repeat the teach-back without prompting

@ReeceBaker0471 How do I stop teach-back feeling like a test of the operator? The wording was mine. I don't want to make that their failure.

On my setup, I asked people to find where my guide forced them to guess. That invited corrections instead of making them defend a wrong answer

A clear recovery sheet should stop those calls. Keep the steps short and put it by the controls

@ReeceBaker0471 Not if the system can't tell them what's physically happening. Better wording can't create a recovery path for an unknown held-workpiece state.

You're right; I promised too much from a sheet. The guide should support defined recoveries and clearly escalate unknown states. Some calls are the correct outcome

Our original handover only showed an empty gripper at startup. It never covered an interruption with the workpiece still held. That's a real gap.

@AnilChan1071 I'm wondering whether selecting the current pocket would allow recovery. Does the held-workpiece case mean a pocket number alone can't explain what should happen?

The pocket number alone doesn't establish the tool and destination conditions. Your integrator needs to define how those are confirmed and which recovery, if any, is permitted

@ReeceBaker0471 My setup had developed an informal habit of consulting whoever knew how to edit the index. A defined escalation route helped us identify uncertainty that the workaround had concealed

An operator also spotted that our screen and printed guide use different names for the same step. I wrote both. Lovely bit of self-sabotage.

We've found a wording problem, but the reviewed recovery guidance isn't ready. I still need to support the team through the unclear cases.

You've found something specific to improve. Keeping support available fits the unfinished guidance