Year Two Varroa Program: Refining Your Management Based on First-Year Data

Your first year of varroa management is mostly about establishing a baseline. You're learning the methods, figuring out your colonies' patterns, and getting comfortable with the calendar. Year two is different. Year two is when your varroa data becomes genuinely powerful.

If you logged your mite counts and treatments consistently through year one, you're now sitting on a record of how your colonies responded. Which treatments worked. Which colonies always ran high. Where you almost missed a critical window. That information, if you use it, can make your year two varroa program meaningfully better than year one.

Beekeepers who review their year-one data before planning year two reduce treatment failures by 40%. That number makes sense when you understand what the data reveals.

TL;DR

This guide covers key aspects of year two varroa program: refining your management based on f
Mite monitoring should happen at minimum every 3-4 weeks during active season
The 2% threshold in spring/summer and 1% in fall are standard action points based on HBHC guidelines
Always run a pre-treatment and post-treatment mite count to calculate efficacy
Treatment records including product name, EPA number, dates, and counts are required for state inspection compliance
VarroaVault stores all monitoring and treatment data with automatic threshold comparison and state export formatting

What Your Year-One Data Actually Tells You

Before you build your year two beekeeper varroa program, pull your records and look at four things.

1. Treatment Efficacy Scores

For each treatment you ran, compare your pre-treatment mite count to your post-treatment count. What percentage reduction did you achieve?

90%+ reduction: Treatment worked correctly
70-90%: Adequate, but worth reviewing application method
Below 70%: Either the treatment was applied incorrectly, or you have an early resistance signal

If you used Apivar and only achieved 60% reduction, that's not a failure to investigate later, that's something to act on before you apply Apivar again this season.

2. Rebound Rate

How fast did mites climb after treatment? A colony that rebounds to threshold levels in 6 weeks needs a different management approach than one that stays below threshold for 4 months.

Fast rebound typically means either heavy reinfestation from neighboring colonies or a high local mite pressure environment. Slow rebound might suggest some genetic resistance in the colony, worth noting if you're thinking about queen replacement.

3. Missed Windows

Were there points in the year where your mite count was higher than you'd have liked when you finally got around to treating? That's data on your calendar gaps. If you got to late September without a fall treatment and found counts at 5%, the fix for year two isn't a better treatment. It's an earlier trigger date.

4. Colony Outliers

Which colonies always ran high? Which ones barely needed treatment? Consistent outliers, in either direction, tell you something about genetics, location, or management that deserves attention in year two.

Refining Your Calendar

The most common year-two improvement is calendar adjustment. Year one often has treatment timing driven by convenience ("I finally got out there") rather than biology. Year two should be driven by data.

Work backwards from your year-one records:

When did mite loads first hit 1% in spring? If it was consistently late April, your first spring count should be in late March so you can treat before the threshold breach, not after.

When did fall build-up start accelerating? If counts were spiking by late July, your fall treatment window should open in early August, not September.

What was your average time from treatment to below-threshold count? If OA vaporization took you 5 weeks to fully knock down mites, build that 5-week lag into your planning so you're not caught with supers on during treatment.

VarroaVault's year-over-year analysis compares your second-year performance against year one automatically, flagging where timing improved and where it didn't.

Evaluating Treatment Rotation

Year two is also when treatment rotation starts to matter. If you used Apivar both cycles in year one, rotating to a different class in year two isn't just good practice, it's resistance insurance.

Look at your year-one treatment log:

What classes did you use? (Amitraz / formic acid / oxalic acid / thymol)
Were you in the same class for both cycles?
Did any treatment show below-expected efficacy?

Build year two around a different lead treatment if you used the same synthetic two cycles in a row. Most beekeepers find a pattern of alternating: one synthetic cycle (Apivar or Apistan), one organic cycle (OA or formic acid), rotating every season.

Addressing Colony-Level Problems

Chronically High Colonies

If specific colonies were consistently above threshold despite treatment, they need individual attention in year two. Options:

Requeen with a hygienic or VSH queen line. Genetics play a real role in mite population growth. A new queen from a mite-resistant line can change a colony's trajectory.
Check for reinfestation pathways. Is this hive close to a feral colony or a poorly-managed neighbor? Reinfestation from outside can overwhelm good treatments.
Increase count frequency. If you were checking every 8 weeks in year one, drop to every 6 weeks for problem colonies in year two.

Consistently Low Colonies

Don't ignore the colonies that performed well. Document what's different about them. Is the queen line different? Is the location different? Is there less forager sharing with high-mite colonies?

If you've been tracking queen introductions alongside mite counts in VarroaVault, you may see a clear correlation between queen source and mite trajectory. That's selection data you can use.

What Should Change in My Year-Two Varroa Program?

This depends on what year one showed you. But here are the most common year-two refinements:

Earlier trigger dates. Most first-year beekeepers treat reactively, after counts get high. Year-two beekeepers treat before threshold breach, based on trend data.

Smarter treatment selection. Year one is often whatever was recommended at the bee club. Year two is matched to colony brood status, temperature window, super status, and resistance history.

Better post-treatment verification. Many year-one beekeepers skip the post-treatment count. Year-two beekeepers know it's the only way to confirm the treatment worked. It's non-negotiable.

Queen management integration. Year two is when you start connecting your requeening schedule to your mite history. High-mite colonies get priority for genetic upgrades.

Building Your Year-Two Plan in VarroaVault

VarroaVault's calendar builder for refining varroa management in the second year works from your existing treatment history. When you open the year-two planning view:

Your year-one counts appear on a timeline so you can see mite trajectory by month
Your efficacy scores are displayed next to each treatment event
The system suggests calendar adjustments based on where you were early or late relative to threshold
A treatment rotation recommendation flags if you used the same class in both cycles

You're not starting from scratch, you're building on evidence.

A Real Pattern Worth Looking For

Pull your year-one data and look specifically at the August-September window. Did you treat? When? What were counts at treatment time versus what they were at first winter inspection?

This window is the single most consequential decision in the annual varroa calendar. Colonies that go into winter with low mite loads have dramatically better survival rates than those that don't. If your year-one records show you were late to this window, make a specific commitment for year two: first fall count by August 1, treatment decision by August 15.

That one change, earlier fall treatment based on your own historical data, is often the highest-value adjustment a second-year beekeeper can make.

How do I use my year-one varroa data to improve?

Start by reviewing four metrics: your efficacy score for each treatment (pre vs. post count percentage drop), your rebound rate after treatment, the timing of your worst late-season counts, and which colonies consistently ran high. Those four data points will show you whether your calendar needs adjustment, whether any treatments underperformed, and which colonies need genetic intervention. Import your counts into a timeline and look for patterns. The data tells you more than any calendar template can.

What should change in my varroa program in year two?

The most impactful changes are usually calendar-based: earlier trigger dates based on when you actually saw threshold breaches in year one, and a harder commitment to the fall treatment window. Beyond timing, year two should include treatment class rotation if you used the same synthetic twice in year one, post-treatment efficacy verification as a non-negotiable step, and a plan for chronically high colonies that may need requeening.

How does VarroaVault help me analyze my varroa history?

VarroaVault's year-over-year analysis view overlays your year-one and year-two count timelines, shows efficacy scores for each treatment event, and flags calendar gaps where mite loads were rising without intervention. The treatment rotation tracker shows your class history across cycles and recommends when to switch. The colony comparison view lets you sort colonies by average mite load and identify outliers worth addressing.

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.

Getting Started

Before spring buildup, run through your year-one records and build a specific plan, not "I'll treat when mites get high" but "I'll count by March 15, treat if above 1%, target August 1 for my fall treatment trigger."

For the foundational year-one framework this builds on, see the first-year beekeeper varroa management guide. For calendar planning tools, the varroa treatment calendar builder walks you through building a full-season schedule from your historical data.

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.