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.

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

@JamieBrown0904 You're right to limit my wording. The map supports understanding the program; recovery instructions must come from the responsible integrator's approved procedure, not from inferred call order.

@MiaAllen0296 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.

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