Pollination Contract Terms Template: Ready to Customize
Beekeepers who use a written contract with standard clauses are 70 percent less likely to face a disputed invoice. That gap reflects the difference between a contract that defines what was agreed and a handshake that leaves both parties filling in the blank spaces with their own recollection when something goes wrong.
The PollenOps pollination contract terms template includes 14 standard clauses covering strength, count, timing, cancellation, and payment. Every clause is written to protect commercial beekeepers against the most common dispute scenarios while remaining fair enough that growers will sign without extensive negotiation.
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.
The 14 Standard Clauses
1. Parties and Effective Date. Names and contact information for beekeeper and grower, plus the contract execution date. Establish who is bound and when the contract begins.
2. Crop and Site Description. The specific crop being pollinated, the orchard or field address, and the GPS coordinates of the hive placement site. Specificity here prevents disputes about which yard or which orchard block is covered.
3. Hive Count. The total number of hives to be delivered. Specify whether this is a minimum count (you deliver at least X) or a target count (you deliver approximately X subject to available colonies meeting strength requirements).
4. Colony Strength Requirements. Minimum frames of bees, minimum frames of brood (if specified), and queen status (laying queen required). Define how strength is measured: frames fully covered with bees, visually estimated, or formally inspected. Specify what happens if colonies delivered below minimum: replacement within 48 to 72 hours at no charge, or credit against the invoice.
5. Delivery Date and Bloom Trigger. The delivery window (not a single day, but a date range) tied to bloom stage. Define bloom stage as a percentage of open flowers in the orchard (20 percent bloom, for example) or as a specific calendar window. Specify that PollenOps bloom timing alerts serve as the delivery trigger.
6. Placement Location. Where within the orchard or field hives will be placed. If the grower has specific placement requirements (distance from water sources, shading preferences, access road requirements), document them here.
7. Weather and Force Majeure. Define conditions that excuse non-performance without breach: extreme weather events, freeze events that damage bloom, natural disasters. This protects both parties from disputes about outcomes driven by conditions neither controls.
8. Removal Date and Terms. When hives will be removed after bloom, defined as a fixed date or as a number of days after bloom completion. Specify who initiates removal: beekeeper at their discretion, or grower notification followed by removal within a defined window.
9. Pesticide Notification. Grower's obligation to notify beekeeper at least 48 hours before any pesticide application that could affect colonies. Specify the consequences if notification is not provided (beekeeper liability for bee loss is reduced or eliminated; grower may be liable for replacement cost of lost colonies).
10. Hive Mortality During Placement. Who bears responsibility for colony losses during the placement period. Standard language: beekeeper is responsible for losses from natural causes; grower is responsible for losses from pesticide exposure without prior notification; force majeure events are shared risk.
11. Payment Terms. Total contract amount, payment schedule (deposit on signing, balance at delivery, or invoice at delivery with 30-day payment terms), and late payment provisions (typically a 1.5 percent monthly fee on overdue balances).
12. Invoice and Documentation. What documentation accompanies the invoice: GPS delivery confirmation, hive count at delivery, strength assessment results if required. Specify that PollenOps delivery records constitute the official documentation of delivery.
13. Dispute Resolution. How disputes will be resolved: first through direct negotiation, then through mediation if negotiation fails, with arbitration or court proceedings as a last resort. Specify jurisdiction for any legal proceedings.
14. Cancellation. Terms under which either party can cancel before delivery: grower cancellation with less than X days notice forfeits deposit; beekeeper cancellation refunds deposit with X days notice or provides a replacement beekeeper.
Using the Template with PollenOps
The PollenOps contract template integrates directly with the contract management system. When you create a new contract in PollenOps, the template's standard terms populate the contract framework, and you enter the specific terms (hive count, delivery window, payment amount) for that particular grower and season.
Contract terms stored in PollenOps link to the delivery record, inspection records, and invoicing so that every piece of documentation for the season references back to the agreed terms. If a dispute arises over the delivery date, the GPS check-in links to the contract's delivery window clause. If a dispute arises over hive count, the delivery record links to the contracted minimum.
For the pollination contract template download, see pollination contract template. For the full contract management platform, see pollination contract software.
Frequently Asked Questions
What clauses should a pollination contract template include?
A complete pollination contract should include, at minimum: identification of the parties, a specific description of the crop and site, the contracted hive count and colony strength requirements, the delivery date or bloom trigger window, a pesticide notification obligation for the grower, a clear statement of who bears liability for hive mortality under different scenarios, payment terms with a specific invoice date and due date, and a dispute resolution process. Experienced operators add force majeure language for weather events, specific removal date terms, and cancellation provisions. The PollenOps template includes all 14 clauses that cover these areas in detail. Operators with legal questions about specific clause language should consult an agricultural attorney in their state, since contract enforceability depends on local law.
Is the PollenOps contract template legally reviewed?
The PollenOps template clauses are drafted with standard commercial contract best practices for agricultural service agreements and have been reviewed by agricultural attorneys for general commercial use. However, the template is not state-specific legal advice, and legal requirements for contract formation and enforceability vary by state. For contracts involving large sums (almond contracts above $50,000, for example), having an agricultural attorney in your state review the specific terms before the season is worth the investment. For standard commercial contracts in the $5,000 to $25,000 range, the template's standard clauses reflect typical industry practice and provide meaningful protection without custom legal review for each contract.
How do I customize the PollenOps contract template for my operation?
The template opens with the 14 standard clauses pre-populated. Customize by entering the specific terms for each contract: grower name and contact, site address and GPS coordinates, contracted hive count, strength requirement (specific frame count), delivery date range, payment amount and schedule, and removal date. Clauses that don't apply to your operation can be removed or marked as not applicable. If you have operation-specific terms (for example, a recurring annual contract with a specific grower that includes a pricing adjustment formula), add those as additional clauses at the end of the standard template. When the contract is finalized in PollenOps, it generates a PDF that both parties can sign electronically or print and sign.
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.