General field guides

Keep welfare reports and disease notifications as distinct records

Identify what each document reports before combining it with another account. Preserve its source, purpose, dates and stated status, then link related records explicitly. A welfare report and a disease notification can concern the same setting without becoming interchangeable documents or two separate incidents.

Updated 848 words · 4 min read

Name the document before naming the event

Start with the received document rather than a broad folder label such as “animal-health cases.” Record its title, publisher or sender, identifier, version and the purpose stated in the document. A submitted concern, an acknowledgement, a later update and a published summary are different record types.

Use the labels supplied by the source. If its purpose is unclear, retain that uncertainty and seek clarification from the document owner. This guide describes a register; it does not decide which organization has authority or assign an official classification to an account.

Separate identities that can otherwise collapse

Give the document a stable local ID while retaining the sender's original identifier. Keep the subject or event ID separate. Several documents may concern one setting, and a single document can refer to several matters. A filename or spreadsheet row number is not enough to describe that relationship.

Store what the document actually says separately from the editor's interpretation. A source heading that includes “notification” should remain attributed to that source. It should not silently replace the label on an earlier complaint or be applied to every item in the same email thread.

Record detail Question it answers
Document ID and edition Which account was received?
Stated purpose Why was this document created?
Source and date Who issued it, and when?
Subject relationship What other record does it concern?
Status as supplied What does this source say about its own account?
Local interpretation What additional link or summary did the editor create?

Work through a mixed folder

In a fictional archive, item W-17 is titled “welfare concern.” Item N-4 is titled “disease notification.” Both mention the same premises during the same week. Item A-8 is an acknowledgement that W-17 was received.

There are three documents in that folder. That does not establish three incidents, two affected premises or a confirmed relationship between the concerns. Retain W-17 and N-4 as separately identified accounts, and link A-8 to the concern it acknowledges. Record the shared premises reference in the controlled working register without treating the matching name as proof that every account describes the same event.

If an authorized clarification later identifies a relationship, preserve its source and date. Do not rewrite the original documents as if they contained that clarification from the beginning.

Keep each status attached to its account

An update may revise one document while leaving another unchanged. Preserve which record it supersedes, what changed and the source's explanation. A status such as “closed” needs its own context: do not transfer it from one account to an unrelated record simply because they share a subject label.

When creating a summary table, name the unit counted. A total of documents received is different from a count of identified events or premises. Keep separate totals where the relationship has not been established instead of forcing one convenient figure.

Prepare a public copy deliberately

Keep complainant names, private contact details and precise premises information in the controlled working record unless their public inclusion has been specifically resolved. A public explanation can use local document IDs and a description of the relationship without reproducing the entire correspondence.

Review quotations and downloadable rows together. Removing a name from the paragraph is ineffective if the same identity remains in an attachment or filename. This is a publication-design choice, not a promise of anonymity or a statement about a particular disclosure requirement.

Use the duplicate-event guide when several rows may describe one event, and the timeline correction guide when later accounts change the summary. The useful result is a traceable set of documents whose purposes and relationships remain visible.

Questions when preparing a combined summary

Do matching premises references establish one incident?

They identify a relationship to investigate, not necessarily one event. Preserve each document's purpose and the evidence for any event-level link. Use an explicit unresolved relationship when the authorized clarification is absent.

Does “closed” mean the same thing across accounts?

Keep the status attached to the source document and its stated scope. Closing a correspondence task, welfare account or disease investigation can describe different actions. Do not transfer the word without its context.

Which count belongs in the headline?

Name the unit and use the supported total: documents, identified events or premises. If the event relationships are unresolved, a document total should not be presented as a confirmed incident total. Explain that limitation rather than forcing one figure.

In a second fictional register, a revised notification replaces an earlier edition but both are imported as new events. Linking the document versions preserves two source records and one represented account relationship. A later summary can explain the revision without doubling the incident count. The record should make that distinction visible to editors, readers and download users alike, while keeping private correspondence details in the controlled working file.

Cite this reference

LivestockDefense. “Keep welfare reports and disease notifications as distinct records.” Updated 2026-11-03. https://livestockdefense.com/guides/animal-welfare-reports-mixed-with-disease-notifications/

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 ↗