WHY ENGLISH?
Describe the gap so the supply chain can control it
Use the routes to identify the supplied item and requirement, state the observed nonconformance, protect evidence, contain affected stock and move from correction to verified recurrence prevention.
Open the full contents · See the How English Works hub
Full contents
Identify item
State requirement
Preserve evidence
Control disposition
Verify action
Practice and next steps
Practice and next steps
Practice and next steps
Practice and next steps
Practice and next steps
Practice and next steps
A supplier nonconformance report records that a supplied product, service, process result or document does not meet a specified requirement. English matters because the report must distinguish what was required, what was observed, how much may be affected, what was contained, who may decide disposition and what evidence will prove the issue will not recur.
People searching for supplier nonconformance report, NCR template, supplier corrective action request, rejected material report or how to write a nonconformity often jump too quickly to root cause. The first duty is disciplined description and control. If identity, requirement, evidence and scope are weak, later analysis rests on an unstable record.
NASA's systems-engineering guidance says product verification results and nonconformance reports should capture relevant evidence and corrective action. The JPL supplier portal provides supplier-quality clauses and post-delivery reporting routes, while the U.S. Federal Acquisition Regulation explains official treatment of nonconforming supplies or services. These are authoritative examples of the underlying discipline, not universal contract terms for every buyer.
Use the report map buyer, supplier, purchase order, contract, specification, drawing, revision, item, part number, serial, batch, lot, quantity, receipt, inspection, characteristic, requirement, tolerance, method, equipment, calibration, observation, evidence, deviation, defect, severity, traceability, suspect population, containment, segregation, notification, concession, use-as-is, rework, repair, return, scrap, correction, root cause, corrective action, verification, effectiveness and closure.
Identify the reporting organisation
Fix the buyer site or quality function raising the record to a traceable supplied item and record.
The affected population cannot be controlled when a shared form hides who controls the process.
Use order and genealogy data to state site department and report owner.
Identity example. The receiving-inspection team opens the NCR for the Tuas facility.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why the buyer site or quality function raising the record should remain attached to scope, evidence and authority.
Assign a unique report number
State the identifier linking evidence actions and approvals as a requirement-observation comparison.
The report becomes opinion when email subject lines become the only traceability.
Quote the criterion and use the controlled numbering system.
Evidence example. NCR-26-014 follows the item through disposition and closure.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Name the supplier
Preserve the legal entity responsible under the purchase arrangement while risk and scope are still being evaluated.
Evidence or product escapes when brand distributor and manufacturer are blended.
Contain, label and record contracted supplier and relevant source.
Containment example. The purchase order is with Distributor A while Factory B made the component.
Containment controls exposure; it does not prove cause or permanently correct the process.
Record supplier site
Put the manufacturing or service location connected to the issue through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when all facilities are treated as interchangeable.
Separate correction from prevention and capture exact address or site code.
Disposition example. The affected plating came from the supplier's second approved plant.
Rework, repair, concession, return and scrap are not interchangeable labels.
Match the purchase order
Close the commercial record defining item quantity terms and flow-down requirements on verified effectiveness evidence.
The task list ends before the risk does when the report cites only an invoice.
Define owner, measure and link PO line release and amendment.
Closure example. PO 450012 line 30 specifies the current drawing revision.
A corrective action is credible when the changed system works across an agreed observation period.
Match the contract requirement
Fix the clause or quality condition governing performance and response to a traceable supplied item and record.
The affected population cannot be controlled when generic quality expectations replace agreed obligations.
Use order and genealogy data to quote the exact clause and revision.
Identity example. The contract requires notification before shipment of known nonconforming product.
Good traceability lets the response expand far enough without quarantining the whole world.
Identify the item
State the product service document or process output affected as a requirement-observation comparison.
The report becomes opinion when a family name hides variants.
Quote the criterion and record description part number and configuration.
Evidence example. The issue concerns bracket P-118 revision C.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why the product service document or process output affected should remain attached to scope, evidence and authority.
Capture serial and lot data
Preserve unit and population traceability while risk and scope are still being evaluated.
Evidence or product escapes when one failed sample cannot be connected to stock.
Contain, label and list serial batch heat or date codes.
Containment example. Serials 4102 to 4140 share heat lot H77.
Containment controls exposure; it does not prove cause or permanently correct the process.
Record received quantity
Put the amount delivered under the relevant shipment through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when the defective count lacks a denominator.
Separate correction from prevention and state total inspected and accepted status.
Disposition example. Four of eighty units failed receiving inspection.
Rework, repair, concession, return and scrap are not interchangeable labels.
Record affected quantity
Close confirmed and potentially affected material on verified effectiveness evidence.
The task list ends before the risk does when only the observed failures are contained.
Define owner, measure and separate known defect from suspect population.
Closure example. Four are confirmed and seventy-six same-lot units remain suspect.
A corrective action is credible when the changed system works across an agreed observation period.
Record discovery point
Fix where and when the issue was detected to a traceable supplied item and record.
The affected population cannot be controlled when timing is omitted from containment decisions.
Use order and genealogy data to state process stage date and location.
Identity example. The mismatch was found during final assembly before energisation.
Good traceability lets the response expand far enough without quarantining the whole world.
Name the detector
State the role or system that identified the issue as a requirement-observation comparison.
The report becomes opinion when personal blame replaces traceable observation.
Quote the criterion and record qualified role and method.
Evidence example. A calibrated coordinate-measuring-machine inspection flagged the dimension.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Quote the requirement
Preserve the exact acceptance criterion allegedly not met while risk and scope are still being evaluated.
Evidence or product escapes when phrases such as wrong size lack a standard.
Contain, label and cite drawing clause value unit and tolerance.
Containment example. Drawing C requires 12.00 plus or minus 0.05 millimetres.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why the exact acceptance criterion allegedly not met should remain attached to scope, evidence and authority.
Check revision status
Put the authorised version applicable to the order and item through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when the newest drawing is applied retrospectively.
Separate correction from prevention and match PO date configuration and change notice.
Disposition example. Revision B governed the ordered batch despite revision C now being released.
Rework, repair, concession, return and scrap are not interchangeable labels.
Identify characteristic
Close the measurable or observable property under review on verified effectiveness evidence.
The task list ends before the risk does when the whole item is called bad.
Define owner, measure and name feature location and function.
Closure example. Hole centre distance on datum A is the nonconforming characteristic.
A corrective action is credible when the changed system works across an agreed observation period.
State the observed result
Fix the factual measurement or condition found to a traceable supplied item and record.
The affected population cannot be controlled when cause judgement is mixed into description.
Use order and genealogy data to report value unit location and method.
Identity example. The distance measured 12.14 millimetres at 20 degrees Celsius.
Good traceability lets the response expand far enough without quarantining the whole world.
Calculate the deviation
State the difference from the specified limit as a requirement-observation comparison.
The report becomes opinion when raw numbers force every reader to recompute risk.
Quote the criterion and state magnitude and direction accurately.
Evidence example. The result is 0.09 millimetres above the upper limit.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Identify inspection method
Preserve the controlled way the observation was produced while risk and scope are still being evaluated.
Evidence or product escapes when visual calibrated and destructive methods are blurred.
Contain, label and cite procedure and sampling plan.
Containment example. Inspection followed WI-17 and sampling plan level II.
Containment controls exposure; it does not prove cause or permanently correct the process.
Identify equipment
Put the instrument fixture software or reference used through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when measurement credibility is assumed.
Separate correction from prevention and record asset ID range resolution and calibration status.
Disposition example. CMM asset 03 was within calibration through December.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why the instrument fixture software or reference used should remain attached to scope, evidence and authority.
Check measurement uncertainty
Close whether the result and method can support the conformity decision on verified effectiveness evidence.
The task list ends before the risk does when a near-limit result is treated as exact.
Define owner, measure and apply the agreed decision rule.
Closure example. The uncertainty band does not cross the upper acceptance limit.
A corrective action is credible when the changed system works across an agreed observation period.
Preserve photographs
Fix visual evidence with scale orientation and identity to a traceable supplied item and record.
The affected population cannot be controlled when uncaptioned images cannot be linked to the item.
Use order and genealogy data to label date view and report number.
Identity example. Photo 2 shows the damaged seal beside serial 4108.
Good traceability lets the response expand far enough without quarantining the whole world.
Preserve samples
State physical evidence needed for analysis or customer review as a requirement-observation comparison.
The report becomes opinion when failed parts are reworked before cause work.
Quote the criterion and tag and quarantine representative units.
Evidence example. Two failed and one conforming comparator are held for laboratory review.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Preserve digital evidence
Preserve test files logs images and metadata while risk and scope are still being evaluated.
Evidence or product escapes when screenshots replace source data.
Contain, label and lock native files and checksums.
Containment example. The raw test trace is stored under the NCR record.
Containment controls exposure; it does not prove cause or permanently correct the process.
Separate nonconformance from defect
Put failure to meet a requirement versus broader product-quality or safety implications through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when every deviation is called dangerous.
Separate correction from prevention and use contract and risk language precisely.
Disposition example. The dimension is nonconforming; functional effect awaits engineering evaluation.
Rework, repair, concession, return and scrap are not interchangeable labels.
Classify severity carefully
Close risk-based priority under the organisation's procedure on verified effectiveness evidence.
The task list ends before the risk does when major and critical become emotional adjectives.
Define owner, measure and apply defined criteria.
Closure example. The issue is major because it can prevent assembly but is detected before use.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why risk-based priority under the organisation's procedure should remain attached to scope, evidence and authority.
Assess immediate safety risk
Fix potential harm requiring urgent control or notification to a traceable supplied item and record.
The affected population cannot be controlled when quality paperwork delays protection.
Use order and genealogy data to use the appropriate safety escalation.
Identity example. Shipments stop while engineering checks installed units.
Good traceability lets the response expand far enough without quarantining the whole world.
Define the suspect population
State all material that could share the causal condition as a requirement-observation comparison.
The report becomes opinion when only the failed sample is quarantined.
Quote the criterion and trace common process equipment material and time window.
Evidence example. All parts plated on line 2 since the bath change are suspect.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Contain on-site stock
Preserve actions preventing unintended use of buyer-held material while risk and scope are still being evaluated.
Evidence or product escapes when a warning email substitutes for physical control.
Contain, label and segregate label block and count.
Containment example. Warehouse stock moves to a locked quarantine location.
Containment controls exposure; it does not prove cause or permanently correct the process.
Contain work in process
Put material already inside production through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when receiving inspection is the only search point.
Separate correction from prevention and trace every internal location.
Disposition example. Assembly identifies six units waiting at station 4.
Rework, repair, concession, return and scrap are not interchangeable labels.
Contain finished goods
Close completed items incorporating suspect supply on verified effectiveness evidence.
The task list ends before the risk does when component records do not reach parent serials.
Define owner, measure and use genealogy and shipment holds.
Closure example. The ERP links the bracket lot to twelve finished devices.
A corrective action is credible when the changed system works across an agreed observation period.
Contain supplier stock
Fix unshipped and in-process material at the supplier to a traceable supplied item and record.
The affected population cannot be controlled when buyer containment is assumed sufficient.
Use order and genealogy data to require supplier segregation and status report.
Identity example. The supplier blocks two pallets and one active production order.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why unshipped and in-process material at the supplier should remain attached to scope, evidence and authority.
Contain the distribution chain
State items already shipped onward as a requirement-observation comparison.
The report becomes opinion when post-delivery risk remains hidden.
Quote the criterion and notify approved channels and trace recipients.
Evidence example. Three service centres receive serial-specific hold instructions.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Record containment timing
Preserve when each control became effective while risk and scope are still being evaluated.
Evidence or product escapes when actions appear complete without exposure window.
Contain, label and timestamp discovery notification and hold.
Containment example. The shipping block took effect forty minutes after detection.
Containment controls exposure; it does not prove cause or permanently correct the process.
Notify the right roles
Put quality engineering procurement operations safety and customer interfaces as applicable through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when everyone is copied but no one owns decisions.
Separate correction from prevention and use the escalation matrix.
Disposition example. Product safety leads installed-base evaluation while purchasing contacts the supplier.
Rework, repair, concession, return and scrap are not interchangeable labels.
Write the supplier notification
Close a precise request for acknowledgement containment and response on verified effectiveness evidence.
The task list ends before the risk does when an angry email weakens facts and deadlines.
Define owner, measure and state identifiers requirement evidence quantity and due dates.
Closure example. The notice asks for twenty-four-hour containment confirmation.
A corrective action is credible when the changed system works across an agreed observation period.
Separate correction
Fix action on the detected nonconforming item to a traceable supplied item and record.
The affected population cannot be controlled when sorting or rework is called root-cause elimination.
Use order and genealogy data to name immediate item-level treatment.
Identity example. The supplier replaces the four failed units.
Good traceability lets the response expand far enough without quarantining the whole world.
Separate corrective action
State action eliminating cause to prevent recurrence as a requirement-observation comparison.
The report becomes opinion when training is promised before cause is known.
Quote the criterion and connect action to a verified causal mechanism.
Evidence example. Fixture redesign prevents the part from seating in the wrong orientation.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why action eliminating cause to prevent recurrence should remain attached to scope, evidence and authority.
Avoid premature cause
Preserve a theory stated before evidence supports it while risk and scope are still being evaluated.
Evidence or product escapes when the operator is blamed from one observation.
Contain, label and mark hypotheses and investigation status.
Containment example. Incorrect fixture loading remains a hypothesis pending recreation tests.
Containment controls exposure; it does not prove cause or permanently correct the process.
Control disposition authority
Put the people authorised to decide use rework repair return or scrap through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when the supplier approves its own exception without buyer authority.
Separate correction from prevention and follow contract and quality roles.
Disposition example. Buyer engineering and quality approve a concession within delegated limits.
Rework, repair, concession, return and scrap are not interchangeable labels.
Use return to supplier
Close sending material back under controlled records on verified effectiveness evidence.
The task list ends before the risk does when return closes the issue automatically.
Define owner, measure and preserve traceability and response duties.
Closure example. The return note references the NCR and serial list.
A corrective action is credible when the changed system works across an agreed observation period.
Use rework precisely
Fix processing that brings the item fully into specified conformity to a traceable supplied item and record.
The affected population cannot be controlled when repair and rework are treated as synonyms.
Use order and genealogy data to cite approved instructions and reinspection.
Identity example. The hole is re-machined to the drawing and inspected again.
Good traceability lets the response expand far enough without quarantining the whole world.
Use repair precisely
State action making the item acceptable for intended use without fully restoring specification as a requirement-observation comparison.
The report becomes opinion when a repair is performed without design authority.
Quote the criterion and obtain approved repair data.
Evidence example. Engineering authorises a bonded insert for named serials.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Use use-as-is carefully
Preserve acceptance of a known departure based on authorised evaluation while risk and scope are still being evaluated.
Evidence or product escapes when schedule pressure becomes technical justification.
Contain, label and document function safety interface and approval.
Containment example. Analysis shows the oversized clearance does not impair the limited application.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why acceptance of a known departure based on authorised evaluation should remain attached to scope, evidence and authority.
Use concession or deviation correctly
Put permission for a defined nonconforming condition or planned departure through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when temporary approval becomes a permanent specification change.
Separate correction from prevention and state quantity serials period and conditions.
Disposition example. The concession applies only to twenty units on one order.
Rework, repair, concession, return and scrap are not interchangeable labels.
Use scrap controls
Close irreversible prevention of unintended use where required on verified effectiveness evidence.
The task list ends before the risk does when scrap material returns silently to stock.
Define owner, measure and record destruction or controlled disposal.
Closure example. Rejected safety-critical parts are physically rendered unusable.
A corrective action is credible when the changed system works across an agreed observation period.
Plan sorting
Fix screening a population with a capable method to a traceable supplied item and record.
The affected population cannot be controlled when one hundred percent inspection is assumed infallible.
Use order and genealogy data to define characteristic equipment acceptance and records.
Identity example. The supplier sorts all 600 units with a validated gauge.
Good traceability lets the response expand far enough without quarantining the whole world.
Verify replacement material
State confirming new supply meets requirement and is properly identified as a requirement-observation comparison.
The report becomes opinion when replacement equals acceptance.
Quote the criterion and inspect to an approved heightened plan.
Evidence example. The first three replacement lots receive full dimensional review.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Request root-cause analysis
Preserve evidence-based explanation of occurrence and escape while risk and scope are still being evaluated.
Evidence or product escapes when a five-whys form is demanded for every trivial issue without context.
Contain, label and scale depth to risk and recurrence.
Containment example. The supplier investigates both plating variation and final-inspection escape.
Containment controls exposure; it does not prove cause or permanently correct the process.
Investigate occurrence cause
Put why the product or process became nonconforming through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when escape from detection is the only cause discussed.
Separate correction from prevention and trace process conditions and controls.
Disposition example. Bath concentration drifted because automatic dosing was disabled.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why why the product or process became nonconforming should remain attached to scope, evidence and authority.
Investigate escape cause
Close why existing controls did not detect or prevent release on verified effectiveness evidence.
The task list ends before the risk does when the inspector is blamed without system analysis.
Define owner, measure and review plan method frequency and reaction.
Closure example. Sampling did not include the feature after the control-plan revision.
A corrective action is credible when the changed system works across an agreed observation period.
Investigate systemic cause
Fix management or process conditions enabling occurrence and escape to a traceable supplied item and record.
The affected population cannot be controlled when one local fix leaves wider weakness.
Use order and genealogy data to examine change control training maintenance and oversight.
Identity example. Document revision removed the inspection without cross-functional approval.
Good traceability lets the response expand far enough without quarantining the whole world.
Require evidence for causes
State data tests records and recreation supporting the causal statement as a requirement-observation comparison.
The report becomes opinion when a plausible narrative becomes accepted truth.
Quote the criterion and ask what would falsify the theory.
Evidence example. Recreated dosing failure produces the same thickness pattern.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Build corrective actions
Preserve changes matched directly to verified causes while risk and scope are still being evaluated.
Evidence or product escapes when more care and retraining are the only actions.
Contain, label and alter process error-proofing control and governance as needed.
Containment example. An interlock prevents operation when dosing is disabled.
Containment controls exposure; it does not prove cause or permanently correct the process.
Assign owners and dates
Put accountability for each action through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when the supplier gives one vague completion month.
Separate correction from prevention and name role deliverable and due date.
Disposition example. Process engineering validates the interlock by 18 November.
Rework, repair, concession, return and scrap are not interchangeable labels.
Verify implementation
Close proof that the promised action actually exists and is used on verified effectiveness evidence.
The task list ends before the risk does when a revised procedure attachment closes the record.
Define owner, measure and inspect records equipment and practice.
Closure example. An audit observes three batches using the new interlock and log.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why proof that the promised action actually exists and is used should remain attached to scope, evidence and authority.
Verify effectiveness
Fix evidence that recurrence and escape risk have been reduced to a traceable supplied item and record.
The affected population cannot be controlled when completion is mistaken for effectiveness.
Use order and genealogy data to define measures period and acceptance criteria.
Identity example. Ten consecutive lots meet capability and audit requirements.
Good traceability lets the response expand far enough without quarantining the whole world.
Control recurrence
State using history to recognise patterns across parts suppliers and sites as a requirement-observation comparison.
The report becomes opinion when each NCR is treated as isolated.
Quote the criterion and trend codes and common causes.
Evidence example. Three gasket failures from one supplier trigger a wider process review.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Update risk and controls
Preserve feeding lessons into specifications plans audits and supplier monitoring while risk and scope are still being evaluated.
Evidence or product escapes when the NCR closes without changing prevention.
Contain, label and revise affected system documents.
Containment example. The receiving plan adds a temporary tightened inspection level.
Containment controls exposure; it does not prove cause or permanently correct the process.
Evaluate supplier performance
Put proportionate use of the record in sourcing and development decisions through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when one minor issue blacklists a supplier or repeated issues vanish.
Separate correction from prevention and consider severity recurrence responsiveness and effectiveness.
Disposition example. A responsive containment record offsets none of the need to fix repeated escapes.
Rework, repair, concession, return and scrap are not interchangeable labels.
Communicate without blame
Close firm factual language that supports joint control on verified effectiveness evidence.
The task list ends before the risk does when accusation causes defensiveness and obscures requirements.
Define owner, measure and criticise the gap and evidence.
Closure example. The report states the tolerance failure and required response without guessing motive.
A corrective action is credible when the changed system works across an agreed observation period.
Protect confidential information
Fix controlled use of drawings data and customer identities to a traceable supplied item and record.
The affected population cannot be controlled when the whole NCR is forwarded beyond need.
Use order and genealogy data to share minimum necessary information securely.
Identity example. Supplier analysts receive the relevant drawing excerpt under agreed controls.
Did You Know? NASA product-verification guidance connects nonconformance reports with verification evidence and corrective actions, showing why observation, disposition and follow-up should remain traceable. This is why controlled use of drawings data and customer identities should remain attached to scope, evidence and authority.
Write a bounded closure
State what was corrected what cause was addressed and what evidence supports effectiveness as a requirement-observation comparison.
The report becomes opinion when closed means forgotten.
Quote the criterion and summarise scope disposition action and monitoring.
Evidence example. The named lots were replaced and the validated process control remained effective for ten lots.
A factual nonconformance statement is firm because another competent reader can reproduce it.
Retain the record
Preserve the auditable history of evidence decisions and approvals while risk and scope are still being evaluated.
Evidence or product escapes when email fragments cannot reconstruct the event.
Contain, label and index the report attachments and signatures.
Containment example. The quality system links inspection data concession SCAR and closure review.
Containment controls exposure; it does not prove cause or permanently correct the process.
Learn the transferable skill
Put requirement-observation-action reasoning useful beyond manufacturing through authorised disposition and cause analysis.
The wrong role decides or the wrong cause is fixed when NCR writing is treated as form filling.
Separate correction from prevention and practise fact scope and verification.
Disposition example. Students can report a wrong book shipment without blaming the packer.
Rework, repair, concession, return and scrap are not interchangeable labels.
A worked example
Receiving inspection writes supplier sent bad parts and asks for root cause by tomorrow. The note gives no drawing revision, measurement, equipment, lot, quantity, suspect population or containment instruction. The supplier sorts the four visible failures but ships more from the same process.
A defensible NCR identifies the order, item and lot; quotes the exact requirement; records calibrated measurements; defines confirmed and suspect quantities; blocks related stock; assigns disposition authority; requests occurrence and escape analysis; and closes only after implementation and effectiveness evidence.
English keeps the relationship professional and the risk controlled. The report says what failed, where the requirement lives, how the observation was made, what may be affected and what proof is needed next. It does not need blame to be firm.
A practical checklist
- Buyer supplier and PO exact
- Item revision and lot traceable
- Requirement quoted precisely
- Observation method and units complete
- Evidence preserved
- Known and suspect quantities separated
- Safety and containment immediate
- Disposition authority controlled
- Correction and corrective action distinct
- Occurrence escape and systemic causes tested
- Implementation and effectiveness verified
- Closure preserves monitoring and records
Advice for students, parents and young adults
Students can practise with a harmless delivery error: twelve blue folders were ordered and ten green folders arrived. State order evidence, observed quantity, affected scope and a reasonable correction without accusing the packer.
Parents can reinforce a useful habit: describe first, explain later. What was required? What did you observe? How do you know? What needs to be protected while cause is investigated?
Real nonconformances may involve safety, regulation, contracts and proprietary technical data. Follow the organisation's authorised quality process and qualified engineering, legal or safety advice.
Frequently asked questions
What is a supplier nonconformance?
A supplied product, service, process output or document that does not meet a specified requirement.
Is a nonconformance the same as a defect?
Not always. Nonconformance is a departure from a requirement; defect and safety classifications may involve additional definitions and consequences.
What is containment?
Immediate control of confirmed and potentially affected material so it is not used or shipped unintentionally while the issue is evaluated.
What is the difference between correction and corrective action?
Correction deals with the detected item or condition. Corrective action addresses the cause to prevent recurrence.
Can a supplier approve use-as-is?
Authority depends on the contract and quality system. The party with delegated design or acceptance authority must control the decision.
When should an NCR close?
After affected material is controlled, authorised disposition is complete, required causes and actions are addressed and effectiveness evidence satisfies defined criteria.
The deeper English lesson
Supplier-nonconformance English is requirement-to-control language. It makes the gap observable, bounds the affected population, separates immediate correction from causal prevention and turns closure into an evidence decision rather than a calendar event.
Useful next reading
Continue with writing a root cause analysis, writing a procurement specification, writing a workplace incident report, career vocabulary, and the How English Works.