Cricket Farm KPI Review Meeting: Running a 30-Minute Weekly Ops Meeting

Farms that hold weekly KPI reviews improve FCR performance by an average of 10% in the first 90 days. That improvement happens because weekly reviews create visibility into what's working and what isn't before problems become expensive. When your team looks at mortality rates and FCR numbers together every week, they notice when a bin cluster is underperforming and investigate before it becomes a crop loss.

Most cricket farm operators review performance data occasionally, after a problem is already visible in revenue or inventory. A structured weekly review moves that analysis earlier in the timeline, when there's still time to intervene. It also creates a shared performance context for everyone on the team, so workers understand how their daily actions connect to farm outcomes.

TL;DR

• Farms that hold weekly KPI reviews improve FCR performance by an average of 10% in the first 90 days
• An FCR deviation that no one investigated during the week gets a 10-minute root cause discussion
• Spend 7 minutes reviewing the upcoming harvest schedule and confirming production readiness
• Spend 5 minutes reviewing last week's commitments and capturing this week's commitments
• For a 2-5 person team, everyone who touches production should be in the weekly review
• Let's look at temperature calibration on bins 8-12 before Thursday" is an accountable commitment
• Keep it 30 minutes, structured around the same agenda every week

Duration: 30 minutes.

• Everyone looks at the numbers together.

Minutes 5-15: Drill into what moved

Focus your attention on anything that changed significantly from the prior week.

• An FCR deviation that no one investigated during the week gets a 10-minute root cause discussion.
• Spend 7 minutes reviewing the upcoming harvest schedule and confirming production readiness.
• Spend 5 minutes reviewing last week's commitments and capturing this week's commitments.
• That improvement happens because weekly reviews create visibility into what's working and what isn't before problems become expensive.

Who Should Attend and When to Meet

For a 2-5 person team, everyone who touches production should be in the weekly review. For larger teams, the production lead plus any role with decision-making authority over operations. The meeting doesn't need to be long, and it doesn't need to be formal. What it needs to be is consistent.

Day and time: Monday morning works for most farms because you're reviewing the prior week's data and setting the current week's focus. Avoid Friday afternoons (attention is elsewhere) and daily-shift-change times (too much else is happening).

Duration: 30 minutes. If it runs longer, the meeting has scope creep. Identify the cause and cut it.

Location: At the farm, in front of the monitor or tablet showing your CricketOps dashboard. The data should be visible during the meeting, not described from memory.

The 30-Minute Agenda

Minutes 1-5: Weekly headline numbers

Pull up your cricket farm KPI dashboard and review:

• Average FCR for the week (vs. your target and prior week)
• Average mortality rate for the week (vs. target and prior week)
• Number of bins active, number harvested, number stocked
• Any alerts that triggered during the week

This isn't a conversation yet. It's orientation. Everyone looks at the numbers together.

Minutes 5-15: Drill into what moved

Focus your attention on anything that changed significantly from the prior week. FCR went up 0.3 points? What bins drove that? Mortality rate spiked Tuesday? Was it one bin or farm-wide? Temperature records from that period?

This is where the meeting earns its time. An FCR deviation that no one investigated during the week gets a 10-minute root cause discussion. If you find the cause and correct it, you've prevented that deviation from persisting.

Minutes 15-22: Harvest schedule and upcoming production

Review which bins are approaching harvest in the coming week. Confirm you have packaging inventory and capacity to process them. Note any supply commitments to accounts that depend on this week's harvest.

This is operational planning, not retrospective analysis. It ensures the team knows what's coming and has what they need to execute.

Minutes 22-28: Accountabilities from last week and commitments for this week

What did you commit to last week that needed to happen? Did it? (If not, why not, and what's the updated commitment?) What specific actions is each person committing to this week?

This is the accountability structure that converts meetings from information-sharing into performance management.

Minutes 28-30: Any urgent issues to flag

Open the floor for anything that didn't fit in the structured agenda. Pest observation, equipment issue, supply concern. Keep it brief; anything requiring extended discussion gets scheduled separately.

CricketOps Reports to Pull Before the Meeting

Pull these from your CricketOps dashboard before the meeting starts so the data is visible when the meeting begins:

• Weekly FCR summary: Average FCR by bin for the week, highlighted against your target
• Mortality trend chart: Daily mortality rates for the past 7-14 days across all active bins
• Bin status list: All active bins with current age, projected harvest date, and current health status
• Alert log: Any temperature, humidity, or other alerts triggered during the week
• Harvest log: Bins harvested during the week with yield and quality data

The cricket farm management dashboard aggregates these metrics automatically from your daily production log entries. If your workers are logging consistently, the meeting data is always ready.

Driving Accountability Without Being Punitive

The weekly meeting works as an accountability tool when it's focused on problems to solve rather than people to blame. Frame deviations from target as operational puzzles: "FCR is up this week; what do we think is driving it?" rather than "Why was FCR bad this week?"

This framing invites workers to contribute analysis rather than defend themselves. Workers who contributed to a problem and understand why it happened are far more motivated to prevent it from happening again than workers who were called out for it in front of the team.

When you identify a root cause, assign a specific action with a specific owner and a specific due date. "Let's look at temperature calibration on bins 8-12 before Thursday" is an accountable commitment. "We should probably check the temperature sensors" is not.

Frequently Asked Questions

How do I run a weekly meeting for my cricket farm team?

Keep it 30 minutes, structured around the same agenda every week. Start with your weekly headline KPIs from CricketOps (FCR, mortality rate, bins active), then drill into any metrics that moved significantly from the prior week. Spend 7 minutes reviewing the upcoming harvest schedule and confirming production readiness. Spend 5 minutes reviewing last week's commitments and capturing this week's commitments. Close with any urgent issues. The consistency of the format is what makes it efficient; when the team knows what's coming, they come prepared. Pull your CricketOps reports before the meeting starts so the data is visible from the first minute.

What data should I review in a weekly cricket farm operations meeting?

The four most important datasets for a weekly operations review are: your FCR for the week vs. target, your average mortality rate vs. the prior week and your target, your bin status (which bins are approaching harvest, which are newly stocked, and which are showing health concerns), and any alerts or anomalies that occurred during the week. These four data sets tell you whether your farm is operating at expected efficiency, whether you have emerging problems that need investigation, and whether your harvest schedule is on track. Secondary data to review when time permits: feed cost per pound, packaging inventory levels, and account order fulfillment rate for the week.

How does CricketOps support a weekly farm review meeting?

CricketOps aggregates your daily production log data into the weekly KPI summary, FCR calculation, and mortality trend views that make up the core of the weekly meeting agenda. When your team logs consistently daily, your Monday morning meeting data is automatically ready. The dashboard shows FCR by bin, mortality rate trend, active bin status, and alert history for any time period you specify. Exporting these views to a screen or tablet during the meeting ensures the whole team is looking at the same data. CricketOps also tracks the comparison between current week and prior week, so trend identification (FCR going up or down, mortality rate improving or worsening) is built into the view rather than requiring manual calculation.

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.