Food Safety Program(FSP)

compliance
FSANZ
Verified April 2026

Definition

A documented system based on HACCP principles that identifies food safety hazards and establishes controls to manage them, required for most food businesses in Australia.

Regulatory Source

  • Standard 3.2.1Food safety programs — mandates a documented, HACCP-based food safety program for certain food service and processing businesses

Last verified against current standards: April 2026

Regulatory authority: Food Standards Australia New Zealand (FSANZ)

What is a Food Safety Program?

A Food Safety Program (FSP) is a documented, written plan that identifies the food safety hazards associated with a food business's activities and sets out the systematic controls used to manage those hazards. In Australia, FSANZ Standard 3.2.1 mandates a food safety program based on HACCP principles for certain categories of food businesses.

Who Needs a Food Safety Program?

Standard 3.2.1 currently applies to:

  • Food service to vulnerable persons — aged care facilities, hospitals, childcare centres, and schools preparing or serving food to people who are at greater risk from foodborne illness.
  • Caterers — businesses that handle, serve or sell potentially hazardous food to consumers at temporary events, functions, or markets.

State and territory food legislation may extend the requirement to additional business types. Some states have adopted Standard 3.2.1 for a broader range of manufacturers, and major retailer supplier codes (Woolworths, Coles, Aldi) typically require an FSP or equivalent third-party certification regardless of the regulatory mandate.

What a Food Safety Program Must Contain

Standard 3.2.1 specifies that a food safety program must:

  1. Systematically identify hazards — biological (bacteria, viruses), chemical (allergens, cleaning agents, pesticide residues), and physical (metal, glass, bone) hazards that may occur at each step of the process.

  2. Identify the Critical Control Points (CCPs) where those hazards can be controlled.

  3. Set critical limits for each CCP — the maximum or minimum value that must not be exceeded.

  4. Establish monitoring procedures — how the CCP will be checked, by whom, and how often.

  5. Document corrective actions for when a critical limit is breached.

  6. Establish verification procedures to confirm the program is working.

  7. Maintain records demonstrating the program has been implemented.

The program must be documented, kept at the food premises, and made available to an authorised officer on request. It must be reviewed whenever there is a change in processes, products, or when a food safety incident occurs.

Food Safety Programs and Third-Party Certification

Many food manufacturers choose to obtain third-party certification against internationally recognised food safety management standards such as:

  • SQF (Safe Quality Food) — widely required by major Australian retailers
  • BRC (British Retail Consortium) Global Standard — common in export markets
  • FSSC 22000 — ISO-based food safety system certification

These schemes are built on HACCP and broadly align with Standard 3.2.1, but are more rigorous and comprehensive in scope. Third-party certification does not replace compliance with Standard 3.2.1; both obligations may apply simultaneously.

Common mistakes

Treating the FSP as a static document. A food safety program must be a living system. If a process changes, a new product is added, or a food safety incident occurs, the program must be reviewed and updated. An outdated FSP is worse than no FSP — it gives false assurance while leaving real risks unaddressed.

Inadequate records. The FSP only has legal force if records demonstrate it is being followed. Monitoring records for each CCP must be completed in real time, not reconstructed after the fact.

Confusing Standard 3.2.1 with Standard 3.2.2. Standard 3.2.2 (Food Safety Practices) applies to all food businesses in Australia and covers general hygiene and food handling. Standard 3.2.1 requires a formal documented HACCP-based program and applies to a subset of businesses. Both may apply to your business.

How Batchbase Supports Food Safety Programs

Batchbase provides the batch record and traceability infrastructure that a food safety program's verification and record-keeping requirements depend on. Every production run creates a time-stamped batch record with lot numbers, ingredient quantities, and operator sign-off — the documentation backbone of a functioning FSP.

Related Standards and References

  • FSANZ Standard 3.2.1 — Food safety programs
  • FSANZ Standard 3.2.2 — Food safety practices and general requirements
  • FSANZ food standards code

Manage Food Safety Program (FSP) compliance in Batchbase

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

Built to meet Standard 3.2.1 requirements.