ready means two things in our FR5 handover draft

Both teams agree receipt comes first. Neither draft says how the request remains pending while access is unavailable.

Add that waiting state to the walkthrough. Identify who retains the request and who can cancel it. Otherwise a clear receipt message still leaves the next action undecided.

Walk it on paper. Delay the machine's answer halfway through.

Include the request reference on the paper exchange too. Two identical-looking requests can arrive at different times and still need different answers.

Walkthrough found the integrator expecting the CNC to cancel a request that the CNC considered still pending.

Who tells the operator that it is still pending? That is the screen they will be staring at while both suppliers explain why their own half is correct.

What did the integrator actually mean by cancel? Withdraw this request, or abandon the current part handover altogether?

Bruno, no clear operator indication yet. Ben, withdraw the request only, while retaining the unfinished handover.

Then give withdrawal an answer too. Sending cancel and assuming it happened recreates your first problem.

Ask the teams to include cancellation crossing with an availability response. They need to agree which state follows each order of events before the operator instructions can be written.

And don't restart that handover just because the request disappeared. You still need to know what happened to the part.

Draft now retains the handover identity through request withdrawal. Crossing responses go to a defined review state.

Does review state give the operator an action and a contact, or only another word to read? I would ask someone outside the design meeting to explain it back.

Are both teams signing that definition, Zara? A draft from one side won't settle the other side's retained state.

The ordinary-state agreement also needs the responsible safety review alongside it. Renaming area available must not turn it into permission to enter or move.

Ben, both teams are reviewing it. Bruno, operator wording and escalation remain unfinished. Safety review is scheduled separately; no implementation approval yet.