Finding Gaps in Your Treatment Records: A Self-Audit Guide

Most beekeepers who audit their paper records find at least one treatment they logged incorrectly or not at all. That number is 73% based on surveys of beekeepers who completed a formal self-audit, and it probably understates the real picture because many beekeepers never audit at all. If you've been keeping records for more than one season, there's a good chance something got missed, misdated, or left incomplete.

This guide walks you through a practical self-audit process. It covers what to look for, which gaps matter most, and how to close the holes in your records before they become a compliance problem.

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 Record Gaps Matter More Than You Think

A missing treatment entry feels like a minor paperwork issue until it isn't. Treatment gaps can affect regulatory compliance if you're in a state that requires documented treatment history. They affect your PHI tracking, because if you can't confirm when you treated, you can't confirm when it's safe to harvest. They affect your understanding of efficacy, because if you don't have a baseline and a follow-up count, you have no idea whether the treatment worked.

The worst-case scenario is an insurance claim or state inspection where you're asked to document your treatment history and the records have holes. That's when a missing entry stops being an inconvenience and becomes a real problem.

The Self-Audit Checklist

Work through your records colony by colony. For each hive, ask:

Do I have a mite count before each treatment?

A treatment entry without a preceding count means you treated without knowing whether treatment was necessary. That's not necessarily wrong, but it's a gap in the documentation chain. If you can recall the approximate count from memory, log it retroactively with a note.

Is each treatment entry complete?

A complete treatment record includes: product name, active ingredient, dose, application method, date, colony ID, and start/end of the pre-harvest interval. Check each treatment entry against this list. If anything is missing, fill it in.

Do I have a follow-up count after each treatment?

Post-treatment counts close the loop. They confirm efficacy or flag a failure. If you applied a treatment and never counted again, you don't know whether it worked.

Are there unexplained gaps in inspection dates?

If a hive has inspection records in April and then again in August with nothing in between, what happened in May, June, and July? Either the colony wasn't inspected, which is a management gap, or it was inspected but not recorded. Either way, that's worth noting.

Do all records have dates?

Undated entries are nearly useless for compliance purposes. If you have entries with "did OA dribble in late October" instead of an actual date, try to narrow it down and log a specific date with a note explaining the approximation.

Filling Gaps Retroactively

You can fill most record gaps retroactively if you act before memory fades entirely. Useful sources for reconstructing dates include:

• Purchase receipts for treatments (which show when you bought them)
• Photo metadata from hive inspection photos on your phone
• Calendar entries or text messages from the period in question
• Weather records (if you know treatment required warm weather, you can narrow the date range)

Log retroactive entries with a clear note: "Entry added retroactively based on purchase receipt dated X. Treatment applied approximately Y." This preserves the honesty of the record while still closing the gap.

How VarroaVault Prevents Future Gaps

The record completeness audit tool in VarroaVault flags hives with missing count dates, incomplete treatment entries, or unsigned PHI records. Rather than waiting until you do a manual audit and find the gaps, the software surfaces them in real time.

When you enter a treatment, VarroaVault prompts you for all required fields before saving. If you try to save an incomplete entry, it flags what's missing. If a hive's count date is overdue based on your monitoring schedule, it appears in your dashboard. You can also learn how to track hive treatments digitally to understand how a digital workflow differs from paper-based approaches.

This doesn't mean you'll never miss an entry, but it dramatically reduces the chance. The system is built to notice what you forget.

Reviewing for Systematic Patterns

Once you've done a colony-by-colony audit, step back and look for patterns. Are the gaps concentrated in a particular month? That might tell you something about your workflow in that period. Are certain types of records consistently missing? Maybe your inspection form doesn't prompt for follow-up counts. Are gaps more common in your second apiary than your first? Distance and inconvenience are common culprits.

Understanding the pattern of your gaps helps you fix the cause, not just the individual missing records. Check your beekeeping record keeping requirements to understand what your state requires, then compare that against what your audit revealed.

Setting Up to Avoid Gaps Going Forward

The goal of the self-audit isn't just to find and fix what's already missing. It's to identify the moments in your workflow where records are most likely to slip and build a better system around them.

A few practical changes that close most gaps:

• Log inspections immediately on your phone rather than writing notes to transfer later
• Set reminders for follow-up counts at the time you enter a treatment
• Review all hive records at the start of each month to catch anything that slipped

If you're still using paper, that's fine, but the transfer step from paper notes to a permanent record is where the most gaps occur. Whatever system you use, remove as many transfer steps as possible.

Frequently Asked Questions

How do I find gaps in my varroa treatment records?

Go through your records colony by colony and check for four things: a mite count before each treatment, a complete treatment entry with all required fields, a follow-up count after each treatment, and consistent inspection dates without unexplained long gaps. Also check that every treatment entry has a specific date, not just a month or season. If you find entries that are incomplete or missing entirely, flag them for correction. Working backwards from receipts, photo metadata, and calendar records can help you reconstruct approximate dates for retroactive entries.

Does VarroaVault flag incomplete or missing treatment records?

Yes. VarroaVault's record completeness audit tool actively monitors your records and surfaces hives that have missing count dates, incomplete treatment entries, or PHI records that haven't been confirmed. Rather than waiting until you run a manual audit, the system flags these issues as they develop. When you enter a treatment, all required fields must be completed before the entry saves. This prevents the most common type of gap, which is a partially completed record that gets saved and forgotten.

How do I complete a record gap in VarroaVault retroactively?

In VarroaVault, you can add retroactive entries to any hive record. Navigate to the hive's history, select the appropriate date, and enter the missing information. The system allows you to add a note explaining that the entry is retroactive and the basis for the date (receipt, memory, photo metadata, etc.). Retroactive entries are timestamped with both the event date and the date the entry was created, which maintains the integrity of the audit trail while allowing you to fill gaps in good faith.

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.