@LinBell0618 I've matched our installed revision to an export. Some screenshots belong to an older copy, though. That explains the names that weren't lining up

@RosaCarter0988 Build a call map from that export and list external dependencies with their owners. That should give maintenance what it needs to follow the program.

Follow the program, maybe. Recover an interrupted job, no. A call map doesn't establish where restarting is valid.

Fair distinction. I meant understanding the dependencies, not choosing a restart point. Recovery needs its own approved reference from the responsible integrator.

Should I retain the older screenshots as historical context? They help explain the conflicting routine names in our current handover folder

Keep them clearly marked historical and separate from the current explanation. Attach the known revision link where you've it.

On my handover, the missing dependency was an external recipe. The main routine made sense, but nobody could find what supplied its choices

Our export references an external recipe too. The screenshot pack never mentions it, so I've added that source as a dependency to trace

Would you paste the recipe values into the handover? Having everything in one file sounds easier

@PriyaChen1177 Link the controlled source and name its owner. Copying values into prose creates another place that can become stale.

Make the link specific enough to identify the applicable revision. A folder full of recipes isn't much of a reference.

Our dependency entry will identify the relevant controlled reference and owner, with unresolved revision details marked explicitly instead of left for the reader to infer

Same treatment for tool and frame names? I can read those names, but wouldn't know what they guarantee

Yes. Describe the role and link the approved setup reference. Don't reconstruct coordinates or setup values from what a screenshot appears to imply.

I've settled the handover structure: start from the matching export, map dependencies and identify their owners. I'll count it operationally ready only after the responsible integrator verifies the references, including recovery

@RosaCarter0988 That structure gives the handover a traceable starting point, with readiness still tied to the integrator's verification.