Food safety documentation is the evidence that your hazard controls exist, are followed and work, and every major food safety scheme asks for a version of the same core set. This guide maps that set across ISO 22000, FSSC 22000 Version 7, BRCGS Food Safety Issue 9 and SQF Edition 10, with HACCP underneath all four.
If you run one site and one scheme, your food safety documentation is a document list. If you run several sites, several customers or a scheme change, you need to know which documents are shared and which are scheme-specific. That is the decision this post helps you make.
Free gap assessment
Would your HACCP plan survive an inspection?
Score the whole of the Codex text, free - the good hygiene practices as well as the seven principles, with the US and EU overlays on top.
Run the free HACCP gap assessment → or View premium report sample
Which frameworks the food safety documentation has to serve
None of the four schemes is a law. Each is a voluntary standard or scheme, certified by an accredited body after an audit. Your legal duty comes from food law in the markets you sell into, and the schemes are how you prove control to customers. Documents support certification; they do not grant it.
| Framework | What it is | Who it applies to | Toolkit |
|---|---|---|---|
| ISO 22000 Food Safety | Certifiable international standard | Any organization in the food chain, voluntary or customer-driven | ISO 22000 Food Safety toolkit |
| FSSC 22000 Food Safety | GFSI-benchmarked certification scheme built on ISO 22000 | Manufacturers and other food chain categories whose customers ask for a GFSI scheme | FSSC 22000 Food Safety toolkit |
| BRCGS Food Safety Issue 9 | GFSI-benchmarked certification standard | Manufacturers supplying retailers and brands that require BRCGS | BRCGS Food Safety Issue 9 toolkit |
| SQF Edition 10 Food Safety | Certification code, audits against Edition 10 depend on GFSI benchmarking | Suppliers whose buyers specify SQF | SQF Edition 10 Food Safety toolkit |
| HACCP | Method, not a certificate on its own | Every food business, and the base layer for the four schemes above | HACCP toolkit |
The practical rule: HACCP is the foundation, ISO 22000 is the management system that wraps it, and the other three schemes are what customers actually ask for. FSSC 22000 is built directly on ISO 22000. BRCGS and SQF are separate standards with their own structure, but both are HACCP-based.
For a head-to-head on structure, grading and audit rules, read BRCGS vs SQF and SQF vs FSSC 22000. This post does not repeat those comparisons. It stays on the documents.
The food safety documentation set, document by scheme
Every scheme asks for roughly the same nine families of food safety documentation. What changes is where the requirement sits, how prescriptive it is, and whether an auditor expects to see it tested. The table gives the direction of each requirement. It is a planning map, not a substitute for the text of the standard you license, and the clause detail should always be confirmed against your own copy.
| Document | ISO 22000 | FSSC 22000 Version 7 | BRCGS Issue 9 | SQF Edition 10 | HACCP |
|---|---|---|---|---|---|
| HACCP plan | Hazard analysis and HACCP plan, retained as documented information | Required (the HACCP system sits inside ISO 22000, and FSSC 22000 inherits it) | Fundamental requirement, with a named HACCP team | Required, with a food safety plan built on HACCP | The plan itself: team, flow diagrams, hazard analysis, CCPs, limits |
| Prerequisite programs | Required, selected by you to suit the food chain segment | Required, plus the applicable ISO 22002 part | Required, set out in site standards and procedures | Required, with good manufacturing practice requirements by sector module | Assumed in place; the HACCP plan only works on top of them |
| Manual and policy | Policy and scope required; no manual as such | Same as ISO 22000, plus the scheme’s own requirements | Documented food safety and quality manual required | Policy and a documented system required | Not applicable (HACCP is a method, not a management system) |
| Records and document control | Maintained versus retained documented information | Same, plus certification-body rules on records | Controlled procedures and records, reviewed at audit | At least 90 days of records advised before a recertification audit during an edition change | Monitoring, verification and corrective action records |
| Food safety culture | No standalone clause; handled through leadership, communication and competence | Additional requirement with objectives, a documented plan and measurement | Culture plan with objectives and measurement | Culture assessment plan (new in Edition 10) | Not covered |
| Allergen management | Treated as a hazard in the hazard analysis | Addressed in the additional requirements and PRP layer | Allergen management is treated as a core part of the standard | Required, with a risk assessment and controls | Allergen hazards enter the hazard analysis |
| Traceability | Traceability system required (clause 8.3) | Same, plus scheme additions | Required, and tested during the audit | Required, with product identification and mock tests | Supported by lot and batch records |
| Recall and withdrawal | Procedure required, with a test | Same, plus scheme additions | Required, with testing | Required, with testing | Out of scope |
| Supplier approval | Control of externally provided processes and products | Same, plus scheme additions | Approval and performance monitoring of suppliers | Approved supplier program required | Raw material specifications feed the hazard analysis |
Two points in that table need context. ISO 22000 has no standalone culture clause, which is why FSSC 22000 adds one through its additional requirements. And SQF’s 90-day records advice comes from its guidance for recertification during an edition change, not from a general rule.
Building the HACCP core of your food safety documentation
Start here, because every other document depends on it. A HACCP plan needs a team, product descriptions, process flow diagrams confirmed on site, a hazard analysis, decisions on critical control points, critical limits, monitoring, corrective actions, verification and records. Skip a step and the downstream records have nothing to attach to.
The HACCP toolkit covers that core so it can feed whichever scheme you certify against. If your auditors keep asking where the ISO 22000 operational prerequisite program line sits against a critical control point, our post on OPRP vs CCP is the place to start.
Prerequisite programs come second
Cleaning, pest control, maintenance, personnel hygiene, supplier controls and similar programs are what make the HACCP plan workable. Each scheme wants them documented, but each points to a different source for the content. ISO 22000 leaves the selection to you. FSSC 22000 requires you to apply the relevant ISO 22002 part. Do not guess the numbering of ISO 22002 clauses: the 2025 series was restructured and renumbered, so cite the edition you actually hold.
Management system documents: manual, policy and records
ISO 22000 does not require a food safety manual. Many certified sites keep one anyway because it gives auditors a map. BRCGS and SQF assessors usually look for the same thing in a different shape: a policy, a defined scope, responsibilities, and procedures they can trace to evidence.
For ISO 22000, the distinction that matters is between documented information you must maintain (procedures and plans) and information you must retain (records). Our guide to ISO 22000 mandatory documents sorts them by clause.
The ISO 22000 toolkit gives you the management system layer once. The FSSC 22000, BRCGS and SQF toolkits then add scheme-specific documents on top, so you are not rewriting policy, internal audit and management review procedures three times.
Document control for food safety documentation records
Every scheme audits your records harder than your procedures. A beautiful HACCP plan with blank monitoring sheets fails faster than a plain plan with complete ones. Set retention periods that cover shelf life plus a margin, and make sure each record names who completed it and who verified it.
Food safety culture, allergen, traceability and recall
These four topics are where the schemes diverge most, so they are where you should check your documents hardest.
Food safety culture
FSSC 22000 Version 7 and BRCGS ask for objectives, a documented plan and a way of measuring progress. SQF Edition 10 introduced a requirement for a culture assessment plan. ISO 22000 expresses the idea through leadership and communication. Read our food safety culture guide for the FSSC requirement in detail. One culture plan can serve all four schemes if it names objectives, owners, measures and review dates.
Allergen management
Allergens are a hazard like any other, so they belong in the hazard analysis first. Schemes then ask for more: allergen risk assessment, segregation, cleaning validation, labeling checks and rework rules. Keep the allergen matrix as a controlled document, because it is what your label and changeover procedures point back to.
Traceability and recall
Traceability is one step back, one step forward and through the process, and auditors will usually ask you to prove it with a real lot. Recall and withdrawal procedures need named decision makers, contact lists, regulator notification steps and a test. Our traceability system guide shows how to design and test the system under ISO 22000 clause 8.3.
Supplier approval
Raw materials are where many hazards enter, so supplier approval documents sit upstream of the hazard analysis. You need an approved supplier list, criteria for approval, specifications, a monitoring method and a way to handle a supplier who fails. Food fraud and defense assessments usually draw on the same supplier data.
Order of implementation for food safety documentation
If you start from nothing, build in this order, because each layer feeds the next.
- HACCP plan and the prerequisite programs it relies on.
- Policy, scope, responsibilities, document control and records.
- Supplier approval, traceability and recall, tested once.
- Allergen, culture, food fraud and food defense documents.
- Internal audit and management review, so you can prove the system was checked.
- Scheme-specific additions for the certificate your customer requires.
If you already hold one scheme, the move to a second is mostly the last step. A site certified to ISO 22000 that adds FSSC 22000 adds the Version 7 additions, not a new system. FSSC 22000 Version 6 audits are allowed until 30 April 2027 and Version 7 upgrade audits run from 1 May 2027, so plan your upgrade rather than wait. GFSI recognition is the reason buyers accept these schemes interchangeably, and the Global Food Safety Initiative publishes the benchmarking requirements.
Sector matters when you scope your food safety documentation. A manufacturer supplying a retailer will probably be told which scheme to hold. A business supplying several customers may be asked for different ones, which is exactly when a shared HACCP and ISO 22000 base pays off.
How the five toolkits fit together
Use the FSSC 22000 toolkit if your certification path runs through ISO 22000. Use the BRCGS Food Safety Issue 9 toolkit or the SQF Edition 10 toolkit when a customer names that scheme. Each toolkit is an editable set of food safety documentation to support your system, and certification is decided by a certification body after an audit.
Need more than one scheme? The Food Safety Package covers all 5 toolkits for $299, as one purchase with a separate download per toolkit. It is licensed for internal use by one organization; consultants serving clients need the Consultant Package.
Food safety documentation FAQ
Do I need a food safety manual?
ISO 22000 does not require one. Many sites keep one because it gives auditors a clear map of the system, and BRCGS and SQF auditors expect to see policy, scope and procedures in some organized form. Check your customer’s scheme rules before dropping it.
Can one set of food safety documentation serve several schemes?
Largely yes. HACCP, prerequisite programs, traceability, recall and supplier approval are shared. What differs is the scheme-specific layer, such as FSSC 22000 additional requirements, the BRCGS site standards, or SQF module requirements.
How long should I keep food safety records?
Set the period by shelf life plus a margin, and check any scheme or legal minimum. For SQF during an edition change, the code advises at least 90 days of records before a recertification audit.
Does having the documents make us certified?
No. Documents support the system, and an accredited certification body decides certification after auditing how you operate. Records of real monitoring matter more than the procedures themselves.


