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.

An alert that is sent is not an alert that is seen

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.

What a ladder does that a message cannot

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 alertEscalation ladder
Ends whenThe message is deliveredSomeone acknowledges and acts
If ignoredNothing happensThe alert moves up to the next role
RecordA delivery receipt, if anyWho saw it, when, and what they did
Night and weekendsSame as daytime, often worseSame 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.

Alert on what is about to happen, not only what has

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:

  1. Drift. A reading that moves beyond ±2 °C around the target on either of the two loggers. Nothing is lost yet; this is the cheapest moment to act.
  2. Exhaustion risk. Dry-ice cover falling to two hours before the next top-up or hub. The temperature may still be perfect, but it will not stay that way.
  3. Excursion. A reading beyond −58 °C or −82 °C for 30 minutes becomes a non-conformance, with a QA disposition due within four hours.

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.

Why two live loggers change the conversation

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.

How we would design a ladder

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.

Questions

What is an escalation ladder for cold-chain alerts?

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.

Which temperature alerts matter for ultra-cold shipments?

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.

Who should be on the escalation ladder?

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.

General guidance, current as of the date above. Figures and examples are illustrative unless a source is linked.