Keep the known interval and its uncertainty
Record the last verified working observation, first confirmed problem and basis for each. An alarm may mark detection or communication rather than physical onset. Preserve the interval where exact timing is unknown instead of assigning the notification timestamp as the start.
Retain power, controller and operator records with their actual meanings. A command, current draw, motor sound and competent flow assessment are different evidence. Do not combine them into one unlabeled “pump on” state.
Map the actual system path
Keep the pump, branches, relevant valves and receiving tanks or loops identified separately. A design diagram should retain its version and be checked against actual operations by competent staff. Bypasses or temporary arrangements can change which locations are affected.
This guide supplies no repair, bypass, restart or emergency water-management procedure. Follow the responsible aquatic-health, engineering and safety plan. Do not enter an unsafe electrical or water setting to obtain a missing record.
| Timeline layer | Evidence to preserve |
|---|---|
| Interruption | Known start bounds and detection |
| Equipment | Exact component and competent findings |
| Flow | Actual verification and covered locations |
| Water | Measurement time, method and position |
| Fish | Group, behavior and professional assessment |
Preserve response changes in order
Record actual actions, responsible people and implementation times. A discussed plan is not evidence of completion. Keep source-water changes, temporary equipment and related operations separate so subsequent measurements retain the right context.
Do not use a later satisfactory value as proof that the earlier interval was harmless. Likewise, a missing earlier measurement does not establish a particular cause of illness. Give the professional team the actual observations and uncertainty.
Work through a partial restart
In this fictional system, the motor restarts and the alarm is acknowledged. A later competent check finds that a branch has not regained the intended operation. The maintenance ticket initially used the motor timestamp as restoration for every tank.
The corrected log preserves separate motor, branch-verification and animal-assessment times. It does not calculate each fish’s exposure from the initial ticket or declare recovery from a dashboard state. The qualified team evaluates the actual sequence.
Close technical and clinical tasks separately
Retain competent repair verification and the scope of return-to-use decisions. Keep unresolved temporary work and the person responsible through the next shift. A closed part-replacement task should not erase an ongoing system or fish-health concern.
Preserve stock movements, removals and any later findings with their group identities. A quieter or less crowded tank after fish move does not demonstrate recovery in the original population. Update derived timelines and summaries when source records are corrected.
Use aquaculture references, water-exchange records and before-dawn oxygen history for related distinctions. A useful interruption account follows actual operation and verified recovery without allowing one command timestamp to stand in for the whole system.
Make each restoration claim name its location
A useful restoration entry says what was verified, where and by whom. The motor, one branch and the whole receiving system can have different supported times. Keep those differences in the record instead of allowing the first green dashboard state to close every downstream question.
In a second fictional outage, an operator acknowledges an alarm while a technician continues checking the actual route. The initial export uses acknowledgement as physical restoration. Separating the communication event from competent verification preserves both useful timestamps and the still-uncertain interval.
The next shift needs the current temporary arrangement and outstanding checks as well as completed repair work. Identify the responsible person for each question. A closed parts order or work ticket should not conceal continuing fish observations or an unverified component.
Frequently asked questions
Does a cleared alarm prove normal flow throughout the system?
Retain what the alarm actually represents and the scope of verified operation. A signal change should not be promoted into a system-wide conclusion without the appropriate technical evidence.
Can a later water reading describe the outage interval?
It represents its actual collection point and time. Preserve earlier gaps and response events so the qualified team can interpret the sequence without a fabricated exposure history.
Does moving fish establish recovery in the original group?
Keep the cohort relationship, actual transfers and subsequent observations. A different visible population or distribution after a move does not measure recovery among the original animals. Technical restoration and clinical follow-up need their own evidence and responsibility. The account should support the site contingency plan without supplying a repair, restart or emergency water-management procedure.
A concise incident summary should preserve the actual last verification, discovery bounds and each supported restoration stage. Name any interval that remains unknown so a later reader does not treat a software status change as complete physical evidence.
Cite this reference
LivestockDefense. “Reconstruct a recirculating-system pump interruption honestly.” Updated 2026-11-03. https://livestockdefense.com/guides/recirculating-fish-system-pump-downtime-timeline/
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 ↗