Varroa Scouting Frequency for Commercial Beekeepers: How Often to Test 300 Hives
Testing 15% of hives per apiary using stratified random sampling provides 95% confidence in apiary-level threshold status. This statistical standard -- 15% random sample for 95% confidence -- is the practical foundation for commercial varroa scouting programs that can't test every hive every month.
For a beekeeper managing 300 hives across 20 apiaries, monthly individual testing is 300 alcohol washes per month -- roughly 150 hours of testing time. That's not feasible. Representative sampling, sentinel hive programs, and GPS-prioritized testing reduce that to a manageable number without sacrificing the statistical reliability that makes the data useful.
TL;DR
- Commercial operations managing 50+ hives cannot rely on per-hive manual records without significant time investment
- Treatment efficacy must be tracked across yards, not just individual hives, to detect resistance patterns
- USDA APHIS and state apiarists increasingly request documented treatment protocols for commercial inspections
- PHI compliance across multiple apiaries and multiple treatments requires a systematic tracking system
- VarroaVault's commercial tier supports multi-yard management with yard-level reporting and bulk data entry
- Generating a treatment history report for all apiaries takes under 60 seconds in VarroaVault
The Sampling Math
The statistical relationship between sample size, confidence level, and population size is well-established. For varroa monitoring, the relevant question is: how many hives do I need to test in an apiary to be 95% confident that my sample result represents the apiary-level threshold status?
The answer depends on apiary size:
| Apiary Size | 15% Sample | Required Tests for 95% Confidence |
|---|---|---|
| 10 hives | 1-2 hives | 4-5 hives |
| 20 hives | 3 hives | 6-8 hives |
| 30 hives | 4-5 hives | 8-10 hives |
| 50 hives | 7-8 hives | 10-12 hives |
| 100 hives | 15 hives | 15-18 hives |
The confidence interval levels off at larger apiary sizes because you're sampling from the same statistical distribution. Testing 18 hives from a 100-hive apiary gives you nearly the same confidence as testing 18 from a 50-hive apiary, because the variance in mite load across hives tends to be similar regardless of total apiary size.
For practical commercial scouting, testing 15% of hives per apiary per month gives you a statistically reliable picture of apiary-level mite pressure with roughly 95% confidence in threshold detection.
Stratified Random Sampling
Random sampling from the full apiary is better than convenience sampling (testing the hives nearest the truck) but still less efficient than stratified random sampling.
Stratified random sampling divides your apiary into subgroups (strata) and samples proportionally from each:
Stratification by colony age: Young colonies (first-year packages or nucs) tend to have lower mite loads than established colonies. Stratify your sample to include representation from each age cohort.
Stratification by colony history: Colonies with a documented history of elevated mite counts should be sampled at higher rates than colonies with consistent low counts. Your VarroaVault records tell you which colonies are chronic high-mite outliers -- include those in every testing round.
Stratification by location within the apiary: Colonies nearest the apiary perimeter are more exposed to reinfestation from neighboring operations. Include perimeter colonies disproportionately in your sample.
A stratified sample of 15% of hives that overweights these risk-stratified groups will catch threshold breaches that a purely random 15% might miss.
Sentinel Hive Programs
Sentinel hives are designated indicator colonies monitored more frequently than the rest of the apiary. A properly selected sentinel hive detects apiary-level threshold breaches an average of 10 days earlier than random sampling.
Selecting sentinel hives:
The best sentinel hive in an apiary is one that historically runs at or slightly above the apiary average mite count. A colony that's reliably in the middle-to-upper range of mite load for the apiary serves as a reliable early warning indicator -- when the sentinel hits threshold, the rest of the apiary is close behind.
Avoid selecting your lowest-count colony as a sentinel. Low-mite colonies that stay low often do so because of queen genetics or location advantages that don't represent the apiary as a whole.
Sentinel testing frequency:
For a 30-hive apiary, a reasonable program might be:
- 2-3 designated sentinel hives tested every 3-4 weeks
- Full apiary representative sample (5-6 hives) every 6-8 weeks
- All hives tested at pre-treatment August baseline
This schedule keeps you informed about apiary-level trends without testing every hive every month.
GPS-Prioritized Testing
For beekeepers managing apiaries across a geographic area, not all apiaries face the same reinfestation pressure or mite dynamics. GPS-based prioritization focuses your testing resources on the apiaries with the most risk.
Higher-frequency testing apiaries:
- Apiaries within 2 miles of known untreated or poorly managed operations
- Apiaries in high-density beekeeping areas (near migratory operations, community apiaries)
- Apiaries historically showing above-average mite loads
- Apiaries with recent treatment failures
Lower-frequency testing apiaries:
- Isolated apiaries with no neighboring managed operations within 2-3 miles
- Apiaries with consistently strong treatment efficacy history
- Apiaries with documented low mite loads across multiple seasons
A risk-stratified testing schedule might test high-risk apiaries monthly while testing low-risk isolated apiaries every 6-8 weeks, with all apiaries receiving a full representative sample at pre-treatment August and post-treatment September.
Building a Commercial Scouting Calendar
A practical commercial scouting calendar for a 200-hive operation across 10 apiaries might look like:
April: Full representative sample (15%) from all 10 apiaries. Spring baseline.
May-June: Sentinel hives at each apiary (2-3 hives). Full representative sample for any apiary where sentinel hit 1.5%+.
July: Full representative sample (15%) from all apiaries. Emergency threshold gate -- any apiary where sample average hits 2% gets full treatment within 7-14 days.
August 1-10: Full individual testing of all hives across all apiaries. Pre-treatment baseline for fall treatment efficacy calculation.
September: Full representative sample 30-45 days after treatment. Efficacy calculation for all apiaries.
October-November: Sentinel hives at each apiary for broodless period check.
This schedule produces roughly 400-500 individual mite tests per season across a 200-hive operation -- approximately 2 tests per hive per season -- while providing statistically reliable data at every decision point that matters.
Crew Management and Standardization
Commercial operations with crew conducting monitoring face a quality control challenge that hobby beekeepers don't: different people using slightly different methods produce results that aren't directly comparable.
Standardization requirements for crew-conducted counts:
- Consistent sample size (300 bees per sample)
- Consistent alcohol concentration and soak time
- Consistent sampling location (brood nest frames, not entrance bees)
- Written protocol reviewed at season start
Counts taken by different crew members with unstandardized methods can vary by 0.5-1% for the same colony. At typical threshold levels, that variance is the difference between treating and not treating.
VarroaVault's representative sampling tool calculates the minimum number of hives to test per apiary for statistical significance based on your apiary size and the confidence level you specify. It also supports sentinel hive designation, which automatically increases testing frequency for flagged hives and connects their counts to apiary-level alerts. The commercial beekeeper management software overview covers the full set of commercial-scale features. The mite count tracking app guide covers how to log representative sample data and calculate apiary-level averages.
Frequently Asked Questions
How many hives do I need to test in a commercial operation?
Testing 15% of hives per apiary using stratified random sampling provides 95% confidence in apiary-level threshold status. For a 20-hive apiary, that's 3 hives tested per visit. For a 50-hive apiary, 7-8 hives. For 100 hives, 15-18 hives. The sample should be stratified to include disproportionate representation from high-risk subgroups: established colonies, colonies with documented high-mite history, and perimeter colonies most exposed to reinfestation. At pre-treatment August baseline, test every hive individually rather than relying on representative sampling.
What is representative sampling for varroa monitoring?
Representative sampling is a statistical approach to monitoring that tests a defined subset of hives in an apiary rather than every individual hive. The subset is chosen to reflect the full range of conditions in the apiary -- different colony ages, locations, and mite histories. A properly chosen representative sample of 15-20% of hives provides data that's statistically reliable at the apiary level for threshold detection purposes, making monthly full-apiary monitoring practical for operations that couldn't test every hive every month without sacrificing other management tasks.
Does VarroaVault support sentinel hive designation for commercial monitoring?
Yes. VarroaVault allows you to flag specific hives as sentinels within each apiary. Sentinel hives automatically receive increased testing frequency reminders, and their count results are displayed prominently in the apiary dashboard. When a sentinel hive hits the action threshold, VarroaVault generates an apiary-level alert suggesting a full representative sample to confirm whether the sentinel result represents the broader population. Sentinel count data feeds into the apiary trend analysis separately from the general hive pool, making sentinel performance visible over time.
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
Commercial beekeeping operations need a varroa management system that scales across yards, generates compliance-ready reports, and flags resistance before it costs you colonies. VarroaVault was built for exactly this kind of multi-apiary operation. Start your free trial at varroavault.com and see how it fits your operation.