ISO 22000 clause 10: correct weaknesses and keep the FSMS current
Clause 10 of ISO 22000 requires the organisation to address nonconformities, continually improve the FSMS and keep it updated. These are connected responsibilities with different purposes. Corrective action addresses the causes of a failure; improvement strengthens the system; updating keeps it aligned with current information and operations, even when no failure has been detected.
What clause 10 requires in practice
Clause 10 gives the FSMS three ways to stay healthy. Clause 10.1 deals with nonconformity and corrective action: react to the nonconformity, control and correct it, deal with consequences, then evaluate whether action is needed to remove the cause so it does not recur or occur elsewhere. Action must suit the effects of the nonconformity, and its effectiveness is reviewed.
Clause 10.2 requires continual improvement of the system's suitability, adequacy and effectiveness, with top management using communication, management review, internal audit, verification analysis, validation of control measures, corrective actions and system updating to achieve it. Clause 10.3 requires the system to be kept updated; the food safety team evaluates it at planned intervals and considers whether the hazard analysis, hazard control plan and PRPs need review, using specified inputs. Documented information covers nonconformities, actions, results and updating activities. Product-level responses remain governed by 8.9, and the two sets of requirements are meant to work together.
Why improvement and updating keep the FSMS credible
Food businesses change constantly: new ingredients, customers, equipment, staff and regulations. A system that is certified or documented once and then left alone gradually describes a business that no longer exists. Clause 10 is the discipline that stops that drift. Responding properly to failures prevents repeat cost and complaint, and looking for similar problems elsewhere stops the same weakness surfacing at another site. Improvement activities give management a way to invest in the system on evidence. Updating ensures that the hazard analysis and controls reflect current reality. Together they allow the business to tell customers and assessors, with proof, that its food safety arrangements are alive and learn from what happens.
How to implement clause 10
Join the three sub-clauses into one learning loop and make sure each feeds the others. Clarity about who owns each part prevents corrective action, improvement and updating from running as three unrelated activities.
- Set one route for nonconformities from audits, complaints, verification and incidents, so none are handled outside the loop.
- Separate the immediate correction from the investigation, and require an explicit judgement on whether similar issues exist elsewhere.
- Choose investigation methods that fit the size of the issue, and ask for evidence that a stated cause fits the facts.
- Maintain a short list of improvement ideas drawn from review, audit and analysis, with intended benefits and owners.
- Schedule the food safety team's evaluation of the hazard analysis, control plan and PRPs, and add triggers for earlier review.
- Check effectiveness using operating evidence collected after the process has run again, not on the day of closure.
- Report corrective actions, improvements and updating work to management review so leaders see the full picture.
10.1: respond to nonconformity and investigate causes
React to a nonconformity by controlling and correcting it as appropriate and dealing with its consequences. Then evaluate the need for action to eliminate causes so that the issue does not recur or occur elsewhere. Review the problem, determine causes and consider similar existing or potential failures.
Implement necessary action, review effectiveness and change the FSMS where needed. The response should be appropriate to the effects of the nonconformity. Retain evidence of the nature of the issue, subsequent actions and corrective-action results. A particular investigation form or named root-cause method is not mandatory.
Correction and corrective action should be distinguishable. Restoring a missing instruction corrects its absence. Determining why a change bypassed the communication process can lead to action on the cause. If product may be affected, the appropriate operational controls under 8.9 remain necessary; a system action record is not a product-release authorisation.
10.2: improve suitability, adequacy and effectiveness
Continual improvement draws on communication, management review, internal audit, verification analysis, validation, corrective action and updating. These inputs help management identify whether the system remains appropriate to the organisation, sufficiently resourced and effective in practice.
Improvement need not mean adding more documents. Simplifying an ambiguous handover, improving access to current information or strengthening a provider interface can produce a more reliable process. Define what the change is expected to achieve and what evidence will show whether it helped.
Avoid measures that reward closure without learning. A shorter average closure time may be useful, but it can also conceal superficial investigations. Examine recurrence and the quality of effectiveness evidence alongside administrative timeliness.
10.3: update the FSMS through planned evaluation
Management ensures that the system is continually updated. The food safety team evaluates it at planned intervals, considering whether the hazard analysis, hazard control plan and PRPs need review. Inputs include internal and external communication, information about system performance, verification analysis and management-review outputs.
Record updating activities and report them to management review. Relevant triggers can include new product information, changed materials, altered processes, different service arrangements or new hazard knowledge. An unchanged document date does not show that the underlying assumptions remain valid.
Updating may lead to technical work, including reviewing or validating controls where required. The team should distinguish an editorial correction from a change affecting how the process controls hazards. Follow the relevant operational requirements rather than treating every revision as a document-administration task.
Illustrative example: manufacturing change notices arrive late
A hypothetical manufacturer repeatedly learns about ingredient specification changes after receiving the material. It corrects the immediate information gap and assesses any operational implications. Investigation finds that provider notices go to an individual buyer without a defined route to the food safety team.
Corrective action changes the communication responsibilities and provider instructions. Later changes are sampled to check that the relevant information arrives before use and receives review. The effectiveness decision rests on that operating evidence, not simply on the revised email distribution list.
Illustrative example: food logistics software is changed
A hypothetical food distributor changes how its warehouse software records split lots. The food safety team reviews whether traceability links and test methods need updating. The organisation checks the real workflow, including exceptions, before relying on the revised information.
This is an updating activity even if no product incident has occurred. If testing reveals missing links, the organisation addresses the nonconformity and its consequences. The software provider's release announcement alone cannot establish that the distributor's configured use remains effective.
Evidence and common weaknesses
An auditor may follow one closed finding into later operating evidence or ask how the food safety team evaluated a relevant change. Required documented evidence covers nonconformities, actions and results, together with system updating activities. Supporting information should explain the decisions sufficiently for later review.
Common weaknesses include “retrain staff” as the default response without cause analysis, checking effectiveness immediately before the process runs again, and updating the hazard plan without reviewing connected information. Another is waiting for an incident before considering new knowledge that could affect the system.
Explore each numbered part
10.1 · correct FSMS failures and prevent recurrence elsewhere
An FSMS nonconformity needs a response that addresses both the immediate issue and its causes. This guide explains correction, consequences, recurrence and the check for similar problems elsewhere. Manufacturing and catering examples show how to choose proportionate corrective action, verify effectiveness and update the system without defaulting to generic retraining or another unused procedure.
10.2 · improve the food safety system through evidence
Continual improvement should make the FSMS more suitable, adequate and effective. This guide explains how existing system activities generate improvement opportunities and how management can choose and evaluate them. Manufacturing and catering examples distinguish a useful improvement from more paperwork, a larger dashboard or a change whose food safety consequences have not been assessed.
10.3 · keep the FSMS current as the food chain changes
An FSMS needs updating when its information, controls or operating context change. This guide explains top-management accountability, the food safety team's planned evaluation and the inputs that inform review. Manufacturing and catering examples show how to connect new information with technical decisions, retain updating evidence and report the results back into management review.
Frequently asked questions
Is a correction enough for every nonconformity?
The organisation evaluates the need to eliminate causes and prevent recurrence or occurrence elsewhere. The response depends on the issue and its effects; simply fixing the immediate symptom may leave the underlying weakness.
Must the food safety team update every document at fixed intervals?
The team evaluates the FSMS at planned intervals and considers necessary reviews and updates. The purpose is a current, effective system, not changing every document merely to display a recent date.
Can system corrective action replace product control?
No. Where product or process failures are involved, apply the relevant operational requirements, including evaluation and disposition. System improvement and immediate product protection must remain connected.
Improve the quality of corrective action
Sterling can help strengthen investigation, responsibility, evidence and follow-up within a scoped FSMS engagement. Effivity ISO & GRC automation software and employee learning can support the agreed process. Discuss recurring findings or updating needs. Review and enrol in Root Cause Analysis and CAPA for the investigation discipline, applying it with the technical food safety competence the issue requires.
Return to performance evaluation or the hub, and begin the next system review with context and scope.