FSSC 22000 Version 7 was published in May 2026 and every certified site will be audited against it in an upgrade audit between 1 May 2027 and 30 April 2028. The change that reaches the quality office first is document control. Every procedure, work instruction and record form that references a Version 6 clause has to be reviewed, and the additional requirements have to be reflected in the documented information before the upgrade audit. On paper that is a reprint of the system. On a paperless FSMS it is a managed update, and if the system is maintained by the people who read the scheme documents for a living, it is an update you receive rather than one you perform.
What Version 7 changes for documented information
FSSC 22000 continues to rest on ISO 22000:2018, the relevant ISO/TS 22002 prerequisite programme specification for your sector, and the FSSC additional requirements. Version 7 restructures and tightens the additional requirements rather than rewriting the ISO base. The practical effect on documents is threefold. Procedures that cite additional requirement numbers need the references updated. Topics that Version 6 introduced, such as food safety and quality culture, food loss and waste, communication requirements and equipment management, together with the strengthened allergen management requirement, now carry clearer expectations about the evidence an auditor will look for. And the scheme’s expectations about the integrity of records, including electronic ones, are more explicit.
For the full clause-by-clause position, read the Version 7 scheme documents on the FSSC website and the ASC article series on the additional requirements. This article is about the mechanism of staying current, not the content of each clause.
The paper reality of a version change
A certified site typically holds between 60 and 200 controlled documents. In a paper system each one has a master copy, a distribution list and a set of controlled copies on the floor. A version change means the quality manager opens each master, reviews it against the new requirements, revises, re-approves, reissues, withdraws the old controlled copies and records all of it in the document register. At a realistic two hours per document including approval and reissue, that is 120 to 400 hours. Sites usually do it in a crunch in the three months before the upgrade audit, which is also why upgrade audits raise so many document control non-conformances.
How it works on a paperless system
On ASCloud the document set is a structured library rather than a pile of files. Each procedure is tagged to the clauses it satisfies, so when Version 7 renumbers or expands a requirement, the system shows exactly which documents are affected. Revision is done in the system with version history preserved, approval is an electronic sign-off by the authorised person, and the moment a revision is approved the previous version is withdrawn everywhere. There are no controlled copies to chase because the floor reads the current version on a tablet. The document register updates itself.
The part that matters most is who does the clause mapping. ASC maintains the FSSC 22000 content in ASCloud. With Version 7 published, the ASC team maps the changes and updates the template procedures, checklists and record forms. Clients receive the updates as proposed revisions to accept into their own system, with their site-specific content untouched. That is included in the full document FSMS plan at R3,800 per site per month, along with the same service for BRCGS, GLOBALG.A.P. and HACCP updates.
A sensible timeline from now to the upgrade audit
With upgrade audits starting in May 2027, a site certified today has between seven and nineteen months. Use the first quarter to read the Version 7 documents and run a gap assessment against your current system. Use the second quarter to revise documents and retrain, with an internal audit against Version 7 before the end of it. Hold a management review that explicitly covers the transition. Then run at least one full cycle of the revised records before the certification body arrives, so that there are three months of Version 7 evidence on file. On a paperless system the evidence part takes care of itself, because the records are generated by the revised checklists from the day they are approved.
What the auditor will ask about electronic documents
Expect the upgrade auditor to open the document register and pick three documents at random, then ask to see the version history, the approval and where the floor reads it. Expect questions about access control, which users can approve, and how obsolete versions are prevented from use. Expect a question about backup and data location. A paperless FSMS built for food safety answers all of these from the screen. A shared drive full of Word files answers none of them.
Version 7 updates, applied for you
ASCloud’s full document FSMS includes FSSC 22000 Version 7 content maintained by ASC’s lead auditors. From R3,800 per site per month.
Frequently asked questions
When is the last date to be audited against Version 6?
Version 6 audits end on 30 April 2027. From 1 May 2027 every audit is to Version 7, and upgrade audits run until 30 April 2028. Your certification body sets your specific date within that window.
Do I have to rewrite my whole system?
No. The ISO 22000:2018 base is unchanged. The work is in the additional requirements and in updating references and evidence. A gap assessment tells you how much.
Can ASCloud load my existing procedures?
Yes. Setup loads your current documents and maps them to the clauses. Your site-specific content stays yours, and the scheme content is maintained by ASC.
Does the same apply to BRCGS and GLOBALG.A.P.?
Yes. ASC maintains BRCGS Issue 9 and GLOBALG.A.P. IFA v6 content in the same way, and will do the same for BRCGS Issue 10 when it is published.