The short answer: the SQF Code names no refresher interval at all. Search the training element of the SQFFood Safety Code: Food Manufacturing, Edition 9 for “annual” and you won’t find it. What the code requires instead is arguably stricter: your documented training program must include provisions for identifying and implementing the refresher training needs of the organization (clause 2.9.2.1). You choose the cadence — and then your records have to prove you kept it.
- No clause in SQF Edition 9 mandates a fixed refresher interval — the site defines its own.
- The obligation is real anyway: the program must identify and implement refresher needs, and lapses against your own cadence are findings.
- Edition 10 sharpens this into an explicit duty to determine the frequency of training.
- SQFI guidance suggests annual, seasonal, on-change, and on-drift as typical refresher triggers.
- The one 'at least annually' near training in Edition 9 is the food defense plan review — not personnel refreshers.
What each edition actually says
| Capability | Edition | Refresher language | What it means |
|---|---|---|---|
| Edition 9 (audited today) | Program must include provisions for identifying and implementing refresher training needs (2.9.2.1) | You define the cadence; the auditor holds you to it | |
| Edition 10 (anticipated from Jan 2, 2027) | Site must determine the frequency that training is to be conducted (2.9.1.1) | Defined intervals become an explicit program output |
The practical difference is small but auditable: under Edition 9 a program that says “refreshers as needed” is arguably compliant on paper (if hard to defend); under Edition 10 the frequency itself must be determined. Writing defined intervals per topic now satisfies both editions.
The cadences SQFI’s guidance points to
SQFI’s tip-sheet guidance on training describes refresher training running on several triggers, not just the calendar:
- Annually — the calendar-driven option in SQFI’s list
- At the start of a season — for seasonal operations and returning workforces
- When a product, process, or system changes — change-driven retraining
- When monitoring shows drift — evidence-driven retraining, before it becomes a finding
That last pair matters: a defensible program treats refresher training (calendar-driven) and retraining (change- or evidence-driven) as different mechanisms. When your allergen procedure changes, the people running it need retraining now — not at the next annual refresher.
One trap: the annual review that isn’t refresher training
Edition 9 does contain an “at least annually” requirement in training’s neighborhood — but it belongs to the food defense plan, which must be reviewed and tested at least annually (clause 2.7.1.4; the neighboring instruction clause 2.7.1.3 sets no frequency). That is a plan-maintenance duty, not a personnel-refresher mandate, and citing it as “SQF requires annual training” overstates the code. If a consultant or checklist tells you SQF mandates annual refreshers, they’re describing common practice, not clause text.
Making your cadence provable
Whatever intervals you define, the audit question becomes mechanical: for each recurring topic, can you show the last completion, the defined interval, and the next due date — for every person in scope? That’s the discipline covered in recurring training and certification tracking. On paper it means a well-kept calendar; in software, recurrence does the arithmetic — in a tool like TrainGrid each course carries its interval, completing it schedules the next due date automatically, and anything drifting toward overdue gets flagged while it’s still a reminder rather than a finding.