General field guides

Timestamp an emailed disease alert without confusing the event date

An emailed alert has several clocks: when the event occurred, when the issuer published it, when your organization received it and when someone acted. Preserve those times with their source and timezone. The newest inbox timestamp does not make an old event current or establish when the underlying authority first knew of it.

Updated 873 words · 4 min read

Preserve the original message

Keep the original alert and attachments in the appropriate record with sender, subject, receipt information and links. A forwarded excerpt can lose the issuer’s date, scope or qualification. Retain which part comes from the original authority and which was added by a forwarder.

Use a stable alert or event reference so later updates can be linked. Several emails about one event should not become several independent disease incidents. A newsletter that repeats a notice is a communication event, not automatically a new occurrence.

Label each time by meaning

Record the time supplied by the source, its timezone or uncertainty and what it represents. If only a date is given, retain that precision rather than inventing midnight. Keep the original value alongside any normalized display used in a dataset.

Timestamp Meaning
Event or onset When the underlying observation occurred, if stated
Issue When the authority released this notice
Receipt When the organization received the message
Retrieval When a linked document was obtained
Action When a person actually reviewed or acted
Correction When a later clarification changed the record

Keep receipt separate from awareness

An inbox delivery is not proof that the responsible person read the alert then. Record acknowledgement, review and any instructions or actions separately. A shared mailbox can receive a message while the relevant staff member is unavailable.

If the alert concerns a current animal-health or movement question, follow the appropriate professional and official channels. Completing timestamp fields should not delay an urgent response, and an old email should not substitute for checking the current instruction.

Work through a forwarded historical notice

In a fictional case, a worker forwards a months-old authority notice today without the original date in the excerpt. A dashboard imports today’s receipt as the event date and labels it active. The message history is current, but the underlying occurrence may be historical.

Recover the original notice, preserve the forwarding chain and resolve the status before publication. If current status remains unknown, say so. A recent download or inbox entry cannot supply the missing official update.

Preserve corrected versions

Link a replacement attachment or revised notice to the version it changes. Record what changed: count, location, classification or another field. Do not silently replace an archived message so earlier decisions appear to have used information unavailable at the time.

Use historical-record guidance, event records and source-register design for related structure. The final timeline should let a reader distinguish the event, the communication and the organization’s actual response without manufacturing precision or recency.

Preserve the timezone conversion

If a display converts source timestamps to a local timezone, retain the original value and conversion basis. A message near midnight may appear on another calendar date locally. That display change should not alter the event’s original timestamp or make two versions look like separate incidents solely because their date labels differ.

Build a timeline that survives a handover

Use one row per documented communication or action rather than squeezing the whole history into a single “updated” field. The row should name the actor or issuer, the kind of time recorded, the original timestamp and the document it supports. Where access must be restricted, keep the protected message in the appropriate system and use a stable reference in the working timeline.

Consider this fictional sequence: an authority issues a notice on Monday, a trade group includes it in Tuesday's digest, and a farm manager reads that digest on Wednesday. Monday is the issue date of the underlying notice; Tuesday belongs to the digest; Wednesday describes the manager's review. None of those entries establishes the event's onset if the notice did not state it. The timeline can remain useful with an explicit “not supplied” value.

When a colleague disputes a date, identify which clock they mean before changing the record. They may correctly remember the day the team discussed the notice while another person correctly cites the issuer's publication date. A brief explanation can preserve both accounts without manufacturing a contradiction.

Frequently asked questions

Should every forwarded email become a new alert record?

It can become a communication record linked to the original alert. Keep a separate incident identity so repeated forwarding does not inflate the event count. Where two messages might concern different incidents, leave the relationship unresolved until the issuer's identifiers or other reliable information clarify it.

What if the timezone is missing?

Retain the supplied value and say that the timezone was not provided. Do not silently apply the farm's timezone to an external issuer. If a later clarification supplies the timezone, document the correction and keep the original entry available.

Can a receipt time measure response speed?

It can anchor one defined interval, but name the interval honestly. Receipt-to-review and issue-to-review measure different things. Missing acknowledgement does not prove inaction, and an acknowledgement does not prove completion of the instructed task. State which recorded action ends the interval and report missing evidence separately.

Cite this reference

LivestockDefense. “Timestamp an emailed disease alert without confusing the event date.” Updated 2026-11-03. https://livestockdefense.com/guides/how-to-timestamp-disease-alerts-received-by-email/

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 ↗