QUALITY ENGINEERING

MASTERY GUIDE
VOLUME 5: DOCUMENTATION + SUPPLIER QUALITY
Topics 64 – 80

The paperwork that makes quality provable and repeatable — from the SOP posted at a workstation
to the SCAR that closes the loop with a supplier across the world.

Prepared as a personal study & career guide

Quality Engineering Mastery Guide — Volume 5 Page 1

 TABLE OF CONTENTS

64. SOP (Standard Operating Procedure)

65. Work Instructions
66. Inspection Standards
67. Quality Manual
68. Check Sheets
69. Inspection Reports
70. NCR (Nonconformance Report)
71. CAPA Reports
72. 8D Reports
73. Customer Complaint Reports
74. Supplier Quality Documents
75. Supplier Audits
76. Supplier Development
77. Supplier PPAP
78. Vendor Rating
79. Incoming Material Quality
80. Supplier Corrective Actions (SCAR)

How to use this guide: Documentation can feel dry compared to hands-on inspection and process work — but
every document in this volume exists to answer one question an auditor or a future you will eventually ask:
'how do we PROVE this happened correctly?' Read each topic with that lens.

Quality Engineering Mastery Guide — Volume 5 Page 2

 SECTION 7 : DOCUMENTATION

64. SOP (Standard Operating Procedure)

An SOP is a formal, controlled document describing HOW a specific task or process should be performed
consistently, every time, by anyone qualified to do it — the backbone of process repeatability and a core
requirement of virtually every quality standard.

Document Control The system ensuring only the CURRENT approved revision of an
SOP is in use on the floor, with obsolete versions removed/archived.

Revision History A log at the top or end of the SOP showing what changed, when, and
who approved it — critical for traceability if a process-related issue is
investigated later.

Scope Clearly defines what the SOP covers (and doesn't) — e.g., 'applies to
Line 3 only' vs. 'applies to all CNC lathes plant-wide.'

Training Record Evidence that every operator performing the task has actually been
trained on the CURRENT revision of the SOP — an SOP existing on
paper means nothing if operators haven't been trained to it.

EXAMPLE — Why an outdated SOP is a real quality risk

A torque specification changes from 20 Nm to 25 Nm after an engineering update, and the

Control Plan is updated correctly — but the SOP posted at the workstation still shows the old 20
Nm value. Operators, following the (outdated but still physically present) SOP exactly as written,
continue torquing to the wrong value for weeks until an internal audit catches the mismatch. This
illustrates why document control (ensuring old versions are physically removed, not just that a
new one exists somewhere) is just as important as writing the SOP correctly in the first place.

TIP / COMMON MISTAKE: A common audit finding is 'SOP at the workstation does not match
the current approved revision in the document control system' — always physically check the
document ON THE FLOOR during an audit, not just the master file in the office.

65. Work Instructions

Work Instructions (WIs) are more detailed and specific than an SOP — they break a single step of a process
down into precise, often photo-illustrated, step-by-step actions for a specific station or operation, usually
written for someone with little to no prior experience.

• An SOP might say 'Assemble the bracket per the assembly work instruction' — the Work Instruction is
the detailed document that actually shows HOW, step by step

Quality Engineering Mastery Guide — Volume 5 Page 3

 • Good Work Instructions use photos/diagrams heavily, minimizing reliance on text alone
• Should include clear pass/fail criteria at each check point, referencing the Control Plan where relevant
• Often posted directly at the workstation, sometimes on a screen/tablet for easy updates

EXAMPLE — SOP vs. Work Instruction, in one part's journey

The SOP for 'Bracket Assembly Process' outlines the overall flow: incoming parts →
sub-assembly → torque station → final test → packing. The Work Instruction specifically for the
TORQUE STATION shows a photo of the correct tool, the exact torque value and sequence
(e.g., 'tighten bolt 1 first, then bolt 2, in a criss-cross pattern'), and a photo of what a correctly
seated fastener looks like versus an incorrectly seated one — the SOP gives the big picture, the
WI gives the precise how-to for one specific step within it.

TIP / COMMON MISTAKE: A quick interview distinction: 'SOP = what needs to happen and in
what order (process level); Work Instruction = exactly how to do one specific step (task level),
usually more visual and detailed.'

66. Inspection Standards

An Inspection Standard is a document defining exactly WHAT to check, HOW to check it, and what the
PASS/FAIL criteria are for a specific part or feature — it's the reference an inspector uses to make a
consistent judgment call, especially for visual or subjective characteristics.

• Should specify the exact instrument/method to use for each characteristic (linking back to Topic 7)
• Includes acceptance criteria — numeric limits for measurable features, and reference photos/boundary
samples for visual features (linking back to Topic 11)
• Often organized by ZONE for cosmetic parts (Zone A/B/C, as in Topic 11)
• Should be periodically reviewed against actual customer complaints — if a defect keeps reaching the
customer despite 'passing' inspection, the standard itself may need tightening

EXAMPLE — An inspection standard closing a real gap

A customer complains about a minor dent that 'should have been caught.' Reviewing the
Inspection Standard reveals it lists 'no visible scratches' but never explicitly addresses dents at
all — inspectors were technically following the written standard perfectly, since dents simply
weren't covered. The standard is updated to explicitly define a maximum acceptable dent
depth/size with a reference photo, closing the actual gap rather than blaming inspectors for a
document that was genuinely incomplete.

TIP / COMMON MISTAKE: When investigating an escaped defect, always check whether the
Inspection Standard EXPLICITLY covered that defect type before assuming inspector error — a
shockingly large number of 'inspection failures' are actually 'standard gaps.'

Quality Engineering Mastery Guide — Volume 5 Page 4

 67. Quality Manual
A Quality Manual is the top-level document describing an organization's overall Quality Management System
— its scope, structure, policies, and how it meets the requirements of the standard(s) it's certified to (ISO
9001, IATF 16949, etc.).

• Traditionally described every clause of the standard and how the company addressed it — the 2015
revision of ISO 9001 made a standalone Quality Manual technically optional, though many
organizations still maintain one for clarity and customer/auditor reference
• Typically includes: company quality policy, scope of the QMS (what's included/excluded and why), an
organizational chart showing quality-related responsibilities, and a high-level process map/interaction
diagram
• Acts as the top document in a document hierarchy: Quality Manual → Procedures/SOPs → Work
Instructions → Forms/Records (increasingly detailed as you go down)

EXAMPLE — Using the Quality Manual during a customer audit

A new customer auditing a potential supplier for the first time starts by reviewing the Quality
Manual to quickly understand the company's overall scope (which products/processes are
covered), quality policy, and how responsibilities are organized — before diving into detailed
floor audits of specific processes. The Quality Manual functions as the 'front door' overview that
orients an auditor before they go deep into individual SOPs and Work Instructions.

TIP / COMMON MISTAKE: A useful document hierarchy analogy for interviews: 'Quality Manual
is like a book's table of contents (the big picture); SOPs are the chapters (the processes); Work
Instructions are the detailed paragraphs (the exact steps); Records/Forms are the proof it
actually happened.'

68. Check Sheets

A Check Sheet is a simple, structured form used to collect data as events happen in real time — tallying
occurrences of specific defect types, or recording pass/fail results of specific checks, in a consistent format
that's easy to analyze afterward.

• Should be designed BEFORE data collection starts, with categories pre-defined based on known
defect types or check points — not filled in loosely after the fact
• Feeds directly into Pareto charts (Topic 19) — a well-designed check sheet makes building a Pareto
chart almost automatic
• Can be a simple tally sheet (operator marks a tick each time a defect type occurs) or a structured
pass/fail checklist for a specific inspection point

EXAMPLE — From check sheet to root cause, in one afternoon

Quality Engineering Mastery Guide — Volume 5 Page 5

 A check sheet at final inspection tallies defect types over one week: Scratches (45), Dents (12),
Wrong Label (3), Missing Screw (2). This raw data instantly builds into a Pareto chart showing
scratches as the dominant issue (over 70% of all defects) — the team now knows exactly where
to focus their next Fishbone/Root Cause Analysis session, rather than spreading effort evenly
across all four defect types.

TIP / COMMON MISTAKE: The single biggest design flaw in a check sheet is missing a
category — if operators keep writing 'other' and describing something in the margin repeatedly,
that's a strong signal the check sheet needs a formal new category added.

69. Inspection Reports

An Inspection Report is the formal record of an inspection activity's results — whether IQC, IPQC, FQC, or
OQC — documenting what was checked, the actual measured/observed results, and the pass/fail decision,
providing the traceable evidence that inspection actually happened.

• Should reference the specific specification/drawing revision the parts were checked against
• Records actual measured VALUES where possible, not just 'pass/fail' — numeric data enables trend
analysis (SPC, Cpk) that a simple pass/fail checkbox cannot support
• Must be traceable to the specific lot/batch, date, inspector, and gauge used (linking to Calibration,
Topic 8, and Traceability, Topic 3)

EXAMPLE — Why recording actual values matters more than pass/fail alone

Two inspection reports both show 'PASS' for a hole diameter spec of 10.00±0.05mm. Report A
recorded only 'PASS.' Report B recorded the actual value: 10.048mm. Report B's data reveals
the part was barely inside spec, right at the edge — a warning sign visible ONLY because the
actual value was recorded. If several consecutive parts show this same near-limit pattern,
Report B's data would reveal a drifting process needing attention, while Report A's simple
pass/fail data would show nothing wrong at all until an actual failure eventually occurred.

TIP / COMMON MISTAKE: Whenever possible, insist on recording actual numeric values rather
than simple pass/fail check marks — this single practice enables early warning through SPC and
trend analysis that pass/fail data structurally cannot provide.

Quality Engineering Mastery Guide — Volume 5 Page 6

 70. NCR (Nonconformance Report)
An NCR is the formal document raised the moment a nonconformance (Topic 2) is identified — describing
what was found, the affected quantity/lot, immediate containment, and the disposition decision (use-as-is,
rework, repair, scrap, or return to supplier).

Disposition The formal decision on what happens to the nonconforming material

— typically requires sign-off from Quality, and sometimes Engineering
or the Customer, depending on severity.

Use-As-Is A disposition allowing the nonconforming part to be used without any

rework, usually because engineering review determines the deviation
doesn't affect form/fit/function — sometimes requires a formal
customer concession (Topic 2).

MRB (Material Review A cross-functional team (Quality, Engineering, Production) that

Board) reviews NCRs for significant or ambiguous nonconformances and
decides disposition together.

EXAMPLE — An NCR triggering a disposition decision

An NCR is raised for 500 brackets with a hole diameter measuring 10.06mm against a
10.00±0.05mm spec — just 0.01mm over. Engineering reviews the mating part and confirms the
slightly larger hole still allows the assembly to fit and function correctly with no impact on
strength. The MRB dispositions the lot as 'Use-As-Is' with a documented engineering rationale,
avoiding unnecessary scrap — but this decision is formally recorded on the NCR precisely so
there's a clear paper trail if this same situation is ever questioned later.

TIP / COMMON MISTAKE: Never allow a 'Use-As-Is' disposition to happen verbally or

informally — it must always be documented on the NCR with a clear engineering rationale, since
this decision represents a deliberate deviation from the original specification and needs to be
defensible later, including to a customer or auditor.

71. CAPA Reports

A CAPA Report is the formal document tracking a Corrective and Preventive Action (Topic 24) from the initial
problem description through root cause analysis, action implementation, and effectiveness verification — the
auditable record proving the whole CAPA cycle was actually completed, not just started.

• Typically includes: problem description with data, containment actions taken, root cause analysis
(often showing the 5 Why or Fishbone used), corrective action taken, preventive action taken, and
effectiveness verification results/date
• Should have a clear OWNER and DUE DATE for each action — a CAPA with no owner or deadline
rarely gets completed on time

Quality Engineering Mastery Guide — Volume 5 Page 7

 • Effectiveness verification should happen only AFTER enough time/volume has passed to be
statistically meaningful — closing a CAPA the same week the action was implemented, before real
production data exists, is a common and serious weakness

EXAMPLE — A CAPA report closed too early

A CAPA addressing a recurring scratch defect implements a new packaging design and is
marked 'closed - effective' the very next day, based only on the team's confidence that the fix
should work. Three weeks later, the same scratch defect reappears at a similar rate — because
the effectiveness verification step was skipped entirely, and a subtle issue with the new
packaging (it worked for small parts but not the larger variant) was never caught before the
CAPA was prematurely closed.

TIP / COMMON MISTAKE: A CAPA Report should never be closed on the same day the action
is implemented — effectiveness verification requires waiting through enough real production
cycles to confirm the defect actually stopped recurring, not just that the team is confident it will.

72. 8D Reports
An 8D Report is the formal document capturing all 8 disciplines of the 8D process (Topic 29) — the standard
format many customers (especially automotive) require as the official response to a significant quality
complaint.

• Follows the D1–D8 structure exactly: Team, Problem Description, Interim Containment, Root Cause
(occurrence AND detection), Permanent Corrective Action, Implementation/Validation, Prevention of
Recurrence, Team Recognition
• Customers often have their OWN specific 8D template/portal — a supplier may need to complete a
different customer's exact format for the same internal investigation
• A well-written 8D includes actual DATA and photos, not just narrative descriptions — 'we believe the
cause was X' is weaker than showing the measurement/test data proving X

EXAMPLE — What makes an 8D convincing to a customer

Two 8D reports for the same type of complaint both claim 'root cause: tool wear.' Report A states
this with no supporting evidence. Report B includes a chart showing the dimension trending
upward over the tool's life, cross-referenced with the tool change schedule, plus a photo
comparing the worn tool against a new one. Report B will almost always be accepted by a
customer quality engineer far more readily — because it demonstrates the root cause was
actually PROVEN with data, not just assumed.

TIP / COMMON MISTAKE: If a customer rejects your 8D report and asks for more detail, it's
very often because D4 (Root Cause) lacks supporting data/evidence — always ask 'how do we
PROVE this is the cause?' before submitting, not just 'does this explanation sound reasonable?'

Quality Engineering Mastery Guide — Volume 5 Page 8

 73. Customer Complaint Reports
A Customer Complaint Report is the formal internal record capturing a complaint received from a customer —
separate from (but often the trigger for) an 8D or CAPA — ensuring every complaint is logged, investigated,
and tracked to closure, and enabling trend analysis across many complaints over time.

• Captures: complaint date, customer, part number, lot/batch if known, description of the issue, quantity
affected, and whether it's a safety concern
• Should trigger immediate CONTAINMENT (Topic 2) actions before the full investigation is even
complete
• Feeds a broader complaint database/trend analysis — a single complaint might be an isolated event,
but a Pareto of ALL complaints over 6 months reveals systemic patterns worth deeper investigation
• Response time is often contractually defined by the customer (e.g., containment within 24 hours, full
8D within 5–10 business days) — missing these deadlines can itself damage the customer relationship

EXAMPLE — A single complaint revealing a bigger pattern

One customer complaint about a loose fastener seems minor and isolated at first. But reviewing
the complaint database's trend report shows this is actually the FOURTH similar complaint in 6
months, each from a different customer, each involving the same fastener type — a pattern
invisible if each complaint had only been handled individually and closed. This triggers a deeper,
plant-wide investigation into the torque process for that fastener across all product lines, not just
a fix for the single complaint at hand.

TIP / COMMON MISTAKE: Always log EVERY complaint into the same system/database, even
ones that seem minor or get resolved quickly — the real value often comes from spotting
PATTERNS across many complaints over time, which is impossible if complaints are handled
informally and not centrally tracked.

74. Supplier Quality Documents

Supplier Quality Documents are the collection of records a supplier must provide (or a customer must collect
from suppliers) to prove incoming material/parts meet requirements — the documentation backbone
connecting your IQC process (Topic 13) to the supplier's own quality system.

CoC (Certificate of Supplier's declaration that the shipped lot meets the purchase
Conformance) order/drawing requirements.

CoA (Certificate of Detailed test/measurement RESULTS for the specific lot (chemical
Analysis) composition, mechanical properties) — more detailed than a simple
CoC.

Supplier PPAP Full production part approval documentation submitted before regular
Package production shipments begin (see Topic 77).

Quality Engineering Mastery Guide — Volume 5 Page 9

 Material Safety Data Safety information for hazardous materials/chemicals — required for
Sheet (MSDS/SDS) regulatory and worker safety compliance, not product conformance
itself.

EXAMPLE — Catching a problem through document review alone

A CoA for an incoming steel batch shows a carbon content slightly outside the drawing's
specified range, even though the physical parts have not even been unpacked yet. This is
caught purely through DOCUMENT REVIEW during IQC, before any physical inspection is even
needed — illustrating why reviewing supplier documentation carefully is just as important as
physically inspecting the parts themselves, and can catch issues that dimensional inspection
alone never would (like chemistry, which usually can't be verified with typical shop-floor gauges).

TIP / COMMON MISTAKE: Never treat supplier documents as a formality to file away unread —
a CoA in particular often contains chemistry/property data that NO physical dimensional
inspection at your own facility could ever verify, making careful document review a genuinely
irreplaceable check, not a redundant one.

Quality Engineering Mastery Guide — Volume 5 Page 10

 SECTION 8 : SUPPLIER QUALITY

75. Supplier Audits

A Supplier Audit is a formal, systematic evaluation of a supplier's quality system and/or specific
manufacturing process — conducted on-site (or sometimes remotely) to verify the supplier can reliably
produce conforming parts, before and during an ongoing business relationship.

System Audit Evaluates the supplier's overall Quality Management System against a
standard (ISO 9001, IATF 16949) — broad scope.

Process Audit Focuses on one specific manufacturing process at the supplier,

checking it against documented parameters (same concept as Topic
17, applied to a supplier).

Product Audit Verifies a sample of the supplier's actual finished product meets all
specification requirements.

Audit Finding / A specific, documented gap identified during the audit, usually
Nonconformance requiring a supplier corrective action (SCAR, Topic 80) to close.

Follow-Up Audit A subsequent audit specifically verifying that previous findings were
actually corrected and are holding, not just promised.

EXAMPLE — What a good supplier audit actually verifies

During a supplier audit, the auditor doesn't just ask 'do you have a Control Plan?' — they ask to
see the Control Plan for a SPECIFIC part number, then walk to that exact production line and
verify the operator is actually following it (correct gauge in use, correct frequency, records being
filled in real-time, not filled in all at once at the end of shift). This 'trace and verify' approach
catches the common gap between what a supplier's documentation SAYS happens and what
actually happens on their floor.

TIP / COMMON MISTAKE: A strong audit technique to mention in an interview: always trace a
SPECIFIC part or record all the way through the process, rather than just asking generic yes/no
questions — specific tracing reveals real gaps that generic questions almost always miss.

76. Supplier Development

Supplier Development is the proactive, collaborative process of helping a supplier IMPROVE their capability,
quality, or delivery performance over time — going beyond simply auditing and rejecting bad parts, toward
actively building a stronger, more reliable supply base.

Quality Engineering Mastery Guide — Volume 5 Page 11

 • Can include: joint problem-solving sessions, sharing best-practice knowledge/training, helping a
supplier implement SPC or Poka-Yoke on a specific process, or providing technical support during a
supplier's own process improvement project
• Often prioritized based on supplier segmentation — investing development effort in strategic/critical
suppliers rather than spreading resources thinly across every supplier equally
• A strong long-term alternative to simply switching suppliers every time a problem occurs, especially for
suppliers providing unique or hard-to-replace capability

EXAMPLE — Development vs. simply switching suppliers

A critical single-source supplier struggles with a recurring dimensional issue. Rather than
searching for a replacement supplier (costly and slow, requiring new PPAP and requalification),
the customer sends a quality engineer to help the supplier implement an SPC chart on the
specific problem dimension and adjust their process parameters jointly — within weeks, the
defect rate drops significantly, and the relationship is stronger and more capable going forward,
at a fraction of the cost and risk of qualifying an entirely new supplier from scratch.

TIP / COMMON MISTAKE: A key interview point: supplier development is usually FAR cheaper
and faster than re-sourcing to a new supplier, especially for complex or specialized parts
requiring full PPAP requalification — it's often the more pragmatic first move.

77. Supplier PPAP

Supplier PPAP is simply PPAP (Topic 27) applied specifically to a SUPPLIER's part or process — the formal
approval package a supplier must submit and get accepted by the customer BEFORE regular production
shipments of a new or changed part can begin.

• The same 18 elements and submission levels apply (design records, PFMEA, Control Plan,
dimensional results, initial capability studies, sample parts, etc.)
• The RECEIVING customer's quality/engineering team reviews and formally approves (or rejects,
requesting resubmission) the supplier's PPAP package
• A rejected PPAP means the supplier cannot ship production quantities yet — often requires further
process improvement and resubmission before approval
• Tracked in a Supplier PPAP status log so purchasing/planning knows exactly which parts are
approved for full production versus still pending

EXAMPLE — A rejected supplier PPAP

A supplier submits a PPAP package showing a process capability study with Cpk = 0.9 on a
critical dimension, below the customer's required minimum of 1.33. The customer's quality
engineer REJECTS the PPAP submission and requests the supplier improve their process
(better tooling, tighter process control) and resubmit new capability data — production
shipments cannot begin until an acceptable Cpk is demonstrated and approved, preventing a
known-marginal process from ever reaching full-volume production.

Quality Engineering Mastery Guide — Volume 5 Page 12

 TIP / COMMON MISTAKE: Remember PPAP flows in the SAME direction as any
customer-supplier relationship: it's the supplier who submits, and the CUSTOMER who reviews
and approves — even a large company acts as the 'customer' reviewing PPAPs from its own
component suppliers, and as the 'supplier' submitting PPAPs to ITS customers.

78. Vendor Rating

Vendor (Supplier) Rating is a formal, ongoing scorecard system measuring supplier performance across
multiple dimensions — typically quality, delivery, and sometimes cost/service — used to make objective
sourcing decisions rather than relying on subjective impressions alone.

Quality Score Often based on defect rate (PPM — parts per million defective),
number of complaints, or audit results.

Delivery Score Measures on-time delivery performance — often tracks both early
AND late delivery, since both can disrupt production planning.

PPM (Parts Per A common quality metric: (defective parts ÷ total parts shipped) ×
Million) 1,000,000 — allows fair comparison between suppliers shipping very
different volumes.

Supplier Tiering Classifying suppliers (e.g., Preferred, Approved, Conditional,

Restricted) based on their overall score, affecting how much new
business they're eligible to receive.

EXAMPLE — Why PPM is used instead of raw defect counts

Supplier A ships 10,000 parts/month with 5 defective — a PPM of 500. Supplier B ships 500,000
parts/month with 100 defective — a PPM of 200. A simple raw defect COUNT would make
Supplier A look better (5 vs. 100 defects), but PPM correctly reveals Supplier B actually has a
BETTER defect rate relative to volume shipped — this normalization is exactly why PPM, not
raw counts, is the standard metric for comparing suppliers of different sizes fairly.

TIP / COMMON MISTAKE: If asked to calculate PPM in an interview, remember the formula
precisely: (Defective Units ÷ Total Units Shipped) × 1,000,000 — and be ready to explain WHY
it's used instead of a raw defect count (fair comparison across different shipment volumes).

79. Incoming Material Quality

Incoming Material Quality is the broader discipline of managing quality at the material/component level
BEFORE it enters production — encompassing IQC inspection (Topic 13), but also material certification
review, supplier qualification, and proactive risk assessment of new material sources.

• Goes beyond simple pass/fail IQC inspection to include ongoing MONITORING of incoming quality
trends over time, not just single-lot decisions

Quality Engineering Mastery Guide — Volume 5 Page 13

 • Requires close coordination with Purchasing — a quality engineer should have input into supplier
selection and approval, not just inspect whatever arrives after the fact
• New material sources or grades should go through a formal qualification process (potentially including
supplier PPAP, Topic 77) BEFORE being used in production, not discovered as a surprise on the
receiving dock

EXAMPLE — Proactive vs. reactive incoming material quality

A REACTIVE approach only inspects material as it arrives and reacts to whatever problems
appear. A PROACTIVE approach reviews the new material grade's technical datasheet,
requests a sample lot for trial production BEFORE the full order is placed, and works with the
supplier to align on a PPAP-style approval before committing to regular shipments — catching a
mismatch (e.g., unsuitable heat resistance for the application) weeks before it could have
caused a production-line disruption or a downstream field failure.

TIP / COMMON MISTAKE: A quality engineer's involvement in supplier and material

SELECTION — not just inspection after arrival — is one of the clearest signs of a mature quality
function, and a strong point to highlight in an interview about your own experience.

80. Supplier Corrective Actions (SCAR)

A SCAR (Supplier Corrective Action Request) is the formal document a customer sends to a supplier when a
nonconformance traced back to that supplier is found — requiring the supplier to investigate, contain,
root-cause, and correct the issue, essentially an 8D/CAPA process initiated and tracked BY the customer.

• Typically requires the same elements as an 8D: containment, root cause, corrective action, preventive
action, and effectiveness verification — but submitted back to the CUSTOMER, not just kept internally
at the supplier
• Often has a strict customer-defined response deadline (e.g., containment confirmation within 24–48
hours, full root cause and corrective action within 2 weeks)
• Repeated or unresolved SCARs against the same supplier directly feed into their Vendor Rating (Topic
78) and can affect future sourcing decisions or trigger a formal supplier audit (Topic 75)

EXAMPLE — A SCAR closing the loop across the whole supply chain

A customer's IQC rejects an incoming lot for an out-of-spec dimension and issues a SCAR to the
supplier. The supplier's root cause investigation finds a worn fixture at their own facility,
implements a fixture replacement and inspection schedule, and reports back with data
confirming the next 5 lots are all within spec. The customer's quality engineer reviews this
evidence before formally closing the SCAR — mirroring the exact same discipline (containment,
root cause, verified correction) used internally for an 8D, just applied across a company
boundary rather than within one factory.

Quality Engineering Mastery Guide — Volume 5 Page 14

 TIP / COMMON MISTAKE: A SCAR is essentially '8D, but sent to someone outside your own
company' — the same rigor about not closing until effectiveness is verified applies just as
strongly, arguably more so, since you have less direct visibility into the supplier's actual process
than you would into your own.

Quality Engineering Mastery Guide — Volume 5 Page 15

Quality Engineering Mastery Guide — Volume 5 Page 16
 END OF VOLUME 5

You've now covered the full documentation chain — SOPs, Work Instructions, Inspection Standards, the
Quality Manual, Check Sheets, Inspection Reports, NCRs, CAPA and 8D Reports, Customer Complaint
Reports, and Supplier Quality Documents — plus the Supplier Quality discipline that extends your quality
system across the company boundary: Audits, Development, Supplier PPAP, Vendor Rating, Incoming
Material Quality, and SCAR.

Next up in Volume 6: Customer Quality (Complaint Handling, Warranty, Customer Audits, Customer-Specific
Requirements, Communication) and Statistics (Mean/Median/Mode, Standard Deviation, Normal Distribution,
Histogram, Control Charts, Regression, Hypothesis Testing).

Just say "next volume" whenever you're ready to continue.

Quality Engineering Mastery Guide — Volume 5 Page 17