Cricket Farm Staff Training: What Your Team Needs to Know

Inconsistent feeding protocols across staff members are a top-3 cause of FCR variance between bins. That's a concrete, measurable problem with a concrete, manageable solution: training that creates the same behavior from every person who enters your production space.

Cricket farms rely almost entirely on verbal instruction and on-the-job learning for staff training. No resources exist for this. Farms that add staff find that each new employee develops their own interpretation of what "check the bins" means, what "remove uneaten feed" looks like in practice, and what level of mortality warrants reporting.

This guide gives you the training framework that turns those individual interpretations into a shared standard.

TL;DR

• Inconsistent feeding protocols across staff members are a top-3 cause of FCR variance between bins.
• Cricket farms that use documented SOPs in their management software reduce new employee ramp-up time from 3 weeks to 1 week.
• A training program built on written SOPs produces consistent behavior from every employee -- verbal instruction alone degrades with each retelling.
• By end of week 2, a new employee following good SOPs should be able to perform all daily tasks independently with periodic spot-checks.
• Food safety training is mandatory for any employee who handles food-grade production -- cover personal hygiene, allergen awareness, and corrective action procedures.
• The most important SOP to write first is feeding protocol -- it directly controls FCR and is the most commonly performed task by production staff.

2.

• This one change alone can cut FCR variance across staff by 0.2-0.3 points.

3.

• Every mortality event should be logged with bin ID, estimated count, and date.

4.

• When Bin 14's feed intake logs show a sudden drop or spike, you can see it and investigate before it becomes an FCR problem or a mortality event.
• Then they operate independently with daily check-ins for the first 2-3 weeks.
• These records must be kept for a minimum of 2 years.

How does CricketOps help with staff consistency on a cricket farm?

Why Cricket Farm Staff Training Matters

A single farm worker making the wrong call on feeding quantity across 15 bins twice a day produces more FCR variance than almost any other single factor. They're not doing it intentionally. They just weren't told exactly what "right" looks like.

The same applies to mortality reporting. If your protocol is "let me know if something looks bad," different staff members will have different thresholds for what qualifies as worth mentioning. By the time something has gotten bad enough that everyone reports it, you've lost days of potential early intervention.

Good training isn't about micromanagement. It's about creating a shared baseline of what correct looks like, so that your data is reliable and your processes produce consistent results regardless of who's on the floor.

Core Training Topics for Cricket Farm Staff

1. Bin Monitoring and Daily Checks

Every staff member who enters the production space should be able to perform a daily bin check that identifies and records:

Temperature and humidity: How to read and log the sensors in your facility. What the target ranges are. What to do if a reading is outside target (who to notify, what immediate action to take).

Visual cricket health assessment: What healthy, active cricket behavior looks like versus stressed or dying behavior. How to spot the early signs of a disease event (unusual lethargy, crickets on their backs, abnormal clustering).

Substrate and surface condition: Is the paper towel saturated and needs replacing? Are egg flats in good structural condition or collapsing? Is there visible mold?

Hydration source status: Is the water gel fresh or showing signs of bacterial growth? Do vegetable pieces need replacement?

Train this as a physical walkthrough, not a verbal explanation. Walk the new staff member through the production space with you doing the check while narrating. Then have them do it while you observe. Then have them do it alone and compare their notes to yours.

2. Feeding Protocols

Feeding is where the most variance enters your operation, and it's where the most specific training pays off.

Staff need to know:

• Feed type and composition for each life stage in your current protocol
• Quantity per bin (give specific numbers or measurements, not "a handful" or "about this much")
• Feeding timing (morning, evening, or both? What hours?)
• How to assess whether previous feeding has been consumed (what to look for in the bin before adding more)
• What to do with uneaten feed (remove it? Leave it? Document the quantity?)

Create a printed feeding protocol card for each life stage category in your facility. It should have: feed type, quantity in measurable units (tablespoons, grams), frequency, timing, and what to document. Post this near your feed storage area.

Pre-measured portions by life stage dramatically reduce feeding variability. If you set up daily feeding allotments in labeled containers, the staff member is distributing a measured amount rather than making a quantity judgment. This one change alone can cut FCR variance across staff by 0.2-0.3 points.

3. Mortality Reporting

Train your staff to report mortality by bin, with an estimated count, every day. Not "some died" but "Bin 14, adult stage, approximately 20 dead crickets."

Create a clear reporting threshold: Any bin where the daily dead count exceeds [your baseline plus 50%] should be flagged immediately, not at end of shift. If your bins average 5-10 deaths per day and a staff member finds 40, that's an immediate notification, not a footnote in the daily log.

Remove dead crickets daily. Train staff that this is a daily task, not optional. Accumulating dead crickets increases pathogen load and makes accurate mortality tracking impossible.

Log it, don't just handle it. A dead cricket removed from a bin without documentation means your records don't reflect what actually happened. Every mortality event should be logged with bin ID, estimated count, and date.

4. Food Safety Documentation

For food-grade operations, food safety training is a compliance requirement, not optional. Under FSMA Preventive Controls for Human Food, your training records are part of your required documentation.

Staff who handle crickets destined for human food production need training in:

• Personal hygiene: Handwashing protocols before and after bin contact, hair covering, avoiding cross-contamination behaviors
• Allergen awareness: Cricket protein is a cross-reactive allergen with shellfish. Staff handling cricket products should understand this and follow your cross-contamination prevention protocols.
• Foreign object prevention: No loose jewelry, no unsealed food in the production area, no glass containers near production
• Illness reporting: Staff who are ill should not handle food-contact insects. Train the specific illnesses that require exclusion.
• Record completion: What forms need to be filled out, when, and how specifically

Document your training. For each staff member, keep a record of: which training topics they received, the date of training, and who delivered it. This is a required record under FSMA.

5. Equipment Use and Safety

Train staff on every piece of equipment they'll use:

• How to operate and clean sifting screens and harvest equipment
• Safe handling of bleach and sanitizing solutions (mixing ratios, ventilation requirements, personal protective equipment)
• How to handle and replace temperature/humidity sensors
• Electrical safety around any heat equipment
• Lifting procedures for full bins (bins with 500+ adult crickets weigh more than expected)

How CricketOps Helps with Staff Consistency

When your team logs daily data in a consistent format through a shared platform, it removes the interpretation layer that creates inconsistency. The fields tell the staff member exactly what to record. The system makes their inputs visible to you in real time.

This doesn't replace training. But it does create a structure that makes consistent execution easier for trained staff and makes deviations visible to you faster. When Bin 14's feed intake logs show a sudden drop or spike, you can see it and investigate before it becomes an FCR problem or a mortality event.

The cricket farm management platform is built around exactly this kind of daily workflow logging that supports consistent team execution. And for the record-keeping side of compliance, the cricket farm record-keeping guide maps each training documentation requirement to the business outcomes it supports.

FAQ

How do I train new employees on a cricket farm?

Start with a structured observation period where the new employee follows an experienced person through daily rounds while you narrate every decision and task. Then reverse it: they do the rounds while you observe and correct. Then they operate independently with daily check-ins for the first 2-3 weeks. Back everything with written protocols (feeding quantity, daily check criteria, mortality reporting thresholds) they can reference when uncertain. Don't rely on verbal instruction alone.

What food safety training do cricket farm staff need?

At minimum: personal hygiene protocols (handwashing, hair covering), allergen awareness (cricket's shellfish cross-reactivity), foreign object prevention practices, illness exclusion rules for food handlers, and correct completion of your required food safety records. For operations registered as FDA food facilities under FSMA, training must be documented with records showing who was trained, on what topics, and when. These records must be kept for a minimum of 2 years.

How does CricketOps help with staff consistency on a cricket farm?

CricketOps provides a structured daily logging workflow where staff record specific fields (bin ID, feed amount, mortality count, temperature, notes) in a consistent format. This removes the interpretation variance that creates FCR differences between staff members. It also makes deviations from baseline visible to farm managers in real time, so problems that might otherwise go unreported for days can be caught and addressed within hours.

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)

Consistency Is a System, Not a Standard

You can tell your staff to be consistent. Or you can build systems that make consistency the path of least resistance. The second approach works better.

Written protocols, pre-measured inputs, structured logging, and daily observation during onboarding aren't bureaucracy. They're the infrastructure of a farm that produces the same results regardless of who's on the floor that day.

Build that infrastructure. Document your training. And treat consistent execution as an operational output you can measure, not just a cultural value you espouse.

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.