Why Every Apiary Needs Its Own Varroa Monitoring Schedule
Apiaries within 3 miles of each other can show mite count differences of up to 3% due to local reinfestation dynamics. That's not a minor variation. A 3% difference between adjacent yards means your treatment decisions for Yard A are completely wrong for Yard B if you're managing them identically.
Here's why per-apiary monitoring matters and how to implement it efficiently.
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
Why Mite Pressure Varies Between Locations
Reinfestation from neighboring operations: The single biggest driver of yard-to-yard variation is proximity to other beekeeping operations. An apiary within 1-2 miles of a high-mite operation receives constant reinfestation through robbing and drift. Another yard 5 miles away, isolated from other beekeepers, rebuilds mite populations much more slowly after treatment.
Local vegetation and forage patterns: Different forage patterns affect colony behavior. Yards near high-value forage that attracts robbing from neighboring colonies face higher reinfestation risk. Yards with isolated forage and minimal robbing pressure show slower mite rebuilding.
Microclimate effects: Local temperature patterns affect when brood rearing starts and stops. An apiary in a warm south-facing valley might have brood 3-4 weeks longer than one on an exposed hillside 2 miles away. The extended brood season means more mite reproduction cycles.
Hive quality variation: If you're moving stronger or weaker colonies to specific yards, the yard composition affects the average mite load. Higher-quality colonies maintained below threshold at one yard reduce the average; colonies acquired from unknown sources at another yard might be above average.
Apiary isolation: Truly isolated apiaries (3+ miles from other operations) show lower post-treatment reinfestation rates than yards in dense beekeeping areas. This directly affects how quickly mite counts recover after treatment.
What Happens When You Treat All Yards on the Same Calendar
The common approach is to treat all yards on the same date in August. This makes operational sense for batch treatment days. But if Yard 3 is in a high-reinfestation zone and already hit 3% in June while Yard 1 is at 1.5%, the August treatment date is 6 weeks late for Yard 3.
Alternatively, if you count one "representative" yard and extrapolate to all yards, you're making assumptions that may not hold. The yard you count may have different pressure characteristics than the yards you don't.
The outcome: yards with different pressure profiles get identical management. The high-pressure yard is under-managed; the low-pressure yard may be over-treated.
How to Build Per-Apiary Monitoring Schedules
Step 1: Profile each apiary for reinfestation risk.
For each yard, assess:
- Distance to nearest known beekeeping operations (use state apiary registration data if available)
- Historical mite count patterns (do counts spike faster here after treatment?)
- Presence of dearth periods that increase robbing (orchards, golf courses, suburban landscaping)
Step 2: Assign monitoring intensity based on risk profile.
High-risk yards (within 2 miles of other operations, history of rapid mite rebuilding): Count every 3 weeks during active season.
Medium-risk yards (2-5 miles from other operations, typical mite dynamics): Count monthly, standard HBHC recommendation.
Low-risk yards (isolated, slow mite rebuilding history): Count monthly during active season, with intensification in July-August.
Step 3: Treat each yard based on its own counts, not a unified calendar.
This is the key change. Rather than treating all yards on the same date, treat each yard when its count reaches threshold. Yard 3 at 3% in late July gets treated in July. Yard 1 at 1.5% waits for its August count to confirm before treating.
You still have treatment day efficiencies if multiple yards are ready on the same date. But you're not artificially synchronizing treatment to a calendar when the counts don't support it.
Setting Up Per-Apiary Monitoring in VarroaVault
VarroaVault's per-apiary monitoring calendar allows independent testing schedules for each location:
- Go to Apiary Settings for each apiary.
- Set the monitoring interval (weekly, bi-weekly, monthly, or custom).
- Each apiary's count reminders fire independently on its own schedule.
- Your dashboard shows each apiary's status separately, color-coded by its own threshold comparison.
For operations with 3 yards on different schedules:
- Yard 1: Monthly count reminders (May, June, July, August, September, October)
- Yard 2: 3-week count reminders during July-August (high pressure months), monthly otherwise
- Yard 3: 3-week count reminders year-round (high reinfestation risk)
Each yard shows its own last count date, trend graph, and threshold status in the dashboard. You can view all three yards simultaneously in the multi-apiary view.
Identifying Which Apiaries Need More Frequent Testing
After a full season of per-apiary data in VarroaVault, run the Apiary Comparison report. This shows:
- Average mite count by apiary at each seasonal checkpoint
- Post-treatment recovery rate (how quickly mite counts rebuild after treatment)
- Number of threshold breaches per apiary
- Treatment events per apiary
Apiaries with fast rebuilding, high average counts, or frequent threshold breaches are your high-pressure locations. These need more frequent monitoring and possibly more aggressive treatment protocols (like adding an extra OA vaporization cycle before the main fall treatment).
See also: Multi-apiary management software and Mite count tracking app.
Frequently Asked Questions
Should different apiaries have different varroa testing schedules?
Yes. Mite pressure varies significantly between apiaries based on reinfestation risk, local forage patterns, proximity to other beekeeping operations, and microclimate effects. Apiaries within 3 miles of each other can show count differences of up to 3%. Treating all yards on a unified calendar ignores these differences and leads to under-management of high-pressure yards and over-treatment of low-pressure ones.
How do I set up separate monitoring schedules per apiary in VarroaVault?
Go to Apiary Settings for each location and set the monitoring interval independently. Each apiary generates its own count reminders on its own schedule. The multi-apiary dashboard shows each yard's status independently, color-coded by its own threshold comparison. You can set high-risk yards to 3-week intervals while others remain on the monthly HBHC standard.
Which of my apiaries needs the most frequent testing?
Apiaries within 2 miles of other beekeeping operations, yards with history of rapid post-treatment mite rebuilding, and locations near dearth conditions that increase robbing need the most frequent testing. After one full season of data in VarroaVault, run the Apiary Comparison report to identify which yards have the highest average counts and fastest mite rebuilding patterns.
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.