Beekeeping Hive Record-Keeping System: Build One That Actually Works

Beekeepers with connected record systems detect colony problems 3 weeks earlier than those using disconnected logs. That's the gap between catching a colony in early decline and discovering a dead-out. A system where your mite count data connects to your treatment history, your queen notes connect to your colony strength scores, and your harvest records connect to your PHI tracker is categorically different from a box of notebooks.

Here's what a complete hive record system needs to include and how to build one that actually informs your management decisions.

TL;DR

Most US states require apiaries to maintain treatment records including product name, EPA number, and application dates
Records should be kept for a minimum of 2 years; some states require 3 years for commercial operations
A complete varroa treatment record includes: date, hive ID, product, dose, pre-count, post-count, and PHI end date
Paper records are legally acceptable but create gaps when inspectors ask for multi-year trend data
VarroaVault stores records with automatic date-stamping, hive linkage, and exportable PDF summaries
Digital records reduce audit preparation from hours to minutes

The Six Core Record Modules

A complete hive record system has six connected modules. Most beekeepers keep some of these; few keep all of them in a way that lets them talk to each other.

1. Mite Count Records

The foundation of varroa management. Every mite count record should include:

Date of count
Hive identifier
Count method (alcohol wash, sugar roll, sticky board)
Sample size (number of bees if alcohol wash or sugar roll)
Raw mite count
Calculated infestation percentage
Comparison to threshold at the time of counting
Notes (was brood present? Any abnormal colony behavior?)

Minimum frequency: monthly during active season (April through October). More frequently in August-September when mite pressure peaks. A count before and after every treatment.

Why this record matters: The trend matters more than any single count. A colony at 1.8% in August isn't alarming by itself. A colony that was 0.8% in June, 1.2% in July, and 1.8% in August is showing a trajectory that says 2.5-3% by September without intervention.

2. Treatment Records

Every treatment application should include:

Date applied
Hive identifier
Product name (brand and active ingredient)
Dose and application method
Pre-treatment mite count (the baseline used for efficacy calculation)
Temperature at application (critical for temperature-dependent treatments)
PHI: calculated expiry date if applicable
Supers on/off status at application
Treatment completion date (strip removal, final vaporization, etc.)
Post-treatment count and calculated efficacy

Why this record matters: Treatment records are your resistance early warning system. A year's worth of efficacy calculations tells you whether a product is working the same as last year or declining. It's also your legal defense under FIFRA: proof that you applied registered products at label doses and respected PHI.

3. Queen Records

Every queen event should be logged:

Introduction date (for new queens)
Queen's origin (purchased, raised, swarm cell)
Queen color marking
First confirmed laying date after introduction
Annual re-inspection and confirmation notes
Supersedure or swarm events
Requeen dates

Why this record matters: Colony behavior, mite management success, and honey production all correlate with queen quality and age. When you're diagnosing a persistently high-mite colony, knowing that the queen is three years old and was never from VSH genetics is important context. When you're evaluating whether to requeen, the queen record tells you what you already know about this queen's performance.

4. Colony Strength Records

Logged at each inspection:

Number of frames of bees (covered surface area estimate)
Number of frames of brood (total and capped)
Food stores estimate (honey frames + pollen)
Population trend (growing/stable/declining)
Evidence of disease or pests (other than varroa)

Why this record matters: Colony strength directly affects treatment dosing (OA dribble dose is based on seams of bees; Formic Pro dose depends on colony size). It also provides context for interpreting mite counts: a 2% count on a weak 4-frame colony is more urgent than a 2% count on a booming 15-frame colony, because the weak colony has less buffer.

5. Harvest Records

Every honey extraction:

Date of harvest
Hive(s) harvested
Weight or frames extracted
Any active PHI on the colony at harvest time
Lot identification (if you're tracking for commercial sale)

Why this record matters: PHI compliance requires knowing which treatments were applied to which hives, when, and what the expiry date was at the time of harvest. Honey from a hive with an active Apivar PHI should not be in your harvest. Without a connected harvest-treatment record, you're guessing.

6. Winter/Spring Assessment Records

Pre-winter:

Final mite count before pack-down
OA dribble applied (date, dose, broodless confirmation)
Food stores assessment
Colony strength going into winter

Post-winter:

Spring survival status
First spring count
Spring colony strength

Why this record matters: Year-over-year winter survival data tells you which colonies (and which queen lines) perform best in your climate. Over three seasons, you'll see patterns: colonies that consistently come through winter strong versus those that consistently struggle. This informs requeening decisions and colony replacement strategy.

Why Disconnected Records Fail

The typical beekeeper keeps some version of these records, but in silos:

Mite counts in one notebook
Treatment notes in another
Queen information in their head
Harvest records in a spreadsheet somewhere

The problem isn't the individual records; it's that they can't inform each other. When you're trying to figure out why a colony is struggling in March, you have to piece together information from three places and hope your handwriting was readable. When you're evaluating whether your August Apivar treatment achieved adequate efficacy, you need the pre-treatment count AND the post-treatment count AND the treatment dates AND the strip removal date, all in one place.

Connected records eliminate the assembly step. You see the full colony history in one view.

How VarroaVault Connects the Six Modules

VarroaVault builds connections between records automatically. When you log a treatment, the system links it to the most recent mite count as the baseline. When you log a harvest, the system checks for any active PHI on that colony and flags potential compliance issues. When you log a winter survival assessment in spring, the dashboard shows pre-winter count and treatment status alongside your new entry.

The system architecture connects six record types:

Mite counts connect to: Treatment recommendations (threshold comparison), efficacy calculation (baseline for post-treatment counts), trend analysis, seasonal alerts.

Treatment records connect to: PHI tracking (auto-calculates and tracks expiry dates), protocol reminders (step-by-step reminders for multi-application treatments), efficacy calculation (outcome tracking), resistance flags (flags below-threshold efficacy).

Queen records connect to: Colony strength interpretation, treatment sensitivity notes (new queen flags trigger treatment safety reminders).

Colony strength records connect to: Treatment dose calculations, threshold interpretation.

Harvest records connect to: PHI compliance checks, lot tracking.

Winter/spring records connect to: Year-over-year survival analysis, apiary performance comparison.

Setting Up a System for the First Time

If you're starting from scratch:

Step 1: Create hive profiles for every colony. Assign a consistent numbering system (Yard 1, Hive 1; Yard 1, Hive 2; etc.) that you'll use permanently.

Step 2: Log your current colony state. Do a mite count on every hive and log it. Note current queen status and colony strength. Log any recent treatments you can recall, even approximately.

Step 3: Set your monitoring schedule. Monthly for most hives; every 3 weeks for high-risk locations. Set up VarroaVault's monitoring reminders to match.

Step 4: Set your treatment thresholds. 2% pre-winter, 3% active season is the HBHC default. Adjust for your operation if needed.

Step 5: Commit to logging at the hive, not later. The single biggest failure mode for record-keeping systems is delay. Log on your phone at the hive. Records that have to be transcribed later are records that often don't get transcribed.

How VarroaVault Compares to Other Complete Record Systems

Paper journals capture everything you choose to write but perform no calculations, send no alerts, and can't show you trends. The information is yours if you can find it.

Spreadsheets can calculate and graph but require manual data entry, manual formula creation, and manual maintenance. A well-built spreadsheet system can be excellent, but few beekeepers build and maintain a truly comprehensive one.

VarroaVault is purpose-built for beekeeping record management with mite management as the primary focus. The six record modules connect automatically. Calculations happen on entry. Alerts fire without manual trigger. The mobile-first design means records get logged at the hive, not reconstructed from memory.

Frequently Asked Questions

What should a complete beekeeping record system include?

A complete system covers six modules: mite count records (with method, sample size, percentage, and comparison to threshold), treatment records (product, dose, PHI, efficacy), queen records (introduction, origin, age, events), colony strength records (frames of bees and brood, food stores), harvest records (with PHI compliance tracking), and winter/spring survival assessment. The records become most valuable when they're connected, so a count baseline automatically links to a treatment efficacy calculation, and a harvest record automatically checks for active PHI.

How do all the records connect together in VarroaVault?

VarroaVault links records automatically based on hive ID and date. When you log a treatment, it links to your most recent count as the pre-treatment baseline. When you log a post-treatment count, it calculates efficacy against that baseline. When you log a harvest, the system checks for active PHI on that colony. When you open a hive record, you see the complete connected history: counts, treatments, queen events, strength scores, and harvests in chronological order with cross-references visible.

How does VarroaVault compare to other complete record systems?

Paper journals can't calculate, alert, or trend-analyze. Spreadsheets can do all three but require manual construction and maintenance. VarroaVault is purpose-built with the six core beekeeping record modules already connected. The mobile-first design means records get logged at the hive rather than reconstructed from memory. Calculations, threshold alerts, and protocol reminders happen automatically without manual formula work.

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.