Colony loss context
Use state transitions, queen risk, feeding signals and varroa treatment follow-up to make loss risk visible earlier.
Reports
Reports that turn records into decisions.
BuzzTech reports are designed for the Monday question: what changed, what needs attention now, what can wait, what proof exists, and what decision is still blocked between field work and honey proof?
Daily team dashboard
One live priority board the whole team can work from.
ApiDash puts the current apiary picture where the team can see it: active sites, hive counts, app notes, treatment timing, run priorities, weather windows and monitor lists. It means team meetings, lunch room conversations and field decisions start from the same up-to-date source of truth.
- One-click printable varroa, beekeeping and monitoring run lists.
- Apiary and hive notes from the field are visible for planning and team discussion.
- GPS-based site weather helps crews compare five forecast models for tighter decisions.
- Shared language and live priorities become team knowledge, not one person's memory.
Friction reducerBusy teams need less asking around, fewer rebuilt spreadsheets and a faster way to agree what matters today.
Data-backed urgency
Reports should match the pressure commercial operators are under.
Current NZ data makes the point plainly: winter 2025 colony loss was estimated at 12.8%, Varroa was the most prominent cause, and the industry is operating with fewer hives than the boom years. The system has to surface risk earlier.
Source notes: MPI 2025 apiculture monitoring data | MPI 2025 colony loss survey | Bioeconomy Science Institute 2025 colony loss release | Newsroom 2024 hive number context.
Operational discipline
Fewer hives, higher costs and tighter margins make repeatable records more valuable than heroic memory.
Evidence burden
Export, audit and customer proof depend on records that survive handover between people and systems.
Management rhythm
Reports should create the next work plan, not merely describe the past.
Weekly apiary report, extraction report, compliance pack.
| Signal | Demo result |
|---|---|
| Varroa rechecks overdue | 9 manager review |
| Queen-risk hives | 11 unresolved |
| Production-ready hives | 86 ready |
| ECERT support printouts | 18 ready |
| Shed temperature alerts | 5 manager review |
| Extraction batches | 45 demo batches |
Demo-safePublic proof uses representative examples, fictional locations and anonymised values unless an operator approves a case study.
Round report
Priorities by site, state, action, date and crew note.
State transition report
What moved from weak to recovering, queen-risk to resolved, or production-ready to harvested.
Extraction dashboard
Batch, pallet, box, weight, honey type, yield and source context.
Corrective action register
Monitoring event, cause, action, owner, status and verification.
Sensor exception summary
Temperature, chiller, warm room, hive, scale or plant event translated into work.
Executive summary
A short manager narrative with evidence links and unresolved decisions.
Start with pressure you can measure
Pick one workflow where better records will change the next decision.
BuzzTech starts narrow: varroa follow-up, offline field records, hive tags, ApiDash dashboards, ApiDrums inventory, ApiBlends planning, ApiPos retail stocktaking, RMP evidence, sensor exceptions or a weekly management report. Prove value, then connect the pieces into a durable operating system.
Privacy positionWe do not publish operator data, customer details, locations, screenshots or case examples without permission.