The Field That Nobody Reads Until the Lawsuit
"Does animal have tags or bands?" That question — sitting in the middle of an incident record — is the one that separates documentation from litigation exposure. A tagged animal is someone else's animal. It means another agency, another study, potentially a federal migratory bird permit in play. If your response log doesn't capture that on intake, and the animal later dies in care or gets released in the wrong corridor, you've got a chain-of-custody gap that a legal inquiry will find in minutes.
Wildlife response coordinators who've been through a regulatory audit understand this viscerally. The band number, the tag color, the banding station code — these aren't trivia. They're the first call you make after the animal is stable, to the Bird Banding Lab or to the state program that owns the transponder. That field exists because the alternative is discovering mid-necropsy that you handled a marked research subject from a two-year breeding study.
How the Log Works the Night Shift
A call comes in at 22:40. The duty officer logs the date and time immediately — not after the response, not in the morning. The Caller's name, number, and address go in concurrently. This isn't courtesy data. If the animal's location turns out to be wrong — which happens often when callers are distressed and describing landmarks in the dark — the address gives you a geographic anchor to start from. You can triangulate from there.
Incident Description and Where exactly is the animal located? are separate fields intentionally. The description captures the behavioral state: down but alert, flighting weakly, in the roadway, aggressive. The location field captures the physical coordinates: between the drainage ditch and the fence line on the south access road, approximately 40 meters from the main gate. Officers who conflate the two into one text block create records that read back ambiguously. Dispatching a second unit to a vague address because the first field note mixed "near the canal" with "lying on its side" wastes response time you don't have.
Species is documented as precisely as field conditions allow — "raptor, possibly red-tailed hawk, juvenile plumage" is a valid entry. "Bird" is not. This matters for triage prioritization, for contacting the right rehabilitation facility, and for the post-incident report. Generalist entries create reclassification work downstream.
The Photos subheader exists because the image record supplements everything else. A shot of the animal on intake, before handling, creates a baseline for injury documentation. A shot of the tag or band creates a permanent record without relying on handwritten transcription accuracy.
What a Month of Records Actually Builds
After 30 days of properly logged responses, the data starts to behave like an epidemiological map. You can see which species are appearing at what frequency, which callers are repeat reporters (often indicating a hotspot in their neighborhood), and which types of incidents are generating the longest time-per-mission logs.
Time spent — the field that officers often undervalue — becomes a resource allocation argument when it's aggregated. Thirty-eight minutes average for raptor-down calls versus twelve minutes for small mammal disorientation calls is a number you can bring to a budget conversation. Without the log, it's anecdote.
Duty officer attribution by record also matters when response protocols are being audited or refined. If certain officers' calls consistently resolve faster or generate better species ID data, that's a training signal worth following.
The record closes when the outcome is documented. Released on site. Transported to clinic. Deceased on arrival. Found deceased. That outcome field is the last data point in a chain that started with a caller's address at 22:40, and every field in between either supports the next decision or doesn't.