hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Clause 8.9.2ISO 22000:2018 · Control, evaluate and decide safely

ISO 22000 clause 8.9.2: correct nonconformities while controlling affected food

ISO 22000 clause 8.9.2 requires affected product to be identified and controlled when CCP critical limits or OPRP action criteria are not met. The organisation must maintain methods for identification, assessment and correction, with arrangements to review corrections. It must also retain information describing the nonconformity, causes and consequences of corrections to products and processes.

What clause 8.9.2 requires in practice

Clause 8.9.2 is the first response when a CCP critical limit or an OPRP action criterion has not been met. Whatever product is affected must be identified and kept under control as regards its use and release. The organisation also has to keep documented information that sets out how affected product is identified, assessed and corrected, and how the corrections made will be reviewed.

The clause then splits into three paths. For a CCP failure (8.9.2.2) the affected product is treated as potentially unsafe. For an OPRP failure (8.9.2.3) the organisation works out the food safety consequences and the causes, identifies the affected product and handles it under 8.9.4, keeping the evaluation results. Finally, 8.9.2.4 asks for a record of each correction on nonconforming product or process, covering what went wrong, why, and what followed from it. One way teams meet this is a single event record with separate fields for process fix and product decision; the standard requires the content, not that layout.

Identify what is affected

Use monitoring, production and traceability information to establish the relevant product or period. The task is not limited to the unit being checked when failure is discovered. Consider the evidence supporting the boundary of affected product.

Control use and release while evaluation proceeds. A physical label, system status or other suitable arrangement can contribute, but it must actually prevent unintended use or dispatch. The method should work across relevant storage and operating interfaces.

Keep responsibility and authority clear under monitoring evaluation. The person who notices a failure needs a usable route to the appropriate decision-maker.

ISO 22000 consulting & certification support

Get clause 8.9.2 right the first time — with a global leader in ISO 22000 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Apply the correct starting point

When a CCP critical limit fails, affected product must be identified and handled as potentially unsafe. The later release requirement does not allow it to be released as though a satisfactory sample cancelled the failure.

For an OPRP action-criterion failure, determine the food safety consequences and causes, identify affected product and handle it under the potentially unsafe-product requirements. Retain the evaluation results.

These distinctions prevent a generic deviation process from erasing important food safety decisions. They do not mean an OPRP failure can be ignored or a CCP failure automatically requires only one possible disposition.

Correct and review the action

Use the maintained methods to determine appropriate correction. The action may concern product or process, but its suitability needs competent evaluation. Review corrections carried out so the organisation can establish whether the immediate response was appropriate.

Retain information describing the nature of the nonconformity, causes of failure and consequences. Link this with product identity, relevant evaluation and authority where needed by the connected requirements.

Distinguish correction from corrective action. Correcting the immediate condition does not necessarily eliminate its cause or prevent recurrence.

Why correcting failures properly matters to the business

A failed limit at a control point is the moment when a food business is most exposed. If affected product slips into dispatch because the hold was informal, the cost is a recall, a damaged customer relationship and possibly action by a regulator. If instead the whole day is scrapped out of caution, margin is lost without any evidence that it was needed. A defined correction method sits between those two outcomes. It lets operators act quickly, gives managers a basis for proportionate decisions and shows buyers and assessors that failures lead to controlled outcomes rather than improvisation. It also protects people: nobody should have to decide alone, at night, what happens to a pallet.

How to implement clause 8.9.2

Build the correction method around what really happens on the line when a limit or criterion is missed.

  1. Walk through one past failure and note every point where product, paperwork or people could have moved on without a decision.
  2. Write the method for identifying affected product, starting from the last check that was acceptable and using traceability to find the lots concerned.
  3. Choose a hold arrangement that actually blocks use and dispatch, and test it against rework and transfer routes.
  4. Name who may assess and decide, including cover for nights and weekends, and give operators a direct route to them.
  5. Create a short event record that keeps the process correction, the product decision and the causes visibly apart.
  6. Define how corrections are reviewed afterwards, and who confirms the affected product has a final status.
  7. Practise the method with a realistic scenario, time how long each hand-off takes, and fix whatever slows the response or leaves doubt about who decides.

Illustrative food-processing example

Illustrative example 1

A processor identifies a CCP critical-limit failure. The team determines the affected production interval, controls the product and restores the process through appropriate action. It handles the product through the required potentially unsafe-product and disposition route.

Illustrative example 2

The event record distinguishes the process correction from the product decision. An acceptable reading after adjustment does not establish that earlier product was acceptable.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 8.9.2 alive in Effivity

Record what you decided under clause 8.9.2, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO 22000 programme.

Illustrative catering example

A caterer detects an OPRP observation outside the specified criterion. Competent personnel identify the meals and process period concerned, assess food safety consequences and causes, and record the evaluation and correction.

The team discovers that part of the affected product has reached a separate service location. The correction arrangement therefore includes communication and control at that location, not just a note in the kitchen record.

Evidence and common mistakes

What counts as evidence

Maintain the method and review arrangements and retain the required event information. Follow a correction through to the product's actual status. If records show a hold but the dispatch system still permits release, the control may be ineffective.

Common weaknesses

Common mistakes include identifying too narrow a product range without evidence, recording only the equipment adjustment and treating OPRP failure as paperwork. Another is closing the event before the correction has been reviewed and the affected product accounted for.

Explore each numbered part

8.9.2.2 · respond correctly to a CCP critical-limit failure

A CCP critical-limit failure has a specific consequence under ISO 22000: affected product must be treated as potentially unsafe. This guide explains identification, control, escalation and the connection with disposition requirements. Food-processing examples show why restoring the process or obtaining a satisfactory sample does not authorise release of the affected product under the OPRP route.

8.9.2.3 · evaluate an OPRP action-criterion failure

An OPRP failure needs a food safety evaluation, not an automatic assumption that the product is safe or unsafe. This guide explains consequences, causes, affected-product identification and retained evidence. Manufacturing and catering examples show how to preserve control while competent personnel determine the relevant facts and apply the specific release or disposition requirements.

Frequently asked questions

Is correction the same as corrective action?

No. Correction addresses the detected issue; corrective action addresses causes and recurrence through the applicable requirements.

Can product remain available while evaluation is pending?

Affected product must be identified and controlled regarding use and release. Pending evaluation must not allow unintended entry into the food chain.

Does every failure have the same release route?

No. CCP and OPRP failures have distinct requirements that must be preserved in the evaluation and disposition process.

Check whether a correction record tells the whole story

Discuss a product-and-process correction review with Sterling. The scope can connect identification, decisions, learning and suitable Effivity ISO & GRC automation software support. Review Root Cause Analysis & CAPA, the parent guide and the hub.

Source basis and reading note. This is original practical guidance for ISO 22000. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide management-system certification outcomes. Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO 22000 in your organisation.