Treat a move as a relationship rather than a replacement
A current pen answers where pigs are now. A source cohort answers which earlier group they belonged to. Overwriting the source with the destination produces a tidy roster but discards information needed for later feed, health and contact questions. Keep both identities joined by the movement event.
The relationships can run in both directions. One cohort may split between several destinations, while one destination receives several cohorts. A single batch-name column cannot represent both reliably. A source-to-destination table is more useful when its quantities and time basis are clear.
Be honest about precision. If the operation follows subgroups rather than individual pigs, retain that level. Do not create individual identities afterward or imply every destination animal shared one source event. A supported subgroup link is valuable without pretending to be finer than it is.
Reconcile exceptions while the move is fresh. An animal held back for care, a changed destination or a count discrepancy should remain visible. Do not invent a transfer to balance the ledger or copy every source record onto all pigs in a new mixed pen.
Test retrieval with an ordinary question: could the next caretaker trace one destination subgroup to its earlier history without relying on memory? Resolve ambiguous labels before another move extends the chain. This information supports care but does not decide stocking, mixing or handling arrangements.
Freeze the membership before the move
Keep a dated snapshot of the source pens and the best available animal identifiers. Where individual identity is unavailable, define the subgroup and record that limitation. Do not imply individual traceability when the farm can follow only a batch.
Record who authorizes the sorting plan and the relevant welfare and health instructions. This article addresses documentation, not a stocking-density rule or handling procedure. Obtain the appropriate professional advice for the actual groups and facilities.
Separate origin from current location
Give the original cohort a stable identifier that survives the move. Add destination pen and membership interval as separate fields. If several cohorts enter one pen, retain all source links rather than assigning every pig the destination’s newest group label.
Keep split and merge relationships explicit. A source cohort can divide into several destinations, while one destination can contain several sources. A single “new batch” field cannot represent both relationships without losing information.
| Movement field | Purpose |
|---|---|
| Stable source identity | Preserves earlier history |
| Actual move time | Establishes membership interval |
| Destination | Locates animals after sorting |
| Quantity or identities | Shows what moved and its precision |
| Exception | Retains animals held back or moved elsewhere |
Reconcile counts with exceptions
Compare source departures and destination arrivals using the same unit and interval. Keep deaths, temporary holds and other departures separate. If a count does not balance, record the discrepancy and resolve it against the actual records instead of creating a fictitious transfer.
Preserve changes to the plan. A destination may become unavailable, or a subset may remain for professional assessment. The completed movement ledger should describe actual use, not simply confirm that the planned sorting task was marked done.
Work through a mixed destination
In this fictional example, Pen D receives pigs from Cohorts A and B. A later feed concern involves a lot supplied to Cohort A before sorting. If every pig in D now carries only the new pen label, the earlier exposure account is lost.
A retained source-to-destination link identifies the relevant subgroup while preserving uncertainty where individual matching is unavailable. It does not establish which pig consumed a particular amount or whether a later illness is related. It keeps the history available for the veterinarian and traceability review.
Carry earlier records forward by relationship
Keep veterinary findings, feed lots and other events attached to their original animal group and dates. Link the sorted groups to that history rather than copying every record onto the whole destination pen. Blind copying can create false exposures among pigs that were never in the source group.
When publishing summaries, state whether counts refer to original cohorts, current pens or individuals. Do not add a source-cohort total to a destination total as though the same pigs are two independent populations.
Test retrieval after the next ordinary move
Ask another worker to trace one destination subgroup back to its source without relying on memory. Resolve ambiguous labels and preserve the correction. Confirm that future moves can extend the chain rather than replace it.
Use pig references and feed traceability for related questions. The practical result is a location history that remains usable after the physical arrangement changes, with the true precision of animal identity made explicit.
Common questions
Should the original batch be renamed?
Keep the source identity and add the new location relationship instead of replacing the history.
Are subgroup records useful?
Yes, if the true precision and any uncertain allocation are stated.
Can source and destination totals be added?
No. They may describe the same pigs at different stages of the movement chain.
Cite this reference
LivestockDefense. “Sorting pigs by size while preserving their earlier history.” Updated 2026-11-03. https://livestockdefense.com/guides/sorting-pigs-by-size-without-breaking-cohort-traceability/
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 ↗