What it is about
Mistakes happen in every operation. Clause 8.7 requires a nonconforming output to be identified and controlled so that it is not used or delivered by mistake. This applies to material at goods receipt, to parts in production, to finished products and to services, and it also applies when the defect only comes to light at the customer’s after delivery.
There are several ways of dealing with a nonconforming output: correcting it, segregating, containing, returning it or suspending the service, informing the customer, or accepting it under a concession. Which route fits depends on the nature of the defect and its effect. After a correction, conformity with the requirements is verified again.
What must be recorded is the nonconformity, the actions taken, any concessions obtained and who decided how to deal with it. This record turns the individual defect into a source of data: recurring defects show where the system is weak.
In the audit, the line to 10.2 corrective action matters. 8.7 governs how the nonconforming output itself is handled, that is limiting the damage. 10.2 asks about the cause and how a recurrence can be prevented. Not every scrapped part needs an elaborate root cause analysis, but for every nonconformity it has to be evaluated whether one is needed.
What the auditor checks
“Where do you keep blocked goods, and how do I recognise them?”
Whether defective parts are clearly identified and kept apart from good goods, for example in a quarantine area, with a hold tag or with a status in the system. The question is often asked during the walk-round, right in front of the quarantine area.
“Show me the last three cases. Who decided what happens to them?”
Whether the decision on rework, scrapping, return or concession is recorded and was made by an authorised person.
“Was the reworked part checked again?”
Whether conformity was confirmed again after a correction, before the part moved on.
“When did the customer agree to this deviation?”
For concessions: whether the customer was asked where the contract provides for this or it matters to them, and whether their consent is on file.
“What do you do if a defect only shows up at the customer’s?”
Whether there is a route for defects after delivery: informing the customer, recalling or replacing, and narrowing down which other deliveries might be affected.
“Which defects recur, and what have you done about them?”
The link to key figures and to 10.2: whether defect data are analysed and whether recurring defects have triggered a corrective action.
Which evidence convinces
Identified and segregated blocked goods
The most visible evidence. During the walk-round it shows immediately whether the rules are lived.
Records per nonconformity
Description of the nonconformity, action, decision and the person deciding. These are exactly the details the standard requires.
Recorded concessions
With reason, extent, authorised person and, where necessary, the customer’s consent.
Evidence of re-inspection after rework
It shows that a corrected part does not move on unchecked.
An analysis of defects over time
Defect rates, complaints by type and cause. It links 8.7 with [9.1](/en/standard-chapters/9-1-monitoring-and-measurement) and shows whether lessons are learned from individual defects.
Typical nonconformities
Blocked goods not recognisable
Defective parts stand next to good goods without identification. In an isolated case this is a minor nonconformity; if the operation has no rules at all for nonconforming outputs, the requirement is not met: a major nonconformity.
Decision without authority
Who may decide on rework or concession is not defined, or whoever happens to be there decides.
Defects without records
Defects are put right but recorded nowhere. That also removes the basis for recognising patterns.
Concession without the customer
Parts outside specification go out under a concession, although the contract requires the customer’s consent and it was not obtained.
Rework without re-inspection
The corrected part goes straight to dispatch. Nobody knows whether the rework succeeded.
8.7 and 10.2 mixed up
Either every defect gets a full root cause analysis until nobody reports defects any more, or none does, even when it keeps recurring. Both show that the line between handling and preventing is not clear.
Differences by standard
ISO 9001ISO 9001
Only ISO 9001 has a clause of its own on nonconforming outputs. ISO 14001 and ISO/IEC 27001 deal with nonconformities together with corrective action in 10.2: react, contain the consequences, eliminate the cause. The 2026 edition of ISO 9001 keeps 8.7.
How IMScollect covers it
In IMScollect, 8.7 sits in the nonconforming outputs area: one list for product complaints and service complaints, each case with date received, the customer or the supplier that caused it, and the responsible people. Every case passes through four stages, immediate action, root cause analysis, corrective action and effectiveness check, each with its own tasks and evidence.
For root cause analysis, 5 Whys and the Ishikawa diagram are available, and the case produces an 8D report as a PDF for the customer or the supplier. A supplier’s complaints appear on the supplier, so that they feed into its next evaluation. Blocked batches and concessions are recorded in the release module (see 8.6), nonconformities from your own observation under corrective actions.
Frequently asked questions
What is the difference between 8.7 and 10.2?▾
8.7 governs how the nonconforming output is handled: identify, block, decide, correct. 10.2 looks for the cause and prevents recurrence. A defect starts in 8.7 and leads on to 10.2 when its cause has to be eliminated.
What is a concession?▾
The decision to use or deliver a product despite a deviation from the requirements. It needs an authorised person, a record and, where agreed, the customer’s consent. It applies to a defined extent and does not change the requirement permanently.
Does 8.7 also apply to services?▾
Yes. A defective service often cannot be segregated because it has already been provided. Correction, informing the customer and, if necessary, suspending the service then come to the fore.
Does every scrapped part have to be recorded?▾
What is required are records of nonconformities and the decisions about them. For scrap in an ongoing process, a collective record can be enough, for example per shift or order, as long as it is clear what was decided and by whom.
