How to Set Up a Varroa Resistance Monitoring Program for Your Apiary
Resistance doesn't announce itself. It creeps in over 3-5 years as declining efficacy scores, treatments that used to achieve 95% reduction that now achieve 75%, populations that recover faster after treatment than they used to. Resistance can be detected as declining efficacy 1-2 years before it reaches the point of treatment failure -- and that 1-2 year window is your opportunity to rotate out of the problem before it costs you colonies.
Setting up a personal resistance monitoring program isn't complicated. It requires consistent pre- and post-treatment counts, an accurate efficacy calculation, and a trend tracking system that surfaces the signal before it's obvious.
TL;DR
- Varroa monitoring should happen at minimum once per month during active season (every 3-4 weeks)
- Sticky board counts are the least accurate method; alcohol wash is the gold standard
- The 2% threshold in spring/summer and 1% in fall are widely recommended action points
- Monitoring before and after every treatment allows efficacy calculation and resistance detection
- A count from the outer frames or entrance produces lower, less accurate results than brood nest samples
- VarroaVault stores every count with date, method, and result to build a trend dataset over multiple seasons
What Resistance Actually Is
Acaricide resistance in varroa is the same mechanism as antibiotic resistance in bacteria: repeated exposure to a toxin selects for individuals with natural tolerance, and those individuals reproduce more successfully. Over time, the tolerant subpopulation becomes dominant.
The key difference from antibiotic resistance is that varroa resistance is often regional and local at the same time. A population in your apiary may develop resistance to a product that still works perfectly in an apiary 20 miles away. This is why monitoring your own efficacy data -- not just relying on regional resistance reports -- is the most reliable approach.
Resistance is also reversible if caught early. Rotating away from an active ingredient class for 2-3 years allows susceptible mites to repopulate from neighboring sources, restoring efficacy when you return to that product class.
The Core Protocol: Calculate Efficacy After Every Treatment
The foundation of resistance monitoring is consistent efficacy calculation. The formula is simple:
Efficacy % = ((Pre-treatment count - Post-treatment count) / Pre-treatment count) x 100
Example: Pre-treatment count of 3.5%, post-treatment count of 0.3%. Efficacy = ((3.5 - 0.3) / 3.5) x 100 = 91.4%.
Benchmarks:
- Above 95%: Excellent, no concern
- 90-95%: Good, normal variation
- 80-89%: Monitor closely, consider rotation sooner
- Below 80%: Strong resistance signal; rotate immediately and investigate
The catch: you need a minimum pre-treatment count to calculate meaningful efficacy. A pre-treatment count of 0.5% that drops to 0.1% gives an 80% efficacy score -- but at those low absolute numbers, statistical noise dominates. Set a rule in your resistance monitoring program that efficacy calculations are only interpreted when the pre-treatment count is above 1.5%.
Building Your Resistance Trend Record
A single efficacy data point doesn't mean much. A trend over 3-4 treatment events is where the signal becomes clear.
Log your efficacy score for every treatment event and by product name. VarroaVault's resistance trend report graphs treatment efficacy scores over 3 years to show declining efficacy before resistance is confirmed. You're looking for:
- Consistent scores at one level: Normal, healthy pattern. Efficacy is stable.
- Gradual decline over 3-4 seasons: Early resistance signal. Rotate now.
- Sudden drop: May indicate a different problem (incorrect application, high reinfestation, extreme resistance). Investigate before concluding resistance.
The trend graph needs at least 3-4 data points per product to be meaningful. This is why you need at least 2-3 years of consistent pre- and post-treatment counting before the resistance monitoring program produces actionable insights.
Setting Up the Protocol in Your Apiary
Step 1: Define your pre-treatment count window.
Count every colony (or a representative sample) within 7 days before treatment starts. Log these as "pre-treatment baseline" counts in VarroaVault.
Step 2: Apply treatment exactly according to label.
Resistance monitoring data is only valid if your application was correct. Underdosing artificially inflates the resistance signal. Record your application date, product, dose, and any deviations from standard protocol.
Step 3: Post-treatment count timing.
For strip products (Apivar, Apistan): count 3-4 weeks after strip removal.
For formic acid: count 21-28 days after treatment completion.
For OA vaporization extended protocol: count 30 days after the last vaporization.
Step 4: Calculate and record efficacy.
Enter both counts in VarroaVault. The system calculates efficacy automatically and adds the data point to your trend graph.
Step 5: Compare to your historical record.
After each treatment event, look at your trend graph for that product. Is the current efficacy score consistent with previous seasons, or lower?
What Efficacy Decline Rate Should Trigger Rotation?
The general guideline: if your efficacy score for a given product class drops by 10 percentage points or more from your historical average, or if you record two consecutive treatment events below 80% efficacy, rotate immediately.
Don't wait for a single low efficacy score to confirm the pattern. One low reading could be a measurement error, reinfestation, or an application problem. Two consecutive low readings in successive treatment events are a much stronger signal.
When you rotate, document the rotation in your records. Note the date, the reason (declining efficacy), and the product you're switching to. When you return to the original product class 2-3 years later, compare your efficacy scores to the baseline you established before the rotation.
The Mite Resistance Management Connection
Your apiary-level resistance data doesn't exist in isolation. The [treatment rotation planning](/treatment-rotation-planning) system in VarroaVault connects your efficacy trend data to your rotation plan, so if efficacy is declining for a product you're scheduled to use next season, the system surfaces a rotation recommendation before you make the treatment purchase.
State apiarists in many states are interested in apiary-level resistance data. If you experience consistent treatment failures with a specific product class, reporting to your state apiarist contributes to the national resistance surveillance network.
Frequently Asked Questions
How do I know if resistance is developing in my apiary?
The clearest signal is declining post-treatment efficacy over 2-3 successive treatment seasons. Calculate your efficacy score after every treatment event using the formula: ((pre-treatment count - post-treatment count) / pre-treatment count) x 100. A healthy score is above 90%. If your scores for a specific product class are declining -- for example, from 93% in 2023 to 88% in 2024 to 79% in 2025 -- that's a strong resistance signal. Resistance can be detected this way 1-2 years before treatment failure occurs.
What efficacy decline rate should trigger a rotation?
Rotate when: your efficacy for a product class drops below 80% in a single treatment event with a pre-treatment count above 1.5%, OR when you see two consecutive treatment seasons where efficacy is 10+ percentage points below your established baseline for that product. Don't wait for full treatment failure. The point of resistance monitoring is to catch the trend early enough to rotate while the current product still provides some benefit, not to wait until it stops working entirely.
Does VarroaVault generate a resistance trend report?
Yes. VarroaVault's resistance trend report graphs your treatment efficacy scores over time, organized by active ingredient class. When you have at least 3 treatment events logged for a product class, the trend line becomes visible. The report flags declining trends automatically when efficacy drops below your historical average by 10+ percentage points, and the rotation planner uses your trend data to recommend appropriate rotation timing.
How do I know if my varroa treatment is working?
Run a mite count 2-4 weeks after the treatment ends and compare it to your pre-treatment count. The efficacy formula is: ((pre-count - post-count) / pre-count) x 100. A result above 90% indicates effective treatment. Results below 80% should trigger investigation for possible resistance, application error, or reinfestation. Log both counts in VarroaVault to track efficacy trends across treatment cycles.
How often should I check mite levels in my hives?
At minimum, once per month (every 3-4 weeks) during the active season. Increase to every 2 weeks when counts are near threshold or after a treatment to verify it worked. In fall, monitoring frequency matters most because the window to treat before winter bees are raised is narrow. VarroaVault's monitoring reminders can be set to your preferred interval for each apiary.
What records should I keep for varroa management?
Each record should include: date of count or treatment, hive identifier, monitoring method used, number of bees sampled, mites counted, infestation percentage, treatment product name and EPA registration number, dose applied, treatment start and end dates, and PHI end date. State apiarists typically expect this level of detail during inspections. VarroaVault captures all of these fields in a single log entry.
Sources
- American Beekeeping Federation (ABF)
- USDA ARS Bee Research Laboratory
- Honey Bee Health Coalition
- Penn State Extension Apiculture Program
- Project Apis m.
Get Started with VarroaVault
The information in this guide is most useful when you have your own mite count data to apply it to. VarroaVault stores every count, flags threshold crossings automatically, and builds the treatment history you need for state inspections and effective management decisions. Start your free trial at varroavault.com.