Buyers should treat a deviation as a controlled exception, not an informal promise that a molded part is probably usable. Contain the affected material, compare it with the approved specification, assess functional and regulatory risk, and obtain written authority before release. A concession may authorize a narrowly defined nonconformance, but it does not revise the drawing, validate a process, or remove the need for corrective action.
A signed concession should identify exactly what may ship, why it is acceptable for the stated use, which lots or cavities it covers, and when the authorization expires.
01
Define the exception before deciding whether it can be accepted
In a contract injection molding program, the baseline is the released requirement set: drawing revision, material and color callouts, approved sample, inspection plan, packaging requirement, and agreed functional test. A deviation is a measured or observed departure from that baseline. A concession is the buyer’s written, limited authorization to accept a known departure. A supplier’s explanation of a defect is not authorization to ship it.
Start with the missed requirement, how it was verified, and the resulting product risk. Record the characteristic, nominal and tolerance or visual standard, method, actual result or defect description, production period, lot, cavity if applicable, and held quantity. Photographs help with cosmetic defects but do not replace measurements or an agreed visual standard.
Classify the consequence before disposition. Escalate any condition affecting safety, compliance, material identity, traceability, sealing, electrical function, fit, or a critical interface to responsible engineering and quality contacts. Do not make an open-ended ‘use as is’ decision for these conditions. Confirm project-specific requirements for regulated products and end markets.
This approach supports injection molding defect analysis. It stops a sorting decision from becoming an undeclared specification change and gives teams a common record when a symptom returns.

02
Use a four-part evidence package for each deviation
Ask for a deviation request before release. It should identify the part and revision, feature, quantity and traceability range, detection point, containment, inspection evidence, risk assessment, proposed disposition, and requested validity. State whether material has already shipped, been assembled, or mixed with conforming stock. This gives cross-border teams an unambiguous decision record.
Match evidence to the failure mode. For a dimensional departure, request datum scheme, instrument or gauge method, readings or traceable summary, and sample logic. For a cosmetic condition, request viewing conditions, defect-location photos, and severity counts. For function, request the test setup, acceptance condition, and result. Compare material or color evidence with the approved requirement, not an informal substitute standard.
One accepted part does not prove a capable process. NIST defines capability as a comparison of an in-control process output with specification limits, using capability indices [2]. Use capability evidence only when measurement method, stability, distribution, and sample basis suit the part. Set any numerical target, study size, or sampling plan as a project-specific requirement.
For critical-to-quality features, link the request to the control plan. Identify the process or tooling condition under review, containment inspection frequency, and evidence needed for routine release. FDA’s lifecycle validation principles emphasize collecting and evaluating process data from design through commercial production [1].
03
Choose a disposition that matches the risk and the evidence
The table separates common buyer decisions. It is a comparison framework, not a substitute for the contract, applicable law, or buyer technical authority. The correct route depends on use, failure consequence, and available evidence.
A concession should be specific and temporary: identified material, defined condition, and stated shipment or period. To make the new condition routine, use change control to update requirements, review validation impact, revise inspection documents, and communicate the effective revision. Repeated concessions for one cause signal that the process, tool, gauge, or specification needs correction.
Rework is different from concession. It aims to make a nonconforming item meet the released requirement before distribution; the current US device-quality regulation defines it this way [3]. Require an approved instruction, traceability, verification to the original criteria, and confirmation that rework adds no damage or other risk.
| Observed condition | Minimum evidence | Buyer disposition | Control before release |
|---|---|---|---|
| Meets released requirements | Traceable inspection and release record | Accept | Release under the agreed inspection plan |
| Minor, bounded departure with demonstrated no-impact rationale | Measured extent, risk review, lot and cavity traceability | Consider written concession | Segregate and ship only the approved scope |
| Departure can be restored to the released requirement | Approved rework method and post-rework verification | Rework, then re-inspect | Keep rework and verification records with the lot |
| Unknown extent, repeating defect, or material mix risk | Containment report and expanded inspection findings | Hold pending investigation | No release until scope and cause are understood |
| Safety, regulatory, critical function, or traceability impact | Formal engineering and regulatory review as applicable | Reject or escalate | Do not use concession as a shortcut |

04
Link containment to corrective action and process validation
Containment decides what happens to material already made. Corrective action explains why the failure occurred and prevents recurrence. Require both for a systemic or potentially systemic condition. Separate the escape point from the physical cause. For example, flash may relate to the tool, process pressure, parting surface, clamp behavior, resin state, or measurement interpretation; test the relevant hypotheses.
An injection molding defect analysis package should include the problem statement, evidence, traceability scope, timeline, investigation results, correction, effectiveness check, and preventive control-plan or instruction update. Ask how other cavities, earlier lots, and future runs will be checked. After a mold repair, process-window, resin-source, or measurement-method change, agree the injection molding process validation evidence needed before routine release resumes.
Do not let an accepted concession conceal process drift. Compare pre- and post-correction data using the same method where possible. Record the approved condition, containment inspection level, and decision owner.
05
Write concession language that purchasing can enforce
Put the deviation-and-concession workflow in the quality agreement, purchase order terms, or another controlled document. State who may request, review, and approve an exception; whether email is valid; response time; and whether shipment can occur before written approval. Procurement should stop commercial acceptance of a delivery notice or invoice from becoming an engineering approval.
Name the part and revision, condition, traceability range, quantity, evidence, risk rationale, approved use or restriction, disposition, and expiry. State any labeling, separate packing, certificate wording, or shipment notification. A concession must not silently alter warranty, regulatory responsibility, or future criteria.
For injection molding acceptance, close the record after shipment. Confirm what shipped, retain linked inspection and approval records, verify corrective-action outcome, and trend recurrence.

Practical takeaway
Before you move
to the next review.
- Define the released drawing, material, visual, functional, packaging, and inspection requirements that form the acceptance baseline.
- Require a unique deviation request before shipment, with part revision, lot and cavity traceability, affected quantity, and containment status.
- Classify the nonconformance by safety, regulatory, function, fit, traceability, cosmetic, and commercial impact before disposition.
- Request evidence matched to the defect: measurement method and data, visual standard and photos, functional test results, or material records as applicable.
- Authorize a concession only in writing, with an exact scope, required labeling or segregation, approval owner, and expiry condition.
- Require approved rework instructions and verification against original requirements whenever rework is proposed.
- Link recurring or systemic defects to root-cause investigation, corrective action, control-plan updates, and agreed validation evidence before normal release resumes.
- Retain the final shipment record, concession, inspection evidence, and corrective-action closure in the project quality file.
FAQ
Common questions
What is the difference between a deviation and a concession for a molded part?
A deviation is the identified departure from the released requirement. A concession is the buyer’s written, limited approval to accept a defined scope of that departure. A concession does not automatically change the drawing, material specification, or routine production acceptance criteria.
Can a supplier ship nonconforming injection molded parts while waiting for approval?
The contract should decide this explicitly. A prudent default is to hold and segregate the material until the authorized technical and quality contacts provide written direction. If an exception is allowed, the agreed process should define notification, labeling, traceability, and the conditions under which shipment may occur.
When should a buyer request more process-validation evidence after a deviation?
Request additional evidence when the correction changes the tool, process window, resin source, measurement method, or another factor that can affect critical features. The evidence should be proportionate to product risk and should confirm that the corrected process can meet the released requirements consistently.
References
Source material
- [1] U.S. Food and Drug Administration, Process Validation: General Principles and Practices
- [2] National Institute of Standards and Technology, What is Process Capability?
- [3] Electronic Code of Federal Regulations, 21 CFR Part 820 Quality Management System Regulation
This guide is general information for early procurement and engineering discussion. It does not replace product-specific DFM, qualification, validation, regulatory assessment or legal advice.