ISO 22000 clause 10.2: improve the food safety system through evidence
ISO 22000 clause 10.2 requires continual improvement of FSMS suitability, adequacy and effectiveness. Top management must ensure that communication, management review, internal audit, verification-result analysis, validation, corrective action and system updating contribute to improving effectiveness. Improvement is therefore part of the operating system, not a separate suggestion campaign.
What clause 10.2 requires in practice
Clause 10.2 requires the organisation to keep improving its FSMS so that it stays suitable, adequate and effective over time. The responsibility is given to top management, who must ensure improvement actually happens through a stated set of mechanisms: communication, management review, internal audit, analysis of verification results, validation of control measures and combinations of control measures, corrective actions, and updating of the system.
The clause does not ask for a separate improvement scheme, a suggestion box or a minimum number of projects. It treats improvement as an outcome of activities that already exist. That means evidence of improvement can usually be found in the records of those activities: a management review decision that led to a changed process, an audit finding that resulted in clearer responsibilities, or a verification trend that triggered a revalidation. What matters is that the system becomes more suitable, more adequate or more effective over time, and that this is a consequence of deliberate decisions rather than chance.
Identify the result that should improve
Describe the weakness or opportunity and the intended benefit. It may concern a more reliable handover, clearer monitoring decisions, better availability of competent personnel or more effective review of changes.
Use evidence to establish the need. Audit findings, recurring correction records, verification trends and relevant communication can reveal where the system struggles. Successful practice can also identify an opportunity, provided its applicability is evaluated.
Avoid equating improvement with additional documents or software. Those can support a change, but the intended result should concern how the FSMS works and the decisions it enables.
Connect existing activities instead of duplicating them
Use management review to decide priorities and resources, corrective action to address failures and updating to maintain a current system. Verification and validation provide different technical information that can inform improvements.
Make information flow between these activities. A recurring verification weakness should not remain separate from audit planning and management decisions. A management decision should reach the team responsible for the affected plan or PRP.
Not every improvement begins with a nonconformity. Better understanding of a process or a changed operating need can justify a proactive improvement while the current arrangement still meets requirements.
Evaluate the change and its effect
Define how the organisation will know whether the improvement worked. Use evidence related to the original need, not simply a record that the new arrangement was introduced.
Consider the food safety consequences of the change before implementation. An efficiency improvement can alter process conditions or responsibilities and may require technical review or validation. Improvement language does not exempt the change from existing controls.
Review results and adjust where necessary. Continual improvement involves learning from the effect of actions, including cases where a proposed solution did not achieve the intended outcome.
Illustrative food-manufacturing example
A manufacturer finds repeated uncertainty in identifying product affected by a monitoring failure. It improves the relationship between monitoring records and production intervals, develops personnel and tests the revised arrangement through scenarios.
The useful result is faster, more dependable identification supported by evidence. The improvement is not simply the addition of another field to a form.
Evidence and common mistakes
Use records from the relevant system processes to show the need, decision, implementation and result. A separate improvement register can be useful but is not prescribed by clause 10.2.
Common mistakes include counting ideas as completed improvements, repeatedly fixing symptoms and claiming success from purchase or training completion alone. Another is selecting changes for visible novelty while leaving a recurring significant weakness unresolved.
Keep the scale appropriate. A focused change that resolves a persistent decision problem can be more valuable than a broad programme with no clear evidence of effect.
Choose an improvement with a clear food safety benefit
Discuss an FSMS improvement priority with Sterling. The scope can connect implementation, learning and appropriate Effivity ISO & GRC automation software support. Review KPIs, Objectives & Management Review, the improvement overview and the hub.
How to implement clause 10.2
Make improvement part of normal work by connecting the existing inputs to one prioritised list. This avoids a separate improvement scheme that competes for attention with audit and corrective-action work.
- Collect improvement opportunities from review decisions, audit observations, analysis results, validation outcomes and communication from customers and staff.
- Describe each opportunity in terms of the weakness or need, the benefit expected and the part of the FSMS affected.
- Prioritise with top management, favouring changes that remove a recurring weakness or support a stated objective.
- Before implementing, ask the food safety team whether the change touches hazard control, and arrange validation or review where it does.
- Assign an owner and define in advance what evidence will show that the change worked.
- Pilot where practical, then extend the change only after checking that conditions at other sites or shifts are comparable.
- Report results at management review, including changes that did not work, and record what was learned.
Frequently asked questions
Does continual improvement mean constant process change?
No. It means continuing to improve the system's suitability, adequacy and effectiveness through appropriate evidence-based action.
Can improvement occur without a nonconformity?
Yes. Opportunities can arise from learning, changed needs or better ways of achieving the intended result.
Does software installation demonstrate improvement?
Only if suitable evidence shows the intended system benefit. Installation is an activity, not the final effectiveness judgment.
Illustrative catering example
A catering business learns from one site's effective handover practice. Before extending it, the food safety team evaluates differences in service arrangements at other sites and adapts the approach where necessary.
Later verification examines whether the changes improve handover reliability. The organisation does not assume that copying a successful form transfers every condition that made it work.