Varroa Monitoring System: Building a Routine That Sticks

Beekeepers who commit to 6 annual counts catch 90% of threshold breaches versus 55% for those who count only when concerned. The difference is not technique -- it's consistency. A monitoring system that you actually execute on a fixed schedule outperforms a theoretically ideal system that you only use when something looks wrong.

This guide builds your minimum viable monitoring routine: 6 mandatory count dates, the thresholds that apply at each one, and the system design that makes all 6 happen without relying on memory or motivation.

TL;DR

Treatment decisions should always be triggered by a mite count result, not a fixed calendar date
Different treatments have different temperature requirements, PHI restrictions, and brood penetration capabilities
Always run a post-treatment count 2-4 weeks after treatment ends to calculate efficacy
Efficacy below 80% warrants investigation -- possible resistance, application error, or reinfestation
Rotate treatment chemistry to prevent resistance buildup across successive cycles
VarroaVault logs treatment events, calculates efficacy, and flags when rotation is recommended

Why 6 Counts and Not More

Extension beekeeping programs often recommend monthly counts from April through October -- seven counts per season. That's the optimal protocol for research apiaries. For working beekeepers with jobs, families, and hives spread across multiple locations, seven counts is aspirational in a way that leads to zero counts after the first missed one.

Six counts is the number that a structured review of commercial beekeeper data identifies as the minimum that catches the breaches that matter. The six events are timed to align with the moments when mite population dynamics shift most dramatically -- and when the consequences of missing a high count are most severe.

A missed count in early June is recoverable. A missed count in August is not. Your system needs to ensure the August count happens above all others.

The 6 Mandatory Count Dates

Count 1: April Baseline

When: First week you open hives for spring inspection, typically April 1-15 in zones 5-6, March 15 to April 1 in zones 7-8.

What you're measuring: Your starting point for the season. The winter cluster has broken, the queen has resumed laying, and brood is expanding. Your April count tells you what survived winter and whether any colonies came through with elevated mite loads.

What to do with it: An April count below 1% is ideal -- watch and monitor monthly. A count of 1-2% in April suggests moderate starting pressure that will require careful summer tracking. Above 2% in April is elevated for this point in the season and warrants logging with a plan to recount in 4-6 weeks and treat by June if the trend is rising.

Count 2: May-June Pre-Flow

When: 4-6 weeks after your April baseline, before your main nectar flow begins.

What you're measuring: The trend from April. Mite populations grow at 2-3x per month during active brood-rearing. A colony at 0.5% in April can be at 1.5% by May if conditions are favorable for mite reproduction. The pre-flow count confirms whether your April baseline was stable or growing.

What to do with it: If your count has doubled or more from April, the trend is aggressive. Your treatment window is narrowing. If your count is flat or only slightly elevated, you're on track for a summer monitoring cadence.

Count 3: July Mid-Season

When: July 1-15.

What you're measuring: Mid-season mite pressure at the point when any elevation becomes urgent. A 2% count in July requires action within 7-14 days. A 3%+ count in July is a crisis requiring immediate response regardless of honey flow status.

This is the count that beekeepers most often skip because July is busy with honey supers and summer management. Missing July means arriving at August without knowing where your colonies stand -- and August is when the consequences become permanent.

What to do with it: Below 2%: track closely and prepare for your August treatment. At 2-3%: treat within 14 days using a product compatible with your current super status. Above 3%: emergency treatment immediately.

Count 4: Pre-Treatment August Baseline

When: August 1-10, before your fall treatment begins.

What you're measuring: Your starting point for the fall treatment. This count establishes the "before" number that you'll use to calculate treatment efficacy 3-4 weeks later.

This is the most important count of the year. August mite loads determine winter bee quality. Every colony above 1% in August should be treated immediately. Every colony should receive an August treatment regardless of count results -- a low count in August doesn't mean treatment isn't warranted.

What to do with it: Log the count, begin treatment August 1-15, schedule your post-treatment count for 30-45 days later.

Count 5: Post-Treatment Verification (September)

When: 30-45 days after your August treatment start date.

What you're measuring: Treatment efficacy. Calculate: ((pre-treatment count - post-treatment count) / pre-treatment count) x 100. You're looking for above 90% efficacy. Below 80% efficacy warrants investigation for resistance, reinfestation, or application error.

What to do with it: An efficacy above 90% with a post-treatment count below 0.5% is a good outcome. An elevated post-treatment count (above 1%) requires a second treatment or a resistance investigation. Log your efficacy calculation now -- you'll use it for product rotation decisions next year.

Count 6: October-November Broodless Check

When: When you confirm or suspect the colony has gone broodless, typically late October to mid-November in zones 5-6.

What you're measuring: Your winter starting point and the opportunity for a clean-up OA dribble.

What to do with it: A confirmed broodless colony at above 1% is worth treating with an OA dribble before cluster formation. One dribble on a broodless colony achieves 90-97% efficacy and can drive mite loads to near-zero before winter. A colony below 0.5% at this stage is in good shape for winter.

Scheduling: From Intention to Action

The gap between "I plan to count 6 times this year" and "I counted 6 times this year" is a system design problem. Three things that close the gap:

Fixed calendar dates, not floating intentions. "I'll count in July when things calm down" doesn't work. "I count on July 10 every year" does. Block specific dates in your calendar before the season starts.

Same-day counting. If you're opening a hive anyway, bring your counting supplies. The incremental time for a mite wash during a routine inspection is 15 minutes. The activation energy to make a special trip for a count is much higher.

Written logging within 24 hours. Count data that isn't logged is lost. A count you remember as "it was low, maybe 0.5%" two months later is worthless for trend tracking. Log date, hive ID, method, bee count, mite count, and result percentage the same day you count.

System vs Willpower

A monitoring system that relies on your motivation to stay consistent will fail in a busy summer. The design principle for a durable routine is: make the system do the work that willpower currently does.

Automatic reminders remove the reliance on memory. A pre-scheduled count date removes the decision about whether today is a good time to count. A habit of logging immediately removes the step of trying to recall what you found later.

The varroa monitoring frequency by season guide explains the biology behind each count timing in detail. The mite count tracking app overview covers how to set up automated reminders and trend alerts in VarroaVault.

VarroaVault's minimum viable monitoring plan covers all 6 mandatory count events with automatic reminders for each. When it's time to count, you get a notification with the date, the hive, and what threshold to watch for. When you log the result, the system tells you what it means and what comes next.

When Life Gets in the Way

Inevitably, a count gets missed. Your July 10 date falls during a family event, and you don't count until July 20. What then?

A 10-day slide on a non-August count is usually manageable -- you've delayed some information but not lost the window. Count as soon as you can and use the delayed result.

Missing your August count entirely is a different problem. If you arrive at September without a pre-treatment count, you've lost the ability to calculate treatment efficacy. Treat anyway -- an August or early September treatment on a colony of unknown mite load is still better than no treatment -- but acknowledge that you've lost the verification data.

The system isn't perfect even when followed exactly. But a system that catches 5 out of 6 events reliably outperforms an ideal 7-count plan that produces 2 actual counts.

Frequently Asked Questions

What is the minimum number of mite counts I should do per year?

Six counts per year represents the minimum that catches 90% of threshold breaches before they cause irreversible damage. The six events are: April baseline, May-June pre-flow, July mid-season, August pre-treatment, September post-treatment verification, and October-November broodless check. Each serves a specific purpose in tracking mite population dynamics and verifying treatment outcomes. Fewer than 6 annual counts significantly increases the risk of missing a threshold breach during the critical summer buildup period.

What are the 6 most important mite count dates?

April (baseline after winter), May-June (pre-flow trend check), July (mid-season emergency threshold gate), August 1-10 (pre-treatment baseline before fall treatment), September (post-treatment efficacy verification 30-45 days after August treatment), and October-November (broodless period clean-up assessment). The August count is the most consequential -- it establishes your fall treatment baseline and determines whether your winter bee cohort will be protected. Missing August is the single most costly monitoring gap a beekeeper can have.

Does VarroaVault remind me about all 6 key monitoring events?

Yes. VarroaVault's minimum viable monitoring plan covers all 6 mandatory count events with push notification reminders sent at the appropriate time for your location and climate zone. When you log a count result, the system calculates what it means in seasonal context, tells you whether you're above or below threshold, and schedules your next reminder automatically. The system doesn't require you to remember when to count -- it tells you when the window is open.

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.