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.4ISO 22000:2018 · Control, evaluate and decide safely

ISO 22000 clause 8.9.4: control, evaluate and dispose of potentially unsafe food

ISO 22000 clause 8.9.4 governs product that may be unsafe after a nonconformity. The organisation must prevent inappropriate entry into the food chain, keep the product controlled while it is evaluated and determine a justified disposition. The rules distinguish CCP critical-limit failures from OPRP action-criterion failures, so one generic release checklist is not enough.

What clause 8.9.4 requires in practice

Clause 8.9.4 covers what happens to product that may be unsafe. Its general rule is to prevent such product from entering the food chain unless the organisation can show the hazard is already at, or will be brought to, an acceptable level, or that the product still meets the acceptable level despite the nonconformity. Until evaluation and disposition are finished, the product is retained under the organisation's control.

Three parts follow. Under 8.9.4.1, product that has already gone beyond the organisation's control and is later judged unsafe triggers notification of relevant parties and a withdrawal or recall, with controls, responses and authorisations kept as records. Under 8.9.4.2, each affected lot is evaluated; CCP-affected product is not released, while OPRP-affected product may be released as safe only on stated evidence. Under 8.9.4.3, anything not releasable gets a disposition, with the approver identified. Taken together, the clause forms one decision chain rather than separate checklists.

Maintain control while the decision is pending

The general requirements address the evidence needed to prevent unsafe entry into the food chain and the need to retain potentially unsafe product under control until evaluation and disposition. Identify the product and maintain its status across relevant locations and systems.

Competent personnel need the information and authority to decide. Commercial urgency does not change the evidence required. A product hold should remain effective even when stock is transferred or personnel change shifts.

If product that has left the organisation's control is subsequently determined unsafe, notify relevant interested parties and initiate the required withdrawal or recall. Do not treat the inability to physically hold the stock as an end to responsibility.

ISO 22000 consulting & certification support

Get clause 8.9.4 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 evaluation route

Evaluation for release applies to each lot affected by the nonconformity. Product affected by a CCP critical-limit failure must not be released and follows the disposition requirements.

After an OPRP failure, release as safe requires one of the specified evidence conditions: other evidence of effective control, evidence of the intended combined control outcome, or appropriate sampling, analysis or verification demonstrating conformity with the acceptable hazard levels.

These are substantive evidence conditions. They do not create a general rule that one satisfactory sample permits release after any failure.

Determine and authorise disposition

Disposition addresses products not acceptable for release. Permitted routes include suitable reprocessing or further processing, redirection to another use without affecting food safety in the chain, or destruction or disposal.

The chosen route needs an appropriate technical basis and any applicable external requirements. Record what happened and identify the approving authority. Product should remain controlled until the authorised arrangement is completed.

Why potentially unsafe product needs a decision chain

The moment a lot is questioned, three groups pull in different directions: production wants to keep moving, sales wants to deliver and quality wants to be certain. Without a defined chain the loudest voice tends to win. A clear route from hold, to evaluation, to approved disposition gives each group a role and keeps the food safety judgement with people qualified to make it. It also limits cost, because lots with proper evidence can be released with confidence, while lots without it are dealt with early, before they are shipped and need recalling. For customers and authorities, the existence of this chain, and records showing it was followed, is a strong signal of a trustworthy supplier.

How to implement clause 8.9.4

Treat the three sub-clauses as one workflow and design it end to end before an event tests it. Test each hand-off with people from production, warehouse and quality, because that is where records and reality part company.

  1. Map the journey of a questioned lot from first doubt through hold, evaluation, decision and completed action, marking every hand-off.
  2. Define what status labels or system blocks apply, and check that they survive transfers, rework requests and shift changes.
  3. Appoint evaluators by product area and state what authority each has to release, redirect or reject.
  4. Write two separate release routes into the instruction, one for CCP failures and one for OPRP failures, so nobody blends them.
  5. Set out how products already outside the site are identified, and when the recall arrangements are triggered.
  6. Create one record that follows the lot, showing evidence, evaluator, approver and the physical outcome.
  7. Run a desk exercise on a recent event and see whether the record alone tells the full story.

Illustrative food-manufacturing example

Illustrative example 1

A manufacturer identifies a lot affected by a CCP failure. It controls the lot and considers whether a technically justified further-processing route is available. The decision follows the disposition requirements rather than ordinary release based on a later satisfactory sample.

Illustrative example 2

The record links the affected lot, technical basis, approval and completed action. Restoring the original process is recorded separately from the fate of that lot.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 8.9.4 alive in Effivity

Record what you decided under clause 8.9.4, 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 food-distribution example

A distributor receives information that challenges the safety of identified stock, some of which has moved to customers. It controls remaining stock, evaluates the information with competent personnel and communicates with relevant parties. Where product outside its control is determined unsafe, it initiates the appropriate withdrawal or recall.

The exercise follows product location and status rather than treating a central warehouse hold as complete control of every affected unit.

Evidence and common mistakes

What counts as evidence

Retain product-control information, relevant responses from interested parties, authority, evaluation results and disposition records as required. Evidence should explain both the decision and its execution.

Common weaknesses

Common mistakes include a hold without effective dispatch restriction, unrecorded release authority, applying OPRP release evidence to a CCP failure and redirecting food without evaluating the new use. Another is closing a record while the product remains physically unresolved.

Connect the work with traceability, correction and withdrawal or recall.

Explore each numbered part

8.9.4.1 · keep potentially unsafe product under effective control

A product hold must remain effective until evaluation and disposition are complete. This guide explains the general evidence conditions, control of stock and the response when unsafe product has already left the organisation. Manufacturing and distribution examples show why labels, system status, external communication and approving authority need to work together.

8.9.4.2 · make a defensible evaluation for product release

Release decisions after a nonconformity must follow the control category and evidence. This guide explains lot-level evaluation, the restriction after a CCP failure and the three evidence routes available after an OPRP failure. Manufacturing examples show why a satisfactory test or the existence of another control needs careful interpretation before an authorised decision is made.

8.9.4.3 · authorise and complete a safe product disposition

Product that is not acceptable for release needs an authorised final route. This guide explains permitted disposition options and the evidence needed to show what happened. Manufacturing and distribution examples distinguish a technically justified further process or alternative use from an informal attempt to recover commercial value, while preserving control and approving authority.

Frequently asked questions

Does potentially unsafe mean proven unsafe?

No. It identifies a status requiring control and evaluation. The uncertainty must be resolved through the applicable evidence and disposition requirements.

Can affected lots be evaluated as one group?

Each affected lot must be evaluated. Shared evidence may be relevant where justified, but the record must account for each lot.

Can product be donated instead of destroyed?

Any redirection requires a suitable basis that food safety in the chain is not affected and applicable requirements are met. Donation is not an exemption.

Make the product decision traceable from hold to outcome

Discuss a potentially unsafe-product control review with Sterling. Support can connect decisions, authority, training and suitable Effivity ISO & GRC automation software arrangements. Explore HACCP Awareness, 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.