Rework needs its own reason, return step and authorization while preserving the item's original route.
Index
An item sent back to an earlier operation follows a different path from an accepted batch; hiding that return distorts timing and consumption.
The rule that changes the scope
Rework needs its own reason, return step and authorization while preserving the item's original route.
An ERP may record additional work; a custom module helps when exception routes vary by defect and product revision.
The additional route should not be represented as a new saleable item. Retain physical identity and associate corrective work entries with it. Bring defects that return to different operations when commissioning the module; the easy case of always returning to one bench does not prove the full rule. Also define how an item that cannot be corrected leaves the route without creating an approval that never occurred.
Specify operational deliverables
- Link the item or subassembly to the point where the deviation was identified.
- Separate normal-route consumption from material used during corrective work.
- Record the release criterion after reinspection instead of treating a return as approval.
Test the exception before acceptance
In a hypothetical scenario, a corrected item fails again; the second rework route should remain linked to that item and expose the new decision.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a rework order and the sequence used to release the item again.