Submit the exact product revision, preserve its evidence and ask the responsible reviewer to decide.
Product Engineer selects the intended item and prepares the design basis. Confirm the product code and name against the source so similar labels cannot send the file to the wrong product. Resolve any identity disagreement before submitting work to the reviewer.
Product Engineer submits the file with its revision, document type and responsible reviewer. The design action validates the linked product and reviewer against attributed source evidence. A repeated product, revision and document-type identity receives a reasoned refusal.
Engineering Reviewer examines the immutable submitted evidence and approves the design basis or requests a supported correction. Identify the actual reviewer decision when explaining the outcome; the assigned reviewer's name is only part of the review context.
Product Engineer follows the supported correction path and appends attributed successor evidence. Preserve the original submission and explain why the successor was necessary. The reviewer needs to retrieve both when comparing the corrected basis.
Product Engineer supplies the reviewed context for the engineering change. Ask Production Planner to identify the intended manufacturing instructions before affected work is released. Resolve conflicting interpretations with Engineering Reviewer while the source evidence is available.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.