Three things to take away
- Use batch or pallet references across warehouses and vehicle changes.
- Separate event time, upload time and manual entry time.
- Handover includes record coverage and outstanding actions.
The situation: two records with a gap between them
The cold store and carrier keep separate temperature records. During a receiving dispute, both can export their own segment, but nobody can readily explain time on the dock or when a vehicle changed. Another round of phone calls is needed.
Begin with one transfer task. Link the batch or pallet to each leg, device and handover. Preserve both vehicle references and the transfer time when the load changes trucks, rather than treating a registration number as the identity of the goods.
- Cold-store releaseBatch / device linked
- Dock handoverLoading confirmed
- In transitLogger recording
- Depot receivingQuality review pending
Continuity: put separate segments on one timeline
Record release, dock waiting, loading, departure after closing and the next receiving milestone, with a source and confirmation owner. Display device event time separately from platform receipt time, align time zones and flag manual entries.
A travelling logger may help connect stages, but coverage depends on placement, battery, connectivity and handling. Show a data gap explicitly. Do not turn interpolation or a carried-forward reading into an apparently continuous measured record.
The minimum useful handover record
| Operating step | Action | Evidence to review |
|---|---|---|
| Load identity | Link batches or pallets across legs | Batch, device and vehicle-change mapping |
| Timestamps | Separate collection, upload and confirmation | Source, time zone and manual-entry flags |
| Ownership | Assign contacts and outstanding actions | Acknowledgement, owner and next step |
| Receiving | Check coverage and quality disposition | Gap explanation, attachments and findings |
Ownership: hand over the unresolved action as well
When dock waiting exceeds the agreed operating condition, the site contact checks capacity and load status. In-transit exceptions go to the relevant carrier and quality owner. Responsibility follows the agreed process and confirmed records, not a location point alone.
The receiver checks batch identity, device presence, accessible records and open quality actions. A transfer or other intervention should include a reason, time and operator so the next team understands what happened.
Review: establish coverage before claiming efficiency
Check milestone confirmation, data gaps, unresolved handovers and the steps required to retrieve a shipment report. Separate routine handling, queues and quality inspections when reviewing waiting; one elapsed-time figure does not explain the cause.
The intended output is a traceable release-to-receipt record. A system assembles evidence but temperature alone does not determine liability or product acceptance. Review agreements, physical checks and the quality finding together.
Questions, answered
Can records from different carriers be combined?
Agreed exports or interfaces can bring them together. First align load references, times, units and field meanings, while keeping source attribution.
How should an interruption appear in the report?
Show the gap, the last valid collection time and any later upload. Missing data must not appear as normal measured conditions.
