Documenting Hive Loss During a Pollination Contract
pesticide exposure is cited as the cause in over 60 percent of in-contract hive mortality disputes. When colonies die during a pollination contracts, the question of who is responsible and who pays depends almost entirely on what documentation exists. A loss report generated in PollenOps includes environmental data, last inspection record, and GPS yard log, creating the evidence chain needed to defend against grower liability claims or support your own claim against a grower whose spray program caused the loss.
Undocumented hive loss during a contract is a liability exposure for the beekeeper. You may have delivered strong colonies in good faith, and a spray event or disease outbreak may have caused the loss. Without documentation, you're in a "your word against theirs" situation that resolves unfavorably for both parties and often results in lengthy and expensive disputes.
TL;DR
- A well-written pollination contract covers hive strength requirements, payment terms, delivery/removal windows, pesticide liability, and dispute resolution.
- Standard payment structure is 50% on delivery and 50% on removal; push for no longer than 14-day net on the back half.
- Hive strength disputes are the most common source of non-payment; third-party inspection at delivery is the cleanest resolution.
- Pesticide kill provisions should require grower notification 24-48 hours before any application within foraging range of placed hives.
- Contracts signed by November have stronger pricing leverage than those negotiated in December or January.
Who Is Responsible for Hive Mortality During a Contract?
The answer depends on the contract language and the documented cause. In a well-drafted contract, liability for hive mortality is allocated based on cause:
Beekeeper's liability: Colony losses from varroa mite-related disease, colony collapse unrelated to pesticide exposure, absconding, queen failure, or other conditions within the beekeeper's management responsibility.
Grower's liability: Colony losses caused by the grower's pesticide applications, either through direct spraying during bloom or through movement of systemic pesticides from treated fields into foraging colonies.
Shared or no-fault loss: Colony losses from weather events, naturally occurring pathogens at levels that don't reflect management negligence, or other causes not attributable to either party.
The contract should specify these liability allocations explicitly. If your contract is silent on pesticide liability, you're negotiating from the document rather than from clear terms when a spray event occurs.
How to Document Hive Loss During a Contract
When you discover colony losses during a pollination contract, the documentation steps you take immediately determine your legal and insurance position:
Step 1: GPS-tagged photo documentation. The moment you discover the loss, open PollenOps mobile app and begin photographing the affected colonies with GPS tagging active. Capture images of dead and dying bees at the hive entrance, inside the hive, and on the ground nearby. The GPS coordinates and timestamp are embedded in the photo record automatically.
Step 2: PollenOps loss report generation. In PollenOps, open the affected yard and initiate a hive loss report. The report pulls your most recent inspection record for the affected colonies, the delivery GPS log showing when and how colonies were placed, and any environmental notes from your inspection history. Enter your current field observations: colony count affected, estimated mortality level per colony, and any observable cause indicators.
Step 3: Physical sample collection. Collect dead and dying bees in sealed, labeled containers for potential laboratory analysis. Laboratory analysis for pesticide residues or disease is your strongest evidence for establishing cause. Samples should be frozen immediately to preserve analytic integrity.
Step 4: Grower notification. Notify the grower in writing through PollenOps messaging or email, noting the date and time of notification. Do not remove dead colonies from the yard until the grower has had an opportunity to inspect and until you've confirmed whether an insurance adjuster will survey the site.
Step 5: Third-party inspection request. For significant losses, request inspection by the state apiary inspector, an independent apiculture consultant, or both. Third-party documentation of the loss event provides an independent record that carries more weight than self-documentation alone.
Using PollenOps Records in a Liability Defense
When a grower claims your hive loss was due to management negligence rather than their spray program, your PollenOps contract compliance documentation records are your primary defense.
The delivery GPS log shows exactly when your colonies arrived and at what location. The pre-move strength assessment shows the colony condition at delivery. Healthy colonies at 8 frames of bees with a laying queen are not the condition of management-negligent colonies. The yard inspection history shows what condition your colonies were in from delivery through the loss event. The timestamped loss report documentation establishes when you discovered the problem and what your immediate response was.
This documentation chain answers the grower's implicit or explicit claim: "Your bees were weak and died from your own poor management." Your records show they were strong at delivery and the timeline is inconsistent with management-related decline.
Using PollenOps Records in a Grower Claim
When you want to pursue recovery against a grower whose spray program caused your loss, the same records support your claim. The PollenOps hive count verification records establish what you had before the loss. The GPS delivery logs establish that your colonies were at the contracted location during the spray event. The loss report timeline establishes that the mortality occurred immediately after the spray application rather than over a gradual period consistent with disease-related decline.
Laboratory analysis of dead bees showing pesticide residues, combined with your PollenOps documentation, creates a claim that insurance adjusters and legal counsel can work with. Without documentation, pesticide liability claims often fail not because the evidence against the grower is weak but because the evidence establishing your colonies' prior condition doesn't exist.
Frequently Asked Questions
How do I document hive loss during a pollination contract?
Document immediately and systematically. Start with GPS-tagged photos of affected colonies using the PollenOps mobile app. Generate a PollenOps hive loss report that pulls your delivery GPS log, last inspection record, and current field observations. Collect dead and dying bee samples in sealed containers for laboratory analysis. Notify the grower in writing with a documented date and time. Don't remove dead colonies from the site until an adjuster or inspector has surveyed them. Request third-party inspection from the state apiary inspector or independent consultant for significant loss events.
Who is responsible for hive mortality during an active pollination contract?
Responsibility depends on documented cause. Colony losses from beekeeper management failure (varroa-related disease, starvation, queen failure) are the beekeeper's liability. Losses from the grower's pesticide applications (either direct spraying during bloom or systemic pesticide movement into foraging colonies) are the grower's liability. Your contract should explicitly allocate liability by cause so the allocation isn't determined by negotiation after the fact. Well-drafted contracts with clear pesticide liability language protect beekeepers from being held responsible for events outside their control.
Can PollenOps records help me defend against a grower liability claim?
Yes. PollenOps delivery GPS logs, pre-move strength assessments, and yard inspection history create a documented baseline establishing your colony condition and the timeline of events. If a grower claims your hive losses resulted from management negligence, your records showing strong colony condition at delivery and a loss timeline consistent with acute external cause (spray event) rather than gradual management-related decline provide your primary defense evidence. Laboratory analysis of dead bees combined with PollenOps documentation gives insurance adjusters and legal counsel a defensible claim structure.
What are the most common clauses in a commercial pollination contract?
A standard commercial pollination contract covers: hive strength minimums at delivery, payment terms (typically 50% on delivery, 50% on removal), delivery and removal dates, pesticide notification requirements, liability provisions for colony losses, truck access and yard location details, and dispute resolution procedures. Force majeure clauses addressing crop failure and operator inability to deliver the full hive count are also standard in well-written contracts.
How should pesticide liability be addressed in pollination contracts?
The contract should require growers to notify operators at least 24-48 hours before any pesticide application within foraging range (2-3 miles), specify the operator's right to remove hives immediately upon notification, and define liability for documented colony losses attributable to pesticide exposure. Without this clause, recovering compensation for pesticide kills requires proving causation after the fact, which requires lab testing, communication records, and timestamped photos of dead bees collected before cleanup.
What is a typical contract renewal strategy for commercial beekeepers?
Most successful commercial operators begin renewal conversations with existing growers in July, confirming the coming season's hive count and rate before new grower outreach. Existing grower relationships command better pricing stability than new contracts and require less pre-season sales effort. Sending growers a season-end report documenting hive placements and colony performance reinforces the relationship and creates a natural opening for renewal discussion.
Sources
- USDA Agricultural Research Service
- Bee Informed Partnership
- American Beekeeping Federation (ABF)
- American Honey Producers Association
- Project Apis m.
Get Started with PollenOps
Managing pollination contracts across multiple growers and crops is where most commercial operations have the most to gain from better systems. PollenOps centralizes contract lifecycle management from initial quote through signed agreement, delivery documentation, and final invoice. Try it for your next season.