Common internal audit and corrective action pitfalls include internal audits that skip parts of the standard, auditors who check their own work, and corrective actions that fix the symptom without finding the root cause or proving the fix worked. SQF, BRCGS, IFS Food and FSSC 22000 all require a planned internal audit program and a corrective action process that includes root cause analysis. Below are those requirements side by side, four illustrative case studies of how they fail, and what a root-cause fix looks like.
Internal Audits and Corrective Actions at a Glance
Internal audits and corrective actions are how a food safety system checks and corrects itself. Your internal audit finds the gap, and your corrective action process closes it so it stays closed. When either one is weak, the same problems keep coming back.
- 240,000+Corrective actions raised across BRCGS audits in 2024-25BRCGS Annual Report 2024-25[1]
- Top 10Internal audits (clause 3.4.1) were among BRCGS's 10 most common food non-conformities of 2021, across 22,000 auditsBRCGS Compliance Report 2022[2]
- 2 of 10IFS Food knock-out requirements cover internal audits (5.1.1) and corrective actions (5.11.3)IFS Food Version 8[3]
- 28–40 daysDeadlines for answering major and minor certification audit findings: 28 days for BRCGS and FSSC 22000, 30 for SQF Edition 9, 40 for Edition 10Scheme rules[4][5][6][7]
Key takeaways
- There's no such thing as a "GFSI audit." GFSI benchmarks certification programs. Your site is audited to a recognized scheme, such as SQF, BRCGS, IFS Food or FSSC 22000, by a certification body.[8]
- SQF, BRCGS and IFS Food expect the whole standard to be audited on a yearly cycle by trained or competent auditors. BRCGS bars auditors from auditing their own work, IFS requires independence from the audited department, and SQF asks for it where practical. FSSC 22000 builds on ISO 22000's internal audit clause and adds its own rules.[3][5][6][9]
- The stakes differ. Internal audits and corrective actions are fundamental clauses in BRCGS, knock-out requirements in IFS Food and mandatory elements in SQF, and corrective action becomes an SQF Core Clause in Edition 10.[3][6][9][10]
- A correction fixes the problem in front of you. A corrective action stops it from coming back. FDA's preventive controls rule draws the same line and also requires you to evaluate the affected food.[11]
- Repeat findings escalate. BRCGS raises a non-conformity against clause 1.1.12 when a previous corrective action didn't work, FSSC 22000 says an unaddressed minor can become a major, and SQF Edition 10 lets auditors add non-conformances under the corrective action clause.[4][5][7][9]
Updated October 5, 2026. Checked against the SQF Food Manufacturing Code (Edition 9 and the Edition 10 checklist), BRCGS Global Standard Food Safety Issue 9 (Parts II and III), IFS Food Version 8, the FSSC 22000 scheme (Versions 6 and 7) and 21 CFR Part 117. The four case studies are illustrative composites, not real companies or audits.
Is There Such a Thing as a GFSI Audit?
No. The Global Food Safety Initiative (GFSI) doesn't audit food sites or issue certificates. It benchmarks certification programs against its own requirements and recognizes the ones that meet them. Recognized programs include SQF, BRCGS Food Safety, IFS Food, FSSC 22000, PrimusGFS and CanadaGAP.[8] When a buyer asks for "GFSI certification," they mean a certificate to one of those schemes.
GFSI does set ground rules on corrective action. Its 2024 Benchmarking Requirements tell scheme owners to make sure certification bodies verify that audited sites carry out their corrective action plans, and that corrections or corrective actions are returned and verified within a set time before a certificate is awarded.[12] Each scheme sets its own deadline for closing audit findings.
SQF Edition 9 is the GFSI-recognized edition today. SQFI expects Edition 10 audits to start no earlier than January 2, 2027, depending on GFSI benchmarking.[13] FSSC 22000 Version 6 is audited until April 30, 2027, and Version 7 audits start May 1, 2027.[14] This article cites SQF Edition 9 and FSSC 22000 Version 6, and notes where the newer versions change them.
What Do the Schemes Require for Internal Audits?
SQF, BRCGS and IFS Food expect a planned internal audit program that covers the whole standard each year, run by competent people who are independent of what they audit, with findings that flow into corrective action. The details differ, and the differences are where sites get caught.
| Scheme (clause, status) | How often and how much | Who can audit | What happens to the results |
|---|---|---|---|
| SQF Edition 9 (2.5.4, mandatory) | In full, at least once a year, covering every applicable requirement using the SQF checklist or a similar tool | Trained and competent; independent of the function audited where practical | Objective evidence recorded; corrective and preventive actions taken; results reported to management and the people responsible[6] |
| SQF Edition 10 (2.5.4, mandatory) | Same annual, full-code coverage | Independent where practical (now in 2.5.4.1); auditor training moves to 2.9.1.2 and must include a documented assessment | Findings and adverse trends go through root cause analysis under 2.5.3; audit results feed the monthly management update (2.1.2.2)[10] |
| BRCGS Food Safety Issue 9 (3.4, fundamental) | At least four audit dates spread through the year; frequency set by risk and past performance; every activity covered at least once a year | Trained and competent; must not audit their own work | Reports show conformity and non-conformity with evidence; actions and timescales agreed and verified; summary reviewed in management review[9] |
| IFS Food Version 8 (5.1.1, knock-out) | Every IFS requirement, planned within 12 months and completed within 15; critical activities audited more often | Competent and independent from the audited department | Results documented and reported to senior management and the people responsible; covers off-site storage the company owns or rents[3] |
| FSSC 22000 Version 6 (same in Version 7) | Internal audit under ISO 22000:2018 clause 9.2, with quality elements added to the audit scope (2.5.9) | Multi-site certification only (categories E, F and G; Version 7 adds BIII): auditors independent of the areas they audit, assigned by the central function | Multi-site certification only: every site audited at least annually, or more often based on risk, and corrective action shown to be effective (2.5.18.2)[5] |
| FDA 21 CFR Part 117 | No internal audit clause; the food safety plan must be reanalyzed at least every 3 years | A preventive controls qualified individual (PCQI) does or oversees record review | Monitoring and corrective action records reviewed within 7 working days, unless a longer time is justified in writing[11] |
Summarized from the scheme texts cited. ISO 22000:2018 itself is not freely published, so the FSSC row lists only what the FSSC scheme adds.
BRCGS clause 3.4.1, which sets the scope and schedule of the internal audit program, was among the ten most common Food Safety non-conformities in BRCGS's 2021 audit data. In Issue 9 it requires every activity to be covered at least once a year across at least four audit dates, with the HACCP or food safety plan, prerequisite programs, and food defense and food fraud plans in scope.[2][9] So check that your program reaches every clause, area and shift, and that the schedule meets your scheme's frequency rule.
Internal audits aren't the only check. SQF requires regular site and equipment inspections (Edition 9 2.5.4.3, Edition 10 2.5.2.2), and IFS Food requires planned site and factory inspections (5.2.1).[3][6][10] BRCGS 3.4.4 requires a separate, documented inspection program covering hygiene and fabrication, set by risk and at least monthly in open product areas.[9] These inspections matter: in BRCGS's 2024-25 data, all five of the most common Food Safety non-conformities sat in Section 4, Site Standards, led by premises and equipment hygiene (4.11.1), with doors (4.4.8) and walls (4.4.1) also in the five.[1]
What Do the Schemes Require for Corrective Action?
A correction fixes the problem in front of you: re-cleaning a line, re-cooking a batch, relabeling a pallet. A corrective action removes the cause so it doesn't come back. A preventive action stops a similar problem before it happens somewhere else. FDA defines a correction as fixing a problem without the other steps of a corrective action procedure, such as reducing the likelihood it will recur and evaluating the affected food.[11] SQF Edition 10 renames its clause "Corrections, and Corrective and Preventative Action" to make the same distinction.[10] BRCGS uses the words a little differently: after an audit, its "corrective action" is the immediate fix, and its "preventive action plan" addresses the root cause.[4]
| Scheme (clause, status) | Your procedure must cover | After a certification audit |
|---|---|---|
| SQF Edition 9 (2.5.3, mandatory) | How corrective and preventive actions are determined, put in place and verified, including the root cause | Evidence sent so the auditor can verify and close every minor and major within 30 calendar days, each with a documented root cause analysis; more time possible with temporary controls (for majors, only for structural, seasonal or lead-time fixes)[6] |
| SQF Edition 10 (2.5.3, mandatory Core Clause) | Corrections, root cause method, corrective and preventive actions, verification that they worked, and communication of results; covers complaints, audit findings, recalls, regulatory issues and negative trends | All corrective actions approved by the auditor and closed within 40 calendar days; a repeat finding can earn extra non-conformances under 2.5.3[7][10] |
| BRCGS Issue 9 (3.7, fundamental) | A procedure with root cause analysis and preventive action; for safety, authenticity or legality issues: assessment of consequences, owner, timescale, and verification that actions worked | Evidence of correction, root cause analysis and a preventive action plan within 28 calendar days, or no certificate; if the action proves ineffective by the next audit, a non-conformity against 1.1.12[4][9] |
| IFS Food Version 8 (5.11, knock-out at 5.11.3) | Root cause analysis at least for safety, legality, authenticity and repeat issues; corrections; corrective actions with owners and timescales; effectiveness assessed | Action plan sent by the certification body within 2 weeks; returned within 4 weeks with evidence that corrections are done; corrective actions may be finished later, by the recertification audit at the latest[3] |
| FSSC 22000 Version 6 (Part 3, 6.2) | For each audit nonconformity: the correction, an investigation of causative factors (root cause), exposed risks and a corrective action plan | Minor: correction evidence and plan approved within 28 days. Major: closed within 28 days, or the certificate is suspended[5] |
| FDA 21 CFR 117.150 | Written procedures to correct the problem, reduce the chance it recurs when necessary, evaluate all affected food and keep adulterated or allergen-misbranded food out of commerce | No certification audit; corrective action records reviewed by or under a PCQI within 7 working days, unless a longer time is justified in writing[11] |
Summarized from the scheme texts cited. FDA exempts timely corrections from its corrective action procedure requirements only for allergen cross-contact and sanitation conditions, or for minor, isolated problems that don't directly affect product safety (21 CFR 117.150(c)). Allergen labeling problems aren't covered.
The certification schemes share the same core: a root cause, a plan with timescales, and proof the action worked. BRCGS and IFS Food also require a named owner. A record that stops at "retrained staff" or "re-cleaned" meets none of them. For root cause methods such as the 5 Whys and fishbone diagrams, see our guide to root cause analysis in SQF audits.
Critical findings don't get these windows. An SQF critical non-conformance means automatic failure at an initial audit, and Edition 10 states that one raised at recertification suspends the certificate immediately.[6][7] In BRCGS a critical means no certificate.[4] FSSC 22000 suspends the certificate within 3 working days.[5] In IFS Food, a knock-out requirement scored D means no certificate, and an existing certificate is withdrawn.[3]
Four Non-Conformance Case Studies
The four cases that follow trace an internal audit that verified nothing, a CCP deviation corrected three times without a root cause, an allergen mix-up written off as operator error, and a closed minor finding that returned at recertification — each one a corrective action that treated the symptom and left the system untouched.
These four cases are illustrative composites, not real companies or audits. Each follows a finding from a weak first response to an example of a corrective action that addresses the root cause, and lists the clauses involved.
The fixes below are examples for learning, not advice for any particular site. Your certification body decides whether evidence closes a finding, and Kiwa ASI's certification auditors don't advise clients on specific corrective actions.
The internal audit that checked boxes
- Illustrative
- SQF
- Internal audit
In this illustrative SQF case, a snack plant’s internal audit was a two-day desk exercise that marked every clause compliant with no objective evidence — no records named, no areas visited, no interviews. The certification auditor then found floor problems a simple walk-through would have caught, including an overdue thermometer calibration.
- The site
- A 120-person snack plant, certified to the SQF Food Manufacturing Code for three years. The QA manager runs the internal audit once a year: two days in November, working through the SQF checklist at a desk and marking each clause "compliant."
- What the auditor found
- The internal audit record marked every clause compliant but held no objective evidence: no records named, no areas visited, no one interviewed. The environmental monitoring and approved supplier programs had been marked compliant without being examined. On the floor, the certification auditor found problems a walk-through would have caught, including an overdue thermometer calibration and a torn strip curtain at the dock. The QA manager had also audited the HACCP and sanitation programs they run.
- The first fix
- Redo the checklist the next week, this time with notes. That fills the paperwork gap but leaves the reason it happened, so next year's audit would look the same.
- Root cause
- The program depended on one person and one date. No one else was trained to audit, and site management never saw the results, so no one noticed the audit wasn't finding anything.
- A root-cause fix
- Train two or three people from production, maintenance and QA as internal auditors, and assign them so no one audits their own area. Spread the program across the year in modules ranked by risk, so CCPs, allergen control and sanitation get more attention and every clause is still covered at least annually. SQF only requires the full annual audit, but BRCGS and IFS Food require risk-based frequency, and spreading the work makes it easier to do well. Require evidence for every finding: the record checked, what was seen, who was interviewed. Trace one finished lot back through its records. Log every finding in the corrective action system and report results to site management monthly.
- How to show it worked
- The next modules produce findings with evidence attached, findings close on time, and the same issues stop appearing at the certification audit. Keep the auditor training records and assignments; the certification auditor may ask for them.
- Clauses involved
- SQF Edition 9 2.5.4.1 (full audit at least annually, every applicable requirement, objective evidence) and 2.5.4.2 (trained, competent and independent where practical).[6] Edition 10 keeps full scope, objective evidence and independence in 2.5.4.1, moves auditor training to 2.9.1.2 with a documented assessment, and adds audit results to the monthly management update (2.1.2.2).[10] The same gaps would breach BRCGS 3.4, a fundamental clause, and IFS Food 5.1.1, a knock-out requirement.[3][9]
The CCP deviation fixed three times
- Illustrative
- BRCGS
- Corrective action
In this illustrative BRCGS case, a ready-meals plant recorded three cook-step CCP failures in six weeks and “fixed” each by re-cooking the batch — until the auditor checked the handheld probe and found it reading high, putting every batch recorded as passing in doubt. Correcting a deviation three times without asking why is the finding.
- The site
- A plant making refrigerated vegetarian ready meals, certified to BRCGS Food Safety Issue 9. The cook step for a rice and bean filling is a critical control point (CCP), monitored by probing the core temperature of every batch with a handheld thermometer.
- What the auditor found
- Over six weeks, operators had recorded three batches below the critical limit. Each time they re-cooked the batch, wrote "re-cooked, OK" and a supervisor signed. No one asked why. The auditor checked the handheld probe against the site's reference thermometer and found it reading high. That raised a harder question: had batches recorded as passing really reached the limit?
- The first fix
- Re-cooking was a correction. It dealt with each failed batch but not the reason batches kept failing, and it never questioned the batches that passed, or the re-cooked batches checked with the same probe.
- Root cause
- The probe was a spare bought outside the calibration program, so it had no ID number, no due date and no accuracy checks. Monitoring records were signed every day, but no one looked at them for a trend.
- A root-cause fix
- Identify all product monitored with this probe since it went into service, including the re-cooked batches. Hold what is still on site, decide on withdrawal or recall for anything shipped, and notify the certification body within 3 working days if product is withdrawn or recalled. Put every monitoring device on the calibration list with an ID and due date, add a documented accuracy check before each shift, and remove uncalibrated devices from the floor. Route CCP deviations to the HACCP team for root cause analysis, review monitoring records for trends, and have the HACCP team review the plan and its verification procedures, validating any changes.
- How to show it worked
- Calibration records for every device, accuracy checks logged each shift, no unexplained deviations in the weeks that follow, and a record of how the suspect product was assessed and what happened to it. At the next audit, the auditor checks whether the preventive action worked.[4]
- Clauses involved
- BRCGS 2.11.1 (CCP corrective action, including product made while the process was out of control), 2.12.2–2.12.3 (verification and HACCP plan review), 3.7 (root cause analysis and verified preventive action, a fundamental clause), 3.11.4 (certification body told of a recall or food safety withdrawal within 3 working days) and 6.4 (calibration; 6.4.4 keeps at-risk product from sale).[9] For an FDA-regulated U.S. plant: 21 CFR 117.150 (evaluate all affected food), 117.165(a)(1) (calibration) and 117.165(a)(4) (PCQI review of monitoring and corrective action records).[11]
"Operator error," again
- Illustrative
- IFS Food
- Corrective action
In this illustrative IFS Food case, a bakery co-packer shipped tree-nut cookies in nut-free film after a changeover mix-up, recalled product, and closed the corrective action with “root cause: operator error, action: retrained.” Four months later the same mix-up recurred on another shift — because near-identical film designs, the real cause, were never addressed.
- The site
- A bakery co-packer certified to IFS Food Version 8 makes two private-label cookies on the same line. One contains tree nuts. The printed films for the two products look almost the same.
- What the auditor found
- During a changeover, a roll of the nut-free cookie's film was loaded on the line running the tree-nut cookie, so tree-nut cookies shipped without a tree-nut declaration. A consumer complaint led to a recall. The corrective action record said "root cause: operator error" and "action: operator retrained." Four months later the same mix-up happened on another shift and was caught in-house. At the IFS audit, the auditor found no root cause analysis beyond "operator error" and no check of whether the first action had worked.
- The first fix
- Retraining one operator. "Operator error" says what happened, not why the error was possible, so the conditions that allowed it were still there for the next shift.
- Root cause
- Both films were stored on the same rack with near-identical artwork. The changeover procedure didn't require the old film to be cleared from the line, and no one checked the label against the product at start-up.
- A root-cause fix
- Store films for allergen-containing products separately and mark them clearly, and ask the customer whether the artwork can be made easier to tell apart. Clear all packaging from the previous run at every changeover. Add a signed label check at start-up, at each changeover and whenever a new roll is loaded. If you use a barcode scanner, test it at the start and end of every run. Because the allergen labeling control failed, reanalyze that part of the food safety plan.
- How to show it worked
- Weeks of complete changeover and label-check records, scanner test results, and a planned challenge, such as staging the wrong roll at the line, that the check catches.
- Clauses involved
- IFS Food 1.2.6 (certification body informed of any product recall within 3 working days), 4.5.3 (labels checked at the start and end of each run and at every product changeover), 4.19.3 (allergens declared as the law requires), 5.9.1 (recall procedure; knock-out requirement 9), 5.11.1 (root cause analysis for safety, legality and repeat issues), 5.11.3 (corrective actions with owners and timescales; knock-out requirement 10) and 5.11.4 (effectiveness assessed). A knock-out requirement scored D means no certificate, and at a recertification audit the current certificate is withdrawn.[3] Under FDA rules, labeling the finished food is a food allergen control. The exemption for timely corrections in 117.150(c) covers allergen cross-contact and sanitation, not labeling, and a preventive control that proves ineffective requires reanalysis of the food safety plan (117.170(b)).[11]
The minor that came back
- Illustrative
- SQF
- Repeat finding
In this illustrative SQF case, a dairy ingredients plant closed a minor — unsigned weekend pre-op sanitation inspections — by retraining the weekend crew. The finding returned at recertification because nobody checked weekend records afterwards and the internal audit only sampled weekdays; the root cause was a weekend shift with no sanitation lead.
- The site
- A dairy ingredients plant certified to the SQF Food Manufacturing Code.
- What the auditor found
- A certification audit raised a minor non-conformance: pre-operational sanitation inspections on weekend shifts were often unsigned. The site retrained the weekend crew, sent the evidence, and the finding was closed on time. At the next recertification audit the auditor found the same gap. The internal audit hadn't caught it either, because it only sampled weekday records.
- The first fix
- Retraining, closed on paper. No one checked weekend records in the weeks that followed, so no one knew whether it had worked.
- Root cause
- Weekend shifts had no sanitation lead, and the form required a QA signature when no QA staff were on site. The corrective action changed neither condition, and the internal audit sample never covered weekends.
- A root-cause fix
- Name and train a weekend sanitation lead qualified to carry out the pre-op inspection, revise the form to fit weekend staffing, and have QA review weekend records first thing Monday. Widen the internal audit sample to every shift. Log the finding on a trend sheet so a repeat is flagged before an external auditor sees it.
- How to show it worked
- Complete weekend records over a sustained period, QA review sign-offs, and an internal audit report that sampled weekend shifts.
- Clauses involved
- SQF Edition 9 11.2.5.7 (pre-operational inspections by qualified personnel; 11.2.5.8 in Edition 10), 2.5.3 (corrective and preventive action, including verification) and 2.5.4 (internal audits).[6] Edition 9 has no explicit repeat-finding rule. Under Edition 10, 2.5.3 is a Core Clause, so its non-conformances cost more points (2 for a minor, 7 for a major), and the auditor may add non-conformances against it for a repeat finding.[7][10] BRCGS raises a non-conformity against clause 1.1.12 when a previous corrective or preventive action proves ineffective, and FSSC 22000 says an unaddressed minor can become a major at the next audit.[4][5][9]
Why Do Corrective Actions Fail?
Corrective actions usually fail for the same few reasons. Here is what goes wrong, what the schemes expect instead, and where the requirement sits.[3][9][10][11]
| Pitfall | What the schemes expect instead | Where it's required |
|---|---|---|
| Recording the correction as the corrective action ("re-cleaned," "re-cooked") | The immediate fix plus an action that removes the cause | SQF Ed. 10 2.5.3.1; BRCGS 3.7.2; IFS 5.11.2–5.11.3; 21 CFR 117.150 |
| "Human error" or "retrained staff" as the root cause | A root cause analysis that explains why the error was possible (for example, the procedure, equipment, layout, staffing or supervision) | Root cause analysis: BRCGS 3.7.2; IFS 5.11.1 |
| No look at affected product | An assessment of product made while control was lost, and a decision on what happens to it | BRCGS 2.11.1 and 3.7.2; 21 CFR 117.150(a)(2) |
| No owner or due date | A named person and a timescale for each action | BRCGS 3.7.2; IFS 5.11.3 |
| Closed without checking it worked | Recorded verification that the action was implemented and is effective | SQF Ed. 10 2.5.3.1; BRCGS 3.7.2; IFS 5.11.4 |
| No trend analysis | Root cause analysis when one type of problem increases, not only for single events | BRCGS 3.7.2; SQF Ed. 10 2.5.3.1 and 2.1.3.2 |
| Internal audit findings that never reach the corrective action system | Internal findings handled like external ones, with agreed timescales and verified completion | SQF 2.5.4.1; BRCGS 3.4.3; IFS 5.1.3 and 5.11 |
| Missing the certification body's deadline | Evidence in early enough to be accepted: BRCGS, 28 days to submit; FSSC 22000, 28 days for approval or closure; SQF, 30 or 40 days for the auditor to close (Ed. 9 or 10); IFS, 4 weeks after receiving the action plan | BRCGS Part III; FSSC Part 3 6.2; SQF Part A; IFS Part 1 4.1.1 |
How Do You Build an Internal Audit Program That Finds Problems First?
A good internal audit program finds problems before the certification auditor, a customer or a regulator does. These eight steps cover the core internal audit requirements of SQF, BRCGS and IFS Food, so one program can serve whichever scheme you're certified to.
- 01List everything in scopeEvery clause of your scheme, every area and shift, and your FDA food safety plan. IFS Food explicitly includes off-site storage the company owns or rents, and FSSC 22000 adds quality elements to the scope.[3][5]
- 02Rank it by risk and historyAudit CCPs, allergen controls, sanitation and areas with past findings more often. BRCGS and IFS Food both tie audit frequency to risk.[3][9]
- 03Spread the schedule across the yearBRCGS needs at least four audit dates through the year, IFS Food a 12-month plan completed within 15 months, and SQF a full audit at least annually. Monthly modules avoid a one-week rush.[3][6][9]
- 04Keep inspecting between auditsRun the separate site and equipment inspections your scheme requires. In BRCGS that means hygiene and fabrication inspections at least monthly in open product areas.[3][9][10]
- 05Assign independent, trained auditorsNo one audits their own work: BRCGS forbids it, IFS Food requires independence from the audited department, and SQF asks for it where practical. SQF Edition 10 requires a documented assessment as part of internal auditor training.[3][6][9][10] Our Principles of Internal Auditing course covers planning, evidence and follow-up.
- 06Audit with evidenceSample records, observe the work and interview the people doing it. Trace one finished lot back through its records, like the vertical traceback SQF Edition 10 describes for certification audits. Record what conforms as well as what doesn't.[7][9]
- 07Feed findings into corrective actionTreat internal findings like external ones: root cause, owner, due date and a check that the fix worked.[9][10]
- 08Report and reviewSend results to the people responsible and to senior management, and review a summary at management review. SQF Edition 10 adds audit results to the monthly management update.[3][9][10]
How Do You Write a Corrective Action That Holds Up?
Corrective actions are judged on evidence, not intent. A response that walks through these eight steps covers what the schemes ask a corrective action to include.
- Describe it with evidence. What happened, where, when, how much product, and which requirement it breaks.
- Contain and correct. Stop the line or hold product as needed, and fix the immediate problem.
- Assess affected product. Decide what happens to product made while control was lost. Under FDA rules, food you can't show is unadulterated, and correctly labeled for allergens, stays out of commerce.[11]
- Find the root cause. Use the 5 Whys or a fishbone diagram, and keep asking until you reach something you can change. "Human error" isn't an answer; ask what made the error possible.
- Fix the cause. Give each action an owner and a due date. If the permanent fix takes time, such as a structural repair, put temporary controls in place and agree on the timeline with your certification body.[5][7]
- Update what the fix touches. Procedures, forms, training and the HACCP or food safety plan. FDA requires the food safety plan to be reanalyzed when a preventive control proves ineffective.[11]
- Verify it worked. Collect evidence that the action was carried out and that the problem hasn't come back, and record who checked.
- Close, report and trend. Report to management and track problems by type, so a pattern gets a root cause analysis of its own.[9]
IFS Food lists examples of acceptable evidence that corrections were carried out: training records, updated procedures with traceable changes, before-and-after photos, proof that changes were communicated, internal audit or inspection reports, and repair invoices. A repair quote doesn't count, because it only shows an intention to fix.[3]
How Kiwa ASI Can Help
Kiwa ASI audits U.S. food sites against GFSI-recognized schemes. SQF certification is through ASI Food Safety, LLC, an SQFI-licensed, ANAB-accredited certification body. We deliver BRCGS audits as a listed office of Kiwa Agri Food (UKAS-accredited) and Kiwa España (ENAC-accredited), and IFS Food audits as the U.S. office of Kiwa España. FSSC 22000 certificates are issued by a Kiwa group certification body licensed by Foundation FSSC. See our SQF, BRCGS, IFS and FSSC 22000 pages for audit options. Our certification auditors can explain a finding but can't tell you how to fix it. That keeps the audit impartial.
To build in-house skills, Principles of Internal Auditing, BRCGS internal auditor training, HACCP training and PCQI training are offered through ASI Training and Consulting, LLC, which operates separately from the certification body and has no effect on audit outcomes.
Frequently Asked Questions
What is the difference between a correction and a corrective action?
A correction fixes the immediate problem, such as re-cooking a batch or relabeling product. A corrective action removes the cause so the problem doesn't come back. FDA's preventive controls rule defines a correction as fixing a problem without the other steps of a corrective action procedure, such as reducing the likelihood that the problem will recur and evaluating affected food. SQF Edition 10 renames its clause "Corrections, and Corrective and Preventative Action" to make the difference clear.
How often do internal audits have to be done?
SQF requires a full internal audit at least once a year. BRCGS requires a scheduled program with at least four audit dates spread through the year, covering every activity at least annually, with frequency set by risk and past audit performance. IFS Food requires every requirement to be audited on a plan that covers 12 months and is completed within 15, with critical activities audited more often. FSSC 22000 sites follow ISO 22000:2018 clause 9.2 plus FSSC's additional requirements.
Can the QA manager audit the programs they run?
Not under BRCGS, which says internal auditors must not audit their own work. IFS Food requires auditors who are independent of the audited department, and SQF asks for independence from the function audited where practical. Small sites can swap areas between trained staff or bring in an outside auditor for the QA programs.
Do internal auditors need formal training?
SQF, BRCGS and IFS Food don't name a specific course. SQF and BRCGS require internal auditors who are trained and competent, and IFS Food requires competent auditors. SQF Edition 10 adds a documented assessment as part of the training. FSSC 22000 sets minimum education, experience and training for internal auditors in multi-site programs.
How long do we have to close non-conformities after a certification audit?
BRCGS: evidence of correction, root cause analysis and a preventive action plan within 28 calendar days. FSSC 22000: minor action plans approved and majors closed within 28 days. SQF: closed within 30 calendar days under Edition 9 and 40 under Edition 10. IFS Food: the completed action plan, with evidence of corrections, within 4 weeks of receiving it. Critical findings don't get these windows; they can mean a failed audit or a suspended or withdrawn certificate.
Is retraining an acceptable corrective action?
Sometimes as part of one, rarely on its own. If the root cause is a gap in training, retraining fits. But "operator error" often means something made the error easy to make, such as a confusing procedure, look-alike materials or no check step. Fix that, then show the problem hasn't come back.
Does FDA require internal audits?
21 CFR Part 117 has no clause called internal audit, but it requires similar checks: calibration and other verification activities, review of monitoring and corrective action records by or under a PCQI within 7 working days (or longer if a PCQI justifies it in writing), written corrective action procedures, and reanalysis of the food safety plan at least every 3 years.
What happens if the same non-conformity comes back?
It usually gets more serious. BRCGS auditors check every previous non-conformity at the next audit, and if the corrective or preventive action didn't work they raise a non-conformity against clause 1.1.12. FSSC 22000 says a minor not addressed by the next audit can become a major. Under SQF Edition 10, the auditor may raise extra non-conformances against the corrective action clause, which is a Core Clause.
Is there a GFSI certificate?
No. GFSI recognizes certification programs but doesn't audit sites or issue certificates. Your certificate is for the scheme you were audited to, such as SQF, BRCGS, IFS Food or FSSC 22000.
Can our certification body help us fix non-conformities?
Your certification auditor can explain what a finding means but can't tell you how to fix it, because the certification body has to stay impartial. Internal auditing training is available through ASI Training and Consulting, LLC, which operates separately from the certification body and has no effect on audit outcomes.
Find problems before your auditor does
Talk to our team about SQF, BRCGS, IFS or FSSC 22000 certification audits, or build your team's internal audit skills with live online training.
Questions? Email US.Info@kiwa-asi.com or call 1 (800) 477-0778.
Keep reading
- BlogRoot Cause Analysis in SQF AuditsMethods, examples and a five-step process.
- BlogTop 10 BRCGS Non-ConformitiesWhat auditors find most, and the evidence that closes it.
- BlogValidation vs. VerificationWhat auditors expect to see behind every critical limit.
- PagePrinciples of Internal AuditingOne-day live online course built on ISO 19011.
- PageBRCGS Internal Auditor TrainingAudit your own site to the standard before the auditor does.
- PageSQF CertificationAudits by an SQFI-licensed, ANAB-accredited certification body.
Sources
- BRCGS. Annual Report 2024-25 (“2024-25 at a glance”, p. 7; “Top five non-conformities of 2024-25”, p. 14). brcgs.com, archived copy (PDF)
- BRCGS. Compliance Report 2022, “BRCGS Food Standard: Top 10 non-conformances raised during 2021”. brcgs.com, archived copy (PDF)
- IFS. IFS Food Version 8 (April 2023), Part 1 (KO requirements, post-audit action plan, chart 5) and Part 2 (4.5.3, 5.1 Internal audits, 5.11 Management of deviations, non-conformities, corrections and corrective actions). ifs-certification.com (PDF)
- BRCGS. Global Standard Food Safety, Issue 9, Part III: Audit Protocol (non-conformities and corrective action; Issue 9 text published for the Issue 10 consultation). brcgs.com, archived copy (Word)
- Foundation FSSC. FSSC 22000 Scheme, Version 6.0 (April 2023), Part 2 (2.5.9 Quality control; 2.5.18 Multi-site certification, food chain categories E, F and G) and Part 3 (6.2 Nonconformities). fssc.com (PDF)
- SQFI. SQF Food Safety Code: Food Manufacturing, Edition 9 (Part A, non-conformance grading and close-out; Part B, 2.5.3 Corrective and Preventative Action and 2.5.4 Internal Audits and Inspections). sqfi.com (PDF)
- SQFI. SQF Food Safety Code, Edition 10, Part A: Implementing and Maintaining the SQF Food Safety Code (A2:17 Conducting the Audit, A2:21 Corrective Actions; updated September 1, 2026). sqfi.com
- GFSI. Recognised Certification Programme Owners (accessed October 5, 2026). mygfsi.com
- BRCGS. Global Standard Food Safety, Issue 9, Part II: Requirements (clauses 2.11, 3.4, 3.7, 6.2, 6.4; Issue 9 text published for the Issue 10 consultation). brcgs.com, archived copy (Word)
- SQFI. SQF Food Safety Code: Food Manufacturing, Edition 10, Checklist and Change Document (2.1.2.2, 2.5.2.2, 2.5.3, 2.5.4, 2.9.1.2). sqfi.com (Excel); change document (Excel)
- U.S. FDA. 21 CFR Part 117, Current Good Manufacturing Practice, Hazard Analysis, and Risk-Based Preventive Controls for Human Food (§§ 117.3, 117.135, 117.150, 117.165, 117.170, 117.180, 117.190). ecfr.gov
- GFSI. Benchmarking Requirements version 2024, Part II: Implementation Handbook (5.23 and 5.24, Management of Certification). mygfsi.com (PDF)
- SQFI. Edition 10 FAQ (accessed October 5, 2026). sqfi.com
- Foundation FSSC. FSSC 22000 Scheme, Version 7.0 (May 2026), and Version 7 Upgrade Process (Version 6 audits allowed until April 30, 2027; Version 7 audits from May 1, 2027). fssc.com (PDF); upgrade process (PDF)