Food Safety Audit

compliance
FSANZ
Verified April 2026

Definition

A systematic examination of a food business's food safety management system, including HACCP plans, GMP compliance, documentation, and operational practices.

Key Takeaways

  • Food safety audits assess whether your food safety program is adequate in design and effective in practice
  • Third-party audits by approved auditors are required under FSANZ Standard 3.2.1 for businesses with a mandatory FSP obligation
  • Audit frequency is risk-based — higher-risk businesses (e.g. RTE manufacturers) are typically audited more frequently
  • Non-conformances raised at audit must be closed within agreed timeframes; repeat non-conformances escalate to compliance action
  • Internal audits conducted between third-party audits help identify gaps early and demonstrate continuous improvement

Regulatory Source

  • Standard 3.2.1Food safety programs — businesses subject to Standard 3.2.1 must have their food safety program audited by an approved auditor

Last verified against current standards: April 2026

Regulatory authority: Food Standards Australia New Zealand

What is a Food Safety Audit?

A food safety audit is a systematic, independent examination of a food business's food safety program to determine whether activities and their results comply with planned arrangements, and whether those arrangements are implemented effectively. Under FSANZ Standard 3.2.1, businesses that are required to have a food safety program must have that program audited by an approved auditor at a frequency set by their state or territory food regulatory authority — typically every six to twelve months for high-risk operations.

The audit is not just a check that the paperwork exists. An approved auditor will verify that the food safety program reflects the actual production process, that staff can demonstrate they follow the documented procedures, and that records show the system has been working continuously — not just on the day of the audit.

Who Needs a Food Safety Audit?

Standard 3.2.1 applies to food service businesses serving vulnerable persons (hospitals, aged care facilities, childcare centres), businesses that handle unpackaged potentially hazardous food at certain steps (caterers, some retailers), and certain food manufacturers and processors. The specific scope varies by state and territory, as each jurisdiction has adopted Standard 3.2.1 with some variations.

Businesses seeking third-party certification under schemes such as SQF, BRC/IFS, or FSSC 22000 are also subject to regular external audits as a condition of maintaining certification, regardless of whether Standard 3.2.1 formally applies to them.

Food Safety Audits in Practice for Australian Food Manufacturers

What happens in an audit? A typical Standard 3.2.1 audit covers: review of the food safety program documentation (is it current, does it reflect actual operations?); review of records (are CCPs being monitored, are corrective actions documented, are training records current?); observation of production (are staff following the documented procedures?); interview of staff (do they understand their food safety responsibilities?); and inspection of premises and equipment.

Common findings that lead to non-conformances:

Food safety program not updated after process changes. If you added a new product or changed a recipe six months ago and did not update your HACCP plan and CCP list, the auditor will note this as a non-conformance.

Records not available for review. Missing batch records, incomplete CCP monitoring logs, or temperature records that show suspiciously round numbers all raise red flags. Auditors distinguish between records that demonstrate genuine monitoring and records that appear to have been fabricated or back-filled.

Staff unable to explain their food safety responsibilities. Your food safety program may be perfect on paper, but if a production operator cannot explain what the critical limit is for the CCP they monitor every day, the program is not effectively implemented.

Preparing for audit: Conduct a self-audit — or a gap assessment by a food safety consultant — three to four months before your scheduled audit. This gives you time to address non-conformances before they become official findings. Ensure all records are filed and retrievable, staff training records are current, and your food safety program document reflects your actual current operations.

How Batchbase Supports Audit Readiness

The most common audit finding is missing or incomplete records. Batchbase addresses this by making record-keeping the default action during production rather than a separate administrative task. CCP monitoring results are recorded during the batch; cleaning tasks are logged against a schedule; corrective actions are documented in the system at the time they occur.

When an auditor arrives, all records are searchable and printable from Batchbase — batch records, CCP logs, corrective action histories, and cleaning records — rather than scattered across paper forms and spreadsheets. This significantly reduces the administrative burden of audit preparation and demonstrates that your food safety system is genuinely operational, not paper-only.

Related Standards and References

  • FSANZ Standard 3.2.1 — Food safety programs (audit requirement, clause 8)
  • FSANZ food standards code
  • Your state or territory food authority sets the audit frequency and auditor approval requirements

Manage food safety audit compliance in Batchbase

Batchbase automates FSANZ compliance, nutrition labelling, allergen tracking, and batch costing for Australasian food manufacturers.

Built to meet Standard 3.2.1 requirements.