Device Rework: Defining the Instruction and Reverification

What Counts as Rework Under the QMSR

When final inspection rejects a production lot—whether an under-torqued fastener on an electromechanical chassis, a sterile pouch with a localized seal defect, or an optical sensor exhibiting signal drift—manufacturing and quality teams face an immediate operational decision: can the nonconforming lot be reprocessed, what regulatory standard governs the intervention, and what documentation must exist before an assembler touches the hardware?

Under the Food and Drug Administration (FDA) Quality Management System Regulation (QMSR), which took effect on February 2, 2026, rework is formally defined at 21 CFR 820.3(b): “Rework means action taken on a nonconforming product so that it will fulfill the specified requirements in the medical device file (MDF) before it is released for distribution.” This codified definition establishes a rigid operational and temporal boundary that dictates medical device quality systems across the United States.

Crucially, the timing boundary is absolute: rework is exclusively a pre-release activity. In the preamble to the QMSR final rule (89 FR 9284, February 2, 2024), FDA answered Comment 39. Some comments asked the agency to adopt ISO 9000's definition of rework and to clarify how the term applies across the device life cycle. FDA declined. It finalized its own definition in 21 CFR 820.3 so rework would stay consistent with the framework for postmarket monitoring and reports, including corrections, repairs, removals, and recalls under sections 518 and 519(g) of the FD&C Act and 21 CFR parts 7, 806, and 810. FDA stated that action on a nonconforming product after the device has been released for distribution is not rework, because the rule treats rework as action taken before release. Section 820.7 incorporates Clause 3 of ISO 9000:2015, the edition named in the regulation. A later edition, including ISO 9000:2026, does not change that incorporation or the 820.3 definition. Once the device has been released for distribution, later work is postmarket servicing or depot repair, a correction or removal under 21 CFR part 806, or commercial single-use device reprocessing. None of those is production rework.

Within the pre-release manufacturing workflow, nonconforming product must be segregated and controlled under an established nonconformance management procedure complying with ISO 13485:2016 clause 8.3. When nonconforming material review boards (MRBs) evaluate dispositions, they generally have four pathways: scrap the material, return it to a supplier, accept it under concession when the procedure and the applicable regulatory requirements allow that authorization, or authorize rework. Choosing rework starts a documented sub-process.

What ISO 13485 Clause 8.3.4 Actually Requires

Under the QMSR, 21 CFR 820.7 incorporates ISO 13485:2016 and Clause 3 of ISO 9000:2015 by reference. Section 820.10 requires a manufacturer subject to the part to document a quality management system that complies with the applicable requirements of ISO 13485 and the other applicable requirements of part 820. The rework duties therefore come from ISO 13485:2016 clause 8.3.4, as incorporated. The four duties below follow that clause. Confirm the exact incorporated sentences in the ANSI IBR read-only copy before quoting them. They are requirements, not a suggestion:

1. Documented Procedures with Adverse Effect Analysis: Perform rework under documented procedures that take into account the potential adverse effect of the rework on the product. The procedure has to be approved before the work starts. The adverse-effect assessment belongs in that procedure and has to fit the actual change: heat, stress, surface contamination, or a disturbed joint are examples, not a list that applies to every device.

2. Mirrored Review and Approval Authority: Those procedures undergo the same review and approval as the original procedure. If design engineering approved the original assembly instruction, design engineering approves the rework instruction. A line supervisor's informal note does not replace that route. The clause reuses the original procedure's approval route. It does not invent a new set of job titles.

3. Mandatory Reverification Against Specifications: After rework, verify the product against the applicable acceptance criteria and regulatory requirements. That means each reworked unit, against the criteria the rework could have affected. It is not an automatic repeat of every finished-device test, and it is not a release based only on a statement that the unit looks acceptable.

4. Comprehensive Production Records: Maintain records of the rework under clause 4.2.5. A record that can be inspected identifies the nonconformance, the instruction revision, the people and equipment used, the verification results, and the disposition. Clause 4.2.5 requires those records to be controlled. It does not prescribe that field list. Section 820.35 adds content for complaint records, servicing records, and the unique device identifier of each device or batch. Labeling examination records are a separate duty under 21 CFR 820.45, kept under clause 4.2.5. Section 820.35 does not rename the old device history record or list rework-traveler fields.

What Changed From the Old 820.90(b)(2)

For three decades under the 1996 Quality System Regulation (QSR), rework compliance was governed by 21 CFR 820.90(b)(2). Manufacturers transitioning their quality systems through the QSR to QMSR transition must recognize how the regulatory baseline has evolved. While the fundamental public health intent remains continuous, the statutory terminology, citation mechanics, and documentation structures have undergone structural changes.

Under former 21 CFR 820.90(b)(2), the adverse-effect determination was documented in the device history record, which firms commonly completed in the batch record before release. Clause 8.3.4 places that assessment in the documented procedure, so it is approved before the rework is performed. The clause's reference to regulatory requirements means verification covers the regulatory requirements the rework could affect. Electromagnetic compatibility, software integrity, or a sterile barrier is in scope only when the rework could have changed it.

Writing the Rework Instruction: The Configuration-to-Claim-to-Evidence Map

A legally defensible rework instruction is an engineering document, not a generic scrap form. Rework is a controlled disposition of nonconforming product. It is not automatically an unvalidated process. A new process validation is required only when the rework uses or changes a process whose output cannot be fully verified and the activity sits outside the already qualified window. Compliance Program 7382.850 is the inspection program that replaced QSIT. Keep the rework instruction, its approval, and the release evidence with the configuration being reworked.

The table below uses five representative rework configurations. Each row is a worked example: a claim the evidence can support, instruction content that makes that claim defensible, an approval route that mirrors the original procedure, and verification evidence that can support release. Job titles and named test methods are examples, not a statutory parts list.

To ensure procedural repeatability, an authoring team should structure every rework traveler around seven standardized engineering sections:

• 1. Nonconformance Identification & Lot Bounding: Reference the parent Nonconformance Report (NCR), exact part number, dash revision, lot/batch number, serial number range, and total quantity of affected units. Establish physical quarantine boundaries to prevent mix-ups.

• 2. Root Cause Summary & Scope of Rework: Document the specific engineering root cause that generated the nonconformance and delineate the boundary of what components may and may not be disassembled.

• 3. Calibrated Tooling, Equipment, and Environment: List all required fixtures, torque drivers, digital calipers, multimeters, and test equipment by equipment ID, model, and required calibration due date. Define necessary environmental controls (cleanroom classification, ESD protection, temperature, humidity) per ISO 13485 clause 6.4.

• 4. Formal Adverse Effect Evaluation: Document an engineering risk analysis evaluating the potential adverse effects of the rework on the product. Address mechanical fatigue, thermal degradation, software state, contamination, and clinical performance, referencing the device risk management file.

• 5. Granular Step-by-Step Procedure: Provide unambiguous, sequential instructions for disassembly, component preparation, modification, and re-assembly. Identify parts that must be scrapped upon disassembly (e.g., O-rings, prevailing torque nuts, tamper-evident seals).

• 6. Objective Reverification Protocol: Specify every inspection and test step required following rework, defining explicit numerical pass/fail criteria, test methods, sample sizes, and required data logging.

• 7. Cross-Functional Engineering Approval Sign-Offs: Provide signature blocks that mirror the approval hierarchy of the baseline work instruction, confirming authorization before execution and final quality acceptance before lot release.

Reverification: How Much Evidence Supports Release

A frequent source of regulatory citations is the failure to distinguish between verification and revalidation following rework. Practitioners often swing between two dangerous extremes: either assuming that a simple visual check is sufficient to release reworked product, or needlessly re-executing full line validation protocols that delay production by months.

The regulatory standard establishes a clear demarcation. Under ISO 13485:2016 clause 8.3.4, verification applies to each rework. Each reworked unit is checked against the applicable acceptance criteria. The check can be inspection, test, or another method the original acceptance activity uses. Revalidation follows ISO 13485:2016 clause 7.5.6, which now carries the process-validation duty formerly stated in 21 CFR 820.75: whenever a manufacturing process produces outputs that cannot be fully verified by subsequent non-destructive monitoring or measurement, the process must be validated. If a rework operation touches, repeats, or alters a validated special process—such as sterile barrier heat sealing, ultrasonic welding, laser cutting, automated potting, or terminal sterilization—the manufacturer cannot rely solely on post-rework inspection. The rework must either undergo full process revalidation or operate strictly within previously qualified Installation Qualification (IQ), Operational Qualification (OQ), and Performance Qualification (PQ) design spaces. Process validation is how that qualified window is established. Rework does not create a second, informal window.

When structuring reverification for standard mechanical or electrical rework, quality engineers often ask: must every single test in the finished device test suite be re-executed? The answer is no, provided a rigorous Bounding Rationale is documented. Repeating 100% of all functional tests can actually degrade product reliability—for example, subjecting micro-connectors to unnecessary mating cycles, wearing gold-plated PCB fingers, or adding thermal stress. A defensible rework traveler defines a targeted reverification scope that tests every parameter the rework could directly or indirectly affect, accompanied by a written engineering rationale justifying why unrelated subsystems remain unaffected.

flowchart TD
    A["Nonconformance found before release"] --> B["Segregate the product and record it"]
    B --> C["Confirm the action is pre-release rework"]
    C --> D["Write the rework instruction"]
    D --> E["Assess adverse effects in that instruction"]
    E --> F["Approve it by the same route as the original procedure"]
    F --> G["Perform the rework"]
    G --> H{"Does the rework use a validated special process?"}
    H -- "No" --> J["Verify each reworked unit against the affected acceptance criteria"]
    H -- "Yes" --> P{"Is the activity inside the qualified process window?"}
    P -- "Yes" --> J
    P -- "No" --> I["Requalify that process before relying on it"]
    I --> J
    J --> K{"Do the results meet the applicable acceptance criteria and regulatory requirements?"}
    K -- "No" --> L["Do not release. Evaluate scrap and corrective action"]
    K -- "Yes" --> M["Keep the clause 4.2.5 record and authorize release"]

The Linemaster Letter: Anatomy of an Undocumented Rework

On May 27, 2026, FDA issued warning letter CMS 730215 to Linemaster Switch Corporation after inspecting its Woodstock, Connecticut facility from February 4 through March 6, 2026. The letter is one QMSR-era example of how an investigator can write a rework observation. It is not a count of how often FDA cites clause 8.3.4, and it is not identified here as the first QMSR warning letter.

FDA stated that the firm manufactures foot pedal accessories for medical devices, including Class II foot pedal controls used with Class IV medical lasers. Violation 1 cites failure to follow ISO 13485:2016 clause 8.3.4:

“Failure to perform rework in accordance with documented procedures that take into account the potential adverse effect of the rework on the product, as required by ISO 13485:2016, Clause 8.3.4.”

The firm already had a written procedure. Q 006 Rev D3, Nonconforming Material Control, dated October 14, 2025, says in section 7.6 that rework and repair instructions shall be documented on the MRR or on form Q6-12, with specific manufacturing and inspection instructions recorded. During a redacted job, the manufacturing manager told the investigator that the foot pedals were nonconforming because, after calibration, the assembler had failed to complete a redacted screw step. The supervisor had the assembler apply torque and recalibrate the units, and that rework was not documented. The letter does not describe a separate actuation-test failure, and it does not name the adjustment screws. Those details are redacted or simply not stated.

In this letter, the rework observation is written as an ISO 13485:2016 clause 8.3.4 failure. Part 820 is cited once, in the statement that the devices are adulterated under section 501(h) because the manufacturing methods are not in conformity with the Quality Management System Regulation. The other observations are also written as ISO clause failures: 7.1, 8.5.2, 6.4.1, and 7.6. That is the citation pattern in this letter. It does not prove how every later observation will be written, and it does not show what an investigator would have cited under the repealed QSR.

FDA said the adequacy of the firm's March 30, 2026 response could not be determined at the time of the letter. The firm planned to review and revise its reprocessing and rework procedures so documentation would cover lots that do not meet specifications, and it planned a retrospective review of reworked lots. FDA's stated gap was the absence of a timeline and of any revised documents. The letter does not say the firm promised retraining, and it does not say a completed health-hazard evaluation of distributed product was missing. FDA asked the firm to supply three things before the response could be assessed:

1. Revised procedures: FDA asked for the revised rework procedures. A promise to revise them, without the documents, was not enough for FDA to judge the response.

2. A timeline: The firm did not provide a timeline for finishing the procedure revision or the retrospective review of reworked lots.

3. The retrospective review, when finished: The review of reworked lots was planned, not described as a completed evaluation. FDA asked for a summary when it was done and for any corrective actions that review required.

When Rework Must Escalate to CAPA and Risk Management

A rework traveler is a tactical disposition for a specific nonconforming batch; it is not a substitute for systemic corrective action. The Linemaster warning letter provides an instructive case study in how production rework breakdowns cascade into systemic quality failures.

Alongside the Clause 8.3.4 rework citation, FDA cited Linemaster under ISO 13485:2016 Clause 8.5.2 (Corrective Action) because customer requests for corrective action were not investigated as the firm's own procedure required. SCAR-00014, dated November 14, 2023, covered six foot pedals that failed calibration verification at the customer's facility. The response to the customer left the root cause blank and listed corrective action as "NA." The letter does not describe that complaint as an intermittent switch failure. FDA also cited ISO 13485:2016 Clause 7.1 (Planning of Product Realization) because the firm had not documented one or more processes for risk management in product realization. Risk-management procedure TM-112 Rev D, section 5.3.2, says process FMEAs are created to assess the highest processing risks and that action is taken to reduce the risk. There was no process FMEA for a foot-pedal accessory used to control Class IV medical lasers. The same procedure did not define who performs and approves risk-management activities, when the file must be updated, or how complaints, adverse events, and recalls are brought into it. A repeated undocumented rework can be the production symptom of that gap. The letter does not say every rework is itself a missing FMEA.

Clause 8.5.2 requires documented corrective action that finds the cause of a nonconformity and reviews whether the action worked. A rework traveler does not satisfy that duty when the same defect shows the process is unstable. The triggers below are examples a firm can write into its own procedure. They are not thresholds in clause 8.3.4 or 8.5.2. Escalation still belongs in the Corrective and Preventive Action (CAPA) investigation:

1. Statistical Process Control (SPC) Thresholds: A procedure may track the rework rate on a p-chart or np-chart and require a corrective-action evaluation when a point exceeds a control limit, or when a run rule the firm has adopted is met. Seven consecutive points on one side of the centerline is a common run rule. It is not an FDA limit.

2. Recurrent Defect Mode Frequency: A procedure may suspend routine rework authority when the same defect recurs, for example across a number of lots or above a rate the firm sets. Three consecutive lots, or 2 percent of a month's output, would be an internal choice. Neither figure is a legal limit.

3. Unanticipated Failure Modes & Risk File Updates: If the rework reveals a hazard the risk-management file does not already address, update that file under the firm's ISO 14971 process before treating the rework as routine. Risk priority numbers are one optional FMEA scoring method. ISO 14971 does not require them.

4. Validated Process Breaches: A single seal defect can still be dispositioned as nonconforming product. Corrective action is indicated when the event shows a validated process may be outside its qualified state, not because every sterile-barrier nonconformance is automatically a CAPA.

Distinguishing Required Mandates, Voluntary Standards, and Commercial Assumptions

Effective RA/QA leadership requires distinguishing between statutory legal mandates, voluntary consensus standards, and erroneous commercial folklore. In device manufacturing, misconceptions regarding rework frequently lead either to regulatory noncompliance or to paralyzing operational overhead.

One commercial assumption is that a sterile-barrier device can never be reworked. If final inspection rejects a pouch seal before release, and before or apart from a terminal sterilization exposure that the validation does not allow to be repeated, the pre-release definition still allows rework. The device can be inspected, placed in a new qualified barrier, and sealed inside the parameters the packaging validation already qualified. What the manufacturer cannot do is release that reseal on a visual check the validation never accepted. Use the seal inspections and tests the packaging validation specifies, which often include a defined destructive peel sample such as ASTM F88, not a new universal test for every pouch. A new ISO 10993 assessment is indicated when the rework adds a cleaning agent, an extra sterilization exposure, or a material the original biological evaluation did not cover. A reseal that uses the same materials inside the qualified process is not automatically a new biocompatibility study.

Records and Inspection Readiness Under Compliance Program 7382.850

On February 2, 2026, FDA stopped using the Quality System Inspection Technique (QSIT) for device inspections and stopped using Compliance Programs 7382.845 and 7383.001. Device quality-system inspections now follow Compliance Program 7382.850 (“Inspection of Medical Device Manufacturers”). The updated program describes the QMSR inspection process. Rework records, nonconforming-product dispositions, and corrective-action files are part of the quality system an investigator can review.

Manufacturers preparing for a QMSR inspection can plan around four facts that FDA has already stated:

1. Retrospective Record Auditing: In FDA’s QMSR Frequently Asked Questions, the agency explicitly affirmed that investigators possess full statutory authority to inspect quality records created prior to February 2, 2026. Transitioning to the QMSR does not grant amnesty for past documentation lapses. Rework records, DHRs, and MRB dispositions executed under the old QSR remain fully subject to inspection throughout their required retention life.

2. Elimination of Former 820.180(c) Inspection Exceptions: Under the repealed QSR 820.180(c), manufacturers enjoyed statutory exemptions protecting internal quality audit reports and supplier audit reports from routine FDA review during facility inspections. Under the QMSR, FDA deliberately eliminated these exceptions. Investigators operating under CP 7382.850 may review internal audit findings, supplier audit reports, and management review records regarding rework rates, supplier nonconformances, and systemic process drift.

3. ISO Certification Does Not Shield from Enforcement: FDA reiterated that it neither issues ISO 13485 certificates nor accepts third-party registrar certificates as a substitute or exemption from FDA inspection. While Medical Device Single Audit Program (MDSAP) reports may be reviewed, FDA maintains independent enforcement authority to issue Form FDA 483s, warning letters, and import alerts based on direct assessment of ISO 13485:2016 compliance.

4. Public Read-Only Access via ANSI IBR Portal: Because ISO 13485:2016 is a copyrighted voluntary consensus standard incorporated by reference into federal regulation, the legally binding text of ISO 13485:2016 can be accessed free of charge in read-only format through the ANSI Incorporated by Reference (IBR) portal. Regulatory affairs and manufacturing teams can verify exact clause text directly through this official portal.