On this page
The Reflex-Quarantine Problem for Kenyan Distributors
A 2 to 8C vaccine consignment clears at Jomo Kenyatta, sits on the apron during a power-bank changeover, and the data logger shows a 90-minute hold that touched 11C. The warehouse reflex is to quarantine the lot and wait for the manufacturer to answer an email that may take a week. Meanwhile the product ages, the customer waits, and nobody can say whether the excursion actually mattered. That reflex is expensive, and under PPB Good Distribution Practice it is also not what an inspector wants to see: a quarantine with no reasoning behind it is as weak as a release with no reasoning behind it.
The better question is not "did it go above 8C?" but "how much of the product's allowable thermal exposure did this event consume?" Most refrigerated biologicals are licensed with a known tolerance for short excursions, often expressed by the manufacturer as a cumulative budget you can convert into degree-hours: temperature above the limit, multiplied by the time spent there, summed across the product's whole labelled life. The Stability Budget Calculator turns a logger trace into that single number so you can see how much budget an event spends and how much is left.
This guide works one realistic event end to end, explains the arithmetic so your team can reproduce it, shows what each output means, and shows how to write the decision up so it survives an audit. It is a companion to your temperature excursion SOP, not a substitute for the manufacturer's stability data or your QA sign-off.
Worked Example: A 2 to 8C Vaccine and a 90-Minute Hold
Take a vaccine labelled for storage at 2 to 8C. The manufacturer's stability dossier allows a cumulative excursion budget of 20 degree-hours above 8C across the product's labelled shelf life. That is the whole tank of fuel the lot is permitted to burn on heat stress, summed over every excursion it ever sees, from factory to patient.
Now the real event. During the apron hold the logger records a 90-minute window above 8C. It is not flat: it climbs, peaks at 11C, and recovers. To keep the arithmetic explicit, treat the excess over 8C as averaging about 2C across those 90 minutes (a peak of 11C is 3C over the limit, but the climb and recovery pull the average down). The exposure is then:
- Average excess above the limit: about 2C (peak 11C is 3C over 8C, averaged across the climb and recovery).
- Duration above the limit: 90 minutes, which is 1.5 hours.
- Degree-hours consumed: 2C times 1.5 hours, which is about 3 degree-hours.
So this single event spends roughly 3 of the 20 degree-hours in the budget. That leaves about 17 degree-hours, or 85 percent of the allowance, still available for the rest of the product's life. On those numbers the disposition is a defensible release, not a reject, provided no earlier excursion has already drawn the budget down and the manufacturer's labelled conditions allow it. The tool does the same sum from the actual logger readings rather than the rounded averages used here, so the real figure might come out at 3.4 or 2.7 degree-hours, but the decision logic is identical: spend, subtract, and read the remaining budget. The exact stress profile (was the climb fast, was the peak brief) is exactly what an excursion impact assessment captures alongside this number.
Flip the same event to show why the budget matters. If this lot had already burned 18 of its 20 degree-hours on a previous shipment, the same 90-minute hold would push it to 21, over budget, and the disposition flips to reject or to a manufacturer referral. The number, not the instinct, makes the call.
What Data You Need and Why
Four inputs drive the calculation. First, the allowable degree-hour budget from the manufacturer's stability dossier or product label, not an internal guess. This is the single most important figure, because every output is measured against it. If the dossier states the tolerance differently (for example, a number of hours allowed at a stated temperature), convert it to degree-hours once and record the conversion.
Second, the upper storage limit, which for a 2 to 8C product is 8C. Exposure is only counted above this line. Third, the temperature series with timestamps from the logger that travelled with the consignment, at the real interval, covering the whole excursion window including the recovery tail. A truncated window that stops at the peak overstates the average excess and understates nothing useful. Fourth, any budget already consumed by prior excursions on the same lot, so the remaining figure is honest.
The minimum file is two columns: timestamp and temperature, headers on row 1, one reading per row. Export raw interval readings from your logger platform (LogTag, Testo, ELPRO, DicksonOne and similar all export CSV), not a chart screenshot or a daily average, because averaging flattens exactly the peak this calculation depends on. If the export is messy, run it through the Data Logger QA Cleaner first. One control matters above the rest: confirm the upper limit reflects the approved label condition, because a wrong limit shifts every degree-hour in the sum.
Reading the Outputs
The tool returns four results. Read them in order:
- Consumed budget: the degree-hours this event spent, summed from the readings above the limit. In the worked example, about 3 degree-hours. This is the cost of the excursion in the product's own currency.
- Remaining budget: the allowable budget minus everything consumed so far, including prior excursions. In the example, about 17 degree-hours, or 85 percent left. This is the number that drives the release decision.
- Projected risk: how close the lot is running to its limit, and how much headroom remains for the journeys still ahead. A lot at 85 percent remaining travels comfortably; a lot at 10 percent remaining should not be sent on another warm-lane trip.
- Disposition guidance: a release, reject, or refer-to-manufacturer indication based on whether remaining budget stays positive with a sensible margin. Treat it as a prompt for QA judgement, not an automatic sign-off.
Never read these in isolation. Pair the numbers with operational context: was this a single hold or the latest of several, is the logger the one that actually travelled with the goods, and does the manufacturer's label allow any excursion at all (some products do not). If the remaining budget is thin, run the same logger trace through an excursion impact assessor for the stress-profile detail, and remember that degree-hours and mean kinetic temperature answer different questions. If you are unsure which to cite, our explainer on what mean kinetic temperature is draws the line between cumulative exposure budgeting and MKT for whole-storage trending.
Documenting the Decision for PPB and GDP Audits
A release-after-excursion is a deviation event, and the degree-hour calculation is your evidence. Capture it the way an inspector expects to see it:
- Attach the raw logger export and the cleaned file used, with the excursion window clearly marked.
- State the source of the allowable budget (manufacturer dossier section or label statement) and any conversion you made to reach degree-hours.
- Record the consumed degree-hours for this event, the running total across all known excursions on the lot, and the remaining budget.
- Write the disposition (release, reject, or referral) and tie it explicitly to the remaining budget and the manufacturer's allowance, so the reasoning is scientific rather than convenient.
- Route it through change control and deviation records with QA sign-off, and carry the running budget forward on the lot so the next excursion is judged against an honest balance.
If you are still building these records, our GMP readiness checklist covers the deviation and stability documentation an inspector will ask for, and the wider set of temperature decision tools lets you keep one consistent evidence trail across mapping, excursions, and budgets.
Frequently Asked Questions
What is a degree-hour and why use it instead of just the peak temperature?
A degree-hour combines how far above the limit the product went with how long it stayed there: degrees of excess multiplied by hours of duration. A brief touch of 11C and a long hold at 9C can damage a product very differently even though one peaks higher. Degree-hours capture the total stress, which is what most stability dossiers are written against.
Where does the allowable budget come from?
From the manufacturer's stability dossier or product label, not an internal estimate. Some products state an allowed time at a stated temperature, which you convert to degree-hours once and record. If the label allows no excursion at all, no budget exists and the calculator cannot manufacture one.
Does remaining budget reset between shipments?
No. The budget is cumulative across the product's whole labelled life. Carry the running total forward on the lot so each new excursion is judged against what is genuinely left, not against a fresh full tank.
Is a positive remaining budget an automatic release?
No. It is evidence for a QA decision, not the decision itself. Final disposition follows your approved SOP, the manufacturer's labelled conditions, and authorised QA sign-off. The tool tells you how much budget is left; a person decides what to do with it.
How is this different from mean kinetic temperature?
Mean kinetic temperature summarises long-term storage exposure as a single weighted temperature for trending. Degree-hour budgeting measures a specific excursion against a finite tolerance to drive a release-or-reject call. They answer different questions, and a strong deviation file often cites both.
Run the Tool with Your Own Data
Enter the allowable budget, your storage limit, and the logger trace from the consignment. Get consumed and remaining degree-hours plus disposition guidance you can take straight into a deviation record.
Open Stability Budget Calculator