Custom FSSC 22000 audit file software development
Appfront builds software for food and packaging producers certified to FSSC 22000. For every requirement of the scheme, from ISO 22000 and the prerequisite programmes to the additional FSSC requirements, it shows which evidence applies and whether it is up to date. Non-conformities from audits are followed up until they are resolved. And because unannounced audits take place at least once every three years, the file is always ready.
What is software for the FSSC 22000 audit file?
FSSC 22000 is a food safety certification scheme recognised by GFSI. It consists of ISO 22000, prerequisite programmes developed for each sector, and additional FSSC requirements, such as those on food safety culture, food defence, food fraud, allergen management and environmental monitoring. A certification body carries out the audit, and at least once every three years this is done unannounced.
An unannounced audit means the file has to be ready on any day. In practice, audit evidence is gathered from folders, records and systems, and is then scattered again afterwards. A non-conformity from the previous audit has been resolved, but the record of it is missing. A environmental monitoring log hasn't been updated for a few weeks. And whoever guides the auditor through the company ends up searching for documents.
We build custom solutions because producers differ: which products and processes are involved, which prerequisite programmes apply, how records are currently kept, and which systems you use. Which requirements apply to your organisation and how they must be demonstrated are determined by the scheme and your certification body; the software ensures the evidence is there.
Evidence per requirement
Every requirement in the scheme, with the evidence from your records, the date, and who keeps it up to date.
Always audit-ready
Warnings when evidence is out of date, and an audit mode for an unannounced audit.
Non-conformities followed up
Non-conformities with cause, corrective action, and deadline, until they are closed and recorded.
How we build your software for the FSSC 22000 audit file
We start with your file: which prerequisite programmes apply, where the records stand now, what came out of the last audits, and where you lose the most time searching. If your HACCP records are already digital or being built, the evidence comes straight from them. That way nobody has to gather anything for the audit.
Your processes, prerequisite programmes, records, and systems.
The requirements as a checklist, with evidence from your records.
Internal and external audits, and follow-up on non-conformities.
Ready for the audit, and maintained when new versions of the scheme are issued.
What software for the FSSC 22000 audit file actually does
The components below come up in almost every FSSC 22000 file. Which ones you need depends on your processes.
Requirements
ISO 22000, PRPs, and FSSC requirements.
Proof
From records, with date and owner.
Alerts
When evidence is out of date.
Audits
Internal and external, with non-conformities.
Deviations
Cause, corrective action, and deadline.
Audit mode
Everything ready for the auditor.
Who we build software for the FSSC 22000 audit file
The software is intended for organisations holding an FSSC 22000 certificate.
Food producers
Many records. Evidence per requirement is the core.
Packaging
Their own prerequisite programmes. The requirements matter most.
Storage and distribution
Multiple sites. An overview is what's needed.
Quality managers
Audit-ready every day. The warnings are the core.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
This page is about the FSSC 22000 audit file. For IFS and BRCGS, see our page on an audit file for IFS and BRCGS; for records on the shop floor, see our page on HACCP monitoring; and for IFS as a whole, see our page on IFS software. You can read about our approach at building software.
Why Appfront for your software for the FSSC 22000 audit file?
An unannounced audit on a day when the evidence is scattered leads to non-conformities that were never necessary. That is what we build against: evidence per requirement, always audit-ready, and non-conformities that get followed up.
Ready every day
Even when the auditor arrives unannounced.
Fewer non-conformities
Out-of-date evidence spotted early.
Demonstrable
Non-conformities closed and recorded.
Security and privacy for software for the FSSC 22000 audit file
The file contains recipes, processes, audit reports, and records. Access is set up by role, and an auditor can be given read access to the part they need.
The software runs in a European data centre or in your own environment, with encrypted storage, daily back-ups, and login with a second factor. Changes to the file are logged.
Frequently asked questions about software for the FSSC 22000 audit file
Questions quality managers ask before getting started.
It sets out the scheme's requirements as a checklist, keeps the evidence from your records against each requirement, flags out-of-date evidence, records audits and non-conformities with follow-up, and has an audit mode for the day itself.
The structure is similar, but the requirements differ. FSSC 22000 consists of ISO 22000, prerequisite programmes, and additional FSSC requirements. If you hold several certificates, a single file can keep the requirements of both schemes side by side, with evidence that counts for both.
According to the schedule, at least once every three years, and the certification body decides which audit that is. Some companies choose to have all audits unannounced. That is why the file must be ready on any given day.
From your records, such as HACCP checks, environmental monitoring, cleaning and training, and document management. Where these are digital, the software retrieves them directly; otherwise they are recorded in the file with date and owner.
On the day of the audit, the software shows the evidence per requirement, the latest records and the status of nonconformities, so the auditor's escort does not have to search for anything. An auditor can also be given read-only access.
The requirements are then updated. The software shows which requirements are new or changed and which evidence is missing, so you can plan the transition.
Ask that first. Some quality systems already have audit and document management, and that may be enough. Custom work makes sense if evidence is currently gathered manually for every audit, if you hold multiple schemes, or if records aren't linked to the requirements.
Ready for an unannounced audit any day?
Tell us which prerequisite programmes apply to you, where your records are kept and what came out of your latest audits. We will show you what the file looks like.