Group, Movement and Inventory Records
A movement note records an event. Group membership lists which animals belong to a group. A physical count checks what is present. Keep all three; none verifies the others automatically.
Record each movement
Movement record
| Date/time | Animal IDs/group | Head count moved | From | To | Reason | Observer | Transport/source reference |
|---|---|---|---|---|---|---|---|
Record a relocation separately from a purchase, sale, birth, death, or membership change. Moving an intact group between pastures does not change its membership or total head count.
If some animals enter or leave a group, record their IDs and the membership change separately. A note saying “moved six heifers” does not identify which six.
Reconcile the count
For a defined group and period:
Expected closing count = opening count + additions − removals.
Keep the dated entries behind each addition and removal. Compare the result with a physical count taken at a stated time. If the counts differ, recount where appropriate and investigate missing or duplicated entries. Record the explanation and correction; do not silently replace the old total.
A physical count can also be mistaken. An unexplained difference remains unresolved until there is evidence for a correction.
Virtual-fence and collar notes
A boundary redraw records a planned area change, not proof that animals moved. Keep the redraw date, area or map reference, group, operator, and any later observed movement separately.
For a collar alert, record the device and animal IDs, timestamp, alert text, and what a person verified. Keep maintenance or fit observations and the action taken. An alert alone does not establish animal behaviour or a reason to cull. Ranch.Bot does not automatically ingest collar data.
Documents and related records
Keep transport documents, sale settlements, and source references with the movement history. Check the Canadian sheep and goat traceability guide and the relevant authority for reporting obligations. A farm note is not a regulatory submission.
Use the same dated group and head-count history for feed records and cost allocation.
Ranch.Bot's boundary
Ranch.Bot stores generic movement records and animal/group links, and manages group membership separately. Review each proposed change before saving. Saving a movement description does not by itself update membership or reconcile a physical count.