A supplier corrective action request (SCAR) should provide enough structure and detail to define the problem, drive effective root cause analysis, and maintain traceability across your QMS, ERP/MES, and supplier systems. Exact formats vary by organization and regulation, but the following elements are typically expected.
1. Administrative and traceability information
- SCAR identifier and revision level
- Date issued and required response dates (interim and final)
- Issuing organization, site, and contact person
- Supplier name, location, and supplier code/vendor ID
- Reference to related records: nonconformance reports, internal deviations, customer complaints, lots/batch numbers, change requests
2. A clear description of the problem
- What is wrong: concise description of the defect or performance issue
- Where it was found: receiving inspection, in-process, final inspection, field, or customer site
- When it occurred: dates, time frame, and detection stage in the process
- How it was detected: inspection method, test, or operational event
- Impact assessment at a high level: potential or actual impact on product quality, safety, delivery, or regulatory commitments, without overstating conclusions
3. Objective evidence and data
- Part numbers, material codes, and descriptions
- Purchase order numbers, line items, and delivery dates
- Lot, batch, heat, or serial numbers for affected units
- Quantities received, inspected, nonconforming, and used
- Measured values and specification limits where applicable
- Inspection records, test reports, or dimensional data (or reference to where they are stored in the QMS/ERP/MES)
- Photos or diagrams if they materially clarify the nonconformance
4. Defined scope and containment expectations
- Statement of known scope at time of issue (e.g., specific lots, time window, production line)
- Explicit request for supplier containment: identification, segregation, and control of potentially affected product at the supplier and in transit
- Expectations for status of material already at your site or at your customer, if applicable
- Required timing for containment results and communication
5. Required supplier response structure
The SCAR should define how the supplier must respond, not just ask for a generic explanation. Common elements:
- Immediate actions: Actions already taken to stop the problem from escaping further, including quarantine, rework, or additional inspection.
- Root cause analysis: A structured description of root cause(s) for both the defect and the escape (why it was not detected earlier). Many organizations require specific methods (5 Whys, fishbone, fault tree) and evidence of data-based analysis.
- Corrective actions: Changes to processes, methods, controls, or training to eliminate the root cause. This should include ownership, due dates, and planned verification.
- Preventive actions (where applicable): Steps to reduce risk of similar issues in related products, lines, or processes.
6. Verification and effectiveness criteria
- How corrective actions will be verified (e.g., updated procedure, revised control plan, capability data, first article inspection, run-at-rate)
- What evidence the supplier must provide (documents, records, data, training evidence)
- Timeframe or number of successful lots/shipments required before the SCAR can be considered for closure, as defined by your internal procedure
7. Documentation and change control expectations
- Requirement to update impacted documents: work instructions, inspection plans, control plans, FMEAs, process flow diagrams, programs, or tooling records
- Expectation that supplier follows its own change control and validation procedures and retains records
- Clarification if any process or design changes require prior approval under your change control, drawing, or specification management processes
8. Regulatory and customer context (where relevant)
In regulated environments or when material flows to aerospace, medical, or similarly controlled applications, the SCAR should at least indicate when additional constraints apply, such as:
- Need to maintain specific records for defined retention periods
- Requirements for notification or approval before rework, concession/use-as-is, or alternative materials
- Any customer-imposed formats, timelines, or reporting expectations the supplier must align with
The SCAR should not imply regulatory compliance or audit outcomes. It is one input into your broader CAPA and supplier management system, not a guarantee of compliance.
9. Expectations for communication and escalation
- Named contact points at both organizations
- Required communication frequency while actions are open
- Escalation path if deadlines, containment, or risk levels are not being met
10. Coexistence with existing systems and data flows
In most brownfield environments, SCARs must coexist with legacy QMS, ERP, MES, and supplier portals. When defining SCAR content, consider:
- Using identifiers that can be referenced across systems (QMS record ID, ERP return material authorization, nonconformance number).
- Ensuring required data fields align with what can be reliably captured from inspection, production, and logistics systems.
- Keeping the SCAR template stable enough to avoid repeated revalidation and retraining, especially where electronic systems are validated.
- Accepting that full replacement of existing supplier quality workflows is often constrained by integration complexity, qualification burden, and supplier readiness. SCAR content should be robust but practical for suppliers operating with varied system maturity.
Overall, a useful SCAR is specific, evidence-based, and structured to support root cause analysis and long-term prevention, while remaining realistic about system integration, supplier capability, and regulatory constraints.
