
Blog · UltraCold
Why ultra-cold alerts need an escalation ladder, not an SMS.
Most cold-chain alerts are sent. Far fewer are acknowledged. At −80 °C, the gap between the two is where shipments are lost.

Most cold-chain alerts are sent. Far fewer are acknowledged. At −80 °C, the gap between the two is where shipments are lost.
Ask a cold-chain team whether they have temperature alerts and the answer is almost always yes. Ask who acknowledged the last one, and how long it took, and the answer is often a pause. Alerts go to a shared inbox, to a phone that is on silent at night, or to a number that belonged to someone who changed roles last year.
For ordinary chilled product that is a nuisance. For −60 °C and −80 °C product it is the whole risk. A single warm hour can cost the shipment, and the product cannot be warmed and re-cooled into compliance. If the alert waits for the morning, the excursion has already happened.
An escalation ladder treats an alert as a task with a clock, not as a notification. If the first person does not act, the alert climbs to the next, and keeps climbing until someone does. In UltraCold the clock starts at 15 minutes to acknowledge; after that the alert moves through logistics, QA, customer QA and senior management, on a time-based ladder from T+0 to T+4 hours across 12 triggers.
| SMS or email alert | Escalation ladder | |
|---|---|---|
| Ends when | The message is delivered | Someone acknowledges and acts |
| If ignored | Nothing happens | The alert moves up to the next role |
| Record | A delivery receipt, if any | Who saw it, when, and what they did |
| Night and weekends | Same as daytime, often worse | Same ladder; the clock does not sleep |
The important design choice is that silence is treated as a signal. A ladder assumes nobody saw the alert until someone proves otherwise.
A ladder is only as good as its triggers. Many systems alert only when the hard limit is crossed, which at ultra-cold temperatures is often too late to save the product. We think three kinds of trigger matter, and they come in a sequence:
The second trigger is the one most often missing. Dry ice is frequently packed by habit rather than by lane, and the first sign of a problem is a rising temperature two hours before the hub. Our guide to dry-ice planning for ultra-cold shipments covers the calculation; the point here is that the plan should also produce an alert when reality drifts from it.
With one logger read at the destination, the investigation starts after acceptance and with no live evidence. With two loggers read live against the band and the hard limits, the ladder can act on a drift while the product is still cold, and a single faulty logger is less likely to cause either a false alarm or a missed one. We compare the two approaches in logger download vs live tracking.
An escalation matrix written in an SOP is a good start. A ladder that runs by itself, and records who acted, is what makes it real. More in the UltraCold guides.
A sequence of roles with time limits. If the first person does not acknowledge an alert within the window, it moves to the next role, and keeps climbing until someone acts, with every step recorded.
Drift beyond the band around target, dry-ice exhaustion risk before the next hub, and excursions beyond the hard limits. Alerting only on excursions is often too late.
Typically logistics, QA, customer QA where agreements require it, and senior management. Confirm notification duties with your QA and regulatory advisers.
See it on your own data. UltraCold — −80 °C, signed off at every step. Book a 30-minute working session with an engineer.