We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
ISO Standards

What Documents You Need for ISO 22000:2018 Implementation

What Documents You Need for ISO 22000:2018 Implementation
In short

A practical list of the documents and records needed to build and run an ISO 22000:2018 food safety management system, grouped by clause area.

In this article
  1. Documents vs records: the distinction that saves effort
  2. Core management system documents
  3. Operational documents: where food safety is controlled
  4. Support, evaluation and improvement records
  5. How to decide what you really need
  6. Building the documents: start from a framework, not a blank page
  7. Frequently asked questions

Teams starting an ISO 22000:2018 project usually ask the same question: how many documents do we actually need? The standard does not give a fixed list or a page count. It requires "documented information" that is needed for the food safety management system (FSMS) to be effective, and it expects that information to match your products, processes and size.

This article sets out the documents and records most food organisations end up with, grouped by area, and explains how to decide what is truly needed.

Documents vs records: the distinction that saves effort#

ISO 22000:2018 uses one term, documented information, for two different things. It helps to separate them when you plan.

  • Documents state what you intend to do: policies, procedures, plans, work instructions, specifications. You maintain and update them.
  • Records prove what happened: monitoring logs, audit reports, training evidence, calibration certificates. You retain them and protect them from alteration.

A common mistake is writing long procedures for activities that only need a simple form, or the reverse: running a critical control with no written plan behind it. Start from risk. The more a process affects food safety, the more precisely it should be defined and evidenced.

Core management system documents#

These documents set the framework. Most auditors will expect to see them early.

  • Scope of the FSMS: the products, processes, sites and activities covered, plus any justified exclusions.
  • Food safety policy: signed by top management, communicated and understood in the organisation.
  • Food safety objectives: measurable targets with owners, plans and review dates.
  • Context and interested parties analysis: internal and external issues, customer and regulatory requirements.
  • Roles, responsibilities and authorities: including the food safety team leader and how the team is formed.
  • Risk and opportunity register: the organisation-level risks you have chosen to address, separate from product hazards.
  • Document and record control procedure: how information is approved, issued, revised, retained and disposed of.

Operational documents: where food safety is controlled#

This is the largest and most scrutinised area. It brings together prerequisite programmes, traceability, emergency readiness and hazard control. If you already run HACCP, much of this will be familiar; our guide on documents needed for HACCP implementation covers the plan itself in more depth.

Prerequisite programmes (PRPs)#

Document the basic conditions and activities that keep the environment hygienic. Typical topics include:

  • Cleaning and sanitation
  • Pest control
  • Personal hygiene and staff facilities
  • Maintenance of buildings and equipment
  • Waste management
  • Water and utility control
  • Allergen management and cross-contamination prevention
  • Supplier approval and incoming material control

Each needs a defined method, a responsible person, a frequency and a record format.

Preliminary information for hazard analysis#

  • Descriptions of raw materials, ingredients, packaging and finished products, including intended use and shelf life
  • Process flow diagrams
  • Descriptions of the process steps and the control measures applied

These should be checked on site and kept current. An out-of-date flow diagram is one of the most common findings in food safety audits.

Hazard analysis and hazard control plan#

  • Hazard identification and assessment, with the reasoning behind the significance decisions
  • Selection and categorisation of control measures, split between critical control points (CCPs) and operational PRPs (OPRPs)
  • The hazard control plan: limits, monitoring method, frequency, responsibility, correction and corrective action for each CCP and OPRP
  • Validation evidence showing the control measures can achieve the intended result

Traceability, emergencies and incidents#

  • Traceability procedure and records linking inputs, processing and dispatch
  • Emergency preparedness and response procedure
  • Withdrawal and recall procedure, with contact lists and test records
  • Procedure for handling potentially unsafe products and nonconforming output

Support, evaluation and improvement records#

These are the records that show the system is being run, not just written.

AreaTypical documents and records
Competence and trainingRole requirements, training plan, training and competence records
CommunicationProcedure for communicating with suppliers, customers, authorities and staff
Monitoring and measuringEquipment list, calibration and verification records
VerificationVerification plan, results of PRP checks and hazard control plan reviews, product testing
Internal auditAudit programme, audit reports, auditor competence evidence
Management reviewAgenda, inputs, minutes and recorded decisions
Nonconformity and corrective actionProcedure, nonconformity log, root cause analysis, action follow-up
Updating the FSMSRecords of changes to hazards, processes or controls and how the system was updated

How to decide what you really need#

Use these steps to avoid both gaps and bloat.

  1. Map the standard to what you already have. Many sites already have cleaning schedules, supplier forms and HACCP plans. Reuse them where they meet the requirement.
  2. Run a gap assessment. List each requirement, note what exists, what is partial and what is missing. This gives you a document plan based on facts.
  3. Consider customer and regulatory requirements. Retailers and national food laws may add documentation expectations beyond the standard. If you are also considering a scheme-based certification, see what documents you need for FSSC 22000 v6, which builds on ISO 22000 with extra requirements.
  4. Match detail to risk and competence. A high-risk ready-to-eat line needs tighter instructions than dry storage. Experienced staff may need a short checklist rather than a long procedure.
  5. Pilot the forms. Have operators fill in the logs for a week. If the form is awkward, it will be completed late or inaccurately.
  6. Control versions from day one. Assign owners, review dates and approval status so the system does not drift.

Keep your wording specific. "Clean equipment regularly" is not auditable. "Clean the filler nozzles after each batch changeover, verified by a swab check" is.

Building the documents: start from a framework, not a blank page#

Writing a complete FSMS from scratch takes time that most food teams would rather spend on the floor. A structured template set lets you edit rather than invent. The ISO 22000:2018 Toolkit from AdWiser provides editable policies, procedures, controls, checklists and worked examples across 7 document areas, along with a gap assessment checklist. Whatever source you use, the templates must be tailored to your products, process steps and hazards before they mean anything to an auditor.

Frequently asked questions#

Does ISO 22000:2018 require a food safety manual?#

No. The standard does not require a manual as a named document. Many organisations still create a short overview of the FSMS because it helps staff and auditors navigate the system, but it is optional.

Can we use our existing HACCP plan?#

Often yes, as a starting point. ISO 22000:2018 builds on the Codex HACCP principles but also expects management system elements such as leadership, risk-based planning, internal audits and management review. Review your plan against the standard and add what is missing, including how you distinguish CCPs from OPRPs.

How long should we keep records?#

The standard expects you to define retention. Base the period on product shelf life, customer and legal requirements and your recall needs, then state it in your document control procedure. Retaining records for at least the shelf life of the product is a common starting point.

If you would like to compare your current documentation with what the standard expects, the ISO 22000:2018 Toolkit and its gap assessment checklist are a practical place to begin.

Share this guide

Ready to put this into practice?

Start with the ISO 22000:2018 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp