Alarm limits vs acceptance limits: setting them correctly
Acceptance limits come from the product; alarm limits sit inside them to give time to act, alert limits inside those. Uncertainty and delay set the gaps.
Three sets of numbers are often confused. The storage condition (for example 2–8 °C) is the acceptance limit — the product requirement. The alarm limit is the value at which the monitoring system demands action; it should trigger before the product limit is breached. An alert or warning limit can sit inside the alarm limit to prompt a check without escalation.
Setting the gap
- Sensor uncertainty: if the monitoring sensor has U = 0.5 °C, an 8.0 °C reading may correspond to 8.5 °C at the product. Guard-band accordingly.
- Response time: a sensor in a metal block responds slowly; the air may already be out of range when it alarms.
- Time to act: the alarm must arrive early enough for someone to intervene.
- Product tolerance: brief excursions allowed by stability data can justify a delay — the justification must be written.
A common arrangement for a 2–8 °C room: alert at 2.5 / 7.5 °C, alarm at 2.0 / 8.0 °C with a short, justified delay, and no delay on the freezing side if the product must not freeze.
| Limit | Value | Comes from | What happens |
|---|---|---|---|
| Acceptance (storage condition) | 2.0–8.0 °C | The product label, from stability data | Breached = product decision required |
| Alarm | 2.5 / 7.5 °C, 15 min persistence | Acceptance, pulled in by sensor uncertainty and response time | Notification and escalation; someone acts |
| Alert (warning) | 3.0 / 7.0 °C | Inside the alarm, for early awareness | Reviewed, not escalated; trend input |
Sizing the gap
The gap between the acceptance limit and the alarm limit is not a round number chosen for neatness. It is the sum of three things, each of which can be estimated.
- Sensor uncertainty. If the monitoring probe carries U = 0.5 °C, a reading of 8.0 °C is consistent with 8.5 °C at the product. Pull the alarm in by at least U, which is the same guard-band logic that governs a calibration certificate.
- Response time. A buffered probe in a metal block lags the air by many minutes. By the time it reads 7.5 °C the air has been warmer for a while, and the product is somewhere between. A slow sensor needs a wider gap than a fast one.
- Time to act. The alarm exists so that somebody can intervene before the acceptance limit is reached. Work out how long intervention actually takes at 03:00 and how fast the room drifts, and make sure the gap buys at least that much time.
Persistence, and the side that gets none
A short alarm delay stops a routine door opening from paging someone at midnight, and it is legitimate — provided it is justified rather than tuned until the alarms stop. The justification is the product's own tolerance: if fifteen minutes above 8 °C is demonstrably harmless for everything stored there, a fifteen-minute persistence is defensible. If it is not, the delay is hiding excursions rather than filtering noise.
The freezing side usually gets no delay at all. Damage from freezing is irreversible for many biologicals and can happen quickly, so a low-temperature alarm is normally immediate even where the high-temperature side is delayed. Asymmetric settings are correct here, and a system configured symmetrically out of tidiness is quietly accepting the worse of the two risks.
Alert limits earn their keep only if someone reads them. An alert-limit breach that never escalated is the early warning the level exists to provide, and it is routinely ignored precisely because nothing happened.
Frequently asked questions
- Is an alarm delay of 30 minutes acceptable?
- Only if product stability data show that a 30-minute excursion to the alarm value has no impact and the risk assessment records that. Otherwise the delay converts excursions into unrecorded events.
References
- [1]EU Guidelines on Good Distribution Practice of medicinal products for human use (2013/C 343/01)
- [2]WHO Technical Supplement 16 to TRS 961 Annex 9: Environmental temperature monitoring systems for fixed storage areas
General technical guidance written against the cited sources. It is not regulatory or legal advice and does not replace the applicable standard, guideline or a qualified reviewer's judgement.
Have a question on this topic?
Ask ValiTrac AI and see the evidence and calculation behind the answer.
Ask ValiTrac AIFree calculator: MKT & logger data check
Paste logger readings from storage or a cargo shipment: MKT per ICH Q1A(R2), time out of range, and which figure actually governs the excursion.
Open the calculatorRelated articles
Choosing monitoring locations from mapping results
Permanent sensors go where the mapping found the worst case — the hot spot, the cold spot, the slowest-recovering position — not where the cable reaches.
Handling temperature excursions in storage and distribution
An excursion is assessed against the product's stability data, not averaged away. Six hours at 12 °C in a 40-day cold-chain profile moves MKT by 0.08 °C.
Temperature monitoring during transport
Every temperature-sensitive shipment carries a calibrated logger placed with the product. Review the record on receipt and close excursions before release.