# Temperature excursion worked case | SourceX

Canonical: https://refer.sourcex.si/guides/temperature-excursion-handling-exception-examples
Last updated: 2026-11-04

The records that explain a temperature excursion are the logger alert with its gap and readings, the handling instruction followed at the time, the escalation and deviation report, and the quality disposition that names who decided and why, per lot. In the worked case below, one pallet produces two different decisions because one lot already carried an earlier excursion. That sequence is useful evidence because every decision left a record a reviewer can check against the rule.

This worked case is part of [exception handling records for AI agents](/guides/exception-handling-ai-agents-data), which sets cold-chain excursions alongside entitlement and promotion cases. In the [six-class exception taxonomy](/guides/enterprise-exception-handling-training-data) it is an out-of-tolerance exception. This page slows one case down to show each decision, the person who made it and the record it left.

## The case: a cross-dock transfer that goes out of range (Illustrative)

The company is fictional: a 250-person pharmaceutical wholesaler in the EU, distributing refrigerated injectable products to hospitals and pharmacies. Every value below is invented.

A pallet labeled for 2 to 8°C storage carries two lots of the same product, Lot A and Lot B, bound for a regional hospital. Lot B arrived at the wholesaler's warehouse a month earlier after a short inbound excursion, which was investigated and closed with the lot released. At 06:10 the pallet is moved from a trunk vehicle to a delivery van at a cross-dock. The data logger stops reporting as the pallet leaves the first vehicle.

## Step by step: who decided what, and the record each decision left

| Time | What happened | Who decided | Record created |
|---|---|---|---|
| 06:10 | Transfer starts; logger stops reporting | Nobody; a gap begins | Logger platform: last reading 5.2°C, then no data |
| 06:48 | Logger reconnects in the van and reads 11.4°C; alarm fires | The alarm system | Alarm event with time, reading and threshold |
| 06:52 | Driver isolates the pallet in the van's cooled section and stops the delivery | Driver, following the written transport instruction | Driver app entry citing the instruction number |
| 07:05 | Dispatcher, under pressure from the hospital, asks whether to deliver anyway; escalates instead | Dispatcher, choosing escalation over delivery | Escalation ticket to on-call quality, time-stamped |
| 07:20 | On-call quality places both lots on hold | On-call quality associate | Quarantine status in the warehouse system |
| 07:40 | Deviation report sent to the hospital and the manufacturer | Quality, as procedure requires | Deviation record in the quality system, with distribution list |
| Day 2, 10:00 | Full logger download: 38-minute gap, then 26 minutes above 8°C, peak 11.4°C | Quality analyst | Logger file attached to the deviation |
| Day 2, 15:30 | Manufacturer's quality unit assesses against stability data, lot by lot | Manufacturer's quality unit | Written assessment referencing each lot's excursion history |
| Day 3, 09:00 | Lot A released; Lot B rejected | Wholesaler's quality lead | Disposition per lot, signed in the quality system |

Three points make this a hard case rather than a routine one. The gap means nobody knows the temperature for 38 minutes. The dispatcher faced a real, documented pressure to deliver. And the right answer differed by lot.

Some of this chain is required, not optional. The EU's Good Distribution Practice guidelines expect alarms on excursions from pre-defined storage conditions, a procedure for investigating and handling excursions, and reporting of transport excursions to the distributor and recipient. In the United States, warehousing procedures must cover quarantine before release by the quality control unit and storage under appropriate temperature conditions. Regulation makes the records more likely to exist; it does not make them linked or retained for years.

## The branch: why Lot A and Lot B ended differently

Lot A had no prior excursion. The manufacturer's stability data allowed the combined exposure, so it was released, with the disposition citing the deviation number.

Lot B had used part of the same allowance during its inbound excursion a month earlier. Added together, the two events exceeded what the stability data supported, so it was rejected and sent for destruction, with a credit note issued to the hospital and a replacement shipped from another lot.

The branch only exists in the records because Lot B's earlier deviation was linked to the lot number. Had the inbound excursion been closed in a separate system, or recorded against a shipment instead of a lot, quality might have released both lots on the evidence of this event alone. That is the lesson for anyone judging the archive: the decisive record was a month old and came from a different leg.

## Why this sequence is useful evidence

For AI training and evaluation, the case has what routine shipments lack:

- **A decision under uncertainty.** The 38-minute gap forces a judgment, and the records show which evidence was used to make it.
- **A tempting wrong path, refused.** The dispatcher's escalation ticket shows the option to deliver was considered and declined. An agent that would have delivered fails this case.
- **Authority at each step.** Driver, dispatcher, on-call quality, manufacturer and quality lead each acted within a defined role, and each left a time-stamped record.
- **History-dependent outcome.** The same event produced two dispositions, which tests whether a system looks beyond the current event.
- **A checked result.** Release, rejection, credit note and replacement are all recorded, so the outcome can be confirmed.

Where these records sit in validated electronic systems, U.S. rules for closed systems require secure, computer-generated, time-stamped audit trails in which changes do not obscure earlier entries. That property is what lets a reviewer trust that the 07:05 escalation really happened before the 07:20 hold.

## Spotting similar cases at a client

Listen for these signals in conversation with a quality director, logistics manager or COO at a wholesaler, 3PL, specialty pharmacy, clinical supply firm or food distributor:

1. Excursions are investigated in a quality management system, not a spreadsheet or email.
2. Dispositions are recorded per lot or batch, with the approver named.
3. Earlier deviations can be found from the lot number.
4. Handling instructions are numbered and versioned, so the driver's entry can cite one.
5. Logger data is attached to the deviation, not left only in the sensor platform.
6. Several years of closed deviations still exist, along with the outcomes (release, rejection, credit).

Two or three yeses suggest a company worth introducing. Partners ask about these at metadata level only: never request deviation reports, logger files or lot numbers. More on spotting resolved exceptions is in [logistics exceptions and their documented resolutions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions); sector context is on [logistics and warehousing](/industries/logistics-and-warehousing) and [healthcare operations](/industries/healthcare-operations).

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Quality agreements with manufacturers may limit what the wholesaler can license, so rights stay open until SourceX reviews them with the company.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client investigates excursions in a quality system and records dispositions per lot with a named approver, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the quality director and the executive who owns those records.

## Sources

- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.C_.2013.343.01.0001.01.ENG
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-H/section-211.142
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11/subpart-B/section-11.10
- https://refer.sourcex.si/terms
