A recording gap, late file start or waiting container may appear near handover. Comparing several handovers is more useful than generalizing from one event.
Align the handover time. Mark handover on the monthly table; keep file time, logger clock and download time in separate fields. Verify the timezone and any logger clock offset.
Examples around handover
- Preparation may be complete while a container waits to be closed.
- Recording may have started without a linked run ID.
- A container in the loading queue may pass to the next team.
Compare time windows
For the hour before and after handover, count runs, completed records, sample gaps and measured excursions separately. Report rates as well as raw counts.
Choose a first step
If a gap repeats, trial a handover checklist item for device status, container ID or pending work. Use the records to assess whether the step helps.
Timing guides review; it is not proof of carelessness or cause.
Track the change
Compare the same time windows before and after adding a check. Note any change in shift boundary or time definition in the comparison.
When there are several handovers
Group night and morning handovers separately; show run volume and record completion for each. Combining groups may hide different patterns.
