Rework and Reinspection Route¶
Rework-and-reinspection process — instantiates Conformance Control and Corrective Feedback
Routes nonconforming output through an authorized repair and mandatory reinspection, with a hard limit on repeat cycles.
Once a board has decided that defective output should be rework rather than scrap, something has to actually fix it and prove it is now good. Rework and Reinspection Route is that execution path. Its defining discipline is the pairing that its name insists on: no rework without reinspection, and no unlimited rework. A reworked unit is not quietly returned to the flow on the assumption the fix worked — it re-enters the conformance check as if new, and it must pass, including checks for any new risks the repair itself introduced. And because a unit that has been reworked several times is usually telling you the process, not the unit, is broken, the route caps the number of cycles a unit may go through before it is escalated or scrapped.
Example¶
On a structural-steel fabrication, a weld fails its non-destructive test — a radiograph shows porosity. The nonconformance is dispositioned to repair, so it enters the rework route rather than being scrapped. The route is specific: an approved weld-repair procedure (grind out the defect, re-weld to a qualified procedure), then mandatory re-radiography of the repaired zone — not a visual glance, the same NDT the weld originally had to pass, plus a check that the repair heat didn't distort the adjacent joint. The repair and its reinspection result are appended to the weld's nonconformance record so the unit's full history travels with it. A rule caps repairs on any single joint at two; a joint failing a third time is escalated as a process problem, not repaired again.
The route's value is that it closes the loop honestly: the fix is verified to the original standard, the new risk it created is checked, and the history is traceable — and a joint that keeps failing becomes a signal instead of an endless repair.
How it works¶
- Execute an authorized repair. Apply a defined, qualified rework/repair procedure — not an improvised fix — matched to the disposition the board assigned.
- Reinspect as if new. Route the reworked unit back through the conformance check to the original acceptance standard; a reworked unit is not conforming until it passes.
- Check the new risks. Verify the characteristics the repair itself could have disturbed, not only the original defect — repair often moves the problem rather than removing it.
- Cap the cycles. Limit how many times a unit may be reworked; exceeding the limit escalates to scrap or to process correction rather than another repair.
Tuning parameters¶
- Cycle limit — how many rework passes are allowed before escalation. A low limit surfaces process incapability fast but scraps more; a high limit salvages value but hides the incapability.
- Reinspection scope — original defect only vs. defect-plus-collateral. Broader reinspection catches repair-induced damage but costs more.
- Procedure formality — a qualified, documented repair method vs. operator discretion. Formality ensures repeatable repairs; discretion is faster but variable.
- Reinspection independence — whether the same person who reworked also reinspects, or an independent check is required for critical characteristics.
- Escalation path — where an over-limit or unrepairable unit goes: scrap, downgrade, or back to corrective action as evidence of a process problem.
When it helps, and when it misleads¶
Its strength is recovering value from defective output without letting an unverified fix slip through — the reinspection gate and the cycle cap are what separate legitimate rework from wishful patching. It also generates a quietly valuable signal: rework rates and repeat-repair counts are direct evidence of where a process is struggling.
Its central hazard is rework as concealment. Repeated correction can damage the output and, worse, it hides the fact that the producing process is incapable — first-pass yield looks fine only because everything eventually passes after enough touching-up.[n1] Rework can also introduce fresh defects the reinspection wasn't scoped to catch, and an uncapped route becomes an infinite loop that launders a broken process into "conforming" units. The disciplines: reinspect to the full original standard plus collateral risks, cap and count the cycles, report first-pass yield separately from final yield, and escalate repeat rework into corrective action rather than treating it as normal.
How it implements the components¶
rework_repair_and_disposition_path— physically executes the repair the disposition assigned and drives the reworked unit back to a conforming (reinspected) state or to escalation.nonconformance_record— appends the repair actions, reinspection results, and cycle count to the unit's existing nonconformance record, keeping its full history traceable.
It does not decide the disposition or open the record (Nonconformance Report and Review Board), authorize final release of the reworked unit (Release Hold and Signoff), or fix the process so the defect stops arising (Corrective and Preventive Action Cycle).
Related¶
- Instantiates: Conformance Control and Corrective Feedback — it is the verified-repair execution path that returns salvageable output to conformance.
- Consumes: Nonconformance Report and Review Board supplies the disposition and the record this route executes against.
- Sibling mechanisms: Nonconformance Report and Review Board · Corrective and Preventive Action Cycle · Automated Conformance Check · Release Hold and Signoff
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Rework and Reinspection Route operates as a repeatable ordered procedure or handoff sequence that coordinates action because it routes nonconforming output through an authorized repair and mandatory reinspection, with a hard limit on repeat cycles.
Independent corroboration: The frozen evidence defines Rework and Reinspection Route as 'Routes nonconforming output through an authorized repair and mandatory reinspection, with a hard limit on repeat cycles', so its operative form is Protocol, Workflow & Routine.
Nearest alternative: Decision, Gate & Allocation — Rework and Reinspection Route includes features of a case-specific gate, selection, routing, prioritization, or resource disposition, but its defining operation is a repeatable ordered procedure or handoff sequence that coordinates action.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Authorized rework followed by mandatory inspection is canonical manufacturing quality assurance.
Related originating lineages:
- Organizational & Management Science — Workflow governance materially adds ownership and limits on repeat cycles.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: routes nonconforming output through an authorized repair and mandatory reinspection, with a hard limit on repeat cycles.
Review resolution: Both blind reviewers agree that engineering_design is the primary historical origin. Explicit reconciliation of alternate origin disagreement starts from reviewer_a’s mechanism-specific evidence: Authorized rework followed by mandatory inspection is canonical manufacturing quality assurance. Reviewer A proposed alternates=organizational_management, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false; reviewer B proposed alternates=systems_cybernetics, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (organizational_management, systems_cybernetics) without an arbitrary cap, selects origin_mode=single_lineage to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=false from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] First-pass yield — the fraction of output that conforms without any rework. Reporting it separately from final yield is the standard way to keep rework from masking a process that only reaches "good" after repeated correction. ↩