Setting Mite Count Threshold Alerts in Beekeeping Software
The treatment threshold is the point at which mite levels require intervention. The practical challenge is acting on the threshold rather than letting colonies sit above it while you wait for a more convenient time to treat. Threshold alerts in beekeeping software remove the memory burden from that process. When a colony crosses the threshold, you get a notification. You do not have to remember to check.
Understanding Treatment Thresholds
The commonly accepted treatment threshold during the active brood season is 2%, or 2 mites per 100 bees in an alcohol wash. Below this level, mite populations are manageable and colony health is generally maintained. At or above this level, mite populations are growing fast enough that intervening now is significantly better than waiting another inspection cycle.
The 2% threshold is not a cliff edge. A count of 1.9% is not safe and 2.1% dangerous. It is a rule of thumb based on population modeling that shows mite populations tend to grow exponentially once they cross a certain density. Treating at or just below 2% gives you the best chance of knocking the population down before it causes measurable harm.
During periods of reduced or absent brood, the threshold changes. A colony with no brood has all mites phoretic, which inflates the apparent infestation rate. A threshold of 0.5% to 1% is appropriate for colonies in or near a broodless period, since even a small mite population will explode once brood production resumes.
Different thresholds apply by season and colony stage:
- Active brood season: 2%
- Late summer / pre-winter: 1 to 2% (treat before winter bees are raised)
- Broodless or near-broodless: 0.5 to 1%
- Post-treatment verification: below 1% expected; above 2% warrants follow-up
How Threshold Alerts Work in Software
A threshold alert system compares your mite count entry against your configured threshold and notifies you when a hive has exceeded it. Effective alert systems also flag hives that are overdue for a count. A hive that has not been counted in 6 weeks during peak season is an unmonitored risk regardless of what its last count was.
Alert types worth having:
- Above threshold now: count entered exceeds threshold, treatment indicated
- Approaching threshold: count is at 1.5% or within a set margin of threshold (early warning)
- Count overdue: hive has not been sampled within your configured monitoring interval
- Treatment overdue: a treatment was indicated (either from alert or last manual notation) and no treatment has been logged since
Each alert type requires slightly different action. An above-threshold alert is an immediate treatment trigger. A count-overdue alert is a reminder to schedule a yard visit. A treatment-overdue alert is the most urgent: something fell through the cracks and a hive is going untreated.
Configuring Alerts for Your Operation
Different operations set thresholds differently. A beekeeper who sells mated queens or operates near other apiaries may use a lower threshold of 1.5% to be more conservative. A beekeeper running a natural selection program may set a higher threshold and rely more on monitoring trends over time.
Software that lets you configure threshold values per hive, per yard, or per operation type is more flexible than software with a fixed universal threshold. Your winter bees need a different trigger level than your summer production hives.
VarroaVault lets you configure treatment thresholds and monitoring intervals at the operation level, with the ability to override for individual hives where different thresholds apply. When a count is entered that exceeds threshold, the hive is immediately flagged on the dashboard. The mite count tracking app captures the count in the field and triggers the alert in real time so you know before you leave the yard.
Acting on Alerts
An alert system only has value if the alerts are acted on. This sounds obvious but is a real operational discipline issue. It is easy to see a threshold alert and think "I'll get to it next week." Next week comes, the count is still in the system, and the mites have spent another week reproducing.
When you receive a threshold alert, the appropriate response is to schedule treatment within the next 7 to 10 days. This is the window between alert and action that keeps varroa manageable. Waiting more than two weeks from an above-threshold count significantly increases the total mite burden the colony experiences.
For multi-apiary operations, threshold alerts that aggregate across all yards in a single dashboard view let you prioritize which yards need treatment attention first. A yard with three hives above threshold is more urgent than a yard with one borderline hive. See the multi-apiary management software overview for how this dashboard organization works in practice.
Threshold Alerts as an Audit Trail
Every threshold alert that was triggered and every treatment logged in response creates an audit trail. If a colony collapses in winter and you want to understand why, you can look back at the alert history. Were counts above threshold and left untreated? Did treatments have adequate efficacy? Were mite counts taken at appropriate intervals?
This retrospective analysis is one of the less obvious but genuinely valuable features of a threshold alert system. It turns your monitoring data into a diagnostic resource.