Supplier Corrective Action Request: Draft a SCAR With AI

A SCAR needs to state the problem with evidence, the requirement that was missed, an immediate containment ask, a request for the supplier's own root cause (including why the defect escaped), dated actions, and a test that shows the fix worked. Without those, you get a one-line apology and the same defect next month.

The weak point is almost always the middle: the request that says "please investigate and respond" invites a surface answer. A good request makes the shallow answer visibly incomplete, because it asks for specific things a shallow answer cannot supply.

Follow me on Instagram@sagnikteaches

A defect worth a SCAR: 38 brackets with wrong hole spacing

Say a solar installer buys 200 galvanised mounting brackets a month from a twelve-person metal fabricator. The drawing calls for two holes 150 mm apart with a tolerance of plus or minus 0.5 mm. On receipt, the installer measures 30 brackets from the lot under an incoming sampling plan and finds 6 with spacing between 151.2 and 151.8 mm. The remaining brackets are then 100 per cent checked: 38 in the lot of 200 (19 per cent) are out of tolerance. They do not fit the rail on site, and two crews have already been delayed.

Connect on LinkedInSagnik Bhattacharya

The cost so far, illustrative: 38 brackets at $6.80 is $258.40, plus three hours of sorting at $28 an hour ($84), so $342.40, not counting two delayed crew days. The same fault in the previous lot was dealt with by email and a verbal "sorry, we'll watch it". That is the pattern a SCAR exists to stop. If the lot was flagged by sample first, an AQL sampling plan for incoming goods explains how those sample sizes are chosen, and a non-conformance report is the internal record the SCAR sits on top of.

Subscribe on YouTube@sagnikteaches

Build the evidence pack before you write a word

The supplier will respond to what they can see. A request that arrives with a clear evidence pack is harder to wave away and easier to act on. Gather five things:

1. The requirement. The drawing page with the tolerance, the purchase order and the revision of both. Write the revision letter.
2. The measurements. A table of the failed pieces with the measured value and the instrument used, plus a few good pieces for comparison.
3. Photographs. The part on the gauge or calliper showing the reading, and the parts laid out by lot, with the delivery note visible.
4. Traceability. Lot number, delivery note, date received, quantity received, quantity checked, quantity rejected.
5. History. Any earlier NCR or email about the same defect, with dates.

Keep the pack as one folder with a one-page index. If you match delivery notes to orders as goods arrive, the receipt dates and quantities are already to hand, with no hunting through emails. Where your measurements were taken with a hand calliper, say so and give its resolution; a supplier with a coordinate machine will test your evidence, and you want it to survive.

The sections of a request that gets a real answer

Use a one-page form with the same sections each time. Suppliers learn it, and you can compare requests across years.

The root-cause section does the most work. Ask for two answers: why the defect occurred, and why it escaped to you. A supplier who explains why a hole was drilled in the wrong place but not why nobody noticed has only found half of it. An inspection step that did not catch 38 of 200 is a second cause, and it needs its own action.

Containment: what you ask for in the first two days

Containment protects you while the real fix is being found. State exactly what you want rather than "please contain". For the brackets:

• Check all finished stock at the supplier for this part and report the quantity checked and rejected within two working days.
• Identify any lots in transit to us and any shipped in the last 30 days, with lot numbers.
• Replace the 38 rejected pieces with checked parts, and mark the delivery "100 per cent inspected" with the inspection record attached.
• Continue to check all pieces of this part until the corrective action is verified.

Containment is also where you decide what you do on your side: quarantine the lot, tag the 38 pieces, and arrange return and credit. For the paperwork on returned goods, a small manufacturer's RMA process covers returns, repairs and credits in order.

The letter that goes with the form

A form on its own can feel like a charge sheet. A short cover note, written by you and polished by an assistant if you wish, sets the tone: firm on facts and open on cause.

Subject: SCAR 2026-07: bracket hole spacing, lot 4417

Hi [first name],

We found 38 of 200 brackets from lot 4417 with hole spacing between
151.2 and 151.8 mm; the drawing (revision C) requires 150 mm +/- 0.5.
Measurements and photos are attached. This is the second lot with this
fault, so I am sending a formal request.

Please do three things:
1. By [date, 2 working days]: check your stock and any goods in transit
   and tell us how many are affected.
2. By [date, 10 working days]: send your root cause, covering why it
   happened and why it was not caught before despatch.
3. By [date, 30 working days]: send evidence that the fix is in place.

We will check the next three lots against the spacing. If you need
anything from us (a clearer drawing, a gauge, a sample), please say.

Thanks,
[your name]

The line "if you need anything from us" matters. It leaves room for a cause on your side, and you will sometimes find one. Keep every figure and date as it is in your own records; the assistant should format, not recalculate.

Let the assistant draft the request from your NCR

Paste your NCR text with the supplier name and prices removed, and give the assistant your standard section headings.

Draft a supplier corrective action request from the NCR below, using
these sections: Identification, Problem, Containment, Root cause (ask
for why it occurred AND why it escaped), Corrective action, Evidence
requested, Closure check. Use only facts in the NCR. Where a fact is
missing, write "MISSING: [what]". Neutral tone, no blame, no
guesses at the cause. Under 350 words.

[paste NCR]

The reply (illustrative) is a tidy form. Fix three things: it may state a revision letter you did not give (check against the drawing), it may write a cause such as "likely operator error" despite the instruction (delete it), and it may set due dates that do not match your agreement. The root-cause section should ask questions only. Anything that hands the supplier an answer risks an easy "we agree" in reply.

What a weak answer looks like, and what a good one does

When the reply comes, compare it to the standard you set. Here are two replies to the same request (illustrative).

Weak: "We apologise for the error. The operator did not follow the drawing. He has been spoken to and retrained. We will take more care in future." This names a person, offers no mechanism and gives nothing you can check. It also leaves untouched the question of why nobody caught 19 per cent of a lot.

Better: "Occurrence: the lot was split across two drilling stations; the program on station 2 was written to revision B (hole spacing 151.5) and not updated when revision C was issued on 3 March, and about a fifth of the lot ran on that station. Escape: final inspection checks a sample of five against overall length only; hole spacing is not on the inspection sheet. Actions: station 2 program corrected and checked on first-off (owner: production lead, done 12 April); hole spacing added to the final inspection sheet with a go/no-go gauge (owner: quality, due 19 April); all open drawings checked against revision list (owner: office, due 30 April)."

The better reply names a mechanism (a drawing revision not carried to a machine program), separates occurrence from escape, gives owners and dates, and produces records you can ask to see. If you cannot tell which of the two you have received, use a short test: could someone else, reading only this reply, make sure the defect cannot happen again? If not, send it back with one specific question.

Questions that push past the first answer

When a reply stops at "operator error" or "human error", ask: what in the process allowed that error to happen, and what stops it happening next time even if the operator is new? A good corrective action changes something physical or procedural, such as a fixture, a gauge, a checklist or a revision control step, and does not depend on people being more careful. Ask "how did the program on station 2 come to hold the old spacing?" Each follow-up question takes one line in your reply and tends to produce the real cause in the second round.

Due dates and the reminder routine

A request without a date drifts. Put every date in a small tracker with the supplier, the SCAR number, the stage, the due date and the status. A sheet is enough, and a chase sheet for purchase orders works in the same way. Set reminders two working days before a due date and on the day after it passes.

Subject: SCAR 2026-07: root cause due tomorrow

Hi [first name],

A reminder that the root cause for SCAR 2026-07 is due on [date]. If
you need more time, tell me today and suggest a new date, and I'll note
it. Lot 4418 is due next week and I will check hole spacing on every
piece in it.

Thanks,
[your name]

Let an assistant draft the three reminder texts once in your voice, and use your email or task tool to send them on schedule. A missed date is not a punishment event; it is a prompt to ask what is stopping them. A supplier who goes quiet after a request deserves a phone call, not a fourth email, and a supplier who misses two dates in a row has told you something about how they treat quality.

Closing the request: three clean lots, not a signature

A SCAR closes when the evidence is received and the fix has been proved over time, not when the form comes back. Define closure in the request itself: "closed after three consecutive lots with zero hole-spacing rejections and receipt of the updated inspection sheet." Keep the inspection going in the meantime, and note each lot's result in the tracker.

For the bracket lots, lot 4418 passed a 100 per cent check on arrival, and lots 4419 and 4420 passed with all 30 sampled pieces in tolerance. The tracker shows three clean lots, the updated sheet is in the folder, and the status changes to closed with a date. If lot 4420 had shown a single failure, the request stays open and goes back to the root cause, because the first fix did not hold. Record closure in the supplier's scorecard; a supplier scorecard for delivery and quality turns repeated SCARs into a figure you can use at the next review.

Use the assistant to read the reply against your standard

The second place an assistant helps is on the way back. Paste the supplier's reply (with names removed) beside your request and ask it to check the reply against the sections you asked for. It is quick at spotting what is missing, and tired people miss that sort of thing at the end of a long day.

Here is a supplier corrective action request and the supplier's reply.
For each section of the request, say whether the reply (a) answers it
fully, (b) answers it partly, or (c) does not answer it. For "partly"
and "no", write one follow-up question I can send. Flag any root cause
that names a person or says "more care", and say what is missing: an
owner, a date, a changed process, or evidence. Do not rewrite their reply.

A typical result (illustrative) lists "Containment: answered fully, 212 checked, 14 rejected; Root cause: occurrence answered, escape not answered; Corrective action: no owner named for action 2; Evidence: none attached." You get four follow-up questions in under a minute, and you still decide whether the answer is good enough. The assistant has no view on whether a fixture change is realistic for a small shop, so use your own knowledge of the process before you push for it.

One request or several: when to bundle

If a supplier's lot has three separate defects, send three requests, not one. A single form with three problems produces a single muddled answer, and it cannot close until the last item is fixed. Equally, do not send a new request for every individual rejected piece: one request covers one defect type and one lot, with later lots added to the same request as repeat evidence. For a defect that keeps recurring across several lots, note the count in the problem section ("third lot in four months") because repetition changes how seriously a supplier treats the request, and how hard you push on the second part of the root cause.

When the cause turns out to be yours

Sometimes the supplier's answer is that they made the part to the drawing and the drawing was wrong. Check it. Open your own file, compare revisions, and look at whether the tolerance can be measured with the equipment the supplier has. In the bracket case, imagine the reply had said that revision C still showed 151.5 mm in the side view and 150 mm in the plan view, and station 2 had been set from the side view. A request that began with a supplier fault would then become an internal correction: fix the drawing, issue a revision, tell the supplier what changed, and replace or sort the lot at your own cost. Say so plainly in your reply and close the request with the cause recorded as customer drawing error. A supplier who sees you accept your side of a cause is more willing to be honest about theirs in the next request.

A quick sum for the effectiveness check

An effectiveness check needs a number, or it becomes a feeling. Decide before you send the request how many pieces you will check and what result closes it. For the brackets, sampling 30 pieces from each of three lots would be 90 pieces. If the supplier's true defect rate had stayed at 19 per cent, the chance that all 90 pass is vanishingly small, so a clean run is strong evidence that something changed. If the defect rate had fallen to 2 per cent, however, a 30-piece sample would often pass by luck: the chance of finding no bad piece among 30 is roughly 55 per cent (0.98 raised to the 30th power). That is the reason for a 100 per cent check, or a larger sample, for the first lot after a fix, then a normal sample once the evidence builds. Write the sample size in the closure line so the supplier knows what clears the request.

A request that blamed one operator and fixed nothing

Imagine a buyer who sends a request about a batch of mislabelled cartons. The reply says the packer misread a label, and the buyer, wanting to move on, closes it. Two months later the same fault returns, packed by a different person. When the buyer goes back and asks why the label could be misread, the answer is that two product codes differ by one digit and are printed in the same font on adjacent shelves, a risk the supplier's staff had lived with for years. The first closure accepted a person as the cause and so left the process alone.

The repair is to reopen the request, ask for a change to the shelf layout and the label design, and keep it open for three lots. The lesson is that any answer which depends on someone being more careful has not found the cause, and a request that closes on such an answer will be back. If you use the 8D format for your own customers, answering a customer complaint with an 8D report uses the same logic from the other side of the table.

Keeping the relationship intact

A request is not a verdict on a supplier, and small suppliers often react badly to forms that read like legal notices. Phone first if the issue is serious, send the form straight after, and thank them when a response is thorough. Note what a good answer looked like and tell them: "your last reply on spacing was exactly the sort of detail we need." Suppliers who feel treated fairly give honest causes; suppliers who feel blamed give short ones.

Keep cost recovery out of the form. If the defect cost you money and your terms allow a claim, send a separate note that refers to the order terms and attaches the cost breakdown ($342.40 in the bracket case, plus any delay costs you can document). Mixing money into a quality request makes the supplier defensive about the cause, which is the one thing you need them to be open about.

Questions about writing a SCAR

When is a SCAR worth sending instead of an email?

Send one when the defect is repeated, affects safety or fit, costs real money or reaches a customer. A one-off cosmetic issue with a fast fix can stay an email. A formal request creates a record, a due date and a closure test, which you will want if the same fault returns or if a customer later asks how you control suppliers.

How long should a supplier have to respond?

A workable starting point is containment within one to two working days, a root-cause answer within ten and implemented actions within thirty, then an effectiveness check over the next few lots. These are working choices, not rules. Write yours into your supplier agreement so a request never arrives with surprise deadlines.

Should the supplier pay for the defect?

That depends on your purchase terms, not on the SCAR. Keep the corrective-action request about the fix, and handle costs in a separate message that refers to your order terms. If a cost dispute becomes large, take advice from a qualified adviser instead of arguing it in a quality form.

Can AI draft the root cause for the supplier?

It can suggest questions that push past the first answer, but the root cause must come from the supplier, who knows their process. If you supply the cause, they may agree without checking it. Use the assistant to draft your request and to review their reply for gaps, not to complete their answer.

Further reads

• Supplier Audit Checklist: Plan and Write Up Visits With AI — Visit a supplier to see whether the promised fix is really in place.
• AI Supplier Negotiation Emails for Importers: Price, MOQ, Terms — Keep quality terms and cost recovery in the same conversation.
• Scrap Rate Tracking: Group Reject Reasons From Shop Notes With AI — Group your own reject reasons to see which suppliers repeat.
• First Article Inspection Report: AI Formats the FAI, You Measure — Reduce repeat defects by checking the first parts after a change.
• Daily Production Report: Summarise Counts, Scrap and Stops With AI — Spot a defect trend on your own line before it becomes a SCAR.
• AI in Plant Engineering: Breakdown Logs and Maintenance Plans — Turn a messy breakdown log into ranked repeat faults and a draft preventive maintenance plan, with the safety items left to a named engineer.
• Mock Recall Template: Run a Traceability Exercise With AI Help — A mock recall template for small food producers: pick a batch, trace it forwards and back, time it, reconcile the quantities and record what failed.
• Six AI Applications in Manufacturing That Need No New Machines — Six office-side AI jobs for a small factory, each with a worked example, a starting step and the check that keeps it honest.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: general quality-management practice for corrective action; ISO 9001 clause 10.2 (nonconformity and corrective action) as a reference, in the 2026 edition that replaced ISO 9001:2015 on 16 September 2026 (as reported by the certification bodies DEKRA and PJR, checked November 2026). Figures and wording in the examples are illustrative.