Use an exception review to improve the next handoff
The useful review begins by asking what another caretaker could misunderstand. A farm batch label may be correct for administrative purposes while concealing different room intervals. Explain both uses rather than forcing the whole history into whichever name the export accepts.
Imagine a fictional receiving list prepared before a late arrival is confirmed. The late pigs eventually enter a different room, but the original list is copied into the weekly summary. The source plan remains evidence of intention; the completed movement records establish a different occupancy question. Keeping both avoids treating the planned roster as a contemporaneous animal count.
An exception entry should answer a specific next question. Is animal matching unresolved, is a move confirmed but its time approximate, or is the receiving instruction still pending? These states should not collapse into one miscellaneous comment. The responsible team can then determine which clarification affects the current decision.
Do not use the review to invent a holding period, turnover cycle or clinical-testing sequence. This article concerns readable history and handoff, not a disease-control protocol. The actual management and welfare plan comes from the qualified farm and veterinary team.
At the next ordinary handoff, ask a relief worker to retrieve the real room membership and current instruction. If doing so requires the author’s memory, improve the labels and exception visibility. A more honest file may look less uniform, but it allows animal outcomes and later reports to be interpreted in the right population. An unresolved count can remain unresolved without assigning a fictitious transfer to make the totals agree.
Define the unit before using the label
State whether the plan concerns a room, building or another specified unit. Keep the intended cohort identity and the actual animals represented. A room number can remain constant while several cohorts use it, and a farm-wide batch label may conceal different room intervals.
Retain the plan version and applicable dates. A revised schedule should not overwrite earlier actual occupancy. The record needs enough history for a later reader to understand which definition applied at the time.
Three rooms do not automatically make one cohort
In this fictional nursery, rooms A and B receive the planned group, while room C has a different real departure interval. Two later arrivals are assigned to the same farm batch for administrative convenience. The export shows one uninterrupted, uniform cohort.
The corrected relationships distinguish:
| Record layer | What it should preserve |
|---|---|
| Plan | Intended unit, dates and cohort |
| Room occupancy | Actual entry and departure intervals |
| Exceptions | Known additions, transfers or unresolved matches |
| Turnover work | Area and task actually represented |
| Receiving decision | Current qualified instruction and responsibility |
This correction does not decide which animals should move or supply a disease-control protocol. It prevents the administrative batch name from erasing the real room history.
Keep exceptions as first-class entries
Give each exception an actual date, source, represented pigs and reason where supplied. An exception note should remain visible when someone exports the main table. Do not hide it in a comment while the summary still claims uniform occupancy.
If the animal identity is uncertain, retain the matching limit instead of allocating the pig to the most convenient cohort. A count balance can show a discrepancy without proving which individual moved.
The responsible team should determine any animal handling, placement and turnover process. This record-design guide does not prescribe a holding period, cleaning cycle, clinical testing sequence or movement order. Follow the actual professional plan rather than moving pigs to make the database agree with the schedule.
Keep outcomes attached to actual occupancy
Record clinical observations, deaths and professional findings with their actual pigs, rooms and intervals. A later event should not inherit the whole planned cohort’s earlier history if the animal arrived separately. A document count is not a count of unique affected pigs.
Preserve the population and observation coverage behind group summaries. A reduced count after pigs depart is not automatically clinical improvement. The case-definition guide explains the separate classification question.
At handoff, identify what is complete, what remains unresolved and who has the current instruction. The farrowing-room turnover example illustrates pen-level occupancy and receiving evidence in a different pig setting. The same care with identity lets the nursery team review its actual exceptions without presenting an idealized plan as an accomplished history.
Common questions
Is room number cohort identity?
No. A place persists while occupants and intervals change.
Should exceptions disappear from exports?
No. Retain actual pigs, dates and matching limits.
Does the label supply a turnover protocol?
No. The responsible team determines management and verification.
Cite this reference
LivestockDefense. “Pig nursery all-in/all-out plans: make actual exceptions visible.” Updated 2026-11-03. https://livestockdefense.com/guides/pig-nursery-all-in-all-out-planning/
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 ↗