Group recording gaps first by logger identity, then by container number. If one container stands out, place each run's logger serial, container label and start and end times side by side. This match checks which record the gap belongs to.
Three checks
- Does the same logger show gaps in other containers?
- Do gaps persist in the same container with different loggers?
- Do the container number on the form, in the logger file and on the physical label agree?
Matching records
For each run, verify container identity from the dispatch form and logger identity from its label; attach the download filename and its time information too. This separates a pattern that stays with the container from one that follows the logger. Association alone does not prove a cause.
Recording position
Add the logger's position and mounting method inside the container to the run form. If the same logger has been used in different containers, compare positions against the model's permitted locations in its manual. Record a position change and its date before treating earlier and later readings as one series.
Verifying the label
Do not guess a number to fill in a worn or hard-to-read label. Verify the physical identity and flag files matched to the wrong container; keep any correction traceable in the record history. If the identity remains uncertain, do not attribute the result to that container.
Recording the finding
State the date range reviewed, verified container and logger identities, position and any unresolved gaps. This note gives a reference point if the same container is reviewed again.
A consistent comparison. If gaps recur, use the same identity fields and time basis for every run. Only matched records show whether gaps move with the container or logger; follow the model manual and authorized quality process for conclusions about function or accuracy.
