ISO 22000 Management Review NZ: Turning Food Safety Evidence into Decisions

An ISO 22000 management review should help management decide whether the food safety management system (FSMS) is working and what it needs next. A folder of monitoring records or a presentation showing completed tasks is useful evidence, but the review also needs a clear route from that evidence to a decision.

This guide is for New Zealand food businesses preparing that decision process. It focuses on food-safety performance, resources and follow-up. For the wider certification pathway, use our ISO 22000 certification guide.

What an ISO 22000 management review is for

As checked on 15 October 2026, ISO’s catalogue identifies ISO 22000:2018 as the current published standard, with Amendment 1:2024. A revision is under development; a draft is not a published replacement. Confirm the edition, amendment and any additional scheme or customer criteria applying to your business.

The official ISO/IAF climate-change communiqué explains the additions to clause 4.1 about determining whether climate change is relevant, and the clause 4.2 note about related requirements of relevant interested parties. Where that assessment identifies food-safety implications, our recommendation is to bring the relevant effects, changes and resource needs into the review. These context changes do not make the practical worksheet below a prescribed climate agenda or a universal carbon-reporting requirement.

NQA’s ISO 22000 implementation guide explains management review as a planned top-management assessment of the system’s continuing suitability, adequacy and effectiveness. It describes retaining information about the review and its results. Its discussion includes performance trends, context changes, resources and improvement, with outputs concerning decisions and actions for improvement and FSMS changes.

That explanatory guide does not reproduce every review input. Use an authorised copy of the applicable standard for the complete requirements. This article offers a practical way to organise the discussion; it does not replace the standard, an internal audit, hazard-control decisions or the certification body’s assessment.

For preparation, ask three connected questions: does the system still fit the food activities and conditions in scope; does it have the support it needs; and what evidence shows that it achieves its intended food-safety outcomes? The useful record explains management’s answer and the action that follows.

Prepare evidence that supports a decision

Define the period, scope and question

State the period being reviewed and the sites, products, processes and outsourced activities it covers. Identify changes since the previous review, such as a new product, supplier, line, shift or storage arrangement. Explain whether each change has already been assessed or still needs a decision.

Begin with previous actions and the food-safety objectives they were meant to support. Separate an action completed on paper from one shown to work. Where something remains open, show its current status, the reason, any interim arrangements and the decision needed from management.

Turn records into an understandable account

For each subject, give a concise summary and a reference to the supporting records. Explain the source, period, coverage and limitations of the information. A count of complaints or incomplete records can be misleading without the amount of activity, the type of issue and whether reporting practices changed.

• Show the comparison: use the same definitions and units when comparing periods, or explain why they differ.
• Keep significant exceptions visible: a reassuring total should not hide a recurring problem on one shift, line or product.
• State evidence gaps: say what was not checked or is still being investigated. Do not turn missing information into a positive result.
• Identify the decision: explain whether management needs to approve resources, change a system arrangement, commission further work or confirm an existing approach.

Keep urgent operational matters in the business’s immediate response process. A planned review is a place to examine their wider causes, resourcing and lessons; it is not a reason to postpone action on a live food-safety concern.

A practical evidence-to-decision worksheet

Use these selected discussion prompts to prepare the review. They are our suggested working questions, not an exhaustive list of ISO 22000 clause 9.3 inputs. Add the subjects required by your actual standard, scope and other applicable criteria.

Audit findings are one source of evidence, not the entire review. If the audit coverage itself needs work, discuss the scope of AFVA’s internal audit support separately. Likewise, staff feedback may reveal barriers that a record count misses; our food safety culture guide considers the wider leadership and reporting environment.

Illustrative review record: repeated late record reviews

Evidence and question: A food manufacturer’s selected records show repeated delays in supervisory review after a shift change. An earlier reminder was issued, but the review does not yet have evidence that the delays reduced. Management asks whether the review task, cover arrangements and available time are clear, rather than assuming another reminder will solve it.

Decision and resources: Management agrees that operations and the food-safety lead will examine the workflow and confirm the cause. Protected review time and a named cover arrangement are authorised for the agreed trial. Any necessary instruction change will follow the business’s document-control process.

Owner and follow-up: The action record names the operations manager, the agreed completion date and the person checking the result. The follow-up will examine relevant records across the affected shifts and ask whether review is timely and useful, rather than checking only that a new instruction exists. The sampling approach and review period are chosen for the actual operation.

Conclusion at this review: The action is open. The record identifies what has been authorised and what evidence is still needed. A later review can then distinguish a completed trial from a demonstrated improvement. No successful outcome is assumed in advance.

Follow the decision through to effectiveness

A useful action log connects the review to everyday work. Our recommendation is to retain the review date and scope, evidence references, the issue discussed, decision and reasons, resources, responsible owner, due date and the agreed follow-up. Use existing systems where they provide a reliable link.

1. Before the review: agree the scope, collect the current evidence, identify gaps and show previous actions. Give the decision-makers enough information to prepare.
2. During the review: discuss the evidence and its limits. Make the decision explicit, including a justified decision to retain an arrangement or request further work.
3. After the review: communicate relevant decisions to the people carrying them out. Put agreed resources and changes into effect, and retain the supporting evidence.
4. At follow-up: check both implementation and effectiveness. Record what was examined, what it showed and whether the action is closed, revised or escalated.

For example, buying equipment demonstrates a purchase; it does not by itself show that the food-safety problem was resolved. The follow-up question is whether the equipment, its use and the surrounding controls produced the intended result. If the evidence is inconclusive, record the next check and who will arrange it.

Keep decisions that affect policy, objectives, responsibilities or other system documents connected to the relevant controlled updates. A review record and the instructions used on the floor should tell a consistent story.

Common management-review mistakes

• Reporting activity without evaluating it: explain what the results mean for the objective or question, not only how many checks took place.
• Allowing one overall figure to hide a recurring issue: show relevant product, site, shift or process differences and the limitations of the comparison.
• Recording “management to action”: name the person responsible and the support agreed so the decision can be carried out.
• Leaving resources implicit: identify the time, equipment, competence or other support needed and who can authorise it.
• Closing an action when a document is issued: distinguish making the change from establishing whether it worked.
• Treating a template as the requirements: check coverage against the applicable standard and criteria rather than assuming these selected prompts are complete.

How AFVA can help prepare the review

Access Food Verification & Auditing Limited provides ISO consulting and preparation support for food businesses, including gap assessments, document review, internal auditing, corrective actions and management-system review. An agreed engagement can help organise the evidence, identify gaps and prepare a practical action record.

Management remains responsible for its system and decisions. AFVA does not issue ISO certificates or guarantee certification. ISO’s explanation of ISO 22000 and certification distinguishes the standard from independent certification. This article offers consulting support; any separate regulated verification or evaluation service needs its own scope and independence assessment.

Start with the decisions your evidence needs

Choose the food-safety questions management needs to resolve, connect each to the available evidence and identify the gaps. Then keep the decisions and follow-up visible. The value of the review is the link between what the business learned and what it did next.

General information only: This is a practical preparation guide, not the complete ISO 22000 requirements, an audit conclusion or a certification decision. Use the applicable authorised standard, amendment, scheme and customer criteria for your scope. Food-safety incidents and separate regulatory obligations need their own timely assessment. Information checked on 15 October 2026.