What Is Corrective Action?
Written by Jason Westland · Edited by Johanna Barnett
In manufacturing quality, corrective action is action taken against an evidence-supported cause by changing the process or control so recurrence risk is reduced.
It is not containment or correction. Containment protects the customer or next process while the issue is investigated; correction deals with the affected product or output; corrective action changes what allowed the issue to occur or escape.
Corrective action process
- 1Define the issue
- 2Contain immediate risk
- 3Correct affected product
- 4Establish the occurrence cause
- 5Establish the escape or detection weakness
- 6Define corrective actions
- 7Verify implementation
- 8Check effectiveness and close
What corrective action means in manufacturing quality
Corrective action in manufacturing quality is a controlled response to an actual nonconformity or quality issue. It uses evidence to establish the cause, changes the process or control associated with that cause, assigns ownership, and checks whether the change worked over a defined review period.
A corrective action record may be linked to a non-conformance report (NCR), customer complaint, audit finding, root cause analysis (RCA), corrective action request (CAR), supplier corrective action request (SCAR), or 8D.
The record should show the problem, affected and suspect scope, containment, correction, supported occurrence cause, escape or detection weakness where relevant, corrective actions, owners, due dates, evidence, verification, effectiveness, and closure decision.
Containment, correction, corrective action, verification, and effectiveness
These terms perform different jobs in a manufacturing quality record and must be reviewed separately.
| Term | What it means | Manufacturing example |
|---|---|---|
| Containment | Temporary action to protect the customer or next process while the issue is assessed. | Place suspect stock on hold, stop shipment, or perform temporary sort or targeted inspection. |
| Correction | Action taken on the affected product or immediate issue. | Rework, repair, scrap, return, replace, relabel, or repack affected product under an approved disposition. |
| Corrective action | Action taken against an evidence-supported cause by changing the process or control so recurrence risk is reduced. | Revise a checklist, change a fixture, add measured verification, update a maintenance control, or change a detection step. |
| Verification | Confirmation that the planned action was implemented as intended. | Confirm the revised document was issued, the obsolete version was removed, required training was completed, and the new control is in use. |
| Effectiveness | Evidence that the implemented action worked over the defined review period. | Review subsequent production, inspection, audit, or complaint data against a defined acceptance criterion. |
Keep verification and effectiveness separate
When corrective action is needed
Use formal corrective action when the issue is repeated, systemic, customer- or supplier-facing, high risk, or evidence shows that the process or detection control must change.
- a customer complaint or return requires process follow-up
- an NCR shows a recurring or systemic weakness
- an audit finding requires action, evidence, verification, and closure
- a supplier issue requires a SCAR response
- inspection failure, scrap, or rework is recurring
- the issue escaped to the next process or customer
- a previous correction or corrective action was ineffective
- evidence supports a cause that requires a method, equipment, document, maintenance, or control change
- an 8D needs D5 corrective action after D4 evidence establishes the occurrence cause and escape weakness
- a customer or internal authority requires a formal corrective-action response
When a local action or routine record is appropriate
Use the smallest controlled record that preserves product status, traceability, ownership, and required approval. A local action or routine production, maintenance, inspection, or document-control record may be sufficient when:
- the issue is minor and isolated
- it is corrected within an existing approved process
- no suspect product or external risk remains
- no special disposition or approval is required
- no repeat or trend signal exists
- the normal record captures completion and verification
Do not downgrade recurring work
The corrective action process
The form can vary by company, customer, and industry, but the review sequence should keep immediate product control, cause evidence, process change, verification, effectiveness, and closure separate.
- 1
Define the issue
State the controlled requirement, actual condition, affected and suspect scope, where the issue was found, and the originating NCR, complaint, audit, CAR, SCAR, or 8D where applicable. Keep possible causes out of the problem statement.
- 2
Contain immediate risk
Protect the customer or next process while investigation continues. Hold suspect product, stop release or shipment, check downstream stock, perform temporary inspection, and identify the clean point as applicable. Containment is temporary control, not corrective action.
- 3
Correct the affected product or output
Complete the approved product action—such as rework, repair, scrap, return, replacement, relabeling, or repacking—and record post-correction verification where required. Do not label sorting or holding as the final correction or disposition.
- 4
Use evidence to establish the occurrence cause
List possible causes, then support or rule them out using the part, records, measurements, tests, drawing, work instruction, control plan, maintenance or calibration history, interviews, and process observation. Do not choose corrective action while the cause is still a guess.
- 5
Establish the escape or detection weakness where relevant
For downstream or customer escapes, determine why the existing control did not detect the condition. Check the inspection method, sampling plan, test coverage, checklist, gauge use, review step, and release decision. The escape weakness may need a separate action.
- 6
Define corrective actions
Each action must match the supported occurrence cause or escape weakness. State what will change, the owner, due date, required evidence, implementation-verification method, effectiveness measure, review window, and acceptance criterion. Training may support a control change; training alone is rarely a complete action.
- 7
Verify implementation
Confirm that each planned change was implemented as intended. Review the issued document, removed obsolete version, changed equipment or fixture, completed training, updated record, and use of the new control. Verification does not prove long-term effectiveness.
- 8
Check effectiveness and close
Review the agreed data after the process runs again. Use the defined production window, lot count, audit sample, inspection result, recurrence rate, or customer data. Close only when the action was implemented, the effectiveness criterion was met, evidence is traceable, approvals are complete, and remaining risk is accepted or assigned.
Stop rule
What a complete corrective action record includes
A complete corrective action record allows another reviewer to understand the originating issue, evidence, process change, implementation result, effectiveness decision, and closure without relying on memory.
| Field | Why it matters |
|---|---|
| Originating issue or related record | Links the corrective action to the NCR, complaint, audit finding, RCA, CAR, SCAR, or 8D. |
| Requirement and actual condition | States what should have happened and what was observed, measured, reported, or returned. |
| Affected and suspect scope | Records the affected and suspect product, lots, work orders, locations, shipments, records, or downstream stock. |
| Containment | Shows how immediate customer or process risk was controlled. |
| Correction and disposition | Shows what happened to the affected product or immediate issue under the approved decision. |
| Possible causes considered | Records the cause paths reviewed before the supported cause was selected. |
| Supported occurrence cause | States the evidence-supported reason the issue occurred. |
| Escape or detection weakness | States why the existing control did not detect the issue where relevant. |
| Corrective actions | Defines the process or control changes linked to the supported cause or escape weakness. |
| Owner and due date | Makes responsibility and timing explicit. |
| Required evidence | Defines the records, measurements, photographs, documents, observations, or approvals needed. |
| Verification method and result | Shows how implementation was checked and what the check found. |
| Effectiveness measure and result | Records the review window, acceptance criterion, evidence reviewed, and effectiveness decision. |
| Closure decision and approver | Records who approved closure, when, and what remaining risk or linked work remains. |
Occurrence cause and escape or detection weakness require separate evidence
When a problem reached a downstream process or customer, the corrective action review must answer two questions: why the nonconformance occurred and why the existing control did not detect it.
Occurrence cause
Why did the issue happen?
Possible cause paths to test include:
- a setup or work instruction omitted a required control
- a fixture or tool condition allowed the error
- a maintenance or calibration control did not detect drift
- a process parameter or material condition moved outside control
Escape or detection weakness
Why was the issue not detected before the next process or customer?
Possible detection weaknesses to test include:
- the inspection plan did not cover the failed feature
- the sampling plan could not reliably detect the condition
- the required gauge or test was not used at the detection point
- the review or release step checked record presence but not record completeness
These are possible cause paths, not conclusions. Use records, measurements, tests, observations, and interviews to support or rule out each path before naming the supported cause.
WORKED MANUFACTURING EXAMPLE
Assembly torque-control audit finding: a worked corrective action example
A process audit finds missing torque rows, measured values, and operator signoffs in sampled assembly records at a fastening station. The work instruction requires a complete torque row with the measured value and operator signoff for every sampled fastener check.
Issue
Required torque rows, measured values, or operator signoffs are missing from sampled assembly records.
Requirement
The work instruction and torque checklist require a complete torque row with a measured torque value and operator signoff for each sampled fastener check.
Actual condition
Some sampled records omit the required torque row; others show a completed check line without the measured value or operator signoff.
Affected and suspect scope
The current station batch and related records since the last confirmed complete review remain suspect until record completeness and available product are checked.
Containment
Place the current station batch on quality hold and block release, review the related records, and repeat the required torque checks where product is still available.
Correction
Repeat the required torque checks where product is available and record the measured results. Where product is no longer available, record the gap and follow the approved escalation or risk decision; do not backfill values from memory.
Evidence reviewed
Audit sample sheet, incomplete records, station print template, work instruction, torque checklist, supervisor review records, torque-tool calibration record, and process observation.
Supported occurrence cause
The station print template allowed the required torque row to be omitted, and the operator checklist allowed the record to be signed off without confirming that every required torque entry was complete.
Escape or detection weakness
Supervisor review confirmed that the record was present but did not verify that each required torque row contained both the measured value and operator signoff.
Corrective actions
- lock the station print template so the required torque row and entry fields always print
- revise the torque checklist to require the measured value, operator signoff, and a completeness check
- add supervisor review of torque-row completeness before batch release
- train affected operators and supervisors on the revised controls
Required evidence
Locked print template, revised torque checklist, training record, supervisor review checklist, and completed torque records.
Verification
Confirm the locked template is deployed, the revised checklist is issued, obsolete versions are removed, required training is complete, and the supervisor review is in use.
Effectiveness target
Review a defined sample of subsequent torque records over the defined review window. Acceptance criterion: every sampled record contains the required torque row, measured value, and operator signoff.
Closure
Close only after implementation is verified and the effectiveness criterion is met. If omissions recur, reopen the cause or action decision.
Strong vs weak corrective actions
A weak entry records activity without defining the process change, ownership, evidence, or effectiveness decision. A strong entry states what changes and how the team will verify and judge it.
Weak entry
Retrain operators.
Training alone does not show what process or control changed.
Stronger entry
Lock the station print template so required torque rows always print, revise the checklist to require the measured value and signoff, train affected operators, and verify use of the revised controls.
It changes the control, defines the required record, supports the change with training, and includes implementation verification.
Weak entry
Monitor torque more closely.
It does not define the trigger, measurement method, record, owner, review window, or acceptance criterion.
Stronger entry
Add measured torque verification at the defined setup or handover trigger, record the result on the controlled setup record, and review subsequent records against a defined acceptance criterion.
It defines the trigger, measurement, controlled record, and effectiveness decision.
Weak entry
Supplier notified.
Notification does not define the supplier investigation, required evidence, review criteria, corrective action, or release condition.
Stronger entry
Issue a supplier corrective action request that defines the nonconformance, response due date, evidence required, review criteria, and release condition.
It defines the formal request and the controls needed to review the supplier response without implying a supplier portal.
Common corrective action mistakes
| Mistake | Better approach |
|---|---|
| Treating containment as corrective action | Record containment separately, then define actions that change the process or detection control associated with the supported cause. |
| Selecting the action before evidence supports the cause | List possible causes and support or rule them out before choosing corrective action. |
| Ending at “operator error” or “training issue” | Identify what allowed the error and why the process or detection control did not prevent it. |
| Ignoring the escape or detection weakness | Ask why the issue reached the next process or customer and whether a separate detection action is required. |
| Writing vague actions such as “review process” | State what will change, who owns it, when it is due, what evidence is required, and how implementation and effectiveness will be checked. |
| Treating task completion as effectiveness | Verify implementation first, then review follow-up evidence against the defined effectiveness criterion. |
| Changing the target after the action fails | Keep the agreed acceptance criterion, reopen the cause or action decision, and record the next controlled step. |
| Tracking the work only in email | Keep the originating issue, actions, owners, dates, evidence, verification, effectiveness, and closure decision in one traceable record. |
How corrective action connects to NCR, RCA, CAR, SCAR, 8D, and corrective action plans
Corrective action may sit inside or link from another quality record. The correct record depends on what must be controlled, who owns the response, and whether a customer or supplier requires a formal submission.
| Record or method | Main purpose | Corrective action connection |
|---|---|---|
| NCR | Controls the nonconformance and product decision. | Link corrective action when the remaining work must change a process or detection control and requires ownership, evidence, effectiveness review, and closure. |
| RCA | Uses evidence to support or rule out possible causes and establish the supported cause. | Choose corrective action only after the cause evidence is sufficient to justify the process or control change. |
| 5 Whys | Tests one focused possible-cause path. | Use the evidence-supported point in the why chain, not the first convenient answer, to define the action. |
| Fishbone diagram | Organizes several possible-cause paths for investigation. | Test the relevant branches with evidence before selecting an action. |
| CAR | Formal corrective action request from a customer or internal quality authority. | The CAR records the requested response, ownership, evidence, review, effectiveness, and closure decision. |
| SCAR | Supplier corrective action request. | Use a SCAR when the supplier must investigate, respond, change its process, and provide evidence for internal review. |
| 8D | Structured D1–D8 response for a customer-impacting, repeated, complex, or high-risk issue. | D5 selects corrective actions, D6 implements and verifies them, and D7 extends prevention to similar risks before D8 closure. |
| Corrective action plan | Controlled action-tracking record. | Tracks actions, owners, due dates, evidence, verification, effectiveness, and closure without replacing the originating NCR, RCA, CAR, SCAR, or 8D. |
Corrective action vs CAPA
CAPA means corrective and preventive action. It is broader than a single corrective action because it also addresses potential issues. This guide covers general manufacturing corrective action; 8Dflow is not a regulated CAPA platform or full QMS.
References and standards context
Use these references as background, then apply your own company, customer, product, process, supplier, and industry requirements.
ISO 9001:2015
Quality management system requirements, including nonconformity and corrective action context.
ASQ Quality Glossary — Corrective Action
Definitions for corrective action and related quality terms.
ASQ — Root Cause Analysis
Background on cause analysis, evidence, and its role in broader problem solving.
This guide follows established manufacturing quality frameworks (ISO 9001, AIAG, ASQ definitions) and is reviewed internally before publishing.
This is provided for general manufacturing quality use. Adapt it to your company, customer, product, process, supplier, and industry requirements before use. It is not intended for medical device, pharma, FDA, Part 11, or validated regulated workflows.
When corrective action work moves beyond a document, the hard part is keeping the originating issue, owners, due dates, evidence, verification, effectiveness, and closure decision together. See how 8Dflow is being built to manage corrective actions.
Use the corrective action plan template
Use the matching template page when you need a controlled record for actions, owners, due dates, evidence, implementation verification, effectiveness review, and closure.