FDA Pest Management

FDA / FSMA wants a written food safety plan with pest control inside it — for every Australian food site exporting to the US. 21 CFR 117 Preventive Controls. The pest pre-requisite, the sanitation programme, the trained operator, the records.

FDA pest management for Australian food sites exporting to the US — FSMA Preventive Controls (21 CFR 117) frame, written food safety plan with pest pre-requisite, GMP and sanitation programme integration. Pest IT supports the QA manager translating FSMA to working programme on the day.

FDA — the United States Food and Drug Administration — administers food safety for the US market through the Food Safety Modernization Act (FSMA), with the working specifications codified across the FSMA rules: Preventive Controls for Human Food (21 CFR 117), Preventive Controls for Animal Food (21 CFR 507), Foreign Supplier Verification Programs (FSVP), Produce Safety Rule (21 CFR 112), and others. For Australian food sites exporting to the US, the FSMA frame applies — directly through the export buyer's foreign-supplier verification, indirectly through the buyer's audit programme, and structurally through the SQF / BRC / HACCP regime stack many Australian food sites already run. FSMA does not require Australian sites to be US-FDA-registered as a manufacturer per se in every case; the export buyer's compliance frame is what reads.

What FSMA Preventive Controls asks of pest management specifically: a written food safety plan that includes pest control as part of the sanitation programme (Current Good Manufacturing Practice, Hazard Analysis and Risk-Based Preventive Controls); written pest control procedures naming the contractor or trained competent person, the pesticide application records, the monitoring frequency, the corrective action sequence, and the verification record; trained operator evidence; and records that read at FDA inspection or at foreign-supplier verification audit. The depth FSMA asks for resembles BRC clause 4.14 in component-specification but reads inside the broader written food safety plan rather than as a stand-alone clause.

Pest IT supplies the systems, the consumables, the documentation patterns, and the design support behind an FSMA-aligned pest control programme for Australian export-context food sites. The Food and Processing Catalogue carries the export-context rollout pattern; the Insect Monitoring Systems Range carries the continuous-monitoring layer the FSMA sanitation programme reads from; The Pestie's FDA Compliance Pack carries the FSMA-aligned documentation set; the SQF Pest Management page is the natural cross-reference for sites running SQF-and-FSMA together. Knowledge Hub FSMA training carries the export-context walkthrough; the Free Design Service specs the pest pre-requisite with the venue, the export buyer's QA team, and the supply-chain frame on contract install.

The pestie translating the regime to the evidence pack

You are the QA manager at an Australian food site exporting to the US, or the trade pestie holding the export-context contract. The export buyer's QA team has named FSMA Preventive Controls in the supplier agreement; the foreign-supplier verification audit is on the calendar, or the buyer's third-party audit references FSMA frame against your pest control programme. FSMA 21 CFR 117 Preventive Controls for Human Food (current at May 2026 — published 2015 with amendments through the FDA's published amendment cycle) is the canonical specification reading. You are not a US site — you do not register under FDA's domestic food facility registration as a US manufacturer in most export cases — but the buyer's audit programme reads against FSMA frame, and your written food safety plan must hold the line. The pest control programme sits inside the plan as part of the sanitation pre-requisite. The pestie's day is the regime translator on the export side — reading the export buyer's contract, running the programme that satisfies FSMA's expectations, generating the evidence the buyer's QA audit reads, writing the report the export buyer's auditor accepts. Pest IT supplies the rodent monitoring layer (the MinkPolice signature digital monitoring range generates the timestamped alarm-trail evidence the FSMA monitoring frequency reads from), supplies the continuous-monitoring fly layer (the Viper signature UV fly unit range carries the FSMA sanitation programme catch-count log), supplies the IPM frame across the export-context pest list, and supplies the documentation pattern that reads at FSMA-and-SQF audit at one venue.

Compliance note

FSMA 21 CFR 117 Preventive Controls for Human Food (current at May 2026) is the canonical pest-control specification reading inside the FSMA rule set. Pest IT supports FSMA-aligned pest control through systems and documentation patterns that satisfy the written food safety plan's pest pre-requisite — never claiming FSMA certification, which is conferred (where conferred) by FDA inspection or by the foreign-supplier verification process. FSMA rules amend on the FDA's published amendment cycle; the Compliance Regime Update Log carries the version history. Most Australian food sites running FSMA against export buyers also audit against SQF, BRC, or HACCP — the Compliance Regime Cross-Reference Map carries the regime overlap pattern. Pest IT supplies the rodent monitoring layer through the MinkPolice signature range, the continuous-monitoring fly layer through the Viper signature range, and the IPM frame through the Insect Monitoring Systems Range and the Pest IT Free Design Service.

Specs the evidence pack with you

Pest IT specs the FSMA-aligned pest control programme with you when the export buyer's audit programme is named, when the supplier agreement references FSMA frame, or when the FSMA stack-up overlaps SQF and BRC and HACCP at one Australian export site. Knowledge Hub FSMA training carries the export-context walkthrough; the Free Design Service maps the written food safety plan's pest pre-requisite, the sanitation programme integration, the trained operator evidence, the monitoring frequency, the trend-analysis layout, and the corrective-action template against your venue, your export buyer's audit calendar, and your existing SQF / BRC / HACCP frame. Specialist consult — bring the export buyer's contract, the existing food safety plan, and the recent buyer-audit observation history; we walk through the gap analysis together.

The cluster's named resource pack

The Pestie's FDA Compliance Pack (scaffolded; content build pending) carries the FSMA-aligned working documentation set: the written food safety plan pest pre-requisite template, the sanitation programme integration reference, the trained operator records format, the monitoring frequency schedule, the pesticide application records template, the corrective-action log format, and the FSMA / SQF / BRC / HACCP cross-regime mapping. Pest IT supplies the systems behind every component — the MinkPolice signature digital monitoring range generates the timestamped alarm-trail evidence the FSMA monitoring frequency reads, the Viper signature UV fly unit range generates the catch-count log the sanitation programme reads, the Insect Monitoring Systems Range carries the kit-and-rotation context. When the FDA Annual FSMA Pack ships — Contextual Persona Annual archetype — it sits at the front of the evidence-tools grid.

Frequently asked questions

What does FSMA require of pest management for an Australian export site?

FSMA 21 CFR 117 Preventive Controls for Human Food (current at May 2026) requires the food site to maintain a written food safety plan that includes pest control inside the sanitation programme. The written plan must cover: the pest control procedure, the contractor or trained competent person, the pesticide application records, the monitoring frequency, the corrective action sequence, and the verification record. For an Australian export site, the buyer's foreign-supplier verification audit reads against FSMA frame; many buyers also audit against SQF or BRC, which read against equivalent components. The Pestie's FDA Compliance Pack carries the FSMA-aligned documentation template.

Does an Australian site need US FDA registration to export to the US?

In most cases, an Australian food site exporting to the US does not register directly under FDA's domestic food facility registration as a US manufacturer; FDA registration of food facilities applies primarily to facilities located in the US. The exporting site is foreign-supplier-verified through the US importer's FSVP (Foreign Supplier Verification Programs) under 21 CFR 1, Subpart L. The buyer's QA team typically conducts the foreign-supplier verification through documentation review and on-site audit; the buyer's third-party audit programme often references FSMA frame against the supplier's pest control programme. Where direct FDA inspection occurs, the site's compliance against FSMA frame becomes immediate. The Pest IT Free Design Service walks the export-context audit pattern with the venue and the buyer's QA team on contract install.

How does FSMA differ from BRC clause 4.14?

FSMA Preventive Controls reads inside the written food safety plan as the pest control component of the sanitation pre-requisite; BRC clause 4.14 reads as a stand-alone clause-grounded specification of the pest management programme. The component overlap is high — both regimes reference contractor or trained competent person, monitoring frequency, trend or pattern analysis (FSMA does not name 'trend analysis' as explicitly as BRC clause 4.14 does, but the analogous pattern reads through the sanitation-programme verification component), corrective action, and verification. The audit moment differs — FSMA inspections (where they occur) read the written food safety plan as a whole; BRC audits read clause 4.14 specifically. Many Australian export sites run both at one venue; the Compliance Regime Cross-Reference Map carries the overlap pattern.

What pesticide application records does FSMA accept?

FSMA's pesticide application record requirement reads against the broader written food safety plan record-keeping specification at 21 CFR 117 Subpart A. A typical pesticide application record reads: the date and time, the operator (named, with training reference), the pesticide product (registered name, EPA registration number where US-registered, APVMA registration number for Australian-registered alternatives, MSDS / SDS reference), the application location (zone, station map), the application method, the rate / dose, the corrective-action trigger that prompted the application, and the post-application verification. The record reads at FDA inspection (where it occurs), at FSVP audit, and at any third-party audit referencing FSMA frame. The Pest IT Free Design Service walks the pesticide application record template with the operator on contract install.

What does an FSMA trained operator look like?

FSMA Preventive Controls 21 CFR 117 requires a Preventive Controls Qualified Individual (PCQI) for some elements of the food safety plan; the PCQI is not specifically a pest control operator role but the food safety plan's qualified individual responsible for the plan's hazard analysis and preventive controls. For pest control specifically, FSMA reads against the broader sanitation programme and CGMP frame — the operator (in-house or contractor) must be trained, competent, and documented. The training reference reads against US-recognised training programmes (Purdue / NPMA / state-licensed), against industry-recognised Australian training, or against the Killgerm signature Approved Contractor frame Pest IT operates under. The Pestie's FDA Compliance Pack carries the trained-operator documentation pattern.

What's in the Pestie's FDA Compliance Pack?

The Pestie's FDA Compliance Pack (scaffolded; content build pending) carries the FSMA-aligned working documentation set: the written food safety plan pest pre-requisite template, the sanitation programme integration reference, the trained operator records format, the monitoring frequency schedule, the pesticide application records template, the corrective-action log format, the FSMA / SQF / BRC / HACCP cross-regime mapping, the foreign-supplier verification audit-prep checklist, and the export-buyer-handover summary. The pack reads against FSMA-context audits and at SQF / BRC stack-ups. The Free Design Service walks the documentation set against the export buyer's audit calendar on contract install.

FDA pest management for Australian export sites in depth

FDA — the US Food and Drug Administration — administers food safety for the US market through the Food Safety Modernization Act (FSMA), enacted 2011, with the working specifications codified across the FSMA rules: Preventive Controls for Human Food (21 CFR 117), Preventive Controls for Animal Food (21 CFR 507), Foreign Supplier Verification Programs (FSVP), Produce Safety Rule (21 CFR 112), Sanitary Transportation Rule, Intentional Adulteration, and others. For Australian food sites in the Pest IT operating context, FSMA applies through the export pathway — the US importer runs FSVP against the foreign supplier; the supplier audit programme references FSMA frame; many US importers' QA programmes audit against FSMA-aligned third-party schemes (SQF and BRC are GFSI-recognised and FSMA-aligned).

FSMA 21 CFR 117 Preventive Controls for Human Food (current at May 2026) requires the food facility to develop and maintain a written food safety plan covering hazard analysis, preventive controls, and the sanitation programme. Pest control sits inside the sanitation programme as a Current Good Manufacturing Practice (CGMP) component; the written plan covers pest control procedure, contractor or trained competent person, pesticide application records, monitoring frequency, corrective action, and verification. The written plan is the working programme document; the records read at FDA inspection (where applicable), at FSVP audit, and at any third-party audit referencing FSMA frame.

The evidence catalogue Australian export sites maintain against FSMA-context audits clusters around five record families. Written food safety plan: the plan document with pest control inside the sanitation programme. Monitoring records: dated, signed inspection logs supplemented by continuous digital monitoring (MinkPolice signature digital rodent sensor alarm trail) and continuous fly catch-count (Viper signature UV fly unit catch log). Pesticide application records: per-application detailed record with operator, product, location, method, dose, corrective-action trigger, post-application verification. Trained operator records: training reference, qualification evidence, supervisory frame. Verification records: programme review, sanitation-programme effectiveness check, corrective action verification. Pest IT supplies the systems generating every record family; the Pestie's FDA Compliance Pack carries the documentation patterns.

The Insect Monitoring Systems Range carries the continuous-monitoring kit-and-rotation context. The Rodent Control Range carries the rodent monitoring kit and the MinkPolice signature digital monitoring range. The Bed Bug & Heat Treatment Systems Range carries response work where export sites have hospitality-adjacent food-and-bev exposure. The Pestie's FDA Compliance Pack carries the FSMA-specific documentation. Knowledge Hub FSMA training carries the export-context walkthrough.

Most Australian export sites running FSMA against US buyers are also SQF, BRC, or HACCP. The Compliance Regime Cross-Reference Map carries the regime overlap pattern in one table — where FSMA aligns with SQF Element 11.2.13, where it aligns with BRC clause 4.14, where the regimes diverge, and where a single working programme reads at multiple audits. The SQF Pest Management page covers Edition 9 Element 11.2.13 in IPM-frame detail; the BRC Pest Management page covers BRCGS Issue 9 clause 4.14 in component-specification detail; the HACCP Pest Management page covers the principles-based foundation; the Codex Alimentarius and Pest Management page carries the international frame.

Pest IT supplies the systems, the consumables, the documentation patterns, and the design support behind an FSMA-aligned pest control programme for Australian export-context food sites. The supports-compliance frame is non-negotiable: Pest IT does not certify FSMA and does not issue audit pass; the FDA's inspection process or the export buyer's foreign-supplier verification audit issues the audit ruling. What Pest IT does is supply the working programme that satisfies FSMA's pest pre-requisite components and generates the evidence the buyer's QA team accepts. The MinkPolice signature digital monitoring range, the Viper signature UV fly unit range, and the Killgerm signature Approved Contractor frame each carry the brand-affirmation weight where the evidence-generation pattern matches the regime. When FSMA rules amend, the Compliance Regime Update Log records the change.

Resources for this regime

Four resources accompany this page: the Pestie's FDA Compliance Pack (the cluster's named regime-specific resource pack tailored to FSMA 21 CFR 117), the Compliance Regime Cross-Reference Map, the Compliance Audit Evidence Reference Library, and the Compliance Regime Update Log. All four are scaffolded with URLs populated; content builds are pending.

Evidence-generating tools for this regime

The Pest IT systems generating FSMA audit-grade evidence cluster around four anchors. The MinkPolice rodent sensor signature range generates the timestamped digital alarm trail FSMA monitoring frequency reads. The Viper UV fly unit signature range generates the continuous catch-count log FSMA sanitation programme reads. The Pestie's FDA Compliance Pack documentation set translates 21 CFR 117 to working programme. The Insect Monitoring Systems Range carries the kit-and-rotation context behind continuous monitoring evidence. When the FDA Annual FSMA Pack ships, it sits at the front of this grid.