Hive Mortality Tracking for Commercial Beekeepers

Commercial beekeepers lose an average of 30 to 40 percent of their colonies annually to various causes including winter starvation, disease, pesticide exposure, and queen failure. At that scale of loss, tracking mortality by yard, cause, and season isn't just record-keeping. It's the data that tells you whether your management practices are working and where your weakest yards consistently produce the most losses.

PollenOps mortality tracking captures hive losses at the yard level with cause codes, inspection notes, and GPS location for every recorded loss. Over multiple seasons, the data builds a loss history that identifies problem yards, problematic time windows, and management gaps that calendar-based tracking misses.

TL;DR

Commercial beekeeping operations face two primary management challenges: operational logistics (hive health, transport, placement) and administrative coordination (contracts, payments, documentation).
Most disputes and revenue losses in commercial beekeeping are preventable with better documentation and clearer contract terms.
The operations that run most profitably are those with disciplined systems for tracking hive health, contract status, and fleet logistics in one place.
PollenOps is built specifically for the operational complexity of commercial-scale pollination services, not adapted from a hobbyist tool.
The most important management decisions (treatment timing, contract renewal, hive allocation) require accurate current data to make well.

Tracking Losses by Yard and Cause

The basic mortality entry in PollenOps captures: yard location (GPS-linked), date of discovery, cause of loss (from a standard code list including pesticide exposure, starvation, queen failure, varroa collapse, disease, and unknown), and inspector notes. You can add photos to a loss entry, which matters when pesticide exposure is suspected and you want a visual record of dead bees at the entrance.

Over a season, the yard-level loss view shows which locations consistently produce losses versus which produce stable populations. A yard that loses 5 percent of colonies each season through queen failure is a different problem than a yard that lost 30 percent in a single event consistent with pesticide exposure. The loss history makes the pattern visible.

Cause coding lets you filter losses by type across your full operation. If varroa-related collapses are concentrated in specific counties or specific time windows, the filter makes that pattern visible in a way that manually reviewing inspection notes does not.

Mortality Tracking and Contract Compliance

When hives die during an active pollination contracts, your mortality record serves two functions: it documents what you actually delivered versus what you contracted, and it provides evidence that helps determine responsibility for the loss.

A loss recorded in PollenOps includes the contract it's associated with, the yard inspection record that preceded the loss, and the environmental data from the yard's location at the time. This record structure means that when a grower disputes your delivery count or claims your hive count fell below contract minimum during the placement period, you have a documented timeline of colony status that goes beyond your word against the grower's.

For pesticide-related losses during a contract, the GPS yard location, the timing of the loss, and photos of the affected colonies are the core documentation for an insurance claim or a dispute resolution conversation with the grower. A loss entry that was recorded at the time of discovery is far more credible in a dispute than a retroactive written account assembled weeks later.

The commercial bee yard management and hive inventory management tools in PollenOps connect to the mortality log so your inventory count updates automatically when losses are recorded.

Mortality Trend Alerts

PollenOps flags unusual loss rates at specific yards based on your historical baseline. If a yard that typically runs 3 percent monthly mortality shows 15 percent loss in a single week, a mortality trend alert prompts an investigation before the problem spreads to adjacent colonies.

Early intervention on a trending loss pattern (whether from a queen failure cascade, a varroa load spike, or an environmental exposure event) is consistently less expensive than waiting until the next scheduled inspection. The alert system replaces the need to manually review loss rates yard by yard each week.

Frequently Asked Questions

How do I track hive mortality by yard location and cause of death?

Open a yard in PollenOps and record a loss entry for each colony that has died since your last inspection. Select the cause code that best matches the symptoms (pesticide exposure, queen failure, starvation, varroa collapse, disease, or unknown), add inspection notes, and optionally attach photos. The entry timestamps the loss, links it to the yard's GPS location, and associates it with any active contract at that yard. You can view loss history by yard, by cause, and by date range from the mortality dashboard. If you manage multiple employees, each driver or inspector can enter losses from the field through the PollenOps mobile app.

How does hive loss tracking affect my contract compliance records?

When a hive loss is recorded at a yard with an active pollination contract, PollenOps updates the effective hive count at that yard and flags whether the count has fallen below the contracted minimum. If you're required to maintain 100 hives at a site and three die, the system shows the shortfall and prompts you to document your replacement response. This record demonstrates that you monitored your contract compliance actively rather than leaving the grower to discover a shortfall at pickup. It also documents the timing of the loss relative to any grower pesticide applications, which matters if the cause of loss is disputed.

What is an acceptable mortality rate for a commercial pollination operation?

There is no single acceptable number, but most commercial operations target winter losses below 20 percent and in-season losses below 3 to 5 percent per month during active pollination placements. The USDA surveys consistently show industry average annual losses of 30 to 40 percent; operations below 25 percent annual loss are generally considered well-managed. In-contract losses above 10 percent at a specific site during a placement period are a flag worth investigating immediately, either for a management cause (poor colony condition at delivery) or an environmental cause (pesticide exposure from nearby applications). Tracking your own historical baseline in PollenOps gives you a more meaningful benchmark than industry averages, since your specific management practices, geography, and crop mix affect what normal looks like for your operation.

What is the difference between commercial and hobby beekeeping?

Commercial beekeeping is distinguished by scale (typically 100+ hives, often 500-5,000+), revenue source (pollination contracts and bulk honey sales rather than local honey retail), and management approach (systematic protocols applied across yards rather than individual colony attention). Commercial operators manage bees as an agricultural enterprise, with the administrative, regulatory, and logistical complexity that entails. Most commercial operators derive the majority of their income from pollination services; honey production is a supplementary revenue stream.

How many hives are needed to make commercial beekeeping a full-time income?

Most beekeeping economists put the full-time commercial threshold at 500-800 hives, assuming efficient operations management and a combination of pollination and honey revenue. At 500 hives and $200/hive for almond pollination, almond season alone generates $100,000 in gross revenue before expenses. Net margins depend on operational efficiency, but well-run operations can achieve 30-50% net margins on pollination revenue. Additional crops and honey production improve per-hive economics but require additional management capacity.

What is the annual revenue potential for a 1,000-hive commercial operation?

A 1,000-hive operation running an almond season ($200/hive) plus blueberry or apple contracts ($80-100/hive) plus summer honey production ($25-40/hive after extraction costs) can generate $300,000-360,000 in annual gross revenue. Net margins after transport, crew, equipment, and hive replacement costs typically run 25-40% for well-managed operations, putting net income at $75,000-145,000 annually. The specific number depends heavily on circuit efficiency, loss rates, and contract quality.

Sources

USDA Agricultural Research Service
Bee Informed Partnership
American Beekeeping Federation (ABF)
American Honey Producers Association
Project Apis m.

Get Started with PollenOps

Managing a commercial beekeeping operation involves more data, more deadlines, and more moving parts than any general-purpose tool was designed to handle. PollenOps brings contracts, yard records, health documentation, and fleet logistics together in one platform built for the realities of commercial-scale beekeeping.