Audit resource
A food safety management system (FSMS) is the document that ties everything else together — HACCP plan, SOPs, allergen policy, monitoring records, audit procedures. An inspector should be able to pick it up and understand how the whole system connects.
Document preview
Full document available in your workspace
Scope statement first — which sites, products, and processes are covered.
A controlled index of all component documents, not just a list of what exists.
Management commitment and review frequency named explicitly, not assumed.
Scope statement
Which premises, which product categories, which processes are in — and which are out. This is what tells an inspector (and your own team) exactly what the system covers.
Document register
A controlled index listing every component — HACCP plan, each SOP, allergen policy, traceability procedure, audit checklist — with version number, last review date, and the person responsible for it.
Management commitment section
Who is responsible for food safety at the site, what their role is, and how often the system gets reviewed. This answers one of the most common inspection questions before it's even asked.
Review log
Dates and brief outcomes of each system review. Even a few lines per review is enough — it's what turns a static document into evidence that the system is actively managed.
A lot of FSMS documents skip this or write it vaguely. But scope is what defines the whole system. Which premises does it cover? Which products? If part of the operation is excluded, why? Getting this right at the start prevents a lot of confusion when the document is reviewed by someone unfamiliar with the site.
For each component — HACCP plan, each SOP, allergen policy, traceability procedure — the FSMS records the document title, version number, last review date, and who owns it. That's what shows the system is maintained, not just assembled once and put in a folder.
Operations change. New products, new processes, new legislation. The document should state how often the whole system is reviewed — annually is typical — and what triggers an unscheduled review. Documenting the outcome of each review, even briefly, provides the audit trail that shows someone is actually in charge of this.
Ready to start?
Try PinkPepper on a real compliance question today.
Free template
Download this template as DOCX
Create a free account to access PinkPepper, then upgrade to Plus or Pro to download all 15 templates as editable Word documents.
Sign up freeAlready have an account? Log in
