- Record the observation first
Note the inspection or condition that made the action relevant.
- Name the action plainly
Record what you actually did, such as feeding, treatment, requeening, combining, splitting, or another colony intervention.
- Add timing and material details that matter
Keep the date and any factual method, amount, or product detail you will need to understand later.
- Create a useful next check
Write what you intend to verify next, not just that the colony needs attention.
Bees / colony history
Record hive actions and follow-ups without losing the why
Keep treatments, feeding, queen or colony-status changes, and follow-up work connected to the hive record that prompted them.
- 1Record the observation first
- 2Name the action plainly
- 3Add timing and material details that matter
- 4Create a useful next check
Actions make sense only in their colony context
A hive action is more useful when it remains beside the inspection, mite check, stores observation, queen status, or other condition that led to it.
Use the hive history to record the factual action and then add a follow-up that names the result you want to check. This preserves the reason for the work without pretending that the software made the decision.
- What you observed
- What action you took
- When you took it
- Details needed to understand the action later
- What you plan to check next
Keep treatment records factual
Record the actual product or method, timing, and relevant hive context as accurately as you can. Do not rely on a vague note such as “treated bees” if the details will matter later.
YFS is a recordkeeping and follow-up tool. It does not provide pesticide instructions, veterinary advice, or a substitute for product-label requirements.
Keep going