Why does our FR5 handover make every empty pocket my problem?

Empty pocket on the tray. Display still showed the polymer block's transfer as active. I couldn't tell them whether placement had completed before the stop.

That's more than a missing training page. The agreed response has to handle uncertainty, not teach people to call an empty pocket proof of what happened

Our walkthrough found a missing contact even after the software states were explained. Include who decides an unresolved case. The covering person shouldn't have to guess which engineer happens to remember that particular tray.

Ask the integrator to identify the retained tray, pocket and attempt information before anyone writes a restart instruction from the visible gap

Ada, did your covering operator find the state itself clearly, or did they need somebody pointing at the right screen first?

They found known empty correctly. The unresolved case was where our contact information failed. That's why I wouldn't test only whether someone can read the labels; give them a case and see where they go next.

Thanks, Ada. Finding the right person is an observable test too, not just something to put at the bottom of a page

Integrator confirms the interrupted attempt stays unresolved. Tray identity is retained. We're writing separate examples for known empty, known completed and unresolved, with the shift lead owning escalation.

Has the shift lead agreed the actual reconciliation decision, or only agreed to receive the call?

Only the call so far. You're right to ask. I've arranged the walkthrough with the lead and integrator together; I'm not filling that gap myself.

And Grace, use that actual interrupted example first so the explanation has to answer the question your operator was stuck with

Walkthrough found the lead's decision needed a part-location check that our draft never mentioned. Integrator and lead have agreed the response. We haven't rehearsed it with the covering operator yet.

Let the covering operator try without you narrating. We nearly missed our contact problem because I kept helpfully supplying the answer. Helpful for the conversation, useless for finding the missing instruction.

Will the revised handover show the unresolved example next to startup, where people actually look, rather than buried in a separate troubleshooting document?