What this decision should produce
A corrective action request should prevent recurrence, not merely request a replacement or apology.
Keep immediate containment, correction of affected units, root cause, corrective action, and effectiveness verification as separate steps. Scale the investigation to defect risk and recurrence. Do not accept “operator carelessness” as a complete cause when the system allowed the error to occur and escape detection.
Describe the problem against a controlled requirement
Identify supplier, purchase order, product, SKU, lot, quantity, production or delivery date, specification revision, and the exact requirement. Describe the actual result with measurements, defect counts, photos, videos, test records, and sample location. Avoid emotional or broad statements such as “quality is terrible”.
State where and when the problem was detected and how samples were selected. Estimate known affected scope without presenting an assumption as fact. If the issue may affect safety, compliance, or customer use, apply immediate escalation and professional review rather than waiting for a routine report cycle.
Require immediate containment and traceability
Ask the supplier to stop shipment or production where appropriate, identify potentially affected materials and batches, segregate stock, protect the customer, and report counts. Containment is temporary risk control; it does not explain why the defect occurred. Set a short deadline suitable to the risk.
Trace the issue through material lots, machines, molds, shifts, operators, subcontractors, rework, inspection records, and shipments. The scope may be smaller or larger than the originally detected lot. Require evidence for the boundary so unaffected stock is not released by guesswork.
Test root cause and corrective action
Ask why the defect was created and why existing controls failed to detect or prevent it. Methods such as five whys, fishbone analysis, process review, or fault-tree thinking can help, but the method name is less important than evidence. A cause should explain the observed pattern and be testable.
Corrective action may change design, supplier, material control, fixture, process setting, error proofing, maintenance, work instruction, training, test coverage, sampling, or approval. Assign owners and completion dates. Update controlled documents and remove obsolete instructions so the fix exists beyond the report.
Verify effectiveness over time
Define how the buyer or supplier will confirm the defect does not recur: first-piece data, controlled trial, increased sampling, process audit, reinspection, capability result, or performance across several lots. A photograph of one good replacement unit is rarely enough to demonstrate effectiveness.
Close the action only after objective evidence meets the agreed criterion. Link the lesson to future specifications, supplier scorecards, inspection plans, and risk assessments. If the problem repeats, reopen the analysis and examine whether the stated cause or implementation was incomplete.
How the decision works in practice
A shipment of 2,400 pumps has 7 percent leakage in customer testing. The request cites the leak-test requirement, affected lot, method, and samples. The supplier contains finished stock and traces the issue to one fixture whose seal wore unevenly. The deeper cause is that fixture-life limits and daily challenge checks were absent. The supplier replaces the seal, adds a cycle counter and challenge sample, updates the work instruction, and provides three consecutive lot records. Reinspection and later receiving results confirm effectiveness.
What should be true before you continue
Keep immediate containment, correction of affected units, root cause, corrective action, and effectiveness verification as separate steps. Scale the investigation to defect risk and recurrence. Do not accept “operator carelessness” as a complete cause when the system allowed the error to occur and escape detection.
Turn the review into a decision record
Do not mark an item complete because it was discussed. Record the current source, revision, date, owner, and remaining uncertainty so another person can understand why the order moved forward.
| Confirm | Evidence to retain | Risk if unclear |
|---|---|---|
| Supplier, order, SKU, and lot identity | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Writing an emotional complaint |
| Exact requirement and actual result | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Confusing sorting with corrective action |
| Detection method and sample basis | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Accepting “human error” alone |
| Immediate containment and customer protection | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Investigating creation but not escape |
| Affected-scope traceability | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Closing on one good photo |
| Creation and escape root causes | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Failing to update future inspections |
| Corrective action with owners and dates | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Writing an emotional complaint |
| Controlled-document and training updates | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Confusing sorting with corrective action |
| Effectiveness criterion and evidence | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Accepting “human error” alone |
| Closure approval and future control update | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Investigating creation but not escape |
Ask for the information in one controlled message
Replace the bracketed details, remove any item that does not apply, and ask the supplier or project owner to identify deviations instead of replying with a general confirmation.
Subject: How to Write a Supplier Corrective Action Request - evidence request for [product / order]
Hello [supplier or project owner],
We are reviewing this decision for [product, model, quantity, destination, and target date]. Please provide or confirm the following points using the current document revision and identify anything that differs from our request:
- Supplier, order, SKU, and lot identity
- Exact requirement and actual result
- Detection method and sample basis
- Immediate containment and customer protection
- Affected-scope traceability
- Creation and escape root causes
- Corrective action with owners and dates
- Controlled-document and training updates
- Effectiveness criterion and evidence
- Closure approval and future control update
For each answer, please name the supporting file, record, photo, sample, person, or date. Mark open items clearly and propose a completion date. We will use the confirmed information with the current specification, quotation, purchase order, quality plan, or shipment file as applicable.
Thank you,
[Buyer name / company]
What to confirm before moving forward
- Supplier, order, SKU, and lot identity
- Exact requirement and actual result
- Detection method and sample basis
- Immediate containment and customer protection
- Affected-scope traceability
- Creation and escape root causes
- Corrective action with owners and dates
- Controlled-document and training updates
- Effectiveness criterion and evidence
- Closure approval and future control update
Problems that make this decision harder
- Writing an emotional complaint
- Confusing sorting with corrective action
- Accepting “human error” alone
- Investigating creation but not escape
- Closing on one good photo
- Failing to update future inspections
Frequently asked questions
What is the difference between correction and corrective action?
Correction fixes detected units; corrective action addresses the cause so the problem is less likely to recur. Both may be needed.
How fast should a supplier respond?
Set timing by risk: urgent containment may be required immediately, while evidence-based root-cause work may need a realistic agreed period.
Should every minor defect receive a full CAR?
Use risk, frequency, trend, customer impact, and recurrence. Simple corrections may suit isolated low-risk issues, while systemic patterns need deeper action.
Turn the open question into a useful message
Use the checklist and related tool first. If the decision is still unclear, send the facts that change the answer so the conversation can begin with the actual product, order, supplier, and deadline.
- Product or project and the exact decision you need to make
- Target quantity, destination market, and required date
- Current quotation, supplier status, and the evidence already checked
- The remaining risk, mismatch, or question that is blocking progress
This guide supports planning and supplier communication. Product compliance, customs classification, taxes, contracts, and market-specific requirements should be confirmed with qualified professionals.