- Create the apiary as the shared place
The yard name and location give every colony common context.
- Give each active colony a stable hive record
Use a name or identifier you will recognize through moves, inspections, and seasonal review.
- Put colony-specific facts on the hive
Inspections, queen observations, feeding, treatments, harvests, losses, and follow-ups usually belong to one hive history.
- Keep genuinely shared context at the apiary
Use the apiary for yard-level facts rather than copying them onto every colony.
Bees / record design
Individual hive records versus apiary-level records
Use the apiary for shared place context and the hive for colony-specific history, actions, and results.
- 1Create the apiary as the shared place
- 2Give each active colony a stable hive record
- 3Put colony-specific facts on the hive
- 4Keep genuinely shared context at the apiary
Use the physical place once
An apiary is the shared location or bee yard. It is the right place for the name and context that applies to the group of hives there.
A hive record is the colony history. Put information there when it could differ from one colony to the next or when you will later want to compare colonies.
- Apiary: yard name, location, and shared context
- Hive: colony identity and individual inspection history
- Hive: actions, treatments, feeding, harvests, and losses
- Hive: follow-up work and seasonal outcomes
Avoid duplicate notes
If a weather event, yard condition, or apiary-wide observation applies to every colony, record it once in the shared context where possible. If one hive responded differently, add the colony-specific fact to that hive.
This keeps later comparisons clearer and avoids turning a single yard observation into several slightly different copies.
Keep going