This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.
Start with a record identifier and an animal list
Give the file a stable local reference, then link the actual animals or defined group to it. Preserve the identifiers on the source documents, their context and any unresolved mismatch. A group number should not imply that membership remained unchanged after arrivals, departures or transfers.
Keep the original arrival record, source history and relevant professional documents available through their own references. A form should help the next caretaker retrieve evidence. It should not replace a qualified report with a single reassuring checkbox.
Use an event table rather than one completion date
The following is an example field design. Adapt it to the responsible veterinarian’s and authority’s actual requirements; the table supplies no quarantine duration, testing schedule or clearance criterion.
| Field | What the entry should establish |
|---|---|
| Record and animal references | Which file and animals the entry concerns |
| Event type | Arrival, observation, contact change, instruction or decision |
| Occurrence time | When it happened, with uncertainty preserved |
| Entry time and author | When it was recorded and by whom |
| Source reference | The note, report or message supporting it |
| Current status | Completed, pending or unresolved, with a reason |
| Follow-up owner | Who must address the stated open question |
Allow a factual note beside structured fields. “Unknown arrival time; transport document requested” is more useful than an invented midnight timestamp. Distinguish a true recorded zero from an unchecked or unavailable observation.
Keep instructions in their own dated history
Retain the issuer, applicable animals, issue date and actual wording of significant instructions. Link later revisions to the earlier version and identify what changed. A caretaker should be able to tell which instruction was available at the time an action occurred.
Record actual implementation separately. An instruction received, a task assigned and a task completed are different events. Where completion is uncertain, make the uncertainty visible to the person taking over rather than hiding it in a comment under a “done” status.
Test the form with a fictional early arrival
Suppose a fictional group arrives on Thursday rather than the planned Friday. The draft form automatically copies Friday into its arrival field and calculates a “release” date. A shift change then makes those generated dates look like completed events.
The revised form preserves Thursday’s actual arrival and Friday’s original plan as separate entries. It labels any scheduled review as pending and keeps the professional decision field uncompleted until a real decision is documented. No arithmetic on the arrival date can establish an authorization that the responsible source has not supplied.
Preserve the source behind each entry
The W3C PROV overview provides a way to describe the origin and production of data. The practical principle here is simple: someone reading the form should be able to find the evidence behind a statement and distinguish it from a later interpretation. The proposed fields are an editorial design, not an official form.
Make the handoff and privacy review practical
Ask another caretaker to locate the animals, current instructions and outstanding follow-up from a completed example. Repair confusing fields before adopting the form. Keep necessary private contacts and premises information under appropriate access controls, and confirm record access and retention needs with the responsible organization.
Use introduction planning for preparing the arrival and movement records for the journey. This form follows the recorded history and decision; the qualified team determines the actual animal-care and quarantine plan.
Keep an aquatic cohort attached to the receiving decision
For newly purchased aquatic stock, preserve actual species, life stage, source documents and shipment-to-tank or pond allocations. Keep the relevant system identifiers and documented changes alongside the cohort. A whole-site name should not replace the specific stock and units represented by a report or instruction.
In a fictional receiving file, a cohort is split between two units, but a planned review date becomes an automatic ready status for both. Restore the actual allocation and the responsible aquatic professional’s documented decisions. Preserve any conditions still unresolved for either unit. The aquatic receiving guide follows the transfer history; this record retains the later decision and its actual scope. No generic duration, testing timetable or clearance rule is supplied.
Cite this reference
LivestockDefense. “Record livestock and aquatic-stock quarantine decisions and handoffs.” Updated 2026-10-31. https://livestockdefense.com/guides/how-to-design-a-livestock-quarantine-record/
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.
- 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.
