Cricket Farm Cleaning and Sanitation Log: Documentation for FDA Compliance
FDA expects sanitation records to document the date, area cleaned, sanitizer used, concentration, and staff initials. A cleaning log that records "bins cleaned" without specifying which bins, which sanitizer, what concentration, and who did it isn't a FSMA-compliant sanitation record. The details matter because they're what allow an auditor to evaluate whether your sanitation program is actually being executed as specified.
Sanitation records serve two purposes: they document that your cleaning is happening, and they create accountability for the specific parameters (sanitizer type, concentration, contact time) that make cleaning effective. The log template below captures all required fields and can be adapted for paper or digital use.
TL;DR
- Quaternary ammonium (Quat) sanitizers: 200-400 ppm effective range for most applications
- Chlorine-based sanitizers: 100-200 ppm for food contact surface sanitization
- Peroxyacetic acid (PAA): 100-200 ppm for most food contact surfaces
- File cleaning logs by week and retain for a minimum of 2 years
- Most FDA food safety inspections review at least 12 months of records; have 24 months accessible
- Entries are automatically timestamped and retained for the FSMA 2-year period
- Quaternary ammonium (Quat) sanitizers: 200-400 ppm effective range for most applications
Quaternary ammonium (Quat) sanitizers: 200-400 ppm effective range for most applications.
- Test with Quat test strips (available from food safety suppliers) and record the tested concentration.
Chlorine-based sanitizers: 100-200 ppm for food contact surface sanitization.
- Test with chlorine test strips and record the result.
Peroxyacetic acid (PAA): 100-200 ppm for most food contact surfaces.
- A Fail means the area was re-cleaned before production continued, which should also be documented.
Filing and Retention
File cleaning logs by week and retain for a minimum of 2 years.
- Most FDA food safety inspections review at least 12 months of records; have 24 months accessible.
- Entries are automatically timestamped and retained for the FSMA 2-year period.
- FDA expects sanitation records to document the date, area cleaned, sanitizer used, concentration, and staff initials.
Cleaning and Sanitation Log Template
CRICKET FARM CLEANING AND SANITATION LOG
Facility Name: _______________________
Week of: ___________________
| Date | Area / Equipment Cleaned | Sanitizer Used | Concentration | Method | Duration | Post-Clean Inspection (Pass/Fail) | Staff Initials |
|------|--------------------------|----------------|---------------|--------|----------|------------------------------------|----------------|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
Notes / Corrective Actions:
______________________________________________________
Supervisor Review: ___________________ Date: ___________
Cleaning Frequency Requirements by Area
Your FSMA food safety plan and GMP requirements specify the cleaning frequency for each area of your facility. Common minimum frequencies for cricket flour facilities:
Food contact surfaces (equipment that touches cricket flour):
- Dryer surfaces: After each production run
- Milling equipment: After each production run, or at minimum daily during production
- Sieving equipment: After each production run
- Packaging equipment food contact zones: Daily during production
Cricket production bins:
- Between each production cycle (before restocking with new crickets)
- Any bin with confirmed disease or pathogen issue: Immediate deep cleaning before any contact with other production
Non-food contact surfaces:
- Processing room floors and walls: Daily during production
- Storage area floors: Weekly minimum
- Break areas: Daily
External surfaces:
- Production room doors, handles, switches: Daily during production
- Loading dock areas: Weekly
Sanitizer Concentration Documentation
Your sanitation log must record the actual concentration used, not just the sanitizer name. Sanitizers have effective ranges; too dilute means insufficient pathogen kill, too concentrated means potential product contamination and surface damage.
Common sanitizers and their effective ranges for food processing:
Quaternary ammonium (Quat) sanitizers: 200-400 ppm effective range for most applications. Test with Quat test strips (available from food safety suppliers) and record the tested concentration.
Chlorine-based sanitizers: 100-200 ppm for food contact surface sanitization. Test with chlorine test strips and record the result.
Peroxyacetic acid (PAA): 100-200 ppm for most food contact surfaces. Use PAA test strips.
Hydrogen peroxide-based: Follow manufacturer's label instructions; concentrations vary by product.
Always use test strips or a titration kit to verify concentration rather than calculating it from dilution alone. Record the verified concentration on the log.
Post-Cleaning Inspection
The post-clean inspection column in the log records whether you visually confirmed the area or equipment is clean before resuming production. This is the verification step of your sanitation program.
A post-clean inspection for food contact equipment should include:
- Visual check for visible residue or debris
- Check that all sanitizer residue has been rinsed (where required by your protocol)
- Confirmation that equipment is reassembled correctly for production
For bins being returned to service after cleaning between cycles:
- No visible debris from prior occupants
- Sanitizer has been applied at the required concentration and contact time
- Bin is dry (or appropriate for your restocking protocol)
Record the result as Pass or Fail. A Fail means the area was re-cleaned before production continued, which should also be documented.
Filing and Retention
File cleaning logs by week and retain for a minimum of 2 years. Most FDA food safety inspections review at least 12 months of records; have 24 months accessible.
In CricketOps, cleaning log entries are stored with automatic timestamps and linked to your cricket farm cleaning sanitation guide SOPs. For paper logs, file in a labeled binder organized by month.
Frequently Asked Questions
What sanitation records must I keep for my cricket flour facility?
FSMA GMP requirements (21 CFR Part 117, Subpart B) require that you maintain records of your sanitation activities for food contact surfaces. At minimum, your records must show the date, the surface or equipment cleaned, the sanitizer type and concentration used, and the identity of the person who performed the cleaning. Additionally, if sanitation is a preventive control in your food safety plan (rather than just a GMP requirement), the monitoring records must also include verification that the sanitizer was applied correctly. Retain all sanitation records for a minimum of 2 years from the date of creation.
How often must I document cleaning in a cricket flour processing area?
Document cleaning of food contact surfaces every time cleaning occurs, which for active production should be at minimum daily and after each production run. Food contact surfaces (dryer surfaces, milling equipment, sieving screens, packaging equipment) must be cleaned between production runs and documented each time. Non-food contact surfaces (floors, walls, non-contact equipment surfaces) should be cleaned weekly minimum and documented per your cleaning schedule. Your written sanitation standard operating procedure (SSOP) specifies the required frequency for each area; your log should show cleaning events at least as frequently as your SSOP requires.
Does CricketOps include a sanitation log template?
CricketOps includes a sanitation log module that allows you to record cleaning events with all required fields: date, area or equipment, sanitizer type and concentration, staff initials, and post-clean inspection result. Entries are automatically timestamped and retained for the FSMA 2-year period. Your cleaning log records are accessible alongside your temperature logs, corrective action logs, and other compliance records in a single dashboard, making audit preparation faster than managing separate paper files. You can also set recurring reminders for scheduled cleaning events to prompt staff to complete and log required sanitation activities on schedule.
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.