Responding to an Audit Finding on Documented Approval
You are the quality lead at a medical device assembler. An internal auditor finds that 14 of 60 production records from the last quarter lack a second-person verification signature on a critical torque step. The procedure requires two signatures. Operators say the second signature is often collected hours later by a supervisor doing a batch review, and that during the busy season the supervisor signs at the end of the week. No product failures have been traced to the torque step in two years. The auditor wants a finding escalated to the quality management review and a possible stop-ship. Your operations director argues the finding is administrative, that the torque values themselves are all in specification, and that a stop-ship would cost about $400,000 in delayed shipments.
1. How should you weigh the operations director's argument against the audit finding?
Read the worked answer
The director is right that the torque values are in specification, but that does not settle the question. The requirement exists to ensure verification happens close enough in time to catch a nonconformance before the unit moves on. A signature collected at week's end cannot serve that purpose, so the records are accurate about the values and misleading about the control.
The absence of failures in two years is weak reassurance. The torque step may be robust, or failures may be escaping detection. Two years of no events is also a small sample for a low-frequency failure mode.
The decision should separate two questions. Is there a real control gap? Yes, because the timing of the signature defeats the intent of the requirement. Is a stop-ship proportionate? Not automatically. A stop-ship is warranted when there is evidence of product risk, and none has been shown.
A proportionate response is to escalate the finding, contain any product currently in process by verifying torque directly, and correct the workflow so the second signature is captured at the station. The $400,000 figure is relevant to selecting the remedy, not to whether the finding is valid.
2. What corrective action would address the root cause rather than the symptom, and how would you verify it worked?
Read the worked answer
The symptom is missing signatures. The root cause is a workflow that makes real-time verification inconvenient, so people defer it. Retraining operators to sign promptly would treat the symptom and would likely fail under busy-season pressure.
A root-cause action changes the process so the correct behavior is the easy one. Options include:
- A station-level interlock that requires the second credential before the unit can advance.
- A supervisor roving verification step scheduled within the shift, not at week's end.
- Electronic capture with a timestamp, so late signatures are visible as late rather than as compliant.
The electronic option is attractive because it also makes the failure mode detectable.
Verification should sample records after implementation and measure two things: the proportion of records with a second signature, and the time gap between first and second signature. A target such as 95% of records signed within 30 minutes would show the workflow change took hold. Track it weekly for a quarter, then monthly. If late signatures persist, the workflow is still fighting the operators and needs another look.