South Australian Public Health (Notifiable Contaminants) Regulations 2020

The regulations rely on a small number of core concepts, defined either in the regulations themselves or by reference to external food‑standards instruments. Understanding how those concepts interlock is necessary to determine when notification duties arise.

Contaminant: Regulation 4 prescribes specific items for the Act’s definition of contaminant in s 3(1). The instrument makes four categories of contaminant: (a) a pathogen listed in regulation 5(1); (b) a toxin produced by a pathogen listed in regulation 5(1); (c) a microorganism referred to in regulation 6(1) (which points to section S27-4 of Schedule 27 of the Code); and (d) a microorganism listed in regulation 7(1).

Notifiable contaminant: The regulations implement the Act’s notifiable contaminant regime by declaring particular organisms or toxins to be notifiable for the purposes of section 67(1) of the Act (regs 5(1), 6(1), 7(1)). The lists in regs 5-7 convert the Act’s generic notification triggers into specific, operational objects.

Responsible person: The duty to report detection or isolation is placed on “the responsible person” under the Act; the regulations refer repeatedly to this role (regs 5(3), 6(2), 7(2)). The regulations do not define who the responsible person is; that definition sits in the Act. For compliance, entities must locate the Act’s definition to determine legal obligations.

Detection or isolation at specified levels: The regime differentiates between simple detection/isolation and detections that cross prescribed microbiological thresholds. Regulation 5(3) requires reporting of detection or isolation of the listed pathogens (without a level caveat). Regulation 6(2) requires reporting where microorganisms listed in S27-4 of Schedule 27 of the Code are detected at a level greater than the “unacceptable microbiological level” as determined by Standard 1.6.1. Regulation 7(2) requires reporting where certain organisms are detected in ready‑to‑eat food at a level equal to or greater than the “unsatisfactory or potentially hazardous level” determined by Table 1 of the Compendium. “Unacceptable microbiological level” and “unsatisfactory or potentially hazardous level” are given precise legal meaning in reg 3 by reference to those external documents.

External standards as normative references and dynamic linkage: The regulations repeatedly incorporate external instruments “as in force from time to time.” Regulation 3 defines the Compendium, ready‑to‑eat food (by cross‑reference to Standard 3.2.2 of the Code), Schedule 27, Standard 1.6.1 and the level terms by reference to those external standards. Regulation 6(3) and reg 8(4) require testing in accordance with Standard 1.6.1. This produces a legal architecture where core technical thresholds and methods are supplied by non‑statutory or Commonwealth instruments that can be updated outside the regulations themselves.

Preliminary or presumptive detection: The regulations distinguish preliminary or presumptive detections from confirmed detections. Regulation 5(4) and reg 8(3) exempt preliminary or presumptive detections from the duty to report, except where the Chief Public Health Officer requires otherwise. This creates a gate for the Chief Public Health Officer to require notification at an earlier stage in the laboratory confirmation process.

Third‑party reporting: Regulation 8 prescribes the circumstances for third‑party reporting under section 68(4) of the Act: where a person is aware or suspects that a responsible person has not reported a detection or isolation, and the awareness or suspicion is founded on a test outcome described in reg 8(2). The regulation therefore enables persons other than the responsible person to trigger the statutory notification apparatus in prescribed circumstances.

Prescribed body: Regulation 9 designates FSANZ as the prescribed body for the purposes of section 109(5)(a) of the Act. The regulations thus identify the Commonwealth food‑standards agency as the relevant technical or advisory body envisaged by the Act in that provision.

Taken together, these concepts produce a two‑part operational test: (1) is the organism or toxin a notifiable contaminant under regs 5-7; and (2) if it is, does the test outcome meet the level or confirmation standard that the regulations require to trigger the reporting duty. Where both parts are satisfied, the responsible person must report to the Chief Public Health Officer as required by the Act.

Primary legal duty‑bearers: The regulations repeatedly create obligations for the “responsible person” to report the detection or isolation of notifiable contaminants (regs 5(3), 6(2), 7(2)). The regulations do not define “responsible person”; that is a term used in the Act. Practitioners must look to the Act to identify which natural or legal persons qualify as responsible persons in different contexts (e.g. food business operators, manufacturers, importers, or others). The practical effect of the regulations is to place mandatory reporting responsibilities on whoever the Act designates as responsible for the food in question.

Testing laboratories and food safety consultants: The regulations require testing to be carried out in accordance with Standard 1.6.1 (reg 6(3) and reg 8(4)). Laboratories that perform microbiological testing for the purposes of compliance with these regulations therefore face an operational obligation to follow those methods and standards; failure to do so may mean that a test is not legally appropriate to trigger reporting duties under the regulations. Food safety consultants, quality assurance providers and in‑house laboratory managers must ensure methods and accreditation align with Standard 1.6.1.

Food businesses handling ready‑to‑eat food: Regulation 7 applies specifically to microorganisms detected in ready‑to‑eat food at unsatisfactory or potentially hazardous levels as determined by Table 1 of the Compendium. Businesses that manufacture, prepare, serve or handle ready‑to‑eat food (a defined term as per reg 3 linked to Standard 3.2.2 of the Code) should have heightened exposure to reporting obligations because thresholds are lower or different for ready‑to‑eat products.

Third parties and external actors: Regulation 8 creates a duty on any person who is aware or suspects that a responsible person has not reported a detection to make their own report when the prescribed circumstances exist. That can include other laboratories, local government environmental health officers, suppliers, customers, or health professionals who receive test reports.

Government decision‑makers: The Chief Public Health Officer holds targeted discretion. The regulations exempt preliminary or presumptive detections from mandatory reporting unless the Chief requires otherwise (regs 5(4), 8(3)). The Chief can also require early reporting in specific cases. Food Standards Australia New Zealand is the prescribed body under reg 9 for the purposes of s 109(5)(a) of the Act, meaning the Chief and other decision‑makers in the notification scheme will rely upon FSANZ as the designated technical authority.

Indirectly affected parties: Because the regulations anchor obligations to external standards “as in force from time to time” (reg 3), any person whose compliance or operations rely on those standards must monitor their evolution. This includes food importers who must anticipate that Schedule 27 or Standard 1.6.1 amendments could change notification thresholds, and suppliers whose products may be tested to different criteria over time.

Costs and resource allocation: The regulations shift costs onto entities responsible for testing and reporting. Responsible persons will have to maintain systems for receiving lab results, distinguishing preliminary/presumptive results from confirmatory results, and reporting confirmed detections. Laboratories must ensure testing conforms to Standard 1.6.1. Where confirmation testing is required, costs of follow‑up tests and potential recalls or hold periods will be borne by businesses. The regulations do not allocate costs or provide funding; they allocate duties.

In short, the instrument affects any person identified as a “responsible person” under the Act, testing laboratories and their methods, operators of ready‑to‑eat food businesses, third parties who may detect unreported contaminants, and government officials who exercise targeted discretion under the notification exemption for preliminary tests.

Duties to report detections or isolations: The central duty the regulations impose is a reporting obligation placed on the responsible person. Regulation 5(3) states that for contaminants declared under reg 5(1) (the listed pathogens and their toxins under reg 5(2)), the responsible person must report if the contaminant is detected or isolated in food. Regulation 6(2) requires reporting where an organism referred to in section S27-4 of Schedule 27 of the Code is detected in food at a level greater than the “unacceptable microbiological level”. Regulation 7(2) requires reporting where the organisms listed in reg 7(1) are detected in ready‑to‑eat food at a level equal to or greater than the “unsatisfactory or potentially hazardous level” in Table 1 of the Compendium. Each of these duties is framed as being “for the purposes of section 68(1) of the Act”, which means the form and destination of reporting will be regulated by that Act provision, but the regulations supply the substantive triggers.

Testing obligations: When the obligation depends on a detection exceeding a level, the regulations require testing in accordance with the Australia New Zealand Food Standards Code Standard 1.6.1. Regulation 6(3) and reg 8(4) make that explicit. Where Table 1 of the Compendium supplies the relevant “unsatisfactory or potentially hazardous level” (reg 3), tests that feed into that table need to use methods compatible with the Compendium if those results are to be relied upon for notification.

Preliminary/presumptive detection carve‑out and Chief’s discretion: Two places carve out preliminary or presumptive tests from the reporting obligation unless the Chief Public Health Officer requires otherwise: reg 5(4) excludes preliminary or presumptive detection or isolation of contaminants listed in reg 5(1) from the reporting duty except where the Chief requires reporting, and reg 8(3) relieves third parties from reporting preliminary or presumptive detections unless the Chief requires otherwise. The effect is that confirmed detections trigger the automatic duty to report, while early or presumptive results do not unless the Chief exercises the power to require them. The right for the Chief to require earlier reporting is embedded in these exemptions.

Third‑party reporting duty when responsible person fails to report: Regulation 8 prescribes the situations under which “a person who is aware, or suspects, that a responsible person has not reported the detection or isolation” must report. Those situations are strictly defined: they are where a test has detected or isolated a notifiable contaminant in food under the circumstances described in reg 8(2) (a-c). Thus third parties have a statutory duty to notify the Chief Public Health Officer when they come across a qualifying test result and suspect non‑reporting by the responsible person.

Linkage to external standards and dynamic thresholding: By defining “unacceptable microbiological level” and “unsatisfactory or potentially hazardous level” by reference to Standard 1.6.1 and the Compendium (reg 3), the regulations give businesses, laboratories and inspectors rights and duties that will change when those external documents change. That is, an entity’s duty to report may expand or contract as the referenced standards are updated “as in force from time to time”.

Designation of FSANZ: Regulation 9 prescribes Food Standards Australia New Zealand as the prescribed body for the purposes of section 109(5)(a) of the Act. That creates a statutory link between the Act’s s 109(5)(a) function and FSANZ, conferring on FSANZ the status the Act requires for consultation, standards adoption or advisory functions, depending on what s 109(5)(a) provides.

No penalties or form specified in the regulations: The regulations do not create a schedule of penalties, nor do they set out the administrative form, timing or procedural modalities for reporting; those are matters left to the Act (for example, the references in regs 5(3), 6(2), 7(2) to section 68(1) of the Act) and possibly to agency practice. Legal duties are therefore split: these regulations supply substantive triggers and test methods, and the Act supplies the mechanics of reporting and any sanctions for non‑compliance.

Obligations on test method conformity and record reliance: Because testing is expressly required to accord with Standard 1.6.1 (regs 6(3) and 8(4)), laboratories and responsible persons derive a duty to use those methods if they want test outcomes to count for notification triggers. That creates an operational duty to ensure testing protocols, accreditation, and chain of custody meet the technical standard.

In summary, the regulations impose duties to notify confirmed or level‑exceeding detections for specified organisms and toxins, require use of specified external testing standards, permit the Chief to require reporting of preliminary results in particular cases, and create a duty on third parties to report when responsible persons have not reported. The precise form, timing and penalties for non‑compliance are governed by the Act rather than by these regulations.

The regulations do not themselves create a bespoke penalty regime, nor do they specify enforcement mechanisms in the text provided. Instead, they operate as a schedule of notifiable contaminants and procedural triggers that plug into the enforcement and sanctions architecture established by the South Australian Public Health Act 2011.

Delegation of enforcement content to the Act: Each reporting obligation set out in the regulations is framed “for the purposes of section 68(1) of the Act” (regs 5(3), 6(2), 7(2)). That indicates the regulations define what must be reported while the Act defines how reporting must be done and what consequences follow for failure to report or for other breaches. Practitioners must therefore consult the Act for the statutory penalty provisions, enforcement pathways, inspector powers, and administrative procedures that apply when a reporting duty is not met.

Chief Public Health Officer’s role in enforcement discretion: The regulations expressly permit the Chief Public Health Officer to require reporting of preliminary or presumptive detections (regs 5(4), 8(3)). That power is an enforcement or precautionary discretion because it allows the Chief to accelerate the flow of information ahead of confirmatory testing where public health protection demands it. The regulations do not specify how the Chief will exercise that power, the standard for invoking it, or whether such a direction is reviewable; those procedural elements will be governed by the Act and by administrative law.

Information flow and third‑party reporting as an enforcement lever: Regulation 8 prescribes circumstances in which persons who are aware or suspect a responsible person has not reported must report to the Chief Public Health Officer. This creates an information‑gathering pathway that can trigger inspections, investigations or enforcement action under the Act. By requiring others to report when a responsible person has not, the instrument broadens the surveillance net and reduces the state’s sole reliance on self‑reporting.

Testing standard compliance as an enforcement nexus: Where the reporting trigger depends on exceeding specified microbiological levels, the regulation that testing must be carried out in accordance with Standard 1.6.1 (reg 6(3) and reg 8(4)) embeds technical conformity into the enforcement equation. If a laboratory’s test does not comply with Standard 1.6.1, regulators may treat the test as irrelevant to triggering the statutory duty; conversely, properly conducted tests can be the basis for enforcement action. The regulations therefore give regulators a clear technical bar against which testing methods can be measured during compliance assessments or prosecutions.

No explicit enforcement procedures in the regulations: The instrument does not say who enforces the reporting duty, how a failure to report becomes the subject of a prosecution or administrative penalty, what defences are available, or the timeframes for enforcement action. Those matters are left to the Act and to the administrative practices established by the Chief Public Health Officer’s office and relevant enforcement agencies. Practitioners should consult s 68 and other relevant provisions of the Act for the procedural content of enforcement, including any prescribed timeframe for notification and penalty scales.

Potential practical enforcement outcomes implied by the scheme: Although the regulations do not enumerate penalties, the structure produces likely enforcement outcomes: notifications should prompt public health investigations; failure to report confirmed or level‑exceeding detections may attract sanction under the Act; and the Chief’s power to require earlier reporting may be used to compel faster action in situations judged to be of heightened risk. However, the regulations leave the mechanics, discretion parameters, and the severity of penalties to the Act and to agency practice.

In short, enforcement and penalties are not created or detailed in these regulations; they are a matter for the Act. The regulations shape enforcement by defining the set of notifiable contaminants, the threshold for notification, the required testing standards, and the situations in which third parties must report , all of which are the triggers that will bring enforcement provisions in the Act into play.

The regulations are explicitly designed to operate in tandem with the South Australian Public Health Act 2011 (the Act) and several instruments under the Commonwealth food‑standards regime. The regulations both import definitions from and defer technical thresholds to those external instruments, producing legal interaction channels that are essential for interpretation and compliance.

Primary statutory interaction with the Act: The regulations repeatedly invoke sections of the Act. Regulation 4 is “for the purposes of the definition of contaminant in section 3(1) of the Act”. Regulations 5-7 operate “for the purposes of section 67(1) of the Act” (declarations of notifiable contaminants) and for the purposes of section 68(1) of the Act (the duty to report detection or isolation). Regulation 8 is linked to section 68(4) of the Act (third‑party reporting where a responsible person has not reported), and regulation 9 to section 109(5)(a) of the Act (prescribed bodies). Therefore the content of these regulations must be read as operational detail that implements and fleshes out the Act’s notification, information and consultation architecture.

Cross‑jurisdictional linkage to the Australia New Zealand Food Standards Code: The regulations import substantive technical content from the Code. Regulation 3 defines “ready‑to‑eat food” by reference to Standard 3.2.2 of the Code, defines “Schedule 27” and “Standard 1.6.1” by reference to the Code, and defines “unacceptable microbiological level” and “unsatisfactory or potentially hazardous level” by reference to Standard 1.6.1 and the Compendium respectively. Regulation 6(3) and reg 8(4) require testing to be carried out in accordance with Standard 1.6.1. Regulation 6(1) declares the microorganisms referred to in section S27-4 of Schedule 27 of the Code to be notifiable contaminants. This creates an operational dependence: changes to the Code or to FSANZ documents will change what the South Australian regulations mean in practice.

Designation of FSANZ as the prescribed body: Regulation 9 prescribes Food Standards Australia New Zealand as the prescribed body for the purposes of s 109(5)(a) of the Act. That establishes an administrative channel for consultation or standards reference back to the Commonwealth agency that drafts and updates the Code. The designation embeds a Commonwealth agency into the South Australian regulatory architecture.

Dynamic incorporation and its legal implications: The regulations’ repeated use of the phrase “as in force from time to time” when importing the Compendium, Schedule 27 and Standard 1.6.1 (reg 3) means that the regulations do not fix technical thresholds statically; instead, they dynamically incorporate future updates to those documents. This raises usual legal effects of dynamic incorporation: the operative legal duties can change without a South Australian statutory amendment; enforcement and compliance risk shift as thresholds or methods are revised at the Commonwealth or FSANZ level.

Interaction with laboratory accreditation and standards regimes: Because the regulations require conformity with Standard 1.6.1 for certain tests, they interact with the broader regulatory and accreditation framework that governs laboratory testing methods and quality assurance. A laboratory’s accreditation status and the standards it uses will affect whether test outcomes are legally sufficient to trigger duties under the regulations.

Limits on regulation and reliance on Act procedure: The regulations do not specify the mechanics of reporting, the timeframe, or penalties; those are located in the Act. Practitioners must therefore consult the Act’s procedural provisions to determine the content of the reporting mechanism, any applicable notice periods, and enforcement consequences. The regulations function as substantive triggers that rely on the Act for the procedural legs of the regime.

Overall, the regulations operate as an instrument that tightly links South Australian public health notification obligations to Commonwealth food‑standards instruments and to the Act’s reporting and enforcement mechanisms, producing a layered regulatory interaction where technical standards come from external codes and statutory enforcement is exercised under the Act.

The regulations contain minimal express amendment history within the text provided. The legislative history section reports the instrument as the South Australian Public Health (Notifiable Contaminants) Regulations 2020, principal regulations No. 25 of 2020. The Gazette reference is 19 March 2020 at page 550, and the commencement notation in the legislative history records that regulation 2 fixed commencement at four months after the day on which they were made, with the principal regulations commencing on 19 July 2020 (Legislative history: Principal regulations 2020 No. 25; Gazette 19.3.2020 p550; commencement 19.7.2020: r 2).

Textual amendment mechanics implied by the instrument: The regulations import external standards “as in force from time to time” (regulation 3). That incorporation method means that numerical thresholds and testing methods can be changed by updates to those external instruments (for example, updates to the Australia New Zealand Food Standards Code, Standard 1.6.1, Schedule 27, or the Compendium) without South Australian subordinate legislation being amended. Legally, the effect is that updates to the Code or Compendium will flow through automatically to change the operational meaning of terms such as “unacceptable microbiological level” and “unsatisfactory or potentially hazardous level”. This is not an amendment to the regulations per se, but it is an operational amendment to the obligations the regulations impose.

No in‑text amendments or schedules: The regulations as provided do not themselves include amendment provisions, savings, transitional provisions or sunset clauses. Regulation 2 establishes commencement timing but no staged implementation. Any future changes to the lists of notifiable organisms or procedural details would require either amendment to these regulations or changes in the external standards where the regulations dynamically incorporate them. The regulation that prescribes FSANZ as the prescribed body (reg 9) will remain until altered by a further subordinate instrument.

Practical consequence for monitoring legal change: Entities subject to the regulations must track two distinct amendment pathways: (1) formal South Australian subordinate‑legislation amendments to these regulations (which would be published in the Gazette and require promulgation under the Subordinate Legislation Act 1978), and (2) updates to the Code, Standard 1.6.1, Schedule 27 or the Compendium, which will change obligations by virtue of dynamic incorporation. The legislative history given shows the original making and commencement dates; it does not record any subsequent amendments.

In short, the regulations were made in 2020 and commenced on 19 July 2020. The instrument’s architecture delegates much of the evolving technical content to external instruments that are incorporated by reference “as in force from time to time”, producing an amendment‑by‑reference dynamic. There are no other amendment entries in the text provided.

The source text contains no judicial decisions, appeals, or reported litigation concerning these regulations. No cases are named in the instrument and no judicial history is recorded in the legislative history section. Consequently there is no statutory litigation history to cite from the text provided.

That absence does not mean disputes cannot arise, or that litigation will not follow. The regulatory structure creates concrete, legally contestable issues that could be subject to administrative review or litigation. The text of the regulations indicates several potential loci of dispute that are anchored in statutory text and technical standards:

• Whether an entity is a “responsible person”: The regulations place duties on a “responsible person” without defining the term; that definition is in the Act. Disputes may arise over whether a given person or entity is the “responsible person” for a particular food item at the relevant time, especially in supply chains with multiple actors (producers, processors, distributors, retailers). The allocation of responsibility in the Act will govern outcomes, but such allocation frequently leads to factual and legal disputes.

• Whether a test result is preliminary/presumptive or confirmatory: The regulations exempt preliminary or presumptive detections from mandatory reporting unless the Chief Public Health Officer requires otherwise (regs 5(4), 8(3)). Differentiating a preliminary test from a confirmatory test may be contentious, particularly where laboratories use rapid screening methods followed by culture or molecular confirmation. Litigation or administrative review could hinge on the definition and status of preliminary tests, and whether the Chief’s direction to require preliminary reporting was lawfully exercised.

• Conformity with Standard 1.6.1 and admissibility of tests: Regulation 6(3) and reg 8(4) require that testing for certain thresholds be carried out in accordance with Standard 1.6.1. Disputes could arise about whether the test method used complied with Standard 1.6.1 in force at the time, whether the laboratory’s methodology was validly applied, or whether procedural errors render the test result legally ineffective as a notification trigger.

• Whether the organism detected falls within the declared lists or referenced Schedule 27: Regulation 6(1) declares the microorganisms “referred to in section S27-4 of Schedule 27 of the Code” to be notifiable. Where the Code’s Schedule identifies organisms by scientific names, strain types, or categories, disputes could arise over taxonomy or strain identification (for example, whether an isolate is properly characterised as a member of a declared species).

• Whether the food is “ready‑to‑eat”: Regulation 7 applies specifically to ready‑to‑eat food, a term defined by reference to Standard 3.2.2 of the Code (reg 3). Disputes over whether a particular product is “ready‑to‑eat” for the purposes of the Code could determine whether the stricter thresholds in reg 7(2) apply.

• The effect of changes in external standards: Because the regulations dynamically incorporate external instruments “as in force from time to time,” litigation could involve questions about which version of a standard applies to a particular test result , the version in force at the time of testing, or another reference point. Parties could litigate whether an amendment to the Code or Compendium has retrospective or prospective effect for notification duties.

• Administrative law challenges to the Chief’s requirements: If the Chief Public Health Officer issues a direction requiring reporting of preliminary results, affected parties may seek judicial review of that direction on administrative law grounds (for example, procedural fairness, reasonableness, or jurisdictional error), depending on the statutory power under which it is exercised.

While none of these points reflects an existing litigation record in the instrument, they identify predictable areas of contestation by reference to the regulation text. Any actual litigation history would be found in court records, reported decisions, or later legislative annotations, none of which appear in the source material provided.

The regulations are concise but contain a number of operational traps for practitioners who do not carefully map the interaction between the regulations, the Act, and external standards. The following non‑exhaustive points are directly grounded in the text and merit attention.

Dynamic incorporation can change obligations without amending the regs: Regulation 3 defines key terms by reference to the Code, Standard 1.6.1, Schedule 27 and the Compendium “as in force from time to time”. Practically, that means a change to Standard 1.6.1, Table 1 of the Compendium, or Schedule 27 will alter what counts as an “unacceptable” or “unsatisfactory or potentially hazardous” level, and thereby change notification duties automatically. Entities that assume the regulations’ obligations are static risk non‑compliance if they do not monitor FSANZ or the Code for updates.

“Responsible person” is not defined in the regulations: The duty to report is repeatedly placed on the “responsible person” (regs 5(3), 6(2), 7(2)). Because the regulations do not define that term, practitioners must consult the Act to determine who must report. Misidentifying the responsible person (for example, confusing the manufacturer with the distributor or retailer) could leave an entity exposed to enforcement for non‑reporting even if another party reports.

Preliminary or presumptive detections are exempt unless the Chief decides otherwise: Regulations 5(4) and 8(3) exempt preliminary or presumptive detections from reporting obligations except where the Chief Public Health Officer requires otherwise. A laboratory or business that treats a rapid screening positive as non‑reportable could be on the wrong side of a Chief’s direction requiring earlier reporting. It is a practical “gotcha” that the Chief can require reporting of presumptive results in specified cases; businesses should have processes to receive and act on any such directions.

Testing methods must conform to Standard 1.6.1: Where thresholds are level‑based, the regulations require testing to be carried out in accordance with Standard 1.6.1 (reg 6(3) and reg 8(4)). Using an alternative accredited method without explicit equivalence may render the test legally ineffective for triggering the reporting duty. This is a technical trap where labs must ensure their methods align with the required standard and that records demonstrate conformity.

Toxins produced by listed pathogens are themselves notifiable contaminants: Regulation 5(2) declares toxins produced by contaminants listed in reg 5(1) to be notifiable. Stakeholders may overlook this because attention often focuses on organisms rather than their toxins; detection of a toxin (for example, botulinum neurotoxin, though specific toxins are not enumerated here) will trigger the reporting duty under reg 5(3).

Third‑party reporting can be triggered by tests of others: Regulation 8(2) prescribes that where a test detects or isolates a notifiable contaminant in food, any person who is aware or suspects a responsible person has not reported must report to the Chief Public Health Officer. This means that suppliers, contract laboratories, local environmental health officers, or customers who receive test results may become obliged to report if they think the responsible person has not done so. Businesses should be aware that non‑reporting by one actor in the supply chain can draw reporting by another.

Ready‑to‑eat classification matters: Regulation 7(2) applies the Compendium thresholds to ready‑to‑eat food only. The legal characterisation of a product as ready‑to‑eat is by reference to Standard 3.2.2 of the Code (reg 3). Misclassifying a product may lead to an incorrect assessment of whether a test result meets the reporting threshold.

No procedural detail in the regulations: The regulations do not set timeframes, forms, or electronic channels for reporting; they refer to the Act for procedural detail. Expect to consult the Act and agency guidance for the mechanics of notification. Assuming a particular form or timeframe absent reference to the Act is a practical error.

Potential versioning disputes: Because tests must be carried out in accordance with Standard 1.6.1 and thresholds are taken from documents that can be updated, disputes can arise about which version of a standard applied at the time of testing. Businesses should record the version of the standard used and the date of testing.

FSANZ is the designated prescribed body: Regulation 9 names FSANZ as the prescribed body for s 109(5)(a) of the Act. Parties seeking to understand the technical basis for thresholds or seeking input from a prescribed body should direct enquiries to FSANZ, not to a different Commonwealth or state agency.

In practice, the main operational gotchas are: (1) failure to monitor the external standards that change obligations; (2) assumptions about who is the “responsible person”; (3) treating preliminary positives as outside reporting risk when the Chief may require earlier notification; and (4) failure to ensure laboratory tests conform to the specified Code standard such that results are legally effective for triggering notification obligations.

Compliance requires aligning organisational procedures with a mix of statutory definitions in the Act, the notifiable contaminant lists and triggers in these regulations, and the technical testing standards incorporated by reference. The steps below are grounded in the regulations’ text and point to practical measures to manage legal risk.

1. Identify whether you are a “responsible person” under the Act, and map responsibilities across the supply chain

• The regulations place reporting duties on the “responsible person” (regs 5(3), 6(2), 7(2)). Consult the South Australian Public Health Act 2011 to determine whether your organisation qualifies as the responsible person for particular food items at particular stages (manufacture, importation, storage, distribution, retail). Document responsibility allocation in contracts and internal SOPs.

2. Review whether your products fall into the categories covered by the regulations

• Check whether your products are “ready‑to‑eat food” as defined by Standard 3.2.2 of the Code (reg 3). If a product is ready‑to‑eat, reg 7 applies; if not, reg 6 or reg 5 may apply depending on the organism. Maintain an up‑to‑date product classification register and legal justification for each classification.

3. Ensure laboratory agreements and in‑house testing use Standard 1.6.1 methods where required

• Regulation 6(3) and reg 8(4) require testing to be carried out in accordance with Standard 1.6.1 of the Code when notification depends on exceeding a numerical threshold. Confirm with your laboratory provider that their methods, accreditation and quality systems comply with Standard 1.6.1 “as in force from time to time”. Include contractual warranties about method conformity, versioning and chain of custody. Record the version of the standard used at the time of testing and preserve raw test data and chain‑of‑custody documentation.

4. Build a test‑result triage flow that distinguishes preliminary/presumptive from confirmatory results

• The regulations exempt preliminary or presumptive detections from mandatory reporting unless the Chief Public Health Officer requires otherwise (regs 5(4), 8(3)). Create a decision tree that defines when a laboratory result is considered presumptive versus confirmatory, who in your organisation is authorised to make that determination, and what steps are triggered in each case (hold product, initiate confirmatory testing, notify regulator if a Chief’s direction exists).

5. Implement reporting procedures keyed to the Act’s mechanics

• While the regulations define what must be reported, the Act provides the mechanism (see the repeated “for the purposes of section 68(1) of the Act” phrasing in regs 5(3), 6(2), 7(2)). Ensure you have procedures to make reports in the form required by the Act, within the Act’s timeframes. Maintain nominated contact persons to receive laboratory notices and to perform statutory notifications to the Chief Public Health Officer. Keep templates for rapid, accurate reporting that capture sample identity, test method and version, numerical result, and chain of custody.

6. Monitor the Code, Standard 1.6.1, Schedule 27 and the Compendium for amendments

• Because the regulations incorporate these documents “as in force from time to time” (reg 3), legal obligations change when the external instruments change. Subscribe to FSANZ and Code update alerts, and incorporate those monitoring obligations into compliance calendars. Update SOPs and lab contracts promptly when threshold or method changes occur.

7. Train staff across the supply chain and maintain supplier contract clauses

• Train procurement, quality, production, distribution and retail staff to recognise notifiable organisms, to understand the difference between preliminary and confirmatory results, and to escalate incidents to the nominated responsible person. Insert clauses in supply, manufacturing and testing contracts that require suppliers and contracted labs to notify you immediately of any test that may trigger a reporting obligation, and to certify that testing methods conform to Standard 1.6.1 where applicable.

8. Maintain records to defend against enforcement action

• Keep records of all test results, method versions, declarations by laboratories whether results are preliminary or confirmatory, correspondence with regulators, and steps taken after receiving a positive or level‑exceeding result. Because the regulations make testing method conformity material to the notification trigger (reg 6(3)), records that show compliance with Standard 1.6.1 will be crucial in any regulatory inquiry.

9. Prepare for third‑party reporting and reputational risk

• Regulation 8 creates obligations for other persons who are aware or suspect non‑reporting by a responsible person to notify the Chief Public Health Officer. Be ready for the possibility that a supplier, customer or independent laboratory report could initiate regulatory scrutiny. Set up incident response protocols that anticipate third‑party notification and that include internal investigations, immediate containment measures, and cooperation with the Chief Public Health Officer.

10. Clarify uncertainties with the Chief Public Health Officer and FSANZ where appropriate

• The regulations give the Chief the power to require reporting of preliminary or presumptive detections (regs 5(4), 8(3)) and designate FSANZ as the prescribed body (reg 9). Where there is uncertainty about whether a test should be reported, whether a product is ready‑to‑eat, or whether a method complies with Standard 1.6.1, seek prompt clarification from the Chief Public Health Officer’s office and, where appropriate, from FSANZ regarding technical interpretation.

11. Consider insurance and commercial contingency planning

• Because reporting can lead to product holds, recalls or public health action, ensure you have commercial contingency plans, recall procedures, insurance coverage for product withdrawal and reputational management. While the regulations do not allocate costs, they create operational triggers that may have material commercial consequences.

12. Audit compliance periodically

• Conduct periodic internal audits to confirm that testing methods, lab contracts, reporting procedures and staff training remain aligned with these regulations and with the Act. Ensure corrective actions are documented and implemented.

In practical terms, compliance is a three‑layer task: identify whether the organism or toxin is within the declared lists (regs 5-7), ensure tests are conducted using the specified Code standard (reg 6(3) and reg 8(4)), and then execute notifications under the Act’s reporting procedure (as referenced throughout). Maintain clear records of authoritative versions of external standards used at the time of testing, and be prepared to respond quickly to Chief Public Health Officer directions that override the preliminary/presumptive reporting carve‑out.