What it means
A failed unit needs rework, but the shop sends it back through a standard operation that does not address the defect. Manufacturing rework routing approval accuracy tests whether the approved path matches the specific nonconformance and was authorized before work began.
Identify the original work order, item, lot or serial and defect record, because a generic rework ticket without that link can cause the corrected unit to lose its production and quality history. Oracle describes rework work orders and controlled work definitions, and these examples show how a route can be defined; they do not say every defect is repairable or that the operator can choose an unapproved path.
Separate a rework disposition from its detailed routing, since quality may agree that rework is possible while engineering still needs to specify which operations, materials and tests apply. Use the approved revision effective when the rework starts, so a later update to instructions does not silently validate work already performed under an older, inadequate route.
Check whether the proposed operation can remove the actual defect, because repeating a cosmetic inspection cannot fix a dimensional failure that requires machining and remeasurement. Include any replacement components with their lot and permitted substitute status, since rework can introduce new material genealogy that the final product record must reflect.
Specify the skilled role and equipment needed, because a route that assumes an unavailable qualified technician is not executable simply because the system accepts its steps. Keep safety and quality holds active until the route and authorization are in place, since moving the unit physically to a rework cell is not permission to start changing it.
Set the approver matrix by product risk and cost, as some corrections require engineering, customer or regulatory involvement and the exact rule belongs to the actual agreement and operating context. Estimate yield and scrap implications separately from technical validity, because a financially attractive repair is not appropriate if it cannot restore the approved specification.
For a route with several operations, preserve their sequence, as testing before the repair or skipping the final verification can make a completed work order misleading. Record who requested the rework, who approved it, and when the first physical step began, showing approval entered after work is done as late rather than silently counting it as prior authorization.
If a unit fails rework verification, retain the failed result and new disposition, and for subcontracted rework confirm the outside facility received the current instructions and controls, since a purchase order line saying repair may not convey the exact acceptance criteria. Distinguish rework from deviation acceptance: in rework the item is changed to meet approved requirements, while a waiver to accept it as-is follows a different authorization path.
Audit from the nonconformance record through route revision, approvals, execution timestamps and final inspection, treat cancelled routes explicitly, and allow one route to cover a defined group only when the defect and specification are truly shared. Compare route errors by defect category and work cell, show open approval requests and age alongside the accuracy rate, and use findings to improve defect-specific instructions and approval gates, because the goal is restored product quality with a traceable path, not more signatures on generic tickets.
In practice
Real-world examples.
Example
A dimensional defect is routed through approved machining and remeasurement, with the route version authorized before the first cut.
Example
A unit is sent to standard packaging rework even though its electrical test failed; the route is held for engineering review.
Example
A second rework attempt retains the failed first attempt, added component lot and new inspection result.
Formula
Calculation
Illustrative accuracy = eligible rework jobs with correct approved route before execution / all eligible rework jobs started in the period x 100. Show pending and cancelled routes separately.
Worked example. An invented plant starts 80 eligible rework jobs in a month, and 72 had a correct, approved, defect-specific route in place before the first physical step.
- Accuracy = 72 / 80 x 100 = 90%.
- Pending and cancelled routes are reported on their own lines, not folded into the 8 jobs that missed the standard.Case study
Seen in the real world.
This fictional case follows Delta Controls. A batch of units failed a connector test. An old generic rework route omitted the final electrical check. Engineering approved a revised route before work resumed, and the site retained the initial held request, revised instructions and each final test result. The case is invented and does not imply a real field failure.
Watch out
Common mistakes.
- 1. Treating a general permission to rework as approval of every operation.
- 2. Applying a later route revision retroactively to work already done.
- 3. Closing the original defect when rework begins rather than after verification.
Questions
People also ask.
Is rework the same as accepting a deviation?
No. Rework changes the unit to meet requirements; deviation acceptance needs its own decision.
Can one approval cover a batch?
Yes if it names the affected population and the common approved route.
What if rework fails?
Keep the failed result and route a new qualified disposition.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related