Start with one actual example the operators brought you. Record what they could see and what you knew that they did not; that often reveals a hidden state assumption more clearly than writing another page of startup instructions.

For an empty pocket I inspect the tray and decide whether it was intentionally left empty. That reason isn't on the screen or the job sheet.

Then the operator lacks evidence, not willingness. The process owner needs to define how intentional empties are identified and what to do when that cannot be established.

Process owner is defining the empty-pocket record. For interrupted transfers, we still need an approved way to reconcile the held block and destination, not just restore the saved index.

Keep those two situations separate in the draft. A known intentional empty can have a defined route, while an uncertain interrupted transfer may need a hold and escalation. Do not teach the same skip action for both merely because the next visible pocket looks empty.

Separated them, with the shift lead named for escalation. Draft and recovery review are unfinished; I haven't told operators the new sheet authorises actions that were never agreed.