How to Document a Cold-Chain Handover Between Carriers and Receivers

A cold-chain handover record should make one question easy to answer later: what happened when responsibility for this load moved from the carrier to the receiving team?

The record does not need to prove that every condition was perfect. Its practical job is to preserve the facts available at the transfer point, identify the people and organisations involved, link the shipment to its temperature evidence, and make any unresolved issue visible to the person authorised to decide what happens next.

This matters because physical receipt, commercial receipt and final quality acceptance are not always the same event. A receiver may need to acknowledge that pallets arrived while a temperature record, damaged package or access event remains under review. Whether that distinction is permitted depends on the product, the parties’ agreement and the applicable operating requirements.

Define the handover point before the vehicle arrives

A usable handover begins before the vehicle reaches the gate. The carrier, warehouse and product owner should understand what event marks the transfer of custody in their process. It might be arrival at a designated bay, completion of unloading, a seal check, count verification, or an authorised receiver’s signature. The relevant event is the one the parties have agreed and documented—not a generic industry convention.

Set out the responsibility boundary in the shipment instructions or route procedure. At a minimum, identify:

• the carrier organisation and operating contact;
• the receiving organisation, site and authorised receiving role;
• the planned delivery window and handover location;
• the shipment reference and handling category;
• the event that starts unloading and the event that closes the handover; and
• the escalation contact if the load cannot be accepted as planned.

This preparation reduces a common ambiguity: a driver may regard unloading as the end of transport responsibility, while the receiving team may believe responsibility changes only after a condition check. Neither assumption is a substitute for a defined process.

Handling requirements should come from the product owner’s approved instructions, contractual terms or shipment documentation. General cold-chain guidance commonly warns against applying one procedure to every temperature-sensitive shipment because product, packaging, route and handling conditions can differ. That is a useful planning principle, but it does not establish a universal operating rule for food, agricultural goods or Chinese operations.

Record the minimum facts needed to reconstruct the transfer

A handover form should be short enough for a busy dock but complete enough for someone not present to understand the transfer. The aim is traceability, not paperwork for its own sake.

Record facts that can be observed or identified at the time. If a field cannot be completed, mark it as unavailable and open an exception rather than filling the gap later from memory.

A practical base record includes the following:

The list is an All China Agriculture operational template, not a legal form. Some loads may need more fields; others may need fewer. For example, a seal check, device calibration record, electronic signature, photo or GPS reference may be appropriate only where a product requirement, customer agreement or internal procedure calls for it.

Attach temperature evidence without treating one reading as the whole story

A temperature value observed at arrival can be useful, but it is not necessarily a full account of the journey. It may reflect air near a door, a display location, a short period after access, or a reading taken at a different time from the product condition being assessed.

The handover record should therefore identify the evidence reviewed rather than relying on an unexplained number. Depending on the shipment process, this may include:

• the logger, sensor or monitoring-device identifier;
• the time the device record was reviewed;
• the available journey record or downloaded file reference;
• any visible alarm status or reported alert;
• the vehicle display reading observed at arrival, including the observation time; and
• the person who supplied or reviewed each record.

Keep the evidence and the interpretation separate. “Vehicle display showed a stated value at 09:12” is an observation. “The load meets release requirements” is an acceptance decision that may require review against product-specific criteria.

For regulated drug products, Health Canada’s guidance on temperature control during storage and transportation describes receiving as an important point in the distribution chain and discusses information sharing among parties. That guidance is specific to its Canadian drug-product context and should not be treated as a requirement for food, agricultural products or operations in China. Its broader lesson is operational: receiving teams need access to relevant information if they are expected to make a defensible handover record.

Do not insert a generic chilled or frozen limit into the form unless the limit is part of the approved handling plan for that load. Temperature criteria can depend on the product, packaging, expected exposure conditions, stability information and applicable requirements.

Make exceptions visible and assign an owner before the handover closes

A missing record, alarm, late delivery, damaged carton or unexpected access event is not automatically proof that a product has failed. It is an exception requiring a documented route to decision.

The handover record should capture the facts without pre-judging the outcome. A simple exception entry can include:

1. What was observed: describe the missing document, alarm indicator, package damage, access concern or other condition.
2. When and where it was observed: include time, location and the person making the entry.
3. Supporting material: reference photos, logger files, seal records, emails or other material where used.
4. Immediate status: state whether unloading paused, goods were segregated, goods were physically received pending review, or another agreed interim action was taken.
5. Notification route: identify who was informed, by what method and at what time.
6. Decision owner: name the role or organisation authorised to determine disposition.
7. Next deadline: set a time for the next update or decision, rather than leaving the case open indefinitely.

Avoid terms such as “spoiled,” “safe” or “rejected” unless an authorised person has made that decision under the relevant procedure. The carrier may supply facts about transport and monitoring; the receiver may document condition at delivery; the product owner, quality function or customer may hold the authority to decide disposition. Those responsibilities should be clear in the shipment agreement or operating procedure.

Use a two-party checklist that separates observation from acceptance

A two-party workflow helps prevent a signature from carrying more meaning than either party intended. Each party should be able to see which items are observations, which are linked records and which require a decision.

Use the following checklist as a starting point for one route or customer process.

Before unloading

• Confirm shipment reference, vehicle or unit identifier and receiving location.
• Confirm the authorised carrier and receiver contacts are present or reachable.
• Check whether the agreed handover point and unloading process are understood.
• Record seal or access status where the shipment process requires it.
• Identify the temperature evidence expected with the load.

During receipt

• Record arrival and unloading times.
• Record visible pallet, package or container condition factually.
• Reference the logger, monitoring device or journey record available.
• Record the time of any displayed-temperature observation.
• Open an exception entry for missing, unclear or unexpected information.

At handover closure

• State whether physical receipt was acknowledged.
• State whether final acceptance is complete, pending or not applicable under the process.
• Assign an owner for every unresolved exception.
• Record the escalation contact and next review time.
• Ensure both parties can retain or access the completed record and linked evidence.

A receiver may be able to acknowledge physical receipt while quality review remains open, but that approach should only be used where the parties’ product-specific process permits it. It is not a universal solution for disputed or temperature-sensitive loads.

Close the record and improve the next transfer

The completed handover record should be stored with its linked temperature evidence, delivery documents and exception references according to the team’s document-control process. Do not rely on a message thread or an individual phone as the only location for a disputed delivery record.

For a practical next step, trial the form on one carrier-to-receiver route. After several handovers, review where records were incomplete or delayed. Look for recurring problems such as unclear responsibility boundaries, missing logger references, inconsistent time entries or escalation contacts that are no longer current.

Then make one controlled update: clarify a field, revise a role instruction or add an escalation contact. A shorter form that reliably captures the transfer point, evidence and exception owner is usually more useful than a detailed form completed inconsistently.

Frequently asked questions

What should a cold-chain handover record include?

It should identify the shipment, carrier, receiver, location, transfer times, observed condition, available temperature evidence and any unresolved exception. The exact fields should follow the load’s handling instructions, agreement and internal procedure.

Who is responsible for temperature records at a carrier-to-receiver handover?

Responsibility should be assigned in the parties’ agreement or operating process. The carrier may provide journey evidence, while the receiver documents what was reviewed at delivery. A product owner or quality role may be responsible for interpreting an exception and deciding disposition.

What should happen if temperature evidence is missing at delivery?

Record that the evidence was unavailable, identify the missing item, notify the agreed contact and assign a decision owner. Do not silently complete the record from assumption. The appropriate interim status depends on the product-specific procedure and agreement.

Does a temperature excursion automatically mean the load must be rejected?

No. An alarm, deviation or missing record should trigger a documented review, not an automatic conclusion. The authorised decision-maker should assess the available evidence against the load’s approved requirements and applicable process.