How Pre-Move Strength Assessments Protected a Beekeeper's Almond Contract

A California almond pollinator's contract for 300 hives included a penalty clause: $400 per understrength hive delivered, with "understrength" defined as fewer than 8 frames of bees at placement. California almond contracts typically include penalty clauses of $200 to $500 per understrength hive delivered, and this was on the higher end.

In the season before using PollenOps, the operator had used informal pre-move checks: a driver walking through the yard, counting estimated frames, flagging obvious problem colonies. In the first season with PollenOps pre-move strength checklists, the structured assessment identified 45 colonies below the 8-frame threshold that informal checking had missed. Removing and replacing those 45 hives before delivery avoided a contract penalty worth $18,000.

TL;DR

The California Almond Board's research supports 6 frames of bees as the minimum effective colony strength for almond pollination.
Many growers now specify 8 frames for premium contracts, with rates at $200-215/hive versus $185-195 for 6-frame minimums.
Hive strength assessment should be documented by yard, date, and assessor to create a defensible record for contract compliance.
A colony assessed at the required strength in January can fall below minimum by February delivery if varroa loads are high or weather stress is severe.
Third-party inspection at delivery is the cleanest resolution for strength disputes and protects operators as well as growers.

Why Informal Pre-Move Checks Miss Understrength Colonies

The pre-PollenOps informal check relied on experienced visual estimation and driver judgment. Experienced beekeepers can estimate colony strength reasonably well in optimal conditions. The problem is that pre-move checks don't happen in optimal conditions: they happen under time pressure, often in the early morning before a planned afternoon move, sometimes in partial darkness or with the colony in transport configuration that makes frame counting difficult.

More importantly, informal checks don't create a record. When a driver walks through a yard and says "looks good," there's no documentation of what was actually assessed, what the count was, or whether any colonies were flagged and swapped. If a grower later claims delivered colonies were weak, the operator's only evidence is the driver's memory.

The 45 flagged colonies in this case study weren't obviously weak. They were in the range of 5 to 7 frames. Not dead, not absconding, not obviously failing. They looked like colonies at the lower end of normal variation. A driver moving quickly through a 300-hive yard in the early morning would have been unlikely to pull every box, do a formal frame count, and flag a colony with 6 frames as below threshold when the target was 8.

The PollenOps pre-move checklist required a frame count for every colony, not just the obviously questionable ones. That systematic requirement turned a subjective walk-through into an objective assessment with a documented result for every single colony in the batch.

The Pre-Move Checklist Process

The PollenOps pre-move strength assessment is triggered automatically 72 hours before a contracted move date. It generates a checklist for the yard with each colony requiring a documented strength score and a binary pass/fail assessment against the contracted threshold.

The assessment covers:

Estimated frame count of bees (not just frames of brood)
Queen status: laying, visible, or unknown
Brood pattern quality: solid, scattered, or absent
Food stores: adequate, marginal, or insufficient
Overall colony score against contracted minimum

Colonies that fail the threshold are flagged red in the system. The operator sees a yard-level dashboard showing how many colonies passed, how many failed, and what the pass rate is as a percentage of the contracted delivery count.

In the case study season, the pre-move assessment was completed 48 hours before a planned delivery. The assessment flagged 45 of 310 assessed colonies below the 8-frame threshold, a 14.5 percent failure rate. The operator immediately identified replacement colonies from nearby yards that were above threshold, swapped them into the delivery batch, and reassessed the replacements before confirming delivery.

The total time from flagging to replacement to re-assessment was approximately 6 hours. The penalty avoided was $18,000. The cost of running the checklist in PollenOps was zero beyond the time invested.

What Happened to the 45 Flagged Hives

The 45 colonies below the 8-frame threshold weren't disposed of. They were moved to a recovery yard where they received supplemental protein and pollen patties, requeening where needed, and 3 to 4 weeks of rebuilding time. By mid-March, 38 of the 45 had reached or exceeded the 8-frame threshold and were added to the operator's available inventory for late-season contracts.

The remaining 7 colonies that didn't recover were merged with stronger colonies to create above-threshold double-nucs that were later split. None of the 45 were a total loss; they were a temporary compliance risk that the pre-move assessment identified in time to address.

The operator's observation was that the 45 colonies would have been delivered to the almond orchard and flagged by the grower's contracted inspector during placement. The grower's contract included a right to count and assess hives at delivery, and the grower exercised that right routinely. The $18,000 penalty was not hypothetical; it would have been charged.

The Documentation Value Beyond Penalties

The hive strength assessment documentation in PollenOps creates a delivery record that shows your pass rate and your process, not just the fact of delivery. When the operator shares the pre-move assessment results with the grower as part of the delivery documentation package, it communicates something important: you assessed systematically, you caught and remedied problems before delivery, and the colonies that were delivered had passed a documented threshold.

This kind of process documentation supports contract compliance documentation in ways that informal pre-move checks never can. Growers who see your pre-move assessment results attached to delivery confirmation understand that what they're receiving is the product of systematic quality management, not just whoever happened to pass the yard the night before.

One additional benefit: the documentation makes renewal conversations easier. When you can show a grower that your delivery pass rate last season was 96 percent of contracted strength and your failed-inspection recovery rate was 84 percent, you're negotiating from data rather than reputation. That data supports premium pricing at renewal.

Frequently Asked Questions

How did PollenOps flag the understrength hives before the move?

PollenOps generates a pre-move strength checklist 72 hours before each contracted move date. The checklist requires a documented frame count and pass/fail assessment against the contracted strength threshold for every colony in the delivery batch. Colonies that fall below the threshold are flagged red in the yard dashboard, giving the operator a clear count of failed colonies and the time to source replacements before delivery. In this case, the 45 flagged colonies were identified 48 hours before planned delivery, leaving enough time for replacement assessment and confirmation.

What was the strength threshold specified in the almond contract?

The contracted threshold was 8 frames of bees at delivery, with a penalty clause of $400 per understrength hive. Eight frames is on the higher end of typical almond contract requirements (which commonly range from 6 to 8 frames), and the $400 penalty per hive is near the top of the industry range of $200 to $500 per understrength delivery. The 45 flagged colonies, at the $400 penalty rate, represented an $18,000 exposure that was completely avoidable through systematic pre-move assessment.

What did the beekeeper do with the 45 flagged hives?

The 45 flagged colonies were moved to a recovery yard and given supplemental protein, pollen patties, and in some cases requeening. Within 3 to 4 weeks, 38 of the 45 had reached or exceeded the 8-frame threshold and entered the available inventory for late-season contracts. The remaining 7 were merged with stronger colonies and later split. The systematic pre-move assessment turned a potential $18,000 liability into a managed inventory event with almost no net loss to the operation.

How is hive strength measured for commercial contract compliance?

Hive strength is typically measured by counting frames of bees: the number of frames in the brood box that are covered (both faces) by worker bees. A frame covered on both faces counts as one frame of bees. Some assessors use a modified approach counting only the top face of each frame. The contract should specify the measurement method, since a hive assessed at 6 frames by one method might be 5 frames by another. Third-party inspection using a consistent, documented method is the cleanest standard for compliance.

What causes hives to fall below strength requirements between assessment and delivery?

Several factors can reduce colony strength between pre-season assessment and delivery: high varroa loads with insufficient treatment response, poor winter weather in northern states during transport south, queen failure or queen loss in the weeks before delivery, and nutritional stress from limited forage. Commercial operators typically re-assess colonies 1-2 weeks before departure to confirm strength has been maintained, replacing any colonies that have declined with stronger hives from their reserve inventory.

Can strength requirements be met with a recently split colony?

No. A recently split colony (within 4-6 weeks) will not have a full brood cycle's worth of adult workers emerging to maintain population. A split colony may appear to have adequate frames at the time of split but will decline in population over the following weeks as older workers die without emerging brood to replace them. Colonies going to almond pollination should have had their most recent split at least 8-10 weeks before delivery to allow full population recovery.

Sources

USDA Agricultural Research Service
Bee Informed Partnership
American Beekeeping Federation (ABF)
Almond Board of California
Project Apis m.

Get Started with PollenOps

Hive strength documentation is the foundation of contract compliance and dispute prevention. PollenOps structures strength assessment records, delivery confirmations, and inspection data so you have the evidence you need when questions arise about contract performance.