Food safetyTemperature monitoring
Cold-chain handovers: document the transfer between two teams
A cold-chain handover record should connect the goods, dispatch and receiving parties, transfer time, relevant observations and acceptance decision. It helps investigate a particular transfer; it is not proof of conditions during an unmeasured journey.
At a glance
A cold-chain handover record should connect the goods, dispatch and receiving parties, transfer time, relevant observations and acceptance decision. It helps investigate a particular transfer; it is not proof of conditions during an unmeasured journey.
Define the decision behind the record
Clarify which team creates the record and which team acknowledges receipt. The sending and receiving observations may use different devices or methods. Preserve those differences rather than merging them into a single apparently continuous measurement.
Connect dispatch, receipt and the transfer decision
Agree which lot identifiers, quantities, units, locations and document references both teams will use. Define the approved checks at dispatch and receipt and who handles a discrepancy. The purpose is to connect the same transfer across two records, not to force the sending and receiving teams to report identical observations taken at different times.
Record actual dispatch and receipt events with their respective checks and methods. Keep substitutions, partial quantities, damaged units and differences in identity explicit. If the receiver records a discrepancy, link its decision to the original transfer rather than creating an unconnected exception that the sending team cannot retrieve.
Reconcile the transfer by confirming what was sent, received and left unresolved. Retain delivery evidence and the responsible review. Test a complete transfer, a split receipt and an identity mismatch. A reviewer should be able to follow each actual event and identify the outstanding decision without assuming that a signature confirms every condition of the product.
Worked example
A central kitchen sends identified containers to another location. The sending team records dispatch references, and the receiving team records its observations against the same transfer. A discrepancy is escalated with both sides of the handover available.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Transfer and product identifiers
- Sending and receiving locations
- Dispatch and receipt timestamps
- Observation source, result and unit
- Acceptance decision and exceptions
Example record and review decision
Fictional record example: TRANSFER-01 / LOT-A: sender, receiver, dispatch and receipt times, actual checks, quantity and equipment references.
Compare the sending and receiving records for the same lot, unit and transfer. Document any time or quantity discrepancy.
A transport document with a signature but no lot reference may confirm handover without establishing which stock it covers.
Test the review, not just the form
Review a completed transfer from the receiving location backwards. Confirm that both teams can find the same shipment without changing its identifier. Where continuous monitoring is claimed, test the actual device and integration rather than inferring it from the handover form.
A few useful answers
Does a receipt measurement prove the whole journey stayed within limits?
No. It describes that observation. Assess transport conditions using the evidence required by the applicable procedure.
Must dispatch and receipt readings be identical?
They are observations made at different events and may use different approved methods. Record their context and assess discrepancies under the procedure. Do not edit one result simply to make the two records appear consistent.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
