When to Reanalyze Your Cricket Flour Food Safety Plan

FSMA requires a full reanalysis of a food safety plan whenever significant changes are made to the production process. That requirement means your food safety plan isn't a one-time document - it's a living system that needs to be revisited when your operation changes. The reanalysis requirement is the least-known FSMA obligation for small food producers, and it's one where non-compliance creates real risk: a facility that's changed its products or processes without updating its food safety plan has a plan that doesn't match reality.

This guide explains what triggers a reanalysis, what the mandatory 3-year review requires, and how CricketOps supports the process.

TL;DR

• The 3-year clock runs from the date the plan was initially validated or last reanalyzed.
• In practice, most active cricket flour operations should expect to conduct some form of reanalysis more frequently than every 3 years due to operational changes.
• The 3-year mandatory reanalysis due date is tracked as a calendar item with reminders.
• FSMA requires a full reanalysis of a food safety plan whenever significant changes are made to the production process.
• That requirement means your food safety plan isn't a one-time document - it's a living system that needs to be revisited when your operation changes.
• For a triggered reanalysis, you may only need to reanalyze the portion affected by the triggering change.
• The reanalysis should be conducted by your PCQI (Preventive Controls Qualified Individual) or with their active participation.

The Two Types of Reanalysis Requirements

Mandatory 3-year reanalysis: FSMA requires that all covered facilities complete a full reanalysis of their food safety plan at least every 3 years. The 3-year clock runs from the date the plan was initially validated or last reanalyzed. Put the 3-year date in your calendar and set a reminder 3 months before it arrives - you'll need time to do it properly.

Triggered reanalysis: A reanalysis must also be completed whenever certain events occur, regardless of when the last scheduled reanalysis happened. These triggers apply immediately to the affected portion of the plan.

Triggered Reanalysis Events

Under 21 CFR Part 117.170, a reanalysis is required when:

New hazard information: If new scientific literature, FDA guidance, or industry data identifies a hazard relevant to your product or process that you haven't previously addressed, you need to reanalyze your hazard analysis and potentially update your preventive controls. For cricket flour, this could include new research on allergen cross-reactivity, new findings on insect-specific pathogens, or FDA guidance updates on insect protein.

Changes to your operation:

• Adding a new product (different cricket species, new processing method, new use application)
• New or modified equipment that affects a CCP or preventive control
• Changes in suppliers that affect your supply chain verification
• New facility, significant facility renovation, or new production area
• Changes in production volume that affect your sanitation or temperature control controls
• New distribution channel that changes who consumes your product (for example, entering a foodservice channel where your product may be consumed by immunocompromised individuals)

A corrective action that reveals a systemic problem: If you implement a corrective action for a deviation and the investigation reveals that the underlying cause represents a broader flaw in your food safety plan - not just a one-time equipment failure - you need to reanalyze the affected portion of the plan.

An unexplained food safety event: A recall, illness complaint linked to your product, or positive pathogen test result that can't be explained by your existing hazard analysis triggers a reanalysis.

FDA or third-party audit findings: If an FDA inspection or buyer audit identifies a food safety concern that your plan doesn't address, that's a reanalysis trigger for the relevant portion of the plan.

What Reanalysis Involves

A reanalysis reviews your current food safety plan - the hazard analysis, preventive controls, and monitoring procedures - and assesses whether they are still appropriate for your current operation. It's not necessarily a complete rebuild of the plan. For a triggered reanalysis, you may only need to reanalyze the portion affected by the triggering change.

The reanalysis should be conducted by your PCQI (Preventive Controls Qualified Individual) or with their active participation. Document the reanalysis process: what was reviewed, what changes were identified, and what updates were made to the plan.

If your reanalysis concludes that no changes to the plan are needed, document that conclusion too. "We reviewed the plan following the addition of a new packaging supplier and concluded that the existing supply chain verification procedures adequately address the hazards presented by this supplier" is a valid reanalysis conclusion - but you need to write it down.

Reanalysis Documentation

For each reanalysis (scheduled or triggered), maintain:

• The date the reanalysis was initiated and completed
• The trigger (scheduled 3-year review, specific change, or event)
• What was reviewed
• What changes were identified and made
• Who conducted the reanalysis (PCQI name and qualification)
• Sign-off on the completed updated plan

CricketOps maintains a change log and plan version history that documents when the food safety plan was modified, what changed, and who reviewed it. This makes it easy to demonstrate the reanalysis history during an FDA inspection without searching through document version histories.

For your food safety plan foundation, see cricket farm food safety plan. For your overall FDA compliance program, see cricket flour FDA compliance.

Frequently Asked Questions

What triggers a food safety plan reanalysis for a cricket flour facility?

A food safety plan reanalysis is triggered by any of the following: a scheduled 3-year review (required for all covered facilities under FSMA), a new or modified product, new or modified production equipment, new scientific evidence about hazards relevant to your product, a corrective action that reveals a systemic flaw in your plan, an unexplained food safety event (recall, illness complaint, positive pathogen test), or FDA/audit findings identifying unaddressed hazards. You're also required to reanalyze when you change your distribution or significantly change your customer base in ways that affect who consumes your product. Any of these events triggers a reanalysis of the affected portions of the plan.

How often do I need to reanalyze my HACCP plan under FSMA?

FSMA requires a mandatory full reanalysis at least every 3 years for covered facilities. This is on top of triggered reanalyses required whenever specific events occur - new products, changed processes, new hazard information, corrective action revelations, or food safety events. In practice, most active cricket flour operations should expect to conduct some form of reanalysis more frequently than every 3 years due to operational changes. Any time you materially change your production process, add a product, or change suppliers for a critical input, review the relevant section of your food safety plan. A brief review and documented conclusion takes less time than an unplanned FDA inspection finding.

How does CricketOps support the food safety plan reanalysis process?

CricketOps maintains a food safety plan version history that records when each section of the plan was last reviewed and modified. The change log feature tracks what changed, when, and who reviewed it. When a reanalysis trigger occurs (entered into CricketOps as a corrective action, a new product setup, or a supplier change), the system prompts a food safety plan review task for the affected section. The 3-year mandatory reanalysis due date is tracked as a calendar item with reminders. After reanalysis, updating the plan in CricketOps creates a new version with a date-stamped record of what changed - the documentation that FDA inspectors look for when they ask "when did you last review your food safety plan?"

How does CricketOps help track the metrics described in this article?

CricketOps provides bin-level logging for the variables that drive production outcomes -- feed inputs, environmental conditions, mortality events, and harvest results. Rather than maintaining these records in separate spreadsheets, you can view performance trends across bins and over time to identify which operational variables correlate with better outcomes in your specific facility.

Where can I find industry benchmarks to compare my operation's performance?

The North American Coalition for Insect Agriculture (NACIA) publishes periodic industry reports with production benchmarks. University extension programs in agricultural states, including the University of Georgia and University of Florida IFAS, occasionally publish insect farming production data. Industry conferences hosted by the Entomological Society of America and the Insects to Feed the World symposium series are additional sources of peer benchmarking data.

What is the biggest operational mistake cricket farmers make in their first year?

Expanding bin count before achieving consistent FCR and mortality targets in existing bins is the most common and costly first-year mistake. At 5-10 bins, problems are manageable. At 30-50 bins, the same proportional problems represent much larger financial losses. Most experienced cricket farmers recommend holding expansion until you have three consecutive production cycles hitting your FCR and mortality targets.

Sources

• Food and Agriculture Organization of the United Nations (FAO) -- Edible Insects: Future Prospects for Food and Feed Security
• North American Coalition for Insect Agriculture (NACIA)
• Entomological Society of America
• University of Georgia Cooperative Extension
• Journal of Insects as Food and Feed (Wageningen Academic Publishers)

Get Started with CricketOps

The practices covered in this article are easier to apply consistently when they are supported by organized production data. CricketOps gives cricket farmers the tools to track what matters -- by bin, by batch, and over time. Start your next production cycle in CricketOps and see how organized data changes the way you manage your operation.