Corrective Action Examples from Real Manufacturing Cases

Each example below follows the same structure: nonconformance, containment, occurrence root cause, detection root cause, corrective action plan, and effectiveness criteria. The detail level is what a customer or surveillance auditor expects to see — not a marketing summary, not a one-line memo. See the corrective action process guide for the full method.

How to read these examples

Pay attention to two things. First, every example has separate occurrence and detection root causes — why it happened, and why the controls did not catch it. Second, every action plan moves at least one action up the controls hierarchy (engineering control or poka-yoke), not just training and procedure updates. Plans that rely entirely on retraining almost always recur.

Example 1: Loose structural fastener (automotive Tier 1)

Nonconformance: Three returned assemblies in one week from an OEM customer with loose bracket bolts on a chassis cross-member. All from the same production day.

Containment: Sort and retorque of all finished inventory at the OEM (1,840 units), the company's warehouse (560 units), and work-in-process on the line (220 units). Stop-ship on two open shipments. Containment closed within 36 hours of complaint receipt.

Occurrence root cause: The DC tool had two active rundown strategies for two different bracket variants. After a changeover the operator manually selected the strategy from a menu, and selected the lower-torque variant by mistake. No interlock existed between the part barcode and the tool program.

Detection root cause: End-of-line torque audit was sample-based (one per 50 units) and the affected lot fell between audit points.

Action plan: Hardware interlock between part scan and DC tool program so the wrong program cannot be selected. Move audit from sampling to 100% torque verification using DC tool data, with automatic alarm on any out-of-window result. PFMEA updated to reflect the new control. Operator instruction revised and reissued.

Effectiveness: Zero recurrence and zero failed torque verifications in 90 days across 22,000 units.

Example 2: Coolant drift causing tool wear (precision machining)

Nonconformance: Leak test failures on a hydraulic housing rose from 0.4% to 12% over a single shift. All failures traced to burrs on the seal land.

Containment: 100% visual and leak retest of the affected day's production. Quarantine of 340 finished units pending sort.

Occurrence root cause: Tool wear accelerated when coolant concentration dropped below the lower spec limit. The carbide insert started smearing the seal land instead of cutting it cleanly.

Detection root cause: Coolant concentration was checked manually with a refractometer once per shift. The check had been signed off on the day in question without a real measurement — operator pencil-whipped the log because the refractometer was missing from the cell.

Action plan: Install an inline conductivity sensor with automatic concentrate top-up and an alarm on out-of-window concentration. Eliminate the manual log entirely. Reduce tool life target by 15% to add margin. Update the control plan and PFMEA.

Effectiveness: Reject rate held below 0.5% for 60 days. Zero coolant alarms unresolved more than the 15-minute SLA.

Example 3: Wrong label on shipped product (medical device CM)

Nonconformance: Customer received cartons labeled with a previous-revision Unique Device Identifier (UDI). Affected 2,200 units in one shipment.

Containment: Recall of the shipped lot. Full inventory audit at the customer site and the company's warehouse. Hold on all open shipments to that customer pending verification.

Occurrence root cause: Label master was updated in the ERP, but the print server had cached the previous PDF and was serving the old version. Cache was not invalidated by the master change.

Detection root cause: No verification scan between the print station and the labeler. The operator visually confirmed the label was applied, not that the data was correct.

Action plan: Tie label master change control to print server cache invalidation in the ERP workflow. Add a barcode verification scanner at the labeler that reads the printed UDI and compares it to the work order; reject any mismatch. Revise the work instruction. Add the verification scan as a control point in the DHF.

Effectiveness: 100% scan match for 90 days. Zero label-related complaints in the same period.

Example 4: Recurring supplier reject (electronics assembly)

Nonconformance: Three consecutive lots of a board-to-board connector rejected at incoming inspection for bent pins.

Containment: Quarantine of all rejected lots. Switch to an alternate-source connector for in-process builds. Escalate to the supplier via SCAR with 8D requirement.

Occurrence root cause (supplier): Supplier changed packaging tray to a thinner gauge without notification. The new tray flexed in transit and pins contacted adjacent rows.

Detection root cause: Change was not communicated through the supplier's PPAP change notification system. Customer's supplier quality agreement did not list tray gauge as a controlled characteristic.

Action plan: Supplier reverted to the original tray and added the change to their PPAP change notification gate. Customer added tray gauge and material to the supplier quality agreement as a controlled characteristic. Read-across to two other connector families from the same supplier.

Effectiveness: Zero rejects over the next eight lots. Read-across identified one similar packaging change in a different connector that was caught before shipping.

Example 5: FOD finding in a turbine assembly (aerospace AS9100)

Nonconformance: Foreign object debris (a piece of safety wire) found inside a turbine module during the customer's incoming inspection.

Containment: Stop-ship on all units of the same configuration. Internal borescope of every unit in WIP. Investigation of every unit shipped in the previous 30 days through customer cooperation.

Occurrence root cause: Safety-wire offcut not collected at the lockwire station; the FOD bag was full and had not been emptied during the shift changeover.

Detection root cause: Final visual inspection did not include the inner cavity that required borescope access. The control plan listed visual inspection only.

Action plan: Replace FOD bags with sealed FOD pouches that lock when full and require sign-off to replace. Add borescope inspection of the inner cavity as a mandatory step before final closeout, recorded in the build record. Update the control plan and PFMEA. Train all assemblers with verification.

Effectiveness: Zero FOD findings over 6 months and 1,400 units, including customer incoming inspection.

Example 6: Internal audit finding (ISO 9001 surveillance)

Nonconformance: Internal audit found that calibration records for two CMMs had expired 14 days earlier; the machines were still in active production use.

Containment: CMMs pulled from service immediately. All production characteristics measured on those CMMs in the prior 14 days re-checked on a calibrated CMM. Three lots of work-in-process placed on hold pending re-measurement.

Occurrence root cause: Calibration scheduler relied on a manual email reminder sent by the metrology technician. The technician had been on leave and the backup was not aware of the scheduled calibrations.

Detection root cause: No automated alert when a calibration due date passed. The CMM did not prevent measurement when expired.

Action plan: Move calibration scheduling from manual email to the CMMS, which generates automatic 30/14/7-day alerts to two named owners. CMM software updated to display calibration status on every measurement screen and to require supervisor override after the due date. Audit procedure updated to include calibration status sampling in every quarterly cycle.

Effectiveness: Zero calibration overruns over the next two quarters. Audit verification confirmed alert system was functioning.

Patterns across these examples

Six things show up in every successful example. Separate occurrence and detection root causes. Containment defined by specific scope, not by activity. At least one engineering control or poka-yoke, not only administrative actions. Effectiveness criteria written when the plan was written, not invented at the check. Read-across to similar parts, processes, or suppliers. A clear link back to the source nonconformance (NCR, complaint, audit finding, SCAR).

For the structure these examples follow, see the corrective action template guide and the corrective action plan guide. For the upstream nonconformance document, see the nonconformance report template.