This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.
Decide what the update actually says
Begin with the specific official report. Record its title, issuing authority, report identifier, publication date and the period or event it describes. Then write the change in one sentence: for example, a report was corrected, a regional status changed, or a follow-up added information. Keep those possibilities distinct.
This is an editorial workflow for a public explanation. Sending information through a competent authority’s reporting channel is a separate task with its own requirements. Removing private details from a web article should not alter the information that an authorized recipient is entitled to receive.
Preserve the geographic precision of the source
The WOAH reporting glossary explains that an outbreak location can be marked approximate when the precise location is unknown or cannot be shared publicly. An approximate marker should therefore remain labeled approximate. It should not be converted into the address of a nearby farm.
If the source identifies a region, write the region. Do not turn its map centre into an exact incident location. A country-level statement and a premises-level statement describe different geographic units; readers need to know which one supports the article.
| Source detail | Suitable editorial treatment |
|---|---|
| Named region | Retain the region and source attribution |
| Approximate location | Keep the approximation visible |
| Unknown event date | State that it is unknown |
| Corrected report | Link the correction and identify what changed |
| Private working address | Keep it out of the public export |
Check combinations, not only the address field
Removing a street address is only one part of preparing a release. Read the caption, filenames, image background, map annotations and downloadable rows together. A distinctive business sign plus an exact date and a small locality may reveal more than any field considered alone.
Treat this as a review question rather than an automatic claim of anonymity. Ask a reviewer what premises they could infer from the proposed public package. If identification remains plausible and serves no necessary public purpose, reduce detail or choose a different illustration. Keep the private source record under appropriate access controls.
The FTC’s business guidance supports collecting only necessary personal information, restricting access and retaining it for an identified need. Those general practices inform this workflow; they do not supply a universal publication permission or farm-record retention period.
Work through an illustrative update
Suppose a fictional official notice reports a status change for “Region A” without naming a farm. An editor drafts a regional summary, then adds a photograph supplied for background. Its caption contains a private operator’s name, and its filename contains a road name.
The regional paragraph is not enough to make that package suitable for publication. Remove the unnecessary identifying material, confirm the photograph’s intended use and review the final file actually served. Keep an internal note explaining the source, the change and the release decision. Nothing in this example describes a real event or premises.
Keep the dates meaningful
Separate the event date, the authority’s publication date and the date the website checked the source. Accessing an old report today does not make the event current. If the source gives only a month, avoid supplying a day that it never established.
When information changes, add a dated correction that identifies the affected statement. Keep the stable article address where appropriate, and update the source link to the exact revised report. A headline should not continue repeating a superseded status after the body has been corrected.
Review the complete public package
Open the rendered article, social-preview image and every attached download. Check visible text and the metadata actually included in exported files. Ensure the public map uses the same geographic scope as the explanation. A private spreadsheet hidden behind a reassuring page label is still a private spreadsheet being released.
Use the map-location privacy guide, image-sharing guidance, source reading and the correction route for the adjacent tasks. A useful update lets readers verify the official statement while avoiding unnecessary disclosure about the people and premises behind it.
Cite this reference
LivestockDefense. “Explain a disease-status update without identifying a private farm.” Updated 2026-10-29. https://livestockdefense.com/guides/how-to-report-a-disease-status-change-without-displaying-private-farm-addresses/
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.
- Federal Trade Commission: Protecting Personal Information: A Guide for Business
Source update: Not provided. Most recent check: 2026-10-29.
Necessary personal-information collection, access limitation and retention principles; no jurisdiction-specific farm-record duty or retention period inferred.
- WOAH Regional Representation for Asia and the Pacific: Glossary of reporting terms
Source update: 2026-10-07. Most recent check: 2026-10-29.
Approximate-location field can represent unknown or non-public precise coordinates; no current event status or legal reporting deadline inferred.