Beekeeping as a Team: Handovers, Roles, and Shared Records

Association apiaries, family operations, and small commercial outfits all hit the same wall. Solo beekeeping runs perfectly well on memory: you know which hive is grumpy, which queen was marked last year, and which colony you meant to requeue. The moment two or three people share the work, that knowledge is invisible to everyone but you — and colonies start getting treated twice, or not at all.

The Three Failures

Almost every problem in a shared apiary is a variation on one of these.

Duplicate work. Two people treat the same colony for varroa a week apart because neither knew the other had been. At best it wastes product; at worst it is an overdose and a residue problem in the wax.

Dropped work. Everyone assumes someone else did the autumn feed. The colony that needed 12 kg gets nothing, and the loss shows up in February.

Lost context. The person who noticed the failing brood pattern in June is on holiday in July, and the colony that needed a new queen quietly builds up to a swarm instead.

None of these are competence failures. They are handover failures.

Give Roles, Not Just Tasks

Splitting work by task ("you do hives 1–5") sounds efficient and usually is not, because nobody owns the outcome. Splitting by role works better in small teams:

• Apiary lead — owns the plan for the season, decides on requeening and treatments, and is the tiebreaker.
• Inspector(s) — do the routine rounds and record what they see, without changing management strategy mid-round.
• Equipment keeper — owns frames, foundation, cleaning, and storage. This is the role most often skipped and most often regretted.

For an association apiary with rotating volunteers, add a rule that nothing irreversible — uniting, requeening, treating — happens without the apiary lead's sign-off.

The Handover Note

The single highest-value habit in team beekeeping is a short written note at the end of every visit, even a fifteen-minute one. Three lines is enough:

1. What I did — boxes added, feeds given, treatments started.
2. What I saw that worries me — queenlessness, chalkbrood, low stores, temper.
3. What needs doing next and by when — the actionable part.

Written the same day. A note written from memory three days later is a story, not a record.

Standardise the Vocabulary

Teams drift apart on language faster than on technique. If one person's "strong" is eight frames of brood and another's is five, your records are noise. Agree on a handful of definitions at the start of the season and write them down:

• Colony strength — measured in seams of bees or frames of brood, pick one.
• Temper — a fixed scale, not adjectives.
• Queen status — seen, eggs seen, or not confirmed. "Probably fine" is not a status.

One Source of Truth

Paper notebooks work for one person in one apiary. With a team they fail predictably: the notebook is in someone's car, two people keep parallel versions, and nobody can search last year's treatment dates when the inspector calls.

Shared digital records solve this, but only if everyone uses the same one and records at the hive rather than at home. Field entry has to be fast enough to do in gloves, in a breeze, with bees on your hands — if it takes more than a minute per hive, people stop doing it.

Permissions Matter

A shared record is only trustworthy if you know who wrote what. Full edit rights for everyone means an accidental overwrite is undetectable. Read-only for helpers, edit rights for inspectors, and an audit trail of changes is the right shape for most groups.

ApiaryPilot supports exactly this: multiple members in one organisation, role-based permissions with read-only members, and every inspection, harvest, and treatment attributed to the person who recorded it — so the handover happens whether or not anyone remembers to send a message.