Beekeeper recording varroa mite treatment details in a complete treatment log example with hive documentation
Accurate varroa treatment logs prevent compliance gaps and improve hive health management.

Varroa Treatment Log Example: What a Complete Record Looks Like

Beekeepers who review a sample treatment log before their first entry are 70% less likely to leave required fields blank. That gap exists because the abstract requirement to "keep records" doesn't tell you what a complete record actually looks like. This page shows you.

Below are worked examples of complete treatment log entries for five common treatment scenarios. Each example includes all 7 required fields plus the recommended additional fields that make your records genuinely useful beyond the minimum.

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

The 7 Required Fields (Every Treatment, Every Time)

  1. Date of treatment -- Not "fall 2025." The specific date: September 15, 2025.
  2. Product name -- The registered product name, not just the active ingredient.
  3. EPA registration number -- This is what state inspectors check. Auto-filled by VarroaVault for all registered products.
  4. Dose applied -- The actual amount you applied, in the units specified on the label.
  5. Colony ID -- Which specific hive(s) received this treatment.
  6. Reason for treatment -- Usually the pre-treatment count result. "Routine fall treatment" is acceptable for scheduled preventive treatments.
  7. PHI start date / super removal date -- When honey harvest becomes legally permissible after this treatment.

Example 1: OA Dribble on a Broodless Colony

| Field | Entry |

|---|---|

| Date | November 8, 2025 |

| Product | Api-Bioxal |

| EPA Registration Number | 87806-1 |

| Active Ingredient | Oxalic Acid Dihydrate |

| Application Method | Dribble |

| Dose | 50 mL of 3.2% solution (5 mL per occupied frame, 10 occupied frames) |

| Colony ID | Hive 3 (Apiary A) |

| Reason for Treatment | Broodless period detected November 6; pre-treatment count 1.8% |

| Pre-Treatment Count | 1.8% (Nov 5, alcohol wash, 300 bees) |

| Brood Status at Treatment | Confirmed broodless (inspected Nov 6) |

| Honey Super Status | Supers removed Sept 25 |

| PHI | 0 days -- no withholding period required |

| Notes | Temperature 52°F at application, bees clustered loosely |

Why this record works: It includes the mandatory fields plus the brood status confirmation (critical for dribble efficacy interpretation), the pre-treatment count that triggered action, and the supers-removed date that confirms PHI compliance.

VarroaVault feature: When you select "dribble" as the method and mark brood status as "broodless confirmed," VarroaVault auto-schedules a post-treatment count reminder for 30 days and marks the PHI as 0 days.

Example 2: Apivar Strip Application (Fall)

| Field | Entry |

|---|---|

| Date | August 8, 2025 |

| Product | Apivar |

| EPA Registration Number | 64771-2 |

| Active Ingredient | Amitraz 3.3% |

| Application Method | Strips, between brood frames |

| Dose | 4 strips (2 strips per brood box, 2 brood boxes present) |

| Colony ID | Hive 7 (Apiary B) |

| Reason for Treatment | Pre-treatment count 2.3% -- above threshold |

| Pre-Treatment Count | 2.3% (Aug 6, alcohol wash, 300 bees) |

| Brood Status at Treatment | Active brood present |

| Honey Super Status | Supers removed Aug 7 prior to treatment |

| Strip Removal Date | September 22, 2025 (42 days after application) |

| PHI Start Date | October 6, 2025 (14 days after strip removal) |

| Notes | 2 brood boxes at application. Strips placed parallel between frames 3-4 and 7-8 |

Why this record works: It captures the critical Apivar-specific fields: separate application date and strip removal date (because PHI is calculated from removal, not application), the actual frame placement for reference, and the super removal documentation.

VarroaVault feature: Apivar strip removal is a separate log entry. When you log strip removal, VarroaVault recalculates your PHI from that date and displays the earliest harvest date.

Example 3: MAQS (Formic Acid) Application

| Field | Entry |

|---|---|

| Date | July 18, 2025 |

| Product | MAQS (Mite Away Quick Strips) |

| EPA Registration Number | 83923-1 |

| Active Ingredient | Formic Acid 68.2% |

| Application Method | Strips on top bars |

| Dose | 2 strips (standard 7-day treatment) |

| Colony ID | Hive 12 (Apiary C) |

| Reason for Treatment | Pre-treatment count 3.1% -- above threshold during flow |

| Pre-Treatment Count | 3.1% (July 16, alcohol wash, 300 bees) |

| Brood Status at Treatment | Active brood present |

| Honey Super Status | Supers present (MAQS is approved for use with supers) |

| Temperature at Application | 72°F (within label range) |

| Strip Removal Date | July 25, 2025 (7-day treatment) |

| PHI Start Date | No withholding period for honey (0-day PHI) |

| Notes | Colony strong, 3 medium supers. Temperature forecast checked -- no days above 85°F in treatment window |

Why this record works: MAQS has strict temperature requirements. Recording the application temperature and confirming the forecast check documents that the treatment was applied correctly.

VarroaVault feature: MAQS entries prompt temperature confirmation before submission. The system flags a warning if your reported temperature is outside the label range.

Example 4: OA Vaporization Series (Brood-Present Protocol)

Because a 3-treatment OA vaporization series involves multiple events, each vaporization is logged separately. Here's what all three entries look like together:

| Field | Entry 1 | Entry 2 | Entry 3 |

|---|---|---|---|

| Date | Aug 12 | Aug 17 | Aug 22 |

| Product | Api-Bioxal | Api-Bioxal | Api-Bioxal |

| EPA Registration Number | 87806-1 | 87806-1 | 87806-1 |

| Method | Vaporization | Vaporization | Vaporization |

| Dose | 2.275g | 2.275g | 2.275g |

| Colony ID | Hive 5 | Hive 5 | Hive 5 |

| Reason | 3rd treatment in extended protocol started Aug 12 | Treatment 2 of 3 | Treatment 3 of 3 |

| Brood Status | Active brood | Active brood | Active brood |

| Notes | Pre-count 2.8% (Aug 10) -- first vaporization today | 5-day interval | Final vaporization -- post-count scheduled Sep 21 |

VarroaVault feature: When you log the first vaporization and mark it as "part of extended protocol," VarroaVault pre-populates reminders for treatments 2 and 3 at 5-day intervals, plus the post-treatment count at 30 days.

Example 5: Formic Pro (Lower-Dose Formic Acid)

| Field | Entry |

|---|---|

| Date | September 5, 2025 |

| Product | Formic Pro |

| EPA Registration Number | 83923-4 |

| Active Ingredient | Formic Acid 46.7% |

| Dose | 2 pads |

| Colony ID | Hive 1 (Apiary A) |

| Reason for Treatment | Routine fall treatment |

| Pre-Treatment Count | 0.9% (Sept 3, alcohol wash, 300 bees) |

| Temperature at Application | 68°F (within 50-79°F label range) |

| Treatment Duration | 10 days (remove pads Sept 15) |

| PHI | 0 days |

Using These Examples in VarroaVault

The treatment log example gallery in VarroaVault shows examples for OA dribble, OA vaporization, Apivar, MAQS, and formic acid. When you start a new treatment entry, the example for your selected product is available as a reference overlay -- you can see what a complete entry looks like while filling in your own data.

The how to track hive treatments digitally guide covers the full treatment entry process.

Frequently Asked Questions

What does a complete varroa treatment log look like?

A complete entry includes all 7 required fields (date, product name, EPA registration number, dose, colony ID, reason for treatment, PHI start date) plus the recommended contextual fields: pre-treatment count result, brood status at application, honey super status, and any temperature or condition notes relevant to the treatment. The examples above show what complete entries look like for the five most common treatment scenarios. VarroaVault's treatment form requires the mandatory fields and prompts for the recommended ones.

What are the required fields I should not skip in a treatment log?

The EPA registration number is the most commonly skipped required field and the one most likely to get your record rejected in a state inspection. State inspectors in 23 states have specifically reported rejecting records that lacked the registration number. After that, the dose field and the PHI date are most commonly incomplete. VarroaVault prevents these omissions by requiring all 7 fields before a treatment record can be submitted -- the EPA registration number auto-fills from the product selection, so there's no excuse for that one to be missing.

Does VarroaVault auto-fill some treatment log fields to save time?

Yes. When you select a product, VarroaVault auto-fills the EPA registration number and active ingredient. The standard dose auto-populates based on the product selection (though you can modify it). The PHI is calculated automatically from the treatment date based on the product's label requirements. For strip products, PHI is calculated from the strip removal date (logged separately) rather than the application date, matching the correct label interpretation.

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.

Related Articles

VarroaVault | purpose-built tools for your operation.