everyone can press start, then the first empty pocket brings me back

Empty pocket. Then a restart where the screen points to a pocket but the operator isn't sure whether the block was already moved. Different problems, currently the same phone call.

Don't let the unsure case offer a confident next-pocket button.

It does offer resume with a highlighted pocket. I've asked controls to review that before we teach it as a recovery route.

Does the screen identify the tray as well as the pocket? A correct pocket number on a replacement tray would still send the operator looking at the wrong physical state.

Good question. Have the operator describe what they think that highlight means, without prompting them. You may find they're taking it as confirmation of a physical part position rather than saved program progress.

We did a paper walkthrough before changing our training screen, with one person describing the actual tray and another the saved state; cheap way to find which decisions the interface was leaving to guesswork.

Operator thought the highlight meant the system had checked that pocket. It hasn't. Controls is adding a visibly unresolved recovery state when physical and saved progress aren't established.

Who do they call from that state?

Shift lead, then maintenance if reconciliation needs it. The lead is helping write that route. We are not asking operators to choose which saved state looks most likely.

Will a cover operator be able to find that contact when the usual lead is away? The recovery instruction needs a working escalation route, not only a familiar person's name.

And let the cover operator try the draft without you translating it; if the instructions work only with their author standing beside them, the phone calls aren't going anywhere.

Backup contact added. Controls review and a cover-operator walkthrough still to do. Thanks, Jane, for challenging the highlight; I had stopped noticing what it seemed to promise.