Building an IFS Food and BRCGS audit file
IFS Food and BRCGS are not a legal requirement but a retail requirement, and without a certificate you won't get onto the shelf. Now that audits can be unannounced, preparing in the weeks beforehand is no longer an option. Appfront builds the file that is kept up to date continuously and in which non-conformities lead to a completed corrective action.
What IFS and BRCGS ask of your file
Both standards are recognised by the Global Food Safety Initiative and are required by retailers as a condition of supply. IFS Food has been mandatory in version 8 since January 2024, with knock-out requirements that feed directly into the outcome if not met, and with a B score counting as a non-conformity. Since Issue 9, BRCGS Food Safety has had twelve fundamental requirements, including HACCP, internal audits, supplier management, corrective and preventive actions, traceability and allergen management.
The real change of recent years is that the audit can take place unannounced. Since 2020, GFSI has required every site to be audited unannounced at least once every three years, and under IFS this is made visible on the certificate. That ends the approach where a team updates the file in the weeks before the audit. The file has to be correct every day.
In practice, things go wrong with non-conformities. An audit produces findings that must be corrected within a set period, with evidence, and the deadline differs by grade and by scheme. The same route applies to internal audits, complaints and deviations from production. If those four live in different systems or in a shared folder, you cannot show at the next audit that a problem has been resolved structurally rather than patched up once.
This file rarely stands alone. Shop-floor records often run through the same app as your inspections, and equipment in production that requires inspection belongs in an inspection log that contributes to the same evidence. We build these pieces as a whole wherever possible, so that a check does not have to be recorded in two places.
This page is about the file itself: non-conformities, corrections and the chain of evidence around them. If you are looking for the level above that, meaning how to monitor the knock-out requirements separately and how to handle an audit that is not announced, see IFS and BRCGS software.
How we build your audit file
We start from the requirements of your scheme and work back to what has to be recorded every day. The result is a file that answers the auditor's question, rather than an archive that merely resembles one.
Do you work under IFS, BRCGS or both, and which version? We go through the requirements and determine, for each one, what evidence you must be able to show and where it comes from. With two schemes, we look mainly for the overlap, because keeping records twice is the biggest waste in this file.
Findings from an audit, an internal audit, complaints and production all follow the same route: record, determine the cause, correct, verify and close. One route, several entry points. That is the core of the system and the part where most design decisions sit.
We work in sprints and start with non-conformity management, because that is where most of the daily traffic is. Your quality department works with us and tests each sprint against real findings from your last audit.
Before handover, we walk through the file with an auditor's questions: show that this requirement is met, and show what happened with this finding. Anything that cannot be shown in two clicks, we adjust.
What the software actually does
Six components that together make up the file. Which ones you need depends on your scheme and on how many sites and product groups you have.
One route for all non-conformities
Audit findings, internal audits, complaints and production deviations follow the same steps: record, root cause analysis, correction, verification and close. A non-conformity is only closed once someone has established that the measure works, not once someone has written it down.
Deadlines that differ by grade
The correction deadline depends on the grade of the finding and on the scheme; a major finding has a considerably shorter deadline than a minor one. The system calculates this per finding and alerts the person responsible, with escalation as the date approaches.
Requirements with their evidence
For each requirement in your scheme, the system records which document, record or measurement demonstrates compliance, and whether that evidence is still current. This is the table an auditor works through, and the place where loose references go out of date fastest.
Production records
Temperatures, metal detection checks, hygiene rounds and glass breakage checks are captured where they happen, with a timestamp and the person who carried them out. An out-of-range value automatically starts the non-conformity process instead of sitting in a logbook.
Supplier evaluation
Both schemes require demonstrable supplier management: certificates, specifications and assessments, with validity dates. A portal where your suppliers submit their own documents keeps this up to date without your people having to chase them.
Audit mode for the day itself
A view organised by the requirements of your scheme, so you can get straight to the evidence an auditor asks for. In an unannounced audit, that is the difference between a calm walk-through and searching while someone watches over your shoulder.
Who we build for
Four situations in which this file gets out of hand fastest. Usually the trigger is an audit that went slightly worse than expected.
Food manufacturers
The core of both schemes. This is where production records and the quality file merge, and an integration with your production system is often part of the same solution.
Packers and co-packers
You produce for third-party brands, each with its own requirements and audits. On top of IFS or BRCGS you therefore have customer-specific requirements, and these need to fit into the same file without turning into a second administration.
Storage and distribution
Different scheme variants, but the same approach: traceability, temperature monitoring and non-conformities that lead to a corrective action. Often with multiple sites, and therefore the question of how to keep a central overview.
Companies with multiple certificates
IFS, BRCGS, an organic certification and sometimes ISO alongside. The gain here lies in recording evidence once that supports multiple requirements, instead of four files side by side. If you already run a quality management system, we build on top of it.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
What we use follows from your situation. For shop-floor records, usability carries the most weight: a screen that asks too much gets filled in from memory at the end of the shift, and then the record is worthless as evidence.
For FSSC 22000, with evidence per requirement and always ready for an unannounced audit, there is our software for the FSSC 22000 audit file.
If you hold AEO status and want to keep track of your control measures, see our page on an AEO control measures file.
Why Appfront
Built around the audit question
We design from what an auditor asks for and test it with a trial run before handover. That is more concrete than complying with a standard on paper.
Closing requires verification
A non-conformity that closes because someone pressed a button is exactly what comes back at the next audit. We build verification as a separate step performed by a different person.
Always up to date
Unannounced audits make last-minute updating impossible. We set things up so the evidence is created where the work happens, because that is the only way to be accurate every day.
One piece of evidence, multiple requirements
If you work under two schemes, the requirements overlap considerably. We link evidence to multiple requirements at once, so you are not maintaining two files for the same reality.
Security and privacy
An audit file contains little personal data, but it does record who carried out which check and who was responsible for a non-conformity. That is traceable to an employee, and it is sensitive, because a non-conformity can come across as one person's mistake when it is usually a process problem. We therefore focus the reporting on the process rather than the individual employee, and limit visibility of who did what to those who need it.
From a business perspective, it matters more that this file contains your recipes, specifications and customer agreements, and for co-packers also those of your clients. Access is therefore granted per role and per product group, with a separate temporary role for auditors who see only what falls within their scope. Records that serve as evidence cannot be changed silently: a correction is visible as a correction and does not overwrite the original. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy (coordinated vulnerability disclosure).
If your raw materials come from your own cultivation or from regular growers, a separate certificate applies there. For the cultivation side, we cover this in GlobalG.A.P. crop registration and audit.
Frequently asked questions about the audit file
Both are GFSI-recognised and largely cover the same ground, but they differ in structure and assessment. IFS uses a score per requirement and knock-out requirements that feed directly into the result; since version 8, the B score counts as a non-conformity again. BRCGS uses fundamental requirements and a classification of non-conformities. Which one you need is determined by your customer; some producers hold both because different retailers ask for different schemes.
Since 2020, GFSI has required every site to be audited unannounced at least once every three years; with IFS, this is visible on the certificate. In practice, it means the approach where a team updates the file in the weeks before the audit no longer works. That is exactly why organisations are starting to build software for this: the evidence has to be created where the work happens, not compiled afterwards.
That differs per scheme and per class of finding: the more serious, the shorter. For the most serious categories it is a matter of a few weeks, for lighter ones longer. Because the exact deadlines can differ per scheme and per version, we make them configurable rather than hard-coding them. What we do enforce is that the clock starts running the moment a finding is raised.
No. Your HACCP plan remains the document in which you record your hazards, critical control points and control measures; that is substantive work for your quality team. The software carries it out: it turns the control measures into records with a frequency, monitors whether they have been completed and starts the non-conformity process when a limit is exceeded. If your process changes, you revise the plan and we then adapt the software.
No, and that is usually the very reason for doing this. The requirements overlap considerably, so we link a piece of evidence to all the requirements it satisfies rather than duplicating it. In audit mode, the auditor then sees the file organised according to their own scheme. In practice, this saves more work than any other feature.
Partly, yes. Temperature loggers, metal detectors and weighing equipment often supply structured data, and this can go straight into the file so nobody has to retype it. Hygiene rounds and visual checks remain manual, but with a scan at the checkpoint so the record is tied to the right place and the right time. What is possible depends on your equipment; we establish that during the discovery phase.
Both schemes require demonstrable supplier management: valid certificates, up-to-date specifications and periodic review. In practice, that means chasing documents that expire. A portal where your supplier submits documents themselves, and where you can see what is missing or about to expire, takes that work off your quality department and keeps the file up to date.
That depends on the number of sites, the number of schemes and how many production records are integrated. Deviation management is usually the quickest to become useful and delivers the most value; the integrations with measuring equipment are the most work. We give a well-founded estimate after the discovery phase, once we know which records originate where.
Ready to build an audit file?
Tell us which scheme you fall under and where your last audit got stuck, and we'll help you think through the deviation process, the shop-floor records and the overlap between your schemes. We build this as a standalone application and as part of a broader project involving custom software or a web application.