State-based beekeeping

Make every hive condition easy to name, act on and follow up.

Commercial beekeeping gets risky when the same hive can be called weak, queen-risk, hungry or just "needs attention" depending who opened it. Field states give crews a shared language for condition, reason, action and next check, so managers can see patterns instead of reading vague notes.

View state cards Field workflow

Beekeeper holding a live brood frame during an apiary inspection — **A state starts with what is seen**The frame, bees and context become a decision record.

The problem

The next crew should not have to decode yesterday's shorthand.

A useful state captures condition, reason, action, owner, review date and outcome. It makes field judgement inspectable without forcing every beekeeper to write an essay on a phone.

Condition

What is the colony showing right now?

Reason

Why does this state matter for the next decision?

Action

What did the crew do while the hive was open?

Follow-up

What should improve, fail or be checked next?

Commercial beekeeping crew working around open yellow hive boxes in the field — **Same hive, same language**States help different people describe the same field reality consistently.

Beekeeper checking an open hive beside rows of yellow hive boxes — **Record while it is visible**The state, reason and action belong beside the open hive.

Two beekeepers making a field decision beside active hive boxes — **Turn judgement into next work**The next crew should know what was seen and what must happen next.

Manager views

Once states are consistent, managers can see the business.

State distribution

Which apiaries are healthy, blocked, queen-risk, hungry, weak or ready?

State transitions

Which hives improved, stalled or worsened after the last action?

Repeat problems

Which sites, lines or yards keep returning to weak or queen-risk states?

Crew consistency

Are different crews describing the same condition in the same way?

Follow-up pressure

What must be checked before the next weather window closes?

Training gaps

Where does the state pattern reveal uncertainty or missing judgement?

The second page

The companion state-card page carries the full field language.

The detailed card page stays live as the practical system: the 16-state language, card anatomy, seasonal judgement, diagnostic worksheet and adoption path crews can use in the field.

Open state-card page Diagnostic worksheet

Start the pilotChoose one state workflow that can prove value in 4-8 weeks: queen risk, weak colonies, feeding, varroa follow-up, splitting, production readiness or another state language the team already argues about.

Hive state cards as the companion field reference — **Second page restored**The detailed card page stays connected to the state-based overview.

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.