SQF Management Review: Essential 2026 Guide and Minutes

SQF management review is the point where site leadership looks at the evidence from the whole food safety system and decides what to change. In the SQF Food Safety Code: Food Manufacturing, Edition 10, it sits at element 2.1.2, and it carries two labels that raise the stakes: it is a Mandatory element, so it can never be reported as not applicable (Part A, A2:8), and it is one of the 11 Core Clauses.

Being a Core Clause changes what a weak review costs. Under A2:19 a minor non-conformance against a Core Clause deducts 2 points instead of 1, and a major deducts 7 instead of 5. A management review that exists on paper but decides nothing is an easy place to lose points you cannot spare.

This SQF management review guide covers what 2.1.2 asks for, the inputs for both the annual review and the monthly update, who should attend, what the outputs should be, and what good minutes contain. For the edition change itself, see our SQF Edition 10 guide.

What 2.1.2 requires: two speeds of SQF management review

Element 2.1.2 (Management Review) has two requirements, and SQFI’s change document marks both as changed in Edition 10:

• 2.1.2.1, the annual review. Site management reviews the whole SQF System at least once a year, against a defined set of inputs.
• 2.1.2.2, the monthly update. Site management is updated at least monthly on a shorter set of topics, so problems do not wait for the annual meeting.

The two belong together. Monthly updates become evidence for the annual review, and actions from the annual review get followed up month by month. Both produce records the Code expects you to keep: management review is on the list of annual records in 2.2.3.3, and monthly management updates are on the system records list in 2.2.3.4.

The SQF Practitioner is the natural organizer. In our reading, requirement 2.1.1.5 makes the Practitioner responsible for briefing relevant people, and it names the annual review and monthly updates among those briefings. Our SQF Practitioner guide covers the role in full.

SQF management review inputs: the annual agenda

2.1.2.1 names what the annual review must look at. In our own words, and in an order that works as an agenda:

The culture input (A4) ties to one of Edition 10’s new requirements, the food safety culture assessment plan at 2.1.1.3. If that plan is still being written, the review is where leadership commits the resources to finish it. Our SQF food safety culture guide explains what the plan needs.

Some inputs the Code does not list are still worth adding: adequacy of resources, changes in law or customer requirements, supplier performance, and the readiness plan for the next certification audit. Label them as additional so nobody confuses them with the required set.

The monthly management update

2.1.2.2 asks for an update to site management at least monthly. The content it describes falls into four groups:

1. Issues affecting the SQF System, such as CCP deviations, label changes, regulatory matters and adverse trends.
2. Corrections and corrective and preventive actions: opened, closed, overdue, and any that failed their effectiveness check.
3. Internal and external audit results, including progress against the internal audit plan. Our SQF internal audit guide covers how that program feeds this item.
4. Food safety complaints: number, category, serious incidents and trend status.

The monthly update does not have to be a separate meeting. It can be a fixed item in an existing management meeting, as long as the four groups are covered every month and minuted so the record stands on its own.

Be clear about one limit. The monthly update is not an escalation route. A CCP deviation, suspected unsafe product in the market or a regulatory warning letter goes to senior management at once. Where an event triggers SQF’s 24-hour written notice to SQFI and the certification body (2.6.3.3 for food safety events, 2.4.1.3 for regulatory warnings or actions), that clock does not wait for the next update. The update then records what happened and what was decided.

Who attends an SQF management review

The Code puts the duty on site management. It does not publish an attendance list, so build one that lets the review take real decisions. A practical setup:

The test is simple: is the person who controls budget and headcount in the room? If not, decisions on resources become recommendations, and the review loses its purpose. Set a quorum in the procedure, for example the senior site manager or a named deputy plus the SQF Practitioner or substitute.

Outputs: what the review must decide

2.1.2.1 lists inputs. Decisions are what show that the review happened, so plan the outputs as carefully as the agenda. For each input, ask three questions and record the answers:

• Is it working? Rising trends, repeat findings and missed tests say no.
• Is it still suitable? New products, lines, suppliers, customers or law may mean the approach must change.
• Is it resourced? Does the owner have the people, time and equipment for the coming year?

A “no” should produce an action, a decision not to act with the reason, or a change routed through change management. Change management is element 2.3.5, a new element in Edition 10, and requirement 2.3.5.1 covers temporary, emergency, unplanned and corrective-action-driven changes.

The annual review should also confirm or revise the food safety policy, set objectives for the coming year, decide resources, and end with the senior site manager’s conclusion on whether the system remains suitable and effective. Every action gets an owner, a due date and a statement of how completion will be shown.

What good SQF management review minutes contain

Minutes are what the certification auditor reads, so write them to be read by a stranger. Whether you use a template or your own format, good minutes hold:

Keep one action list across both levels. Open actions come up at every monthly update, overdue ones get escalated with a revised date and a reason, and actions that fix a non-conformance also go into the corrective action register under 2.5.3 so their root cause and effectiveness are tracked.

Watch for the gaps that make minutes weak: inputs listed with no conclusion against them, trends shown as single-month numbers, actions with no owner, and the same open action carried forward year after year with no decision.

The SQF Edition 10 Toolkit includes a Management Review Procedure that sets out both levels of review with the inputs as a fixed agenda, and a Management Review Minutes and Monthly Update Workbook with an annual minutes tab, a monthly update tab and a single action list.

Timing during the edition change

SQFI anticipates that Edition 10 audits will begin on 2 January 2027, not earlier, and only once GFSI benchmarking is complete, so the date could still move later, according to its Edition 10 FAQ (checked 4 November 2026). Until then Edition 9 stays in use. Part A, A2:7 recommends at least 90 days of records before an audit during an edition change. For SQF management review, that window would hold roughly three monthly updates, so start running the Edition 10 format at least three months before your first Edition 10 audit.

SQF management review FAQ

How often is SQF management review required?

The full review of the SQF System is at least annual under 2.1.2.1, and site management must also be updated at least monthly under 2.1.2.2. You can also add a triggered review after a recall, a failed audit or a major change of scope; the procedure, not the Code, sets that.

Can the monthly update be part of our weekly or monthly operations meeting?

Yes, provided the four monthly topics are a fixed agenda item every month and the record shows each was covered. Keep that section of the minutes separate so it can be retrieved on its own.

Who has to sign the SQF management review?

The Code gives the duty to site management. A defensible practice is for the senior site manager to approve the annual minutes and conclusion, with the SQF Practitioner issuing them.

What happens if we miss a monthly update?

Treat it as a gap in a Core Clause. Circulate the inputs in writing that month and get documented confirmation from site management, then cover both months at the next update. A missed annual review should be raised as a non-conformance in your own corrective action system.