Time out of refrigeration, usually shortened to TOR, is the cumulative time a temperature sensitive product is allowed to sit outside its labeled storage range before its stability data no longer covers it. It is a budget, not a single pass or fail moment: a vial that spends twenty minutes on a loading dock and forty minutes in a delivery van has used an hour of a two hour TOR allowance, with no single event on its own looking like a problem.
That allowance comes from the manufacturer's own stability testing, not a regulatory default. A product with a wide stability margin might carry a TOR of several hours; a fragile biologic might carry one measured in single digit minutes. A TOR figure sitting in a stability filing is also not fixed for the product's whole life: a batch fresh out of manufacture with maximum remaining shelf life can sometimes absorb a longer deviation than the same product close to its expiry date, because the underlying stability margin itself narrows as the product ages.
A cumulative budget across the product's life
TOR does not reset at each handoff. It accumulates across the entire path a batch travels, from the moment it leaves controlled cold storage at the manufacturing site through every transfer, dock wait, and last mile delivery, until the moment a patient or a kitchen actually uses it. A batch that draws down half its TOR budget crossing a border and clearing customs arrives at the hospital with only the remaining half left to spend on receiving, storage, and dispensing, no matter how well the hospital's own cold room performs afterward. This is also why TOR belongs to the batch, not to any single leg of its route: a distributor auditing only their own transport record and finding it clean can still be handling a batch that arrives with almost nothing left to spend, because the deficit was run up somewhere earlier in the chain, out of that distributor's view entirely.
Allocating the budget across the chain
A total TOR allowance has to be split between the manufacturer's own handling, the distributor's transport and warehousing, and whatever unmonitored time the product spends in the hands of the end user before it is administered or consumed. Quality and regulatory affairs teams, the ones who filed the underlying stability data, usually set how the allowance splits between segments; the carriers and pharmacists moving the actual product rarely see the number itself, only a pass or fail flag at the end of their own leg. A common failure is allocating generously at the front of the chain, where handling is well controlled and well documented, and leaving too little for the last mile, where handling is least controlled and least documented. Contract terms between a manufacturer and a distributor sometimes specify each party's share explicitly, in hours or minutes, precisely so a dispute over who caused an eventual overrun has a documented allocation to point to instead of an argument after the fact.
Tracking it in practice
Tracking TOR means totaling every interval the product spent outside its labeled range, not just the worst single reading. That requires a continuous temperature data logger or real time monitoring feed for the whole route, because a spot check at delivery cannot reconstruct how many separate excursions added up along the way. A shipment can pass a receiving check that only looks at the temperature at arrival and still have exhausted its entire TOR budget through several short excursions nobody added together. Software that automatically sums logged excursion minutes against the approved allowance exists, but most cold chains still calculate TOR by hand, after the fact, only when a shipment's temperature chart already looks borderline, which means the calculation usually happens too late to change anything about that shipment's outcome.
Silent draws on the budget
A surprising share of TOR gets consumed by ordinary handling that nobody logs as an event at all: a driver leaving a door open while checking paperwork, a pallet queued on a warehouse floor before anyone scans it into cold storage, a courier's cab running warmer than the trailer during a short urban delivery leg. None of those moments trigger an alarm on their own, because none of them breaches an alert threshold by much, but each one draws down the same finite allowance as a longer, more obvious excursion. A TOR budget that only counts the incidents big enough to trigger an alert is undercounting the shipment's actual exposure by the sum of everything that stayed just under the threshold.
Nobody knows their remaining budget
In practice, most product moving through a cold chain has no running total attached to it at all. Each handler along the route can usually say whether their own leg stayed in range, but almost nobody carries forward a cumulative figure from the leg before, because that requires every previous handler's data to be collected, converted to the same units, and added up before the next leg begins. The result is a budget that exists on paper in the stability filing but is rarely calculated for any real shipment in transit, which means most product in circulation is closer to its TOR limit, or already past it, than anyone handling it actually knows.