Supplier Corrective-Action (SCAR/CAPA) Tracker

The problem this kills

A supplier ships you a defective lot, or misses a delivery window again, and you fire off an email asking them to "fix it." A week later you get a reply that says "we'll be more careful." That isn't a root cause and it isn't a corrective action — it's a promise. So you reply again, the thread grows, people get added to the CC line, and three months later the exact same defect shows up on the exact same part. Nothing was actually fixed, because nothing was ever verified.

The discipline that prevents this — a formal Supplier Corrective Action Request (SCAR), often run as an 8D — lives in scattered email threads, a shared spreadsheet nobody trusts, and your memory. There's no enforced order, so suppliers jump straight to "we replaced the operator" without ever proving the root cause. There's no closure gate, so a SCAR gets marked "done" on the supplier's say-so. There's no aging, so the ones rotting open for 90 days look exactly like the ones opened yesterday. And there's no link back to the supplier scorecard, so a chronic offender keeps winning your business.

This is exactly the kind of stage-gated, evidence-driven process that a small internal tool does far better than email — and you do not need to be a developer to build it.

What you'll build

A simple internal web tool for supplier quality. You raise a SCAR for a nonconformance — pick the supplier, the PO and part, describe the problem, record the quantity and dollar impact, and attach evidence (photos, the rejection report, the failing measurements). The tool assigns a SCAR number, routes it to the supplier, and walks the response through enforced 8D-style stages: containment first, then root cause, then corrective action, then effectiveness verification, then closure.

The stage gates are the point: the supplier cannot submit a corrective action until a root cause has been accepted, and they cannot skip the verification step. AI helps draft and tidy each stage — turning a messy supplier reply into a clean containment summary or a structured root-cause statement — but it never closes anything. A quality owner reviews each stage, and at the end must explicitly verify that the corrective action actually worked before the SCAR is marked closed-effective. Overdue stages trigger alerts, recurrence is tracked across SCARs, and every closure links to the supplier's scorecard.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your business — which suppliers and ERP/quality system you run, how you number SCARs today, which 8D stages you actually use, your part and PO naming conventions, your typical and peak issue volumes, who owns verification, and your nastiest edge cases — and then tailors the data model, the stage definitions, the validations, and every later step to your answers. This is a tool shaped around how your supplier-quality process really works, not a generic template.

From there it walks the agent through the database schema, raising a SCAR with evidence upload, routing it to the supplier, the stage-gated response workflow with its hard ordering rules, the quality owner's per-stage review and the closure-verification gate, overdue alerting by email, recurrence and aging tracking, the scorecard link, and a clean CSV export. Every step ends with a ready-to-copy prompt. Because the whole thing runs on CSV/Sheets in and CSV out with evidence in file Storage, you can build and use it this weekend even with no connection to your existing quality system.

The governance it includes (this is the point)

This drives supplier decisions and cost recovery, so it's built like it matters: login so only your quality and purchasing team can use it, row-level security so you only ever see your own organization's SCARs, and a complete audit trail of every stage submission, review, edit, and closure — who did what, and when. Nothing closes automatically: a SCAR stays open until a quality owner verifies effectiveness and approves closure — the hard human-in-the-loop gate — and a supplier's "it's fixed" is never enough on its own. Stage gates enforce the 8D order so corrective actions can't be accepted without an accepted root cause. And a duplicate guard on the SCAR number — plus a warning when you raise a new SCAR for an already-open identical issue — stops the same problem being tracked twice.

Who it's for

Supplier-quality engineers and buyers who manage recurring supplier defects and delivery failures and are tired of chasing them in email threads with no closure discipline. If you can explain how your SCAR moves from "raised" to "closed-effective," you can build this.

You've got this — open the plan, paste the first prompt, and let it interview you about your supplier-quality process.