A room name is not a cohort identifier
Retain the dates during which a documented cohort occupied a room or unit. A room can be reused, and a cohort can be divided across units. Preserve the real relationships in the existing records so later accounts do not join animals merely because they shared a room label at different times.
Record species and stage as actually supplied by the production record. Do not infer that all larval rooms contain interchangeable animals or that a practice valid for one system applies universally.
Preserve the plan that was actually in force
Keep the approved plan's issuer, version and effective date, plus the responsible team's later amendments. A current revision should not silently become the standard said to govern a historical event. Retain the earlier document where permitted so the event can be assessed against the appropriate version.
This reference concerns the record relationship. It does not design a room barrier, prescribe water treatment or provide cleaning, testing, sterilization or transfer procedures. Those operational decisions remain with the qualified team and applicable requirements.
Separate scheduled work from completed work
An assignment, a checklist entry and a verified technical finding serve different purposes. Retain who made each entry, the actual event time and any later correction. A form signed at the end of a shift does not automatically timestamp every listed task at that moment.
Where the existing plan records equipment, staff work, water-system events or live transfers, preserve the actual identifiers and relevant intervals. Keep uncertainty explicit. A missing signature should remain a documentation gap unless other evidence establishes what happened.
A fictional identifier problem
Imagine two rooms that both use the label batch 17 in separate monthly files. A later export combines the files and treats the entries as one continuous cohort. Restore the source file, production period and stable cohort identity before comparing outcomes.
If one real cohort was split between the rooms, preserve that actual relationship as a separate link. Similar labels should not manufacture a transfer, while a real split should not disappear because the room names differ.
| Record relationship | Question it preserves |
|---|---|
| Room and cohort | Which animals occupied the unit, and when? |
| Plan version | Which issued instructions applied then? |
| Work event | What was actually documented as completed? |
| Technical finding | Who assessed it and within what scope? |
| Amendment | What changed, when and why? |
Record deviations and decisions at their real scope
Retain the original event note and the responsible team's assessment. A documentation deviation is not automatically proof of a biological exposure, while an absence of recorded losses does not certify that a barrier worked. Keep process observations and animal findings distinguishable.
Follow-up actions need the issuing instruction, responsible person and actual completion. Close the administrative task when its documented requirement is met; do not silently convert that closure into product clearance or a final health conclusion.
Use the aquaculture library for connected reading. The useful output is a coherent history of the existing plan and real work, allowing qualified reviewers to see what is established and where a record relationship remains uncertain.
Make a room summary useful at the shift handoff
A handoff should identify the actual cohort, occupied unit and current plan version before listing work. That gives the next person enough context to understand whether an instruction applies to the animals present now or an earlier group using the same room.
Keep exceptions visible. If a task was deferred or its completion cannot be verified, preserve that status and the responsible contact. A complete-looking checklist can be less useful than an honest list of completed work and unresolved questions. Do not backdate later confirmation to make the original shift appear fully documented.
When the technical team reviews an event, retain the finding in its actual scope. A form issue can require correction without proving biological failure. Conversely, no recorded losses during a period does not establish that every planned barrier or process worked. The record should support the assessment rather than decide it through the checkbox labels.
Questions about larval-room records
Does the same room number mean the same cohort?
No. Keep occupancy dates and stable cohort identifiers. A room can be reused, while one real cohort can occupy several units. Preserve the actual relationships instead of joining records by location alone.
Does a signed sheet timestamp every task?
It shows the signature event within its context. Keep actual work times where documented and do not assign a single shift-end time to every task automatically.
Can today's plan be used to describe last month's instructions?
Keep the version in force at the historical event and any later amendment. A current revision can guide current work without becoming the document said to have governed an earlier event.
What closes an unresolved record question?
The relevant clarification or completed requirement should be attributable and dated. Administrative closure should state what was resolved, leaving any separate technical or animal-health question within the responsible team's assessment.
Cite this reference
LivestockDefense. “Marine hatchery room records: keep cohorts, work and the approved plan connected.” Updated 2026-11-03. https://livestockdefense.com/guides/marine-hatchery-biosecurity-between-larval-rooms/
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 ↗