ISO 22000 clause 6.3: keep food safety arrangements coherent during change
ISO 22000 clause 6.3 requires changes to the FSMS, including personnel changes, to be carried out and communicated in a planned manner. The organisation considers the purpose and potential consequences, continued system integrity, necessary resources and allocation or reallocation of responsibilities and authorities. The aim is a coherent system during and after the change.
What clause 6.3 requires in practice
Clause 6.3 applies whenever the organisation decides that the FSMS needs to change. The change, which expressly includes changes of personnel, must be handled and announced through a planned route, instead of drifting in through informal habit.
Four points must be considered during that planning. The first is the purpose of the change and what it might lead to. The second is whether the system will remain whole and effective afterwards. The third is whether resources are available to put the change into effect. The fourth is how responsibilities and authorities are to be allocated or reallocated.
The clause does not list technical reviews, but a change in practice often triggers other requirements, such as updating information under clause 8.6. The outputs are a planned transition, communication to those affected and confidence that the system still functions as a whole. No change form or committee is prescribed.
Identify what the change affects
Start with the intended benefit and the affected products, services, processes, locations and people. A new supplier, altered distribution route or different shift arrangement can affect more than the initiating department. Trace the dependencies before treating the change as a local administrative task.
Consider information used in hazard analysis, prerequisite programmes, the control plan, competence, communication and verification where relevant. The technical review must be appropriate to the change; a management approval does not establish that a revised process has been validated.
Use clause 8.6 for updating operational information and clause 10.3 for wider FSMS updating. These connect with planned change but do not remove its need for deliberate coordination.
Plan resources and responsibility before the transition
Determine who decides, who implements, who supplies information and who checks the result. Consider whether the necessary competence and time are available. A person leaving a role may hold practical knowledge or approval authority that is not visible in the organisation chart.
Define interim arrangements if old and new processes operate together. Specify which information applies to each phase and how the handover is recognised. Otherwise, two individually reasonable arrangements can create an unsafe ambiguity at their interface.
A project record or an existing change process can support this work. Clause 6.3 does not prescribe a universal change form or board. The planning should be proportionate to the consequences, while still addressing the required considerations.
Communicate the change to the people who must act
Communication is part of the requirement, not a final courtesy after implementation. Identify affected operators, supervisors, technical personnel and relevant external parties. Explain what changes, when it applies and where the authoritative information is available.
Check whether the communication can be used at the point of work. A changed instruction available only to office staff may leave a remote catering site following the former arrangement. Confirm the receiving team's understanding and resolve access barriers.
Why planned change matters to the business
Food businesses change constantly: new suppliers, new equipment, new shifts, new managers. Each change can quietly invalidate assumptions that the existing arrangements relied on. Unplanned change is a frequent source of incidents, because the person approving the commercial benefit may not see the food safety consequence. Clause 6.3 protects the business by requiring that consequences, resources and responsibilities are thought through before the change goes live. Handled well, it makes growth less risky, keeps customers informed and avoids the situation where a loss of one experienced person leaves a gap nobody noticed until an audit or an incident exposed it.
How to keep arrangements coherent during change
Use the change routes you already have and add the food safety questions that clause 6.3 raises. Proportion matters: a small shift in a routine task needs a short check, while a new site needs a fuller plan. Either way, make sure the people who must act hear about it first.
- Define what counts as a change to the FSMS, including departures and arrivals of people with food safety responsibilities.
- Add a short checklist to your project or approval route covering purpose, consequences, system integrity, resources and responsibilities.
- Involve the food safety team before approval so that technical reviews and information updates can be planned.
- Agree interim arrangements where old and new methods will run together, and state which information applies to each.
- Tell all affected people, including remote sites and contractors, what is changing and where the current instruction sits.
- Confirm after introduction that operating teams have adopted the new arrangement before closing the change.
- Record lessons for the next change.
Illustrative food-manufacturing example
A manufacturer appoints a new food safety team leader while introducing a process change. The transition plan separates the incoming person's competence development from the technical decisions already underway. Management clarifies interim approval authority and ensures access to the relevant validation and operating information.
A handover review checks unresolved actions and decisions, rather than treating a signed personnel transfer as proof that the FSMS responsibilities have moved successfully.
Illustrative catering example
A caterer moves production to a different kitchen while retaining some service points. The team examines changed equipment, layout, transport interfaces and supervision. It plans the necessary technical reviews and information updates before the new arrangement becomes routine.
During the transition, service staff know which preparation site supplied each delivery and which instructions apply. A later check confirms that obsolete assumptions have not remained in records or local practice.
Evidence and common mistakes
Useful evidence explains the change's purpose, assessed consequences, resource decisions, responsibilities, communication and appropriate completion checks. Not every item needs a separate document, but the account should be coherent enough to follow.
Common mistakes include changing the scope statement alone, bypassing technical review because the change is urgent and failing to plan temporary responsibilities. Another is closing the project before checking whether operating teams have adopted the revised arrangement. Administrative completion and effective implementation are different conclusions.
Frequently asked questions
Do personnel changes count?
Yes. The clause explicitly includes them. Consider competence, knowledge, responsibility and authority affected by the change.
Is a separate FSMS change form mandatory?
No particular form is prescribed. An existing process can work if it supports planned implementation, communication and the required considerations.
Does management approval replace technical validation?
No. Relevant technical requirements still apply. Approval should rely on suitable evidence rather than substitute for it.
Plan the transition before assumptions diverge
Review a proposed FSMS change with Sterling to identify responsibilities, evidence and learning needs. Effivity ISO & GRC automation software can support agreed management arrangements. Explore ISO 22000 Food Safety Awareness; use clause 6 and the requirements hub for the wider plan.