HiveBuzziness

What it does

A crew member arrives at a yard, logs what they did — treatments, feeding, inspections — along with any issues and photos. Every entry is stamped with who, when, and GPS location. A dashboard reads those logs and computes which yards are due for which work, based on configurable maintenance programs, event chains, and condition thresholds.

The operation runs a mixed model — migratory hives on pollination contracts (like almonds) alongside stationary honey production — and the UI is built for high-turnover seasonal crews: fast to use and hard to get wrong.

Highlights

• GPS-stamped field logging — every log records who, when, and where, with photo attachments, so work is fully attributable.
• Scheduling engine — configurable programs, event chains, and condition thresholds drive a "what's due" dashboard across all yards.
• Mite-treatment tracking — treatment durations, temperature bands, and product rotation encoded into the schedule logic.
• Individual crew accounts — real per-user auth and sessions so every action attributes to a person, not a shared login.
• Maps & weather — yard pins on Leaflet/OpenStreetMap with per-yard forecasts pulled by GPS coordinates.
• Security-conscious — yard coordinates and site details stay behind auth; nothing location-sensitive is exposed publicly.

Tech stack