Farm record design

Keep a colony movement ledger separate from boxes and public maps

Record each journey against the colony identity, with actual departure and arrival evidence. Keep the colony, equipment and site as separate linked records. Build a public summary from an approved extract rather than publishing the private movement ledger.

Updated 874 words · 4 min read1 source · scope listed below
A honey bee beside a hive entrance

A honey bee beside a hive entrance. Species or setting illustration; this is not a photograph of a diagnosed case or of the reader’s animals. Credit and license details are linked below.

Apis mellifera carnica worker hive entrance 3.jpg · Richard Bartz, Munich Makro Freak & Beemaster Hubert Seibring, Munich which gave me advice and a protection suite ;) My dog caught 6 bee-stings on the nose, i caught 4. · CC BY-SA 2.5 · Full credit & reuse terms

Reading the sources

This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.

Decide what each identifier represents

Use separate keys for the colony being followed, its equipment, a site and a journey. A box number can identify equipment without being a permanent name for the colony assigned to it. A site code identifies a place without proving which colonies were there on every date.

Retain the private key that resolves site codes to the necessary location detail. Handlers' contact information can live in a separate controlled record linked by a working identifier. The movement table needs enough information to retrieve its sources without becoming a public address book.

Record completed events beside the plan

Keep proposed destination and scheduled date separate from actual departure and receipt. Give a changed route its own revision history. The current plan should not overwrite a completed earlier leg.

Ledger layer Detail to preserve
Journey Stable key and intended membership
Departure Actual colony list, site and supported time
Receipt Receiving record, actual membership and time
Equipment change Item relationship, date and source
Exception Missing confirmation, revised destination or unresolved identity

This is a description of record fields. It provides no transport, colony manipulation or movement-authorization instructions.

Reconcile a partially confirmed journey

Imagine a fictional plan listing eight colony keys for a journey from site S1 to S2. The departure record lists seven; one remains at S1. The receiving entry confirms six of the seven and leaves the final key unresolved.

The useful summary is eight planned, seven recorded as departed, six confirmed as received and one departure awaiting reconciliation. The member that stayed at S1 is a separate exception. Do not close the journey as eight arrivals to match the plan, or as six departures to match the receipt.

Keep the actual key lists behind those counts. A later receipt can close the remaining link with its own date and source. An unknown arrival time should remain unknown; the time the manager notices the missing entry is not a substitute.

Keep the evidence behind the ledger

The W3C PROV overview connects provenance with data, activities and people. In this ledger, retain the original dispatch and receiving entries, their authors and any later transcription. The field design and journey example are original illustrations, not a prescribed data standard.

Keep a location's administrative name changes in the site history. Renaming S2 should not create another journey or make earlier visits disappear. Likewise, an equipment substitution needs its own relationship; it should not silently rename the colony.

Make a separate public extract

Choose the detail needed for the publication's question. A broad regional summary may be sufficient where precise sites, handlers and dates are unnecessary. Review the combined export, including filenames, attached maps and captions. Removing one coordinate column does not address an attachment that still names the private site.

Retain the extract date, included journey IDs, transformations and any unresolved confirmations. The private original remains available for the record's authorized purpose. This workflow does not declare that any publication satisfies a privacy law or that a recorded journey establishes a health status.

Use the colony-split record guide when colony relationships change, and the package-traceability guide for purchase-to-colony links. A recurrent journey ledger should connect those histories while retaining its own actual departures and arrivals.

Make exceptions visible in the journey summary

A journey can be partly reconciled without being either wholly complete or wholly unknown. Show the actual colony lists behind the departure and receiving totals. If one link remains unresolved, retain it as a specific exception rather than changing all the counts to make them agree.

Use the same discipline when a location is renamed or equipment is exchanged. The new administrative label should point back to the historical relationship. It should not create a second journey or make a real earlier movement disappear. Keep source dates and correction dates distinct.

For a public extract, explain the unit and coverage in ordinary language. A count of journeys is different from a count of colonies transported, and repeated journeys by the same colony are not new colonies. State the actual question the summary answers before displaying a total.

Questions about colony movement ledgers

Does a plan establish that every listed colony traveled?

No. Preserve planned membership, actual departure and confirmed receipt separately. A mismatch is a question to reconcile from the evidence, not a reason to overwrite one stage with another.

Is the time of data entry the arrival time?

Only if the evidence establishes that relationship. Otherwise keep the arrival event's known timing separate from the later entry or correction. An unknown event time should remain unknown.

Can the private ledger be published after coordinates are removed?

Review the whole extract, including site names, dates, handlers, attachments and map labels. Other combinations may still identify a private apiary. Use the authorized publication purpose to determine the detail needed rather than treating one deleted column as complete protection.

Does a complete movement ledger establish health status?

It documents the supported movement history. Health findings and official decisions require their own attributable evidence and applicable interpretation.

Cite this reference

LivestockDefense. “Keep a colony movement ledger separate from boxes and public maps.” Updated 2026-11-03. https://livestockdefense.com/guides/honey-bee-colony-movement-tracking/

Add the date you accessed the page. This identifies the current reference; keep a permitted saved copy if your work depends on its exact wording. A citation alone does not establish support for a claim.

How to cite a page and its revision ↗

Sources & boundaries

Read the evidence in context.

These documents support the statements identified in this reference. Check their scope and dates when deciding whether they answer your question.

  1. World Wide Web Consortium: An Overview of the PROV Family of Documents

    Source update: 2013-04-30. Most recent check: 2026-10-30.

    Non-normative overview definition of provenance; original record-linking application only. No official animal-identification requirement or movement authorization established.

Full source register ↗