Rework Traceability – Controlled Re‑Use

This topic is part of the SG Systems Global regulatory & operations glossary.

Updated October 2025 • Genealogy & Disposition • QA, Manufacturing, Supply Chain

Rework is the planned, approved re‑processing of nonconforming material to meet requirements without compromising safety, efficacy, or label claims. It is not a shortcut. It lives under deviation/NC control, routed through NCR/NCMR, dispositioned by MRB, executed in MES/WMS, and released by QA only when evidence proves fitness for use (Lot Release/Finished Goods Release).

“Rework is acceptable; untraceable rework is not. If genealogy, testing, and approvals aren’t airtight, you’re gambling with recalls.”

1) Definitions—Rework vs. Reprocessing vs. Regrade

• Rework: Additional processing to bring material back to spec; see Rework / Controlled Re‑processing.
• Reprocessing: Repeating a defined step within the validated process (e.g., re‑filtration). Usually pre‑approved in the MBR/BMR with limits.
• Regrade: Downgrading to an alternate spec/market with accurate label/claims; triggers labeling control.
• Not allowed: “Silent” reuse or blending without MRB/QA, or anything that breaks registration commitments or patient/consumer safety.

2) Guardrails—When Rework Is Permissible

Rework must be technically justified and risk‑assessed. Expect proof via Process Validation (PV)/PPQ impact, CPV trends, Cleaning Validation, Hold‑Time Studies, and stability considerations (stability). If the risk profile changes, route through MOC/Change Control and update the control plan.

3) Authorization Path—From Nonconformance to MRB Decision

1. Log the event as Deviation/NC → issue NCR/NCMR; place items on Hold.
2. MRB evaluates risk and options: scrap, rework, regrade, return (RMA).
3. Approve a documented rework instruction (inputs, steps, acceptance criteria), link to approval workflow and controls in the MES/eBMR.
4. Close the loop with root cause and CAPA.

4) Status, Segregation & Line Control

Physical and system segregation are non‑negotiable. Use location topology, bin control, and directed put‑away to separate Held vs Released. Prior to execution, enforce line clearance and verify artwork/IDs via label verification.

5) Identity, Lotting & Barcodes—No Ambiguity

Decide whether the output remains under the original lot or becomes a new rework lot. Document the rule and stick to it.

• Encode/track GTIN, Lot (AI 10), relevant GS1 AIs, and handling units via SSCC/GS1‑128.
• Record parent→child transformations in genealogy and exchange as EPCIS events.
• If rework touches saleable serialized units, align with DSCSA/serialization/UDI rules before re‑labeling or repacking.

6) Execution in MES/eBMR—Prove It Happened Correctly

• Use a dedicated rework route with enforced steps, IPC and SPC limits.
• Capture device data (scales, machine vision) with audit trails; no spreadsheets.
• Re‑verify cleanliness (Cleaning Validation) and time limits (Hold‑Time).
• Update the eBMR with clear “REWORK” context and links back to the original lot record.

7) Sampling, Testing & Release

Define a statistical plan (sampling, AQL) and verify results in LIMS. Manage OOS/OOT properly, confirm method suitability (TMV, ISO 17025), and regenerate the CoA and labels if specs or claims changed. QA releases via Lot Release/Finished Goods Release; product remains on Hold until then.

8) Inventory, Costing & Planning

• Reconcile inputs↔outputs via mass balance; track yield variance and WIP.
• Schedule rework consciously—don’t starve new production. Manage obsolescence risks for materials and artwork.
• If customer returns are reworked, integrate RMA inspections and re‑serialization rules where applicable.

9) Failure Modes—Avoid These

• “Stealth” rework with no MRB/QA approval.
• Mixing lots during rework without genealogy—impossible recall math (recall readiness fails).
• Using wrong labels after regrade; skipping label verification/barcode validation.
• Reprocessing beyond validated limits without Change Control.
• Spreadsheet‑based tracking that violates Part 11/Annex 11 and Data Integrity.

10) How This Fits with V5 by SG Systems Global

V5 Solution Overview. The V5 platform treats rework as a first‑class workflow: identity, status, signatures, and genealogy are interlocked and reportable.

V5 QMS. V5 QMS manages approvals, deviations/CAPA, MOC, and Document Control.

V5 MES. V5 MES executes rework routes under eBMR with audit trails, IPC/SPC limits, and review‑by‑exception.

V5 WMS. V5 WMS enforces Hold segregation, directed picking, correct GS1‑128 labeling, and compliant handover at Pack & Ship.

Bottom line: V5 makes rework controllable—not ad‑hoc. You get defensible records, faster QA decisions, and credible recall posture.

11) Metrics That Prove Control

• Rework rate & yield: % lots/units reworked; first‑pass rework success.
• MRB cycle time: detection → decision → closure.
• Genealogy completeness: % rework lots with parent/child links and EPCIS events.
• Mass‑balance delta: variance pre‑ vs post‑rework by lot.
• Label/serialization exceptions: scan failures per 1,000 units after rework.
• Release lead time: rework finish → QA disposition.

12) FAQ

Q1. When do I assign a new lot number?
When composition, route, or risk changes materially; when lots are blended; or when required by labeling/registration. In all cases, maintain parent→child links in genealogy and reflect identity in GTIN/AI 10/SSCC.

Q2. Can I blend rework from multiple lots?
Only if MRB/QA approves and genealogy captures exact composition; sampling increases. Expect tighter IPC and a fresh CoA.

Q3. How do DSCSA/UDI rules interact with rework?
Identity rules (DSCSA, UDI) still apply. If you repack/relabel, ensure correct serialization events and no reuse of retired identifiers; log transformations via EPCIS.

Q4. Does rework change expiry?
It can. Re‑establish expiry with stability evidence or conservative rules; never guess. Consider hold time impact and update labels/CoA accordingly.

Q5. What documentation must QA see before release?
Approved rework plan, executed eBMR with audit trails, passing tests, closed deviation/CAPA, correct labeling/serialization checks, and clear genealogy to the original lot(s).

Q6. How do we keep this fast without cutting corners?
Build it into the system: paperless automated batch records, scan‑enforced status, and review‑by‑exception dashboards.

Related Reading
• Core Controls: Rework | MRB | Deviation/NC | CAPA | MOC | Change Control
• Identity & Genealogy: GS1 GTIN | Lot (AI 10) | SSCC | EPCIS | End‑to‑End Traceability | Batch Genealogy
• Execution & Release: MES | eBMR | WMS | Hold/Release | Finished Goods Release
• Data Integrity & Compliance: 21 CFR Part 11 | Annex 11 | Data Integrity | Audit Trail | Record Retention
• Label & Packout: Labeling Control | Label Verification | Barcode Validation | GS1‑128 Case Label