Food safety inspection vs audit: what is the difference, and why does it matter on your site?

Last updated 7 October 2026

A food safety inspection checks a place, a piece of equipment or a batch against a checklist or specification, usually by a QC or supervisor, and produces a pass or a finding. An audit is a planned, independent check of the whole system against a standard, using sampling and objective evidence, and ends in findings and a report. The owner of an area may inspect it but never audit it.

A production manager at a chilled ready meals plant walks his line every Friday with a checklist headed Internal Audit. The sheets are neat and filed for a full year. Then the certification auditor writes a nonconformity: no evidence of internal audits covering the line. Nothing on the floor was wrong. The name on the checklist was.

Learn to run both jobs properly with Food Safety Inspections and Audit Readiness for QCs and HACCP Teams. You finish with a risk-based audit checklist and a completed inspection and report workbook that stay yours to use on site. About 9 hours online, R1 699.

What is the difference between a food safety inspection and an audit?

Three things separate them: who does the check, what it is checked against, and what it produces. An inspection looks at a thing against a checklist. An audit tests a system against a standard, clause by clause, and it is always done by someone independent of the area.

Most sites use four words as if they mean the same thing: monitoring, inspection, verification and audit. They are four different jobs, done by different people, at different times. When you mix them up, you usually find out from a stranger with a clipboard.

The four checks on a food site, side by side

Check	Who does it	When	Checked against	What it produces	Independent?
Monitoring	The operator running the process	While the process runs	A set limit	A reading	No
Inspection	A QC or supervisor	Before, during or after the run	A checklist or specification	A pass or a finding	Usually
Verification	A QC, the lab or a manager	After the fact	The records and the results	Confirmation, or a doubt	Usually
Audit	A trained auditor from outside the area	To a plan, once or a few times a year	A standard, clause by clause	Findings and a report	Always

A short way to hold it in your head: monitoring watches, inspection looks, verification confirms, and an audit tests the system.

Where do monitoring and verification fit?

Monitoring is the operator watching a control while it works. Verification is someone checking afterwards that the control worked and that the records are true. Both sit next to inspection, and neither is an audit.

Take a footbath. The hygiene supervisor checks the sanitiser strength every two hours and writes it on a sheet. That is monitoring. At month end the QC manager pulls every footbath sheet, checks each reading against the SOP limit, and finds three low readings with no action written next to them. That is verification, and notice what it did. The monitoring recorded the problem and carried on. Verification caught it.

Now the QC walks the salad line before start-up with a checklist and finds a cracked light diffuser over the packing table. That is an inspection: against a checklist, before the run, recorded, by someone who is not the operator. It becomes a finding the moment she writes down the place, the time and the requirement it breaks.

If you work to ISO 22000:2018, the clauses give each job a home. Clause 9.1 covers monitoring and measurement. Clause 8.8 covers verification of the prerequisite programmes and the hazard control plan, and most of a QC’s after-the-fact work lives there. Clause 9.2 is internal audit, the clause that makes auditing compulsory. Your daily checks do not sit under 9.2, and calling them audits does not move them there.

Why does calling an inspection an audit cost sites a nonconformity?

Because a certification auditor tests whether an internal audit actually happened, not whether a sheet carries the word. If the person who did it owns the area, if there was no plan, or if it was not checked against the clauses of a standard, it was not an audit.

This is one of the findings I write most often on sites that otherwise run well. The internal audit schedule is full. The reports are tidy. And the production manager audited production. Independence is the line between an inspection and an audit, and it is not an insult to anyone. It is the reason a finding is believable.

The fix for the Friday walk in the opening story is not to stop it. It is a perfectly good inspection. Rename it on the checklist so nobody mistakes it again, then set up a genuine internal audit: a planned schedule that covers the whole system, carried out by someone trained and independent of the area, checked against the standard, with findings and a report. The case sites in the FS50 course are training scenarios built from real audit patterns, and this exact mix-up is the first one learners untangle.

Stop losing findings on a word. The FS50 course teaches you to tell the four jobs apart, then plan and run a real internal audit on a case study, all marked automatically the moment you submit. Nine hours, self paced on your phone, R1 699.

Who may inspect an area, and who may audit it?

Anyone trained may inspect the area they work in every day, and they should. Nobody may audit their own area, their own work or a procedure they wrote, because they would be reporting on themselves.

ISO 19011:2026, the fourth edition of the auditing guideline, sets out seven principles of auditing: integrity, fair presentation, due professional care, confidentiality, independence, an evidence-based approach and a risk-based approach. Independence is the one inspection programmes break without noticing.

Here is how it plays out. A QC on the salad line wrote the pre-op checklist for that line. The audit programme asks her to audit the cleaning system on the same line. She is the best qualified person on site for the subject, and she is the wrong person for the audit. Swap her with the QC from another line, or put an independent lead auditor on the job and use her as a technical resource. The full set of changes in the 2026 edition is covered in ISO 19011:2026 and your food safety internal audits.

What turns a walkabout into an inspection that counts?

Three things: it is routine, it is risk based, and its sampling is defined in advance. Without those, a walkabout is a stroll with a clipboard.

Under FSSC 22000 Version 7, clause 2.5.12 on PRP verification expects routine site inspections, with monthly given as the example frequency. A high care area and an outside bulk store do not need the same interval. Whatever you choose, write down the reason, because that written reason is what risk based means, and it is the first thing an auditor asks for.

Every check also needs a parent. Ask who asked for it. There are only three honest answers: a certification standard, the law, or a documented decision by your own food safety team. R638 of 2018 is law, and regulation 10 makes the person in charge responsible for the hygiene of the premises, so a site with no certificate at all still has a reason to inspect. What is not an answer is that it has always been done that way. A check with no parent is the first one to disappear when the site is two people short.

What turns an inspection into an internal audit?

A plan, criteria, an independent auditor and a report that answers a question. If there are no criteria, you are inspecting, however long the checklist is.

1. A programme for the year. What gets audited, how often and by whom, owned by the food safety team leader. The risk-based reasoning behind the frequencies is written down.
2. A plan for each audit. An objective that uses the word effective, a scope that names the activities, records and time period, and at least two named criteria such as a clause, a procedure or a regulation.
3. Document review before the floor. Current procedures, the last audit report, recent records and complaints. Reading documents is preparation, not the audit itself.
4. Evidence three ways. Ask, watch and read. What you are told is a lead until a record or an observation backs it up.
5. Findings written as requirement, evidence and gap, graded by written rules and reviewed with the auditee before the closing meeting. The method is set out in how to write a food safety audit finding that gets fixed.
6. A conclusion that answers the objective, a report, a follow-up date and someone named to verify that the corrective actions worked.

Not sure which course fits your job? WhatsApp ASC on +27 61 483 0381.

Which one does the situation call for?

Ask what question you need answered. If it is whether this line, area or delivery is fit right now, inspect. If it is whether the system works and keeps working, audit.

• The line starts in twenty minutes. Pre-op inspection. It is the only inspection with a veto: the line runs or it does not.
• A delivery arrives with a cut seal. Receiving inspection, and a decision to accept, reject or hold.
• A month of chill records needs signing off. Verification.
• The same six walkabout findings reopen every month. Stop closing them one by one. That pattern is a system problem, and an audit of the cleaning or maintenance system will find why.
• A retailer audit or unannounced certification visit is coming. Both. Inspect the floor and the records, and make sure your internal audit cycle is complete. The full routine is in how to prepare for a food safety audit in South Africa.

A useful rule from the listeriosis outbreak of 2017 to 2018, when 1 060 cases and 216 deaths were reported: an inspection finds the broken thing, and an audit finds why the system let it stay broken. A cracked floor joint beside a drain is an inspection finding. A drain positive closed as recleaned, with no trend and no job card, is an audit finding.

Frequently asked questions

Is an inspection the same as an internal audit?

No. An inspection checks a place, thing or batch against a checklist, while an internal audit is a planned, independent check of the system against a standard that ends in findings and a report. A walkabout by the person who owns the area is an inspection, whatever the sheet is called.

Can a QC audit the area she inspects every day?

She can inspect it every day, but she should not audit it. An auditor must be independent of the activity audited, so swap auditors between areas or bring in someone from another department.

What is the difference between verification and inspection?

Inspection looks at the thing itself, such as a line before start-up. Verification checks afterwards that a control worked and that its records are true, such as reviewing a month of temperature sheets or swabbing a surface signed off as clean.

How often should a food factory do internal audits?

The frequency comes from your own audit programme and is set by risk, previous results and changes. Many sites cover every part of the system at least once a year, with high-risk areas more often, but check what your own certification scheme requires.

Do I need a certificate to run inspections and audits?

No. If R638 is your only requirement, you inspect and audit against R638 and your own procedures, and the method is the same.

Will the FS50 course make me a registered auditor?

No. It is practical inspection and internal audit training, not a lead auditor course, and it does not register you with any body.

Learn to inspect like a QC and audit like an auditor

Ready to manage the whole audit programme and audit your suppliers? Carry on to Internal and Supplier Auditing Practices, or see all ASC auditing training.

Sources

• ISO 19011:2026, Guidelines for auditing management systems, ISO
• ISO 22000:2018, Food safety management systems, Requirements for any organization in the food chain, ISO
• FSSC 22000 Scheme Version 7, Foundation FSSC
• Regulations Governing General Hygiene Requirements for Food Premises, the Transport of Food and Related Matters (R638 of 22 June 2018), Foodstuffs, Cosmetics and Disinfectants Act 54 of 1972