Deviation vs Excursion: What’s the Difference?
Last updated: May 8, 2026
When reviewing shipment risk, you may see both excursions and deviations. While they sound similar, they represent two different types of temperature risk.
Understanding the difference is key to interpreting shipment quality and product impact.
The Simple Difference
Excursion = Did the shipment go outside the allowed shipping temperature range?
Deviation = Did the product exceed its allowed time within specific temperature conditions?
What is a Temperature Excursion?
An excursion happens when the temperature goes outside the configured Shipping Temperature Range (STR).
What it tells you:
The shipment left the acceptable shipping temperature band
There was a temperature breach event
What you’ll see:
Excursion periods (start and end times)
Time Out of Range (TOR)
Temperature graph crossing STR thresholds
👉 Excursions are event-based (something happened at a point in time).
What is a Temperature Deviation?
A deviation happens when the product exceeds its allowed exposure time within specific temperature ranges, based on the Product Temperature Range (PTR).
What it tells you:
The product’s stability limits may have been compromised
Time spent in certain temperature conditions exceeded allowed thresholds
How it works:
Temperature is grouped into defined PTR bands
Time is tracked within each band
That time is compared to allowed limits:
Continuous (one long exposure)
Cumulative (total time across the shipment)
👉 Deviations are time-based and product-specific.
Key Concept: You Can Have One Without the Other
You can have an excursion without a deviation
Example: Temperature briefly goes out of range, but not long enough to impact product stability
You can have a deviation without a major excursion
Example: Temperature stays within a broader range but spends too long in a borderline zone
👉 Excursion = threshold breach
👉 Deviation = stability impact
How the Platform Calculates This
Excursion (STR-based)
Triggered when temperature crosses shipping limits (STR)
Creates:
Excursion events
Time Out of Range (TOR)
Deviation (PTR-based)
Tracks time spent in product-specific temperature bands
Compares against allowed duration:
Continuous limits
Cumulative limits
When limits are exceeded → Deviation is triggered
What You See in the Shipment
The platform summarizes temperature risk using a status hierarchy:
Normal
Predicted Excursion
Excursion
Deviation (highest severity)
👉 If both occur, Deviation takes precedence because it reflects potential product impact.
Why This Matters
Understanding the difference helps you:
Avoid overreacting to short excursions
Focus on true product risk (deviations)
Make better decisions during Product Release
Communicate clearly with quality and compliance teams
Quick Tip
When reviewing a shipment:
Start with Deviation (product impact)
Then review Excursions (what happened operationally)