Published April 1, 2026 · Updated April 23, 2026

ISO 9001 Scrap and Nonconforming Product Requirements (Clause 8.7)

ISO 9001:2015 requires manufacturers to document every nonconforming output — including scrapped parts — with a defect description, disposition, and authorizing identity. Three clauses govern this requirement: Clause 8.7 defines what records to keep for each event, Clause 9.1.1 requires trend analysis over time, and Clause 10.2 requires corrective action with effectiveness verification for recurring defects.

Clause 8.7 — Control of Nonconforming Outputs

Clause 8.7 is the section of ISO 9001:2015 that directly governs how manufacturers must identify, control, and document nonconforming product — including scrap, rework, and concessions. It is the clause most frequently cited in audit findings for manufacturers with informal or spreadsheet-based quality systems.

What Clause 8.7 Requires

For every nonconforming output, the standard requires documented evidence of:

  • Description of the nonconformity: What the defect was — not just "scrap" but a specific defect type (dimensional rejection, surface defect, weld crack). This is why reason codes are essential.
  • Disposition taken: What happened to the nonconforming part: scrapped, reworked, released under concession, or returned to supplier. Each of these represents a distinct disposition and should be recorded accordingly.
  • Authorization: The name or role of the person who authorized the disposition. For scrap, this is typically the operator, line lead, or quality technician — but it must be documented, not assumed.
  • Segregation evidence: Auditors expect evidence that nonconforming parts could not accidentally enter the good-product stream. Physical red bins, quarantine areas, or system holds all satisfy this — but some form of control must be documented.

What Auditors Typically Ask

During a Clause 8.7 walkthrough, auditors commonly ask:

"Show me a recent nonconformance — what defect was it, and what was the disposition?"
"Who authorized the decision to scrap this part?"
"How do you ensure nonconforming parts don't ship to customers?"
"What do you do with a part that fails inspection — where does it go physically?"

The most common Clause 8.7 findings are: no documented reason codes (only a scrap count), missing disposition records, and no identifiable authorizing person for scrapped parts. Pareto Base captures all three fields for every logged scrap event.

Clause 9.1.1 — Monitoring and Measurement (Trend Data)

Clause 9.1.1 requires organizations to evaluate the performance and effectiveness of the quality management system. For scrap, this translates into a trend analysis requirement — auditors expect to see scrap rate data over time (typically monthly for at least six months), not just a point-in-time count.

The trend chart serves two audit purposes: it demonstrates that the organization is monitoring quality performance over time (the basic 9.1.1 requirement), and it provides the evidence base for Clause 10.2 corrective action — if scrap is trending upward and no corrective action has been opened, an auditor may cite both clauses.

Common finding

Quality managers often have current scrap data but lack trend history extending 6+ months. If you are starting a new tracking system, begin immediately — even incomplete historical data is better than none. Auditors look for trend awareness, not perfection.

Clause 10.2 — Corrective Action and Root Cause Verification

Clause 10.2 requires that when a nonconformity occurs — or recurs — the organization takes corrective action proportional to the severity, including root cause analysis and effectiveness verification. For scrap, this means recurring defect types (those appearing repeatedly in the Clause 8.7 log) must eventually have a documented corrective action record.

Auditors do not expect a corrective action for every single scrap event — that would be unworkable. They do expect corrective actions for the significant recurring contributors, identifiable via Pareto analysis. A shop with dimensional rejections as their consistent top defect that has never opened a corrective action on that defect type will likely receive a finding.

What a Compliant Corrective Action Record Contains

  • Description of the nonconformity (consistent with the Clause 8.7 scrap log entry)
  • Root cause investigation methodology (5-Why, fishbone/Ishikawa, or other structured method)
  • Root cause conclusion — the fundamental cause, not the symptom
  • Corrective action taken — specific process change, tooling adjustment, training, or other intervention
  • Implementation date
  • Effectiveness verification — data showing the defect rate after the corrective action compared to baseline

The effectiveness verification step is where many corrective action records fail audit scrutiny. Documenting what you did is not sufficient — you must show data proving it worked. A before-and-after scrap rate comparison for the targeted defect type, tracked over at least four weeks post-implementation, satisfies this requirement. Pareto Base Campaign Management generates this comparison automatically.

IATF 16949 Additional Requirements

IATF 16949:2016 (the automotive quality management standard) adds several requirements on top of ISO 9001 that are relevant to scrap tracking. Manufacturers supplying automotive Tier 1 or OEM customers should be aware of these additional obligations.

Clause 8.7.1.1

Customer notification

Requires immediate notification to the customer when nonconforming product has been shipped. This means tracking lot and shipment data alongside defect records so affected customer shipments can be quickly identified. Most IATF auditors ask how quickly you can identify which lots were affected by a known defect.

Clause 8.7.1.2

Control of nonconforming product (rework)

Requires documented instructions for rework operations and re-inspection of reworked parts before release. Rework instructions must be accessible at the point of use — not just filed in an office. Reworked parts must pass the same acceptance criteria as original production.

Clause 10.2.3

Problem-solving methodology

Requires the use of a documented problem-solving process for customer-related issues — typically 8D (Eight Disciplines) or equivalent. The standard mandates that the methodology be defined and consistently applied, not selected ad hoc. Quality managers should have a documented problem-solving procedure that specifies which tool (8D, DMAIC, A3) is used and when.

What Pareto Base Generates Automatically vs. What Needs Other Systems

Pareto Base is purpose-built around the scrap and nonconforming product requirements in ISO 9001. The table below maps each requirement to what Pareto Base handles automatically versus what requires a separate system or manual process.

RequirementClauseStatus in Pareto Base
Defect description (reason code) per event8.7Automatic
Disposition recorded per event8.7Automatic
Authorization identity per event8.7Automatic (logged user)
Scrap rate trend chart (monthly)9.1.1Automatic
Pareto chart of top defect contributors9.1.1Automatic (live)
Corrective action effectiveness data10.2Automatic (Campaign Management)
Root cause investigation documentation10.2Manual (attach to campaign)
Customer shipment lot traceabilityIATF 8.7.1.1Requires ERP/MES integration
Rework instructions at point of useIATF 8.7.1.2Requires separate system
8D / formal problem-solving recordIATF 10.2.3Requires separate system

6-Week Audit Prep Checklist

Use this checklist if you have an ISO 9001 audit scheduled and are not confident your scrap records will satisfy Clauses 8.7, 9.1.1, and 10.2.

Week 1

Audit your current scrap log

Verify that every recorded scrap event includes: defect reason code, quantity, date, disposition (scrap/rework/concession), and the name or role of the person who authorized the disposition. Flag any entries missing these fields.

Week 2

Establish or backfill reason codes

If your scrap log lacks reason codes, define a standardized list of 5–12 defect types relevant to your processes and retroactively tag at least 90 days of historical data. Pareto Base allows custom reason code setup and bulk event tagging.

Week 3

Generate trend data

Create a month-by-month scrap rate trend chart covering at least 6 months. Auditors expect to see trend analysis per Clause 9.1.1 — a single snapshot does not satisfy the requirement. Pareto Base generates this automatically.

Week 4

Run a Pareto analysis

Produce a Pareto chart of your top defect contributors for the audit period. Be prepared to discuss what the chart shows and what corrective actions it has driven. This satisfies both Clause 9.1.1 (trend analysis) and demonstrates process for Clause 10.2.

Week 5

Open or document corrective actions for recurring defects

Identify your top recurring defect type from the Pareto chart. Ensure a corrective action record exists that documents: root cause investigation method (5-Why or fishbone), corrective action taken, implementation date, and effectiveness verification data.

Week 6

Run a mock audit walkthrough

Walk through Clause 8.7's documented information requirements end-to-end using a real scrap event. Can you pull the defect description, disposition, authorizing role, and any related corrective action in under 5 minutes? If not, improve your record linkage before audit day.

Generate audit-ready scrap records automatically

Pareto Base captures the Clause 8.7 records auditors expect — defect reason codes, dispositions, trend charts, and Pareto charts — from every scrap event your team logs.