How to monitor fish and shrimp health cases

A monitored case is a focused timeline for one livestock concern. It keeps observations, actions, media and outcomes together without turning an early suspicion into a diagnosis.

A monitored fish or shrimp health case is a separate timeline for one concern. It should identify the animal or group, record what was observed, show what action was taken and preserve what happened next.

Start a case when an observation needs follow-up across more than one entry. Keep routine feeding, maintenance and water records in their own logs, then link them to the case when relevant.

A case is not a diagnosis. Use neutral descriptions, preserve uncertainty and seek qualified veterinary support when the situation is severe, worsening or beyond routine husbandry.

Trust details

Role
Editorial team
Review details
How this was reviewed
Published
Last reviewed
Next review
On this page
  1. Define one clear case question
  2. Record the starting state
  3. Use a timeline, not a rewritten summary
  4. Separate evidence from interpretation
  5. Link relevant tank events

Define one clear case question

Use a title that describes the concern without asserting a cause: “female guppy resting near the surface” is better than “gill disease” when no diagnosis exists.

Create separate cases for separate animals or materially different concerns unless the evidence shows a shared group event.

Record the starting state

  • Tank and livestock identity.
  • Date and time first observed.
  • Neutral description of behaviour, appearance or injury.
  • Whether the concern affects one animal or a group.
  • Recent feeding, maintenance, livestock, equipment or water-record context.
  • Photo or video with capture context, when useful.
  • Immediate welfare action and the reason.
  • Planned next observation.

Use a timeline, not a rewritten summary

Add each observation and action as a dated event. Do not edit the first entry to match what you learned later. A preserved timeline shows when a sign appeared, when an action occurred and whether the response followed.

You can add a current summary at the top, but the event history should remain intact.

Separate evidence from interpretation

Record “white material visible beneath the abdomen in two photographs” as an observation. Record “possible external growth; identity not established” as an interpretation. Do not convert image similarity into a confirmed diagnosis.

When a qualified professional provides an assessment, record who provided it, the date and the exact advice followed.

Attach water results, feeding observations, maintenance, livestock additions and equipment changes that could help explain timing. A link shows association in the timeline; it does not prove cause.

Avoid copying every routine entry into the case. Include only what helps answer the case question.

Record actions precisely

  • What was done.
  • When it was done.
  • Which animal or tank was affected.
  • Product or equipment identity where relevant.
  • Who advised the action, if applicable.
  • What outcome was expected.
  • When the response would be checked.

Do not record an action as successful until the follow-up observation supports that conclusion.

Set escalation and welfare boundaries

A monitoring plan should state what would trigger immediate escalation, such as rapid worsening, severe injury, inability to swim normally, widespread group effects or failure of life-support equipment. The exact response depends on the situation and available qualified support.

Do not delay urgent welfare action merely to complete the record. Document the action after the animal is stabilised or support has been contacted.

Review the case at each check

  1. Compare the current observation with the previous one.
  2. Record better, unchanged, worse or unclear only when the description supports it.
  3. Check whether the planned action was actually completed.
  4. Add any new water, feeding, maintenance or media evidence.
  5. Set the next check or escalate.

Close the case with an outcome

Close a case when the concern resolves, the animal is transferred to another responsible process, a professional plan takes over, the animal dies, or monitoring no longer has a meaningful next action.

Record the outcome, final date, unresolved uncertainty and any routine change that will continue. Do not delete an unsuccessful case; it remains part of the tank history.

Common case-tracking mistakes

  • Using a diagnosis as the case title before it is established.
  • Mixing several animals and unrelated signs in one timeline.
  • Adding actions without times or follow-up checks.
  • Treating a linked maintenance event as proof of cause.
  • Relying on photos without written context.
  • Leaving resolved cases open indefinitely.

Example case opening

“Case opened 6 August, 17:40 — adult shrimp in 100-litre tank. Green material visible under the abdomen in two close photographs; shrimp still grazing. Identity not established. No medication added. Animal moved only if welfare or contagion risk requires it after further assessment. Next checks: behaviour in two hours, comparable photo tomorrow, and review of recent water and livestock records.”

Keep the case connected but bounded

AquaticFinder Journal can link journal entries, media, water tests and maintenance to a monitored case while preserving each record in its original workflow. A structured folder or spreadsheet can use the same principle.

The useful rule

Describe what you can observe, record every action and response in order, and keep uncertainty visible. Escalate welfare concerns promptly and close the case with an honest outcome.

Continue the workflow

Editorial details and corrections

Role
Editorial team
About the author
AquaticFinder publishes practical aquarium guidance built from approved outlines and directly reviewed published sources.
How this was reviewed
Prepared with AI assistance and checked for workflow accuracy, visible scope, clear uncertainty and avoidance of diagnosis or unsupported husbandry claims.
Published
Last reviewed
Next review
Correction status
Initial publication; no correction history

Submit a correction