Cold chain evidence is not the same thing as “the van was cold”. When a chilled or frozen delivery is questioned, the useful record has to answer a more specific question: what was checked, when, against which control, and what happened if the reading was outside it?
That distinction matters because temperature control sits across a journey. Stock can leave a controlled warehouse, spend time in a vehicle, move through multiple door openings and then be handed to a customer. The evidence should follow the control points that matter to your own products and food-safety system rather than relying on one number written at the end of the day.
This article is operational guidance, not legal advice. Temperature requirements vary by food type and jurisdiction. Before setting limits, check current food-hygiene guidance, Food Standards Scotland's CookSafe temperature-control guidance and the rules in your own HACCP procedures.
Cold chain evidence begins with the control you are trying to prove
Do not start with the device. Start with the control. Which products are temperature controlled? What limits apply? At which points are readings or checks required? What action should be taken when a reading is outside the configured range? Those answers should come from your product requirements, risk assessment and current guidance.
Define the control
Product, limit and control point
Capture the check
Reading, time and context
Record the exception
What was outside the rule?
Record the action
What happened next?
Tie it to delivery
Route, customer and visit record
A software threshold only helps after the operating limit has been defined. Do not copy one temperature across every product or route simply because a system needs a value. Set the threshold from the control your business is required to follow, then use the software to record whether that control was met.
Build the evidence around the journey, not one end-of-day number
| Control point | Operational question | Evidence to retain |
|---|---|---|
| Before loading | Was the stock released into the route under the correct control? | Product/batch identity, relevant temperature check, date/time and any exception |
| During the round | Did the controlled condition remain within the configured operating rule? | Scheduled/intermediate readings, threshold result, alert and action where relevant |
| At handover | What was the condition at the customer visit? | Visit-linked reading where required, timestamp, delivery record and proof |
| Exception | What did the team do when the control failed? | Reason, action, affected stock, escalation and disposition |
The table is deliberately non-numeric because temperature limits depend on the product, process and applicable guidance. GOV.UK's food-safety guidance for delivery reinforces the wider point that food-safety responsibility continues through delivery; your own controls determine what evidence must be retained for the products you carry.
The weakest record is usually the exception, not the normal reading
A page of in-range readings is reassuring. The operational test is what happens when one is not. Does the driver know whether to stop the handover, isolate stock, call the office, record a reason or follow a product-specific instruction? Can the office later see that action alongside the reading?
Software should not decide what happens to affected food. That action belongs in your food-safety procedure and depends on the incident. The system's role is to make the reading, exception and action visible so the team does not have to reconstruct the event later from a phone call or separate note.
Three evidence gaps that only show up when somebody asks a question
A cold-chain record can look complete on a normal day and still be weak when a customer, technical manager or auditor asks what happened to one delivery. Three gaps are worth testing deliberately.
A reading with no delivery context
The number may be valid, but if it is not tied to the route, customer, product or time, somebody still has to work out what it proves.
An alert with no recorded action
The system may show that a threshold was crossed, but the evidence is incomplete if the next decision exists only in a phone call or memory.
A clean handover with a missing middle
A satisfactory reading at delivery does not explain what happened earlier in the round if intermediate checks or exceptions were required by your own control plan.
The point is not to create more records for the sake of it. It is to make sure the records already being captured answer the question somebody is likely to ask later: what control applied to this delivery, and can you show that it was followed?
Join the temperature record to the delivery record
Temperature proof is stronger when it is attached to the operational event it describes. A reading with no customer, route or timestamp may prove that somebody measured something; it does not necessarily prove the condition of a disputed delivery.
This is where electronic proof matters. RouteMagic's ePOD workflow captures the delivery handover, while visit records and the Driver App keep the field event tied to the route and customer. The existing article on delivery exceptions is useful when you want to trace how a disputed drop becomes credits, redelivery and finance work downstream.
Record temperature checks as part of the route
RouteMagic's Temperature Monitoring workflow can prompt checks at intervals through the round, compare readings with configured thresholds, raise alerts and compile a cold-chain log. Temperature reports provide another review point. The advantage is that the check sits inside the route workflow, so it can be matched to the delivery rather than stored on a separate sheet.
The threshold still comes from your own food-safety controls. Set the prompts and limits to match those controls, then make the exception path clear to the driver. For management review, reporting and analytics provides an operational view without changing who owns the food-safety decision.
Audit the evidence by asking for one real delivery
The fastest way to test a cold-chain record is not to inspect the dashboard. Pick one completed controlled delivery from last week and ask somebody who was not on the route to reconstruct it. Can they identify the product, see the relevant readings, understand whether the configured control was met, find the handover evidence and see what happened if there was an exception?
If the answer requires a driver's memory, a WhatsApp photo or a temperature sheet in another folder, the cold chain may have been controlled physically but the evidence chain is still fragmented. Fix the join before adding more readings.
Conclusion
Cold chain evidence is strongest when it is built around the control you actually need to prove. Define the products and limits from current guidance and your own food-safety system, identify the relevant control points through the journey, and make the exception process as clear as the normal reading. Then tie those records to the customer visit so a later question can be answered from one traceable event rather than several disconnected files. RouteMagic can support prompts, configured thresholds, alerts, temperature reporting and a compiled cold-chain log inside the route workflow, but your food-safety procedure still sets the rule. As a practical test, choose one controlled delivery from last week and ask someone outside the route team to reconstruct it without calling the driver or searching through separate folders.
