Use two relationships to answer two legitimate questions
A breeding review may ask which dam gave birth to the piglet. A care review may ask which sow nursed it during a particular interval. Neither question should erase the other. The same later outcome can therefore appear in different grouped summaries without being a second event.
Consider a fictional piglet born in litter A, moved to B and later moved again to C under the responsible plan. A current roster can correctly place it with C while its earlier observations still belong to A or B at their actual times. Copying C backward over the whole record invents a care history and makes the earlier evidence difficult to interpret.
A useful joined report should show the grouping rule. If the question concerns birth dam, use that relationship. If it concerns the care interval, use the dated nurse relationship. Do not add both totals as independent piglets or assign a later diagnosis to the original transfer reason as though it was known then.
Precision matters during a busy week. Where only a subgroup can be followed, preserve that limit rather than creating a complete-looking individual chain. A later recollection may help reconcile a gap when attributed and dated; it should not become a backdated original event. Counts can remain unresolved while the responsible people clarify the actual movement.
The documentation follows the professional welfare and management plan. It does not select piglets for fostering, prescribe timing or define clinical criteria. At handoff, make current membership and continuing care needs understandable to the next worker. A stable litter head count can conceal exchanges in both directions, so identity relationships remain necessary even when the arithmetic balances.
Define the identity model before work becomes busy
Agree on how piglets, birth litters and nurse groups will be identified under the farm’s veterinary and management plan. Keep the original birth link stable. If individual identity is not available, state the group-level limits rather than implying a precise individual history.
Record who makes and documents transfer decisions. This guide does not prescribe which piglets to move, timing or clinical criteria for fostering. Its purpose is to preserve what actually happened under the appropriate professional plan.
Record a transfer as a new event
Capture the source litter, destination, date and time, number or IDs moved and reason recorded by the responsible person. Keep planned transfers separate from completed ones. If a move is changed or canceled, preserve that status instead of deleting the plan without explanation.
| Field | Meaning to preserve |
|---|---|
| Biological dam | Original birth relationship |
| Birth litter | Membership at birth, within identification limits |
| Nurse sow | Care relationship during a defined period |
| Transfer | Actual source, destination and time |
| Observation or loss | Animal/group and event time linked to that history |
Reconcile membership at handoff
Use the transfer log to explain the animals currently present with each sow. A head count alone cannot show where piglets came from or whether an apparent missing animal was transferred. Keep discrepancies open until clarified.
If staff later reconstruct an undocumented move, record the source of the recollection and its uncertainty. Do not backdate it as though it were an original contemporaneous entry. The distinction helps later reviewers judge the reliability of a health comparison.
Work through a misleading litter summary
In a fictional farrowing week, two piglets born to sow A move to sow B. A later loss is entered only under B’s litter. A report grouping losses by biological dam and another grouping by nurse sow can therefore show different patterns without either necessarily being an arithmetic error.
Name the grouping rule in the report and preserve both relationships. Do not count the same loss twice when joining the two summaries. The herd veterinarian can then examine the relevant birth, care and exposure histories instead of receiving one ambiguous litter label.
Keep clinical findings separate from transfer reasons
A transfer reason recorded as “small” or “needs attention” is a management observation, not a diagnosis. Preserve any subsequent professional assessment with its date. A later diagnosis should not be inserted into the original reason as if known at the time.
Review missing transfers, reused litter IDs and unexplained count discrepancies after the busy period. Use the pig hub for related references and the farm observation log for chronological entries. Clear relationships make the dataset useful without rewriting birth identity each time care changes.
Common questions
Does a nurse change replace the biological dam?
No. Preserve birth identity and add the care relationship with dates.
Can birth-dam and nurse-sow reports differ legitimately?
Yes. They group the same events by different relationships; name the rule.
Does an unchanged litter count prove unchanged membership?
No. Transfers in both directions can leave the total stable.
Cite this reference
LivestockDefense. “Cross-fostering records: preserve birth identity and nurse history.” Updated 2026-11-03. https://livestockdefense.com/guides/cross-fostering-records-during-a-busy-farrowing-week/
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 ↗