Pollinator Protection Plans: What Beekeepers Need to Know

Pesticide kill events cost commercial beekeepers an estimated $12 million or more annually. Most of those losses happen in circumstances where better communication between growers and beekeepers could have prevented them, or at minimum, produced documentation for a compensation claim. State Managed Pollinator Protection Plans (MP3s) exist to fix that communication problem.

More than 40 states have adopted Managed Pollinator Protection Plans, and the requirements they create for growers (including notification before certain pesticide applications) directly affect how you position colonies, who you notify about your yard locations, and what evidence you have when something goes wrong.

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.

What a Managed Pollinator Protection Plan Is

A Managed Pollinator Protection Plan, typically called an MP3 or Bee Best Management Practices plan, is a voluntary or regulatory framework developed at the state level that coordinates between pesticide applicators and beekeepers. The plans vary significantly by state, but most share common elements:

A registry system where beekeepers register yard locations so pesticide applicators can identify when bees are nearby
Best management practices for pesticide applications near managed colonies (time of day, application method, product selection)
Notification requirements: in some states, applicators must notify nearby registered beekeepers before certain applications
Dispute resolution guidance for pesticide kill events

The plans came out of a recognition that bee colony losses from pesticide exposure were largely preventable with better coordination, and that the market pressure to improve practices was insufficient on its own. EPA and USDA encouraged states to develop these frameworks as part of the Pollinator Health Task Force's 2015 National Strategy.

How Registration Protects You

The registration component is the most actionable piece for commercial beekeepers. When you register your yard locations with your state's MP3 system:

Pesticide applicators using the FieldWatch or DriftWatch platforms can see your apiary locations before they spray
In states with notification requirements, registered applicators receive automatic alerts when their intended spray area is near a registered apiary
You have documented evidence of your yard's registered status, which matters for any pesticide kill claim

FieldWatch is the dominant platform used by states that have digitized their apiary registry. If your state uses FieldWatch (the majority of states that have MP3s do), registering there means your apiary locations are visible to agricultural pesticide applicators in the same platform as other sensitive site registrations.

The catch: registration only protects you if applicators check the system. Most licensed commercial applicators do. Checking FieldWatch before application is increasingly standard practice and sometimes required under their pesticide license conditions. But drift from neighboring properties, unlicensed applications, and applicators who don't follow protocol still cause kills.

States with Active MP3 Programs

States with strong, actively enforced MP3 programs including FieldWatch integration:

California, Oregon, Washington, Minnesota, Wisconsin, Iowa, Michigan, Indiana, Illinois, Ohio, Pennsylvania, New York, North Carolina, and Florida have developed the most comprehensive plans with active industry participation. In these states, registering your apiaries on FieldWatch and checking the system's alert functionality is standard practice for commercial operators.

States with MP3 frameworks but variable enforcement:

Many Southern and Great Plains states have adopted MP3 frameworks but enforcement and applicator compliance varies. The framework exists and provides some protection, but don't assume the same level of system engagement as you'd find in Minnesota or Michigan.

Notification requirements by state:

California requires notification for certain pesticide applications near registered apiaries under some circumstances. Oregon has some of the strongest notification requirements in the country for commercial bee operations. Contact your state's department of agriculture for current notification requirement details, as these frameworks are actively evolving.

The Connection Between MP3 and Interstate Movement

If you're moving hives across state lines into multiple states in a season, you need to register your yard locations in each state's apiary registry (and ideally in that state's FieldWatch system) within the required timeframe after placement. Some states require registration within 30 days of first placing colonies; others require it before any colonies are placed.

This registration protects your colonies from unannounced applications in the area and gives you standing if a pesticide event occurs. An unregistered yard has significantly less legal and administrative standing in a kill claim than a registered one.

When Something Goes Wrong: First Steps

A pesticide kill event is a time-sensitive documentation situation. The evidence you collect in the first 24-48 hours largely determines what you can recover.

What to do immediately:

Don't clean up or move dead bees from the yard. Bee kill sites with samples of dead bees are evidence.
Collect dead bee samples: 100-200 dead bees in a sealed container, frozen immediately. Label with date, yard location, and time of collection.
Photograph extensively: dead bees at colony entrances, in front of hives, any spray residue visible on vegetation, drift patterns.
Note the date, approximate time you discovered the kill, weather conditions, and wind direction.
Identify any agricultural applications that occurred recently in the surrounding area. Talk to neighbors. Check with the county agricultural commissioner about recent pesticide application permits in the area.

Sample submission for pesticide residue analysis: USDA AMS's National Science Laboratory in Gastonia, NC processes bee kill samples for residue analysis. State labs and some university extension labs also do this analysis. Sample submission fees and turnaround times vary.

Reporting Requirements

Most states with MP3 programs require or recommend reporting pesticide kills:

State Department of Agriculture: File a pesticide incident report. This creates a record and may trigger an official investigation.
EPA: Significant kill events can be reported to EPA's pesticide incident reporting system.
State apiarist: Your state apiarist's office should know about significant kill events; they track patterns across the state.
Insurance: If you carry livestock or crop insurance that covers colony losses, notify your insurer promptly. Missing reporting deadlines can void coverage.

In states with EPA-registered pesticides that have bee precaution labels, a confirmed kill from a product applied in violation of label requirements is a federal pesticide law violation. The applicator can face penalties. Your documented report is what initiates that process.

Preventing Kills Through Proactive Communication

Registration is passive protection. Active protection means talking to your grower contacts about what's being sprayed, when, and where. For every pollination contracts:

Get written confirmation of the pest management plan for the season
Ask specifically about applications during bloom (for any crop where bees are present)
Confirm re-entry intervals and ask that you be notified 48 hours before any application during the contract period
Build this communication requirement into your pollination contract template

Growers who've had pesticide issues with beekeepers before are usually receptive to this conversation, as pesticide kills create litigation exposure for them too. Growers who haven't thought about it will think about it once you raise it professionally.

The commercial beekeepers who have the fewest pesticide problems are typically the ones who treat grower communication as a standard operating procedure, not something that only happens when there's a problem.

Pesticide Application Best Management Practices Beekeepers Can Request

Several MP3 frameworks include applicator best management practices that beekeepers can request as contractual terms:

Applications made at dusk or dawn rather than during active foraging hours
Avoiding flowering cover crops or weeds in the orchard during application
Using the least toxic effective product for the target pest
Applying with low-drift nozzles when adjacent to apiary locations
Providing 48-hour advance notice

These aren't guaranteed. But growers who want your colonies back next year are generally willing to accommodate reasonable requests. A grower who loses their beekeeper because a pesticide event couldn't be prevented, or worse because they were unresponsive after a kill, has a pollination problem that's harder to solve than modifying an application timing.

FAQ

What is a Managed Pollinator Protection Plan?

A Managed Pollinator Protection Plan (MP3) is a state-level framework that coordinates communication between pesticide applicators and beekeepers to reduce bee colony losses from pesticide exposure. Most plans include an apiary registration system (often via FieldWatch), best management practices for pesticide applicators near beehives, and sometimes mandatory notification requirements before certain applications. More than 40 states have developed MP3 frameworks with varying levels of enforcement and applicator participation.

Are growers required to notify beekeepers before pesticide applications?

It depends on the state and the specific pesticide's label requirements. Oregon has relatively strong notification requirements for commercial apiary operators. In most states, notification is a best management practice encouraged under MP3 frameworks but not always legally required. Some individual pesticide labels include bee precaution language that effectively requires avoiding application when bees are present and foraging. Violating these label requirements is a federal pesticide law violation regardless of state requirements.

How do you document a pesticide kill event for insurance or legal purposes?

Collect frozen dead bee samples (100-200 bees in a sealed container) immediately after discovery. Photograph the kill site extensively, noting the date, time, weather, and wind direction. Identify any recent pesticide applications in the surrounding area. Submit bee samples to a lab for residue analysis. File a pesticide incident report with your state department of agriculture and notify your insurer within the required timeframe. Apiary registration in the state's system prior to the event provides documentation that your yard was properly registered. Registered yards have stronger standing in claims than unregistered ones.

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.