What this decision should produce
A defect report should help the supplier identify the affected product, reproduce the problem, contain risk, and prevent recurrence.
Identify the affected goods precisely
Record purchase order, supplier, factory, product, model, revision, lot or date code, shipment, carton number, quantity received, quantity inspected, and quantity affected. If several factories, molds, lines, colors, or components are involved, separate them. A statement such as “many products are bad” cannot support containment or root-cause analysis.
Keep the original packaging, labels, and samples needed for investigation. Note when and where the issue was found: incoming inspection, assembly, customer use, transit, or storage. Conditions such as temperature, load, power source, installation method, or elapsed time may be essential to reproducing the failure.
Describe the requirement and the observed result
Link the defect to a specification, drawing, approved sample, test method, artwork, or purchase-order clause. State the expected result and the actual result using measurements or observable facts. For a leak, record test pressure, time, orientation, and leakage location. For a dimension, record nominal, tolerance, measured value, instrument, and sample count.
Use clear photographs with overview, close-up, scale, label, and orientation. Annotate the location without editing away useful context. Video can show intermittent or functional failures, but include a written summary so the evidence remains searchable and understandable.
Classify risk and contain the problem
Classify the defect according to the agreed critical, major, or minor definitions and explain the customer or safety impact. Immediately identify affected stock, shipments in transit, work in progress, and material at the supplier. Containment may include stop-ship, segregation, 100 percent screening, rework, replacement, or customer notification depending on risk.
Do not confuse containment with corrective action. Sorting removes visible defects from one lot; it does not explain why they occurred or prevent another lot from failing. Keep quantities and screening results so the scale of the problem is known.
Request root cause and verifiable corrective action
Ask the supplier to identify occurrence cause, escape cause, and system cause. The analysis should be supported by records, process data, material traceability, maintenance, training, or experiments where appropriate. “Worker carelessness” is rarely a complete root cause because it does not explain why the process allowed and failed to detect the error.
Corrective actions should name an owner, due date, document or process change, and verification method. Require evidence such as revised work instructions, fixture changes, error-proofing, training records, updated control plans, or capability results. Verify effectiveness on later production rather than closing the issue when a form is returned.
How the decision works in practice
A buyer finds 18 leaking lids in a random sample of 200 units from PO 1047, model SSB-750 Rev C, cartons 12-18. The report cites the 30-second inverted leak test, lists the test conditions, and includes labeled photos showing gasket displacement. The supplier segregates the lot, screens all packed goods, and traces the issue to a feeder setting after maintenance. Corrective action adds a gasket-presence sensor, first-piece verification after setup, and an hourly check. The next two production lots are reviewed for effectiveness.
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 |
|---|---|---|
| PO, model, revision, lot, and carton traceability | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Sending only emotional descriptions |
| Received, inspected, and affected quantities | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Using photos without product or lot identification |
| Expected requirement and actual result | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Reporting a percentage without sample size |
| Test conditions, instrument, and measurements | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Closing the issue after sorting |
| Overview and close-up evidence | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Accepting “operator error” as the full root cause |
| Defect severity and user impact | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Failing to verify the next production lot |
| Immediate stock and shipment containment | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Sending only emotional descriptions |
| Occurrence, escape, and system root cause | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Using photos without product or lot identification |
| Corrective-action owner and due date | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Reporting a percentage without sample size |
| Effectiveness verification on later production | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Closing the issue after sorting |
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 Document Product Defects Clearly - 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:
- PO, model, revision, lot, and carton traceability
- Received, inspected, and affected quantities
- Expected requirement and actual result
- Test conditions, instrument, and measurements
- Overview and close-up evidence
- Defect severity and user impact
- Immediate stock and shipment containment
- Occurrence, escape, and system root cause
- Corrective-action owner and due date
- Effectiveness verification on later production
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
- PO, model, revision, lot, and carton traceability
- Received, inspected, and affected quantities
- Expected requirement and actual result
- Test conditions, instrument, and measurements
- Overview and close-up evidence
- Defect severity and user impact
- Immediate stock and shipment containment
- Occurrence, escape, and system root cause
- Corrective-action owner and due date
- Effectiveness verification on later production
Problems that make this decision harder
- Sending only emotional descriptions
- Using photos without product or lot identification
- Reporting a percentage without sample size
- Closing the issue after sorting
- Accepting “operator error” as the full root cause
- Failing to verify the next production lot
Frequently asked questions
Should a defect report include a requested compensation amount?
Keep the technical evidence and commercial claim clearly organized. Cost can be included, but it should not replace root-cause and corrective-action requirements.
How many defect photos are enough?
Use enough to establish identity, location, scale, variation, and repeated examples. Quality matters more than a large folder of unlabelled images.
What if the supplier cannot reproduce the issue?
Share conditions and samples, jointly review the test method, and preserve traceability. An inability to reproduce does not invalidate evidence but may show that more controlled investigation is needed.
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.