ISO 22000 clause 9.3.3: turn management review into owned changes

What clause 9.3.3 requires in practice

Clause 9.3.3 is about what comes out of the management review. The outputs include decisions and actions related to opportunities for continual improvement, and any need to update or change the FSMS. The clause gives the need for resources, and revising the food safety policy and objectives, as examples of changes to consider.

The organisation keeps documented information as evidence of what the management reviews concluded. In practice that means a record which shows what management concluded, not merely which topics were on the agenda. A decision to keep an arrangement unchanged is a valid output where the evidence supports it. The standard does not require a particular minute format, nor does it require policy changes at every review. It does expect that the review leads to outcomes that can be seen later, including decisions on resources, which links to 7.1, and changes that the food safety team can then carry into its updating work under 10.3.

Separate a decision from a topic discussed

Record what management concluded and why it matters. An entry such as training discussed does not explain whether a need was accepted, what action was chosen or whether further evidence is required.

Decisions can include maintaining an arrangement where it remains suitable, requesting additional information or making a change. The point is not to generate a new project for every agenda item but to make the result clear.

Connect outputs with the relevant inputs and objectives. This allows later reviewers to understand why management selected the action and what it intended to achieve.

Address system changes and resources

Consider whether the FSMS needs updating, including changes to responsibilities, processes, support or control arrangements. Resource decisions may concern people, competence, infrastructure or other support needed for effectiveness.

Policy and objective revisions may be appropriate when circumstances or evidence change. They are not automatically required at every review. Where revision is chosen, apply the relevant planning, communication and documented-information arrangements.

Use FSMS updating to connect management decisions with the food safety team's review of hazard analysis, the control plan and PRPs where relevant.

Make follow-up workable

Assign clear responsibility and a suitable intended completion point as practical action-management choices. Identify the evidence that will show completion and, where relevant, the intended effect. These details make the decision executable.

Follow earlier review actions through subsequent review inputs. An action can be completed while its intended result is not achieved. Management should understand that difference rather than treating closure status as the final judgment.

Where implementation changes the operation, consider the relevant change-planning requirements. A management approval does not remove the need for technical evaluation or validation where applicable.

Why review outputs must become owned changes

Management reviews often fail at the last step. The discussion is thoughtful, the minutes record topics, and six months later the same problem returns because nobody was asked to fix it. Clear outputs are what convert a meeting into improvement. They show which resources were granted, which weaknesses will be addressed and who will report back. For the business, this protects investment: money for equipment or training is released against a stated purpose and later checked against results. It also builds credibility with the food safety team, who see that raising a problem leads somewhere. Customers and assessors who ask to see evidence of management commitment will find it in decisions with owners rather than in attendance lists.

How to implement clause 9.3.3

Capture review results in a form that shows each decision, its reason, its owner and how success will be seen. Short, specific entries serve better than long narrative that never says what was authorised.

1. Use a simple decision log alongside the minutes, with one line for every conclusion reached in the meeting.
2. For each decision, record the related input, the action chosen, the responsible person and when progress will be reported.
3. State resource decisions explicitly, including requests declined or deferred and the reason.
4. Note whether the policy, objectives or FSMS arrangements need updating, and pass those items to the team handling updating.
5. Communicate relevant decisions to the people affected, using existing communication routes, and confirm they understood them.
6. Define the evidence that will show an action produced its effect, as distinct from simply being finished.
7. Carry open actions into the next review pack so leaders see what happened to what they decided.

Illustrative food-manufacturing example

Illustrative catering example

A caterer decides that a new remote-service model requires revised oversight and handover responsibilities. The output assigns the update and specifies which affected teams must be involved.

The next review checks implementation and evidence from the new arrangement. The original discussion is therefore connected with actual changes in the FSMS, rather than remaining an aspiration in meeting minutes.

Evidence and common mistakes