Fish Kill Incident Record: First-24-Hour Field Sheet

Review overdue

This artifact passed its 2026-10-15 evidence or scheduled review date and is excluded from search-engine discovery until it is reassessed.

Browser-local record boundary

Field values are not uploaded by this form. Standard page analytics may record this page visit, not entered values. Nothing is autosaved: download a completed-record CSV or print before leaving. Downloads may contain personal, precise-location, conservation-sensitive, incident-sensitive, restricted-infrastructure, or health-sensitive information; use approved storage and sharing. Do not publish restricted locations, private assets, household or health records, or conservation-sensitive evidence unless each controlling authority and owner has approved the exact scope and precision.

Computed record state

blank

Operational dispositionESCALATE: responsible-authority direction required

Stable record IDNot started

Full-record documentation0 of 13 required fields documented

Safety and authority boundary

Do not enter water, touch carcasses, smell closely, collect samples, or operate equipment to complete this sheet. Human or animal exposure, an active spill or sewage release, unsafe access, or mass mortality requires current local emergency, health, wildlife, or environmental authority direction. This record does not determine cause, declare water safe, or authorize cleanup or treatment.

LakeTech Learning Center · Field record

Fish Kill Incident Record: First-24-Hour Field Sheet

Template ID: fish-kill-incident-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: ESCALATE: responsible-authority direction required
Reviewer attestation: Not recorded
Source guide: fish-kill-triage

Start a browser record to enter values and create a stable ID. You can still print this blank form.

Record view Guided workflow view Full record

Guided view follows recorded workflow branches and preserves evidence from branches you later change. Full view and print always include every field.

1. Record control

Use stable IDs. Keep personal contact details out of exports unless your program requires and protects them.

Core record

Record ID · requiredNot recordedGenerated when you start a browser record; preserved on export and import.Project or parent record IDNot recordedCompleted by and role · requiredNot recordedSensitive data class: personal.Reviewer attestation recorded byNot recordedBrowser-entered reviewer details are not identity-verified and do not authenticate validation.Sensitive data class: personal.Reviewer attestation dateNot recorded

2. Immediate safety gate

For every item record Yes, No, or Unknown. Any Yes or unresolved Unknown can require stopping field work and contacting the responsible authority.

Core record

Human illness or exposure · requiredNot recordedSensitive data class: incident sensitive.Pet, livestock, or wildlife exposure · requiredNot recordedSensitive data class: incident sensitive.Suspected spill, sewage, or active discharge · requiredNot recordedSuspicious scum, discoloration, odor, or sheen · requiredNot recordedUnsafe boat, shore, ice, weather, electrical, or aeration condition · requiredNot recordedAccess restriction: issuer, scope, and timeNot recordedEmergency, Poison Control, clinician, veterinarian, or agency directionNot recorded

3. Discovery and location

Separate what the recorder observed from what another person reported.

Core record

Waterbody · requiredNot recordedCounty, state, Tribal, or local jurisdiction · requiredNot recordedDiscovery date and local time · requiredNot recordedUTC offset (for example −07:00) · requiredNot recordedLast-known-normal date, time, and sourceNot recordedMortality statusNot recordedLatitude, longitude, datum, accuracy, and sourceNot recordedSensitive data class: precise location.Nearest access, affected-area extent, and map/photo IDsNot recordedSensitive data class: precise location.

4. Mortality and scene observations

Record estimates as estimates and keep an original photo/video evidence log.

Core record

Estimated count or range and estimation method · requiredNot recordedAffected shoreline length or area, unit, and methodNot recordedSpecies/taxa, size classes, and identification confidenceNot recordedDistribution: shore, cove, inlet, outfall, aerator, open water, or lake-wideNot recordedWater color, clarity, scum, foam, sheen, odor from safe distance, discharge, vegetationNot recordedWeather, rainfall, wind, ice, inflow, outages, treatment, construction, or upstream-event context and sourceNot recordedEvidence IDs, original filenames, time, station/direction, description, photographer, original preservedNot recordedSensitive data class: incident sensitive.

5. Agency-directed measurements and samples

Only collect or handle samples under appropriate direction. Link full casts to the profile sheet; never erase anomalies.

Core record

Reading IDs: station, time/offset, depth/reference, total depth, temperature, DO, pH, conductance, turbidity, units, flagsNot recordedInstrument make/model/serial, calibration/verification record, stabilization, validation stateNot recordedSensitive data class: operational.Authority/case and plan reference; sample IDs; TAN, NH3, NH4+ or other measurand; as-N or other basis; matrix/fraction/method/unit; station/depth/time/offset; paired pH, temperature, and DO record IDs; container, preservation, holding, receiving lab; custody transfers, receipt/accession; qualifiers, detection/reporting limits, validation state; applicable criterion source/status/jurisdiction/use/effective date; hypothesis, not confirmed causeNot recorded

6. Notifications, actions, and handoff

Do not collapse facts, hypotheses, and unknowns into one cause field.

Core record

Call log: time, organization/person, information given, direction, case number, next updateNot recordedSensitive data class: incident sensitive.Actions/system changes: time, authority, operator, exact change, before/after reading IDs, effect, rollback decisionNot recordedConfirmed factsNot recordedRanked hypotheses, not confirmed causeNot recordedUnknown or pendingNot recordedNext responsible person, action, and due time · requiredNot recorded