Last Updated September 14, 2026
DriftWatch and its beekeeper-focused counterpart, BeeCheck, are free, voluntary online mapping registries that let beekeepers mark their apiary locations so pesticide applicators can see exactly where hives are before they spray — a simple communication fix for a problem that otherwise depends on an applicator happening to know, by word of mouth, that bees are nearby. Run by the nonprofit FieldWatch, the system now covers 28 U.S. states, Washington D.C., and three Canadian provinces as of Vermont’s addition in February 2026, and in several participating states, registering hives is also a practical prerequisite for compensation if a pesticide application does end up killing a beekeeper’s colonies.
Key Takeaways
- DriftWatch began in 2008 as a specialty-crop registry developed by Purdue University’s College of Agriculture and the Office of Indiana State Chemist, later spinning off into the independent nonprofit FieldWatch.
- FieldWatch actually operates four linked registries, not two: DriftWatch (specialty crops), BeeCheck (beekeepers), FieldCheck (for applicators to check both), and SeedFieldCheck (seed companies).
- Vermont became FieldWatch’s 32nd geography in February 2026, bringing the network to 28 U.S. states, the District of Columbia, and three Canadian provinces (Alberta, Manitoba, and Saskatchewan).
- Participation is entirely voluntary and the platform explicitly is not a substitute for any state’s regulatory pesticide-use requirements — it’s a communication layer on top of, not instead of, existing law.
- In some states, registering hives through BeeCheck is a practical condition for beekeepers to be eligible for compensation if a documented pesticide-drift incident kills or damages their colonies.
- A handful of states — including Kentucky, Massachusetts, North Dakota, Oklahoma, South Carolina, and Wyoming — run their own separate apiary or specialty-crop registries instead of participating in FieldWatch directly.
This walkthrough (produced by Manitoba Organics for Manitoba’s DriftWatch registry) shows the actual account-creation and site-mapping process a beekeeper or grower goes through — the mechanics are effectively the same across every state and provincial version of the platform.
Table of Contents
- What DriftWatch and BeeCheck Actually Do
- From a Purdue Pilot Program to a Multi-State Nonprofit
- The Newest Addition: Vermont Joins as the 32nd Geography
- How a Beekeeper Actually Uses BeeCheck
- What the System Can’t Do — and What If Your State Isn’t Covered
- Frequently Asked Questions
What DriftWatch and BeeCheck Actually Do
The underlying problem DriftWatch was built to solve is straightforward: a pesticide applicator spraying a field often has no reliable way of knowing that a beekeeper has hives set up in a hedgerow a quarter-mile away, or that a specialty vegetable grower has a pesticide-sensitive crop just over the property line — information that, historically, depended entirely on personal relationships and word of mouth in a given farming community. DriftWatch addresses this with a shared, opt-in online map: registered specialty-crop growers and beekeepers mark their site locations, and pesticide applicators can pull up that same map through FieldCheck — FieldWatch’s applicator-facing tool — before planning an application to see what pesticide-sensitive sites sit nearby. BeeCheck is simply the beekeeper-specific front door into the same underlying FieldWatch system, streamlined so an apiary owner — including one managing a large number of hives — can register locations with less data entry than the full specialty-crop DriftWatch form requires.
Aerial applicators are exactly the audience DriftWatch and FieldCheck are designed to reach before a spray run. Photo: USDA Forest Service, public domain.
| FieldWatch Registry | Who Registers | What It’s For |
|---|---|---|
| DriftWatch | Specialty and row crop producers | Marking pesticide-sensitive crop field locations |
| BeeCheck | Beekeepers | Marking apiary/hive locations, with a simplified form for large numbers of sites |
| FieldCheck | Pesticide applicators | Viewing all registered DriftWatch and BeeCheck sites before planning an application |
| SeedFieldCheck | Seed companies | Flagging fields where seed workers are present, for worker-safety planning |
From a Purdue Pilot Program to a Multi-State Nonprofit
DriftWatch didn’t start as a national platform; it began in 2008 as a specialty-crop site registry developed jointly by Purdue University’s College of Agriculture and the Office of Indiana State Chemist, aimed initially at Indiana growers and applicators. As other states recognized the same communication gap, the program expanded well beyond its Indiana origins, eventually spinning out into FieldWatch, an independent nonprofit that now administers DriftWatch, BeeCheck, FieldCheck, and SeedFieldCheck. The organization’s own stated model — “Communication + Cooperation + Collaboration = Successful Co-Existence” — reflects that it was built from the outset as a voluntary coordination tool between groups (specialty growers, applicators, seed companies, and beekeepers) who each have a legitimate interest in the others knowing where they operate.
Ground-rig applications are one of the everyday scenarios DriftWatch and BeeCheck are meant to help applicators plan around. Photo: Stefan Thiesen, CC BY-SA 3.0, via Wikimedia Commons.
The Newest Addition: Vermont Joins as the 32nd Geography
The network is still actively growing. In February 2026, Vermont became FieldWatch’s 32nd geography, joining the existing 27 other states, three Canadian provinces, and the District of Columbia already on the platform. The addition gives Vermont’s beekeepers and specialty-crop growers access to DriftWatch and BeeCheck for the first time.
“The goal is to get beekeepers and crop producers registered through FieldWatch so applicators can access accurate information before spraying.”
“This partnership gives our farmers another tool in the toolbox as we work together to ensure the continued success of Vermont agriculture.”
The pace of expansion — from a single-state Indiana pilot in 2008 to 32 geographies by 2026 — is itself a sign of how the underlying communication problem is a near-universal one across specialty-crop and beekeeping regions, not an Indiana-specific quirk that happened to spread.
How a Beekeeper Actually Uses BeeCheck
In practice, registering is a self-service process: a beekeeper creates a free account on the FieldWatch/BeeCheck platform for their state, then marks the general location of each apiary site on the shared map, along with basic identifying information. Because BeeCheck is designed specifically for apiaries rather than mixed specialty-crop operations, it deliberately asks for less than the full DriftWatch form, which matters in practice for beekeepers managing many out-yards across a season, including migratory operations moving hives seasonally for crop pollination work — the same kind of operation covered in this site’s guide to state bee inspector programs and apiary registration requirements, which is a separate, often mandatory process from the voluntary BeeCheck listing. Once registered, a beekeeper’s sites show up on the same map pesticide applicators are encouraged to check before an application, giving the applicator the option to adjust timing, method, or buffer distance around a known apiary.
Registering an apiary’s location is a self-service, few-minutes process for a beekeeper managing out-yards like this one. Photo: An Errant Knight, CC BY-SA 4.0, via Wikimedia Commons.
Registering on BeeCheck doesn’t replace other pesticide-exposure precautions a beekeeper should still take — this site covers complementary steps in understanding pesticide impact on U.S. beekeeping, reducing drift exposure specifically in pollination yards, and choosing pollinator-safe pest control products for beekeepers who also manage their own land.
What the System Can’t Do — and What If Your State Isn’t Covered
It’s worth being direct about what DriftWatch and BeeCheck are not. The platform’s own materials state plainly that it is not a substitute for any state’s regulatory requirements — registering an apiary doesn’t create a legally enforceable no-spray zone, doesn’t obligate any applicator to actually check the map before spraying, and doesn’t replace whatever pesticide-label restrictions, state apiary registration rules, or local ordinances already apply. It is, deliberately, a voluntary communication layer rather than a regulatory one, which means its real-world effectiveness depends heavily on applicator adoption and habit in a given area — a beekeeper registered on BeeCheck in a region where few local applicators actually consult the map gets a smaller practical benefit than one operating where the tool has become a routine part of local spray planning. That said, in several participating states, hive registration through BeeCheck is also tied to something with real teeth: eligibility for compensation programs when a documented pesticide application does kill or damage a beekeeper’s registered colonies, which gives beekeepers a concrete incentive to register even in areas where applicator uptake is still uneven.
Not every state runs its registry through FieldWatch. Kentucky, Massachusetts, and South Carolina maintain their own state-run apiary registries; North Dakota, Oklahoma, and Wyoming likewise handle specialty-crop or apiary registration outside the FieldWatch system. A beekeeper in one of those states should check with their state department of agriculture directly rather than assuming BeeCheck applies — the absence of a state from FieldWatch’s map doesn’t mean no registry option exists, only that it’s administered separately.
Physical signage like this is the kind of ad hoc, local notification that a shared digital registry is meant to supplement with something more systematic. Photo: jetsandzeppelins, CC BY 2.0, via Wikimedia Commons.
In Kansas, BeeCheck KS is voluntary, and the state itself has no hive registration.
Frequently Asked Questions
What is the difference between DriftWatch and BeeCheck?
DriftWatch is the general specialty-crop pesticide-sensitive site registry; BeeCheck is FieldWatch’s simplified version of the same registry built specifically for beekeepers, requiring less information and designed for registering apiary locations, including large numbers of hives.
Is registering my apiary on BeeCheck free?
Yes, registration is free and voluntary for beekeepers.
Does registering on BeeCheck legally stop pesticide applicators from spraying near my bees?
No. The platform is a voluntary communication tool, not a regulatory one — it does not create an enforceable no-spray zone and does not replace existing state pesticide regulations or label requirements.
Which states currently participate in FieldWatch/BeeCheck?
As of Vermont’s addition in February 2026, FieldWatch operates across 28 U.S. states, the District of Columbia, and three Canadian provinces (Alberta, Manitoba, and Saskatchewan); coverage has expanded steadily since 2008, so beekeepers should check FieldWatch’s own site for current participation in their specific state.
What if my state isn’t part of FieldWatch?
A handful of states — including Kentucky, Massachusetts, North Dakota, Oklahoma, South Carolina, and Wyoming — run their own separate apiary or specialty-crop registries rather than using FieldWatch. Check with your state department of agriculture directly.
Why would I register my hives if it’s not legally binding?
Beyond improving the odds an applicator checks for nearby hives before spraying, several participating states tie BeeCheck registration to eligibility for compensation programs if a documented pesticide-drift incident damages or kills registered colonies.
Is DriftWatch the same thing as state apiary registration?
No. Many states separately require beekeepers to register hives with a state apiary inspector for disease-control purposes; BeeCheck is a voluntary, additional listing specifically for pesticide-drift communication and is not a substitute for mandatory state apiary registration where it applies.
