Mortality Event Logging and Root-Cause Tagging

Mortality logging captures not just a daily death count but the context needed to diagnose why, which system, which batch, observed cause category (disease, water quality, handling, predation, unknown), and ideally a photo or necropsy note attached to the event, since a bare count trend only tells a farm that something is wrong, not what. Structured root-cause tagging, using a controlled vocabulary rather than free-text notes, is what makes mortality data analyzable at scale: a farm running dozens of ponds can query 'show all mortality tagged low-dissolved-oxygen in the last quarter' only if every entry was tagged consistently at the time of recording, not reconstructed afterward from memory. A persistent design tension is capturing mortality fast enough during a crisis (when staff are busy actually responding to the die-off) versus capturing it accurately, which is why well-designed mobile logging lets a quick count be entered immediately with detailed cause tagging added later without blocking the initial record. Aggregated mortality-cause data across cycles and sites is also the raw input for predictive anomaly detection models, so inconsistent tagging at the point of entry quietly degrades every downstream analytics feature built on top of it.