We have only the main-routine pictures at present. No export in the handover folder, and I cannot tell which revision the images show.

I'd sit with the integrator and trace one call out of the main routine. Cheap first check. It should reveal whether the missing material is merely absent from your folder or also unclear to the person handing it over.

Include external inspection recipes. The robot project may call data stored somewhere else.

Nora, I would keep an operator summary linked to the technical record. People need the right fixture, expected sequence and escalation, not every subprogram on the start screen; maintenance still needs the dependencies behind those instructions.

Our quick guide once named a routine nobody had. The link needs checking, not just printing.

Leo, exactly, and a filename isn't an explanation of what the called routine expects from the fixture or ordinary PLC signals, even when the file does exist

We have agreed separate operator guidance and a linked technical index. In the walkthrough, the integrator confirmed the screenshots show an older revision; the current project also calls an external inspection recipe.

Keep the old pictures identified as historical rather than silently replacing them, Clara, because someone may already be using a printed copy and needs to know why it differs from the current screen

Does the proposed export include the current called routines and the recipe reference, with a named owner for each item outside the robot project?

I would have both controls owners walk through an ordinary inspection and an interruption against the current revision. That can expose a dependency list which is complete as a list but still unclear about what the signals mean.

Caleb, how much interruption detail would you put in the operator summary before it becomes another technical manual?

The recognisable condition, permitted action and escalation point, Nora, with uncertainty left explicit. The reasoning and evidence requirements belong in the supporting procedure. I wouldn't use a shorter page as an excuse to omit the difficult decision entirely.

Anil, the export has current subprograms and an external recipe reference, but the recipe file itself is still missing. Isabel, the joint interface walkthrough is scheduled, not completed.

Then the archive is received, not complete for this job. Keep that recipe gap visible.

The recipe owner has now supplied the identified file. We haven't checked that the maintainer can retrieve the complete set from their normal account, so I am not closing the handover.

That retrieval check would have caught our broken link before night shift did. Worth doing.

And keep the fixture assumptions in that final check, because opening all the right files still doesn't establish which installed coupon fixture the instructions describe