Supplier corrective action requests (SCARs): decision records across companies

What does a SCAR record contain?#

A SCAR record contains the request a manufacturer sends to a supplier after a nonconformance, the supplier's response, and the manufacturer's decisions about that response. It usually starts from a receiving inspection failure, a line-side defect or a customer complaint traced back to purchased material.

Read down the last column of the table and the split is plain. The first and last stages are your decisions; the middle is often the supplier's work. That split drives both the value of the record and the rights review.

Why are SCARs valuable decision records?#

SCARs are valuable decision records because they show one company judging another company's reasoning under commercial pressure. The evaluation step, where a supplier quality engineer rejects a weak root cause or accepts a corrective action with conditions, is the kind of judgment AI developers want when building supply chain and quality agents.

Over many years, SCAR history also reveals patterns that no single record shows: which failure modes recur after closure, which corrective actions held, and which supplier relationships ended. That outcome history is what turns a drawer of forms into a dataset.

SCARs also record negotiation. Due dates are extended, containment costs are disputed, and escalations move from engineer to manager to purchasing. Those exchanges teach how real organizations resolve cross-company problems, which clean process documentation never captures.

The supplier confidentiality note#

Supplier confidentiality limits the middle of the SCAR chain. A supplier's root cause analysis can describe its processes, equipment, sub-suppliers and internal failures in detail, and your supply agreement or the supplier's own NDA may treat that content as its confidential information.

The usual approach separates your evaluation from the supplier's submission. Your assessment of the response, written in your own words, normally stays in scope; the supplier's attached 8D, process documents and photos of its plant are excluded unless the terms or a written consent allow them. Supplier names are replaced with stable codes, and anything that singles a supplier out, such as an unusual process or location, is generalized.

Supplier agreements are reviewed with counsel as part of the rights work, in the same way as customer terms. If you issue a supplier quality manual, it may already say how SCAR responses can be used. If it does not, consider adding a clause for future SCARs that lets you keep and analyze responses internally and use them in de-identified form.

What should be screened before licensing SCAR history?#

SCAR history should be screened for supplier content, identities, customer material, money and legal status before any scope is agreed. The list below covers the checks most quality teams need.

• 1Supplier-authored attachments: 8D responses, process flows, control plans and photos.
• 2Supplier identity: names, addresses, contact people and anything that singles them out.
• 3Customer content: drawings and specifications for purchased parts made to your customer's print.
• 4Commercial terms: chargebacks, cost recovery and pricing in the SCAR or linked records.
• 5Personal data: names of your engineers and the supplier's staff.
• 6Legal status: SCARs tied to disputes, recalls or litigation.

How do SCARs connect to NCRs, 8Ds and scorecards?#

SCARs connect upstream to NCRs and downstream to supplier scorecards and sourcing decisions. A SCAR without the NCR that triggered it lacks the evidence, and a SCAR without the scorecard or resourcing outcome lacks the consequence.

Chargebacks deserve a separate look. Cost recovery decisions are useful to model but reveal commercial terms with a named counterparty, so they are usually kept as a categorical field, such as recovered or not recovered, or excluded.

Where does SCAR history live, and how is it exported?#

SCAR history usually lives in a QMS or ERP quality module, with attachments and correspondence spread across email, shared drives and supplier portals. The structured fields come out through the system's reports or database; the attachments and email threads are where most supplier-authored content sits.

Export the structured record first, keyed by SCAR number, with the linked NCR, supplier code, part family, dates, evaluation outcome and closure decision. Bring attachments across only by reference at first, so the rights review can decide which supplier files stay out before anyone copies them.

Check whether the system kept every response round or only the final accepted answer. Rejected rounds hold the evaluation reasoning, the part of the record that is most clearly yours, and they are often overwritten when a supplier resubmits.

Illustrative: an outdoor power equipment assembler scopes its SCAR log#

Illustrative: a fictional assembler of outdoor power equipment buys castings, wire harnesses and plastic housings from a broad supplier base. It tracks SCARs in its QMS, linked to receiving inspection NCRs and a quarterly supplier scorecard.

The VP of quality scopes a package. SCAR forms, evaluation notes, verification results and scorecard changes stay in, with suppliers coded and engineers replaced by roles. Supplier 8D attachments are excluded, as are SCARs on harnesses built to a customer's specification. Chargeback amounts are dropped, but the decision to recover cost is kept as a yes or no field.

Counsel reviews the supply agreements and confirms that the assembler's own evaluation records are not restricted. The resulting package shows how the company judged supplier responses over many years without disclosing any supplier's processes.

How SourceX approaches SCAR records#

SourceX treats SCARs as cross-company records and reviews both directions in the Rights step of the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery): your customers' terms for parts made to their designs, and your supplier agreements for supplier-authored content.

Preparation keeps your decisions and removes supplier identity and attachments. The SourceX Evidence Packet records which suppliers and SCAR types were carved out and who authorized release, and your team approves the final scope before anything is delivered.