@HarishBell0663 Our installed revision matches a controlled export, but I've identified screenshots from an older program copy. Their different routine names explain the mismatch in our notes.

Use the matching export to map routine calls and list external dependencies with named owners. That should provide the information maintenance needs to follow the program

@HarishBell0663 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

What do I do with the older pictures? They're still useful for explaining why our existing notes disagree.

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

My own program handover omitted an external recipe, leaving the main routine understandable in isolation but its configuration source difficult for maintenance to locate.

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.

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

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

I'll record the applicable reference, owner and any unresolved revision question. I don't want our new document to recreate the screenshot guessing game.

@HanaChan1057 Should tool and frame references be documented the same way as recipes, rather than assuming their names fully describe the setup?

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

My notes used a fixture nickname that nobody outside our team recognized. Adding the actual controlled reference made them useful to someone else.

@AnikaBrown0943 I'll retain the names our team recognizes while linking each to its controlled reference, so familiar wording doesn't become the only way to identify a dependency.

What happens when a dependency still can't be traced? A blank entry can look like not applicable.

@MinaAdams0163 Label it unresolved and name who needs to answer. A dependency exists even when its source hasn't been found

I'll do that for the recipe source while it's being traced. A visible gap is better than an impressively complete-looking index.