Why the Excursion Record Matters More Than the Excursion

An excursion is a fact about a shipment. The excursion record is a fact about your quality system. Inspectors spend far more time on the second than the first, because a single excursion on a well-run lane is expected, while an excursion that cannot be reconstructed, explained, or tied to a batch tells them something about every other shipment you have released.

The EU Guidelines on Good Distribution Practice set the standard plainly. Regardless of the mode of transport, it should be possible to demonstrate that medicines have not been exposed to conditions that may compromise their quality and integrity. When a deviation such as a temperature excursion occurs during transport, it should be reported to the distributor and the recipient of the affected products, and a procedure should be in place for investigating and handling excursions.1 The word that matters is “demonstrate.” The burden is on the company to produce evidence, not on the inspector to find a problem.

What the Regulators Ask You to Prove

The requirements come from several directions, and they do not all use the same words. In the United States, 21 CFR 211.142(b) requires written warehousing procedures that cover storage under appropriate conditions of temperature, humidity, and light so that identity, strength, quality, and purity are not affected.2 The distribution section that follows, 21 CFR 211.150, says nothing about temperature at all. It requires that the oldest approved stock is distributed first and that the distribution of each lot can be readily determined to support a recall.3 For certain biologics, 21 CFR 600.15 adds specific temperatures to be maintained during shipment, such as fresh frozen plasma at minus 18 °C or colder.4 Most of the detail on how to handle transport excursions in the US comes from compendial chapters and guidance rather than the regulation itself.

USP <1079>, Risks and Mitigation Strategies for the Storage and Transportation of Finished Drug Products, is the core US compendial chapter. It explicitly covers temperature-sensitive small molecules, vaccines, biologics, biotechnology products, radiopharmaceuticals, and combination products, and it frames storage and transport as a set of risks to be identified and reduced.5 WHO’s technical supplements to its model guidance on time- and temperature-sensitive products go further into practice. WHO’s supplement on transport monitoring states that stakeholders should be able to supply documentary evidence that a product has not exceeded acceptable limits of time, temperature, and humidity exposure, as determined by the manufacturer’s stability data.6 Health Canada’s GUI-0069 says that every excursion must be investigated and that any decision to retain or dispose of affected stock must be based on evidence such as stability data and technical justification.7

Read together, these sources ask for the same chain of proof: a monitoring device you can trust, data you can show is complete and original, a response that protected the product while the facts were gathered, a comparison against stability knowledge for that product, and a decision documented by someone with the authority to make it.

1 year Maximum interval for maintaining and calibrating transport temperature monitoring equipment under EU GDP Chapter 9.2 (1)
3 years Minimum WHO retention period for downloaded time and temperature data in most cases, in a retrievable format (6)
30 trips Sample size over a year that WHO describes as statistically valid for profiling a transport route (12)

Where Most Investigations Lose the Thread

In our experience, the excursion investigation rarely fails at the science. It fails at the data. The logger was set to start recording 30 minutes after activation, so the loading period is missing. The receiving site saved the vendor’s PDF summary and discarded the device. The alarm thresholds in the report were the vendor’s defaults, not the product’s labeled range. The stability data cited in the deviation was for a different container closure. Each of these gaps is small. Together, they leave quality with a disposition it cannot defend.

The rest of this article walks through the six links in the order the data moves, and points out the specific decisions at each step that determine whether the evidence holds up later.

Logger Configuration and Calibration: Building the Evidence Before Dispatch

The most important decisions about an excursion are made before the shipment leaves. Once a logger is in the box, its configuration fixes what you will be able to prove. Sampling interval, start delay, alarm thresholds, probe position, and time settings all shape the record, and none of them can be corrected after the fact.

Choose the Device for the Decision You Will Need to Make

WHO’s transport monitoring supplement describes a range of device types: chemical threshold indicators, chemical time-temperature integrators, electronic temperature indicators, electronic data logging monitors, electronic data integrators, and fixed systems for refrigerated vehicles. It notes that accuracy and performance vary between manufacturers and that devices should be selected against a defined user requirements specification.6 The same supplement records that go/no-go indicators give information at a glance but provide no time-specific traceability, while data logging monitors produce time-stamped readings that can be analyzed.

The practical test is simple: what decision will this device need to support if something goes wrong? A threshold indicator can tell receiving staff to quarantine. It cannot tell quality how long the product spent above 8 °C, which is the question the stability comparison depends on. For any product where an excursion would be assessed rather than automatically rejected, the device needs to produce time-stamped readings.

WHO is also specific that service level agreements with carriers and logistics providers, or internal SOPs where transport is in-house, must state which types of monitoring device are used, when and where they are installed, and how the data they generate is collected, reported, and stored.6 That requirement turns device selection from a purchasing choice into a documented quality decision.

Configuration Settings That Decide What You Can Prove Later

The settings below are the ones we see cause the most trouble in investigations. Each should be defined per product and lane, locked in a controlled configuration profile, and verified before the device is placed.

SettingWhy It Matters for the Excursion RecordCommon Failure
Sampling intervalDetermines whether a short spike is captured and how precisely duration can be calculatedLong intervals chosen to save memory on long lanes, so a brief high reading falls between samples
Start delay and start methodDecides whether packing, staging, and loading are inside the recordDelay set longer than the time to loading, so the first exposure is missing
Alarm thresholds and time delaysDefines when an alarm is reported on the device or in the summaryVendor default ranges left in place instead of the product’s labeled and transport limits
Probe position and typeAir readings near the wall differ from product readings in the core of the loadProbe location not recorded, so readings cannot be interpreted against packaging qualification data
Clock and time zoneLinks readings to custody events, handoffs, and carrier scansDevice clock in one zone, carrier events in another, and no record of the offset
Device and configuration identifiersTies the data file to a serial number, calibration certificate, and shipmentSerial number not captured on the shipment record, so data cannot be matched to a consignment

WHO’s route profiling supplement makes a related point for qualification studies: all devices in a study should be the same model from a single manufacturer and identically programmed for data collection frequency, alarms, and recording.12 The same discipline applies to routine monitoring. If two loggers on the same lane are configured differently, their data cannot be compared, and trending becomes guesswork.

Calibration Evidence for Single-Use and Multi-Use Loggers

EU GDP requires that equipment used for temperature monitoring during transport within vehicles or containers be maintained and calibrated at regular intervals, at least once a year, and that calibration be traceable to a national or international measurement standard.1 Health Canada asks companies to calibrate devices that monitor temperature and humidity, such as data loggers, at predetermined intervals and to make sure single-use monitoring devices are qualified.7

Single-use loggers are usually covered by a manufacturer’s calibration certificate that is valid for a defined period. WHO’s supplement on checking device accuracy explains that such a device can be used through that period without further calibration, but lists circumstances where calibration or recalibration is needed: the certificate has been lost, the device is used beyond the certificate period, it was exposed to conditions outside its data sheet limits such as excessive temperature or shock, its battery was replaced, or its readings are suspect.8

The record-keeping implication is easy to miss. For a single-use logger, the calibration evidence is a certificate tied to a serial number. If the serial number is not captured on the shipment record, the excursion data cannot be linked to its calibration, and the data loses much of its value as evidence. USP <1079.3>, Monitoring Devices: Time, Temperature, and Humidity, provides background on monitoring technologies and their performance characteristics and gives recommendations for qualifying device performance, which is a useful basis for the device qualification your SOPs describe.9

Practical check: Pick five recent excursion investigations at random. For each, try to retrieve the logger serial number, the calibration certificate for that serial number, the configuration profile used, and the raw data file. If any of the four is missing for any investigation, the gap is in the record structure, not in the people doing the work.

Download and Data Integrity: The PDF Report Versus the Raw Data

Most data loggers produce two kinds of output. One is a summary report, usually a PDF, showing a chart, minimum and maximum readings, alarm status, and time above or below thresholds. The other is the underlying data: every reading with its time stamp, plus the device’s configuration, serial number, and status information. Many companies keep the first and lose the second. That choice has consequences.

What the PDF Leaves Out

FDA’s guidance on data integrity and CGMP draws a distinction between static and dynamic records. A static record is a fixed-data record such as a paper record or an electronic image. A dynamic record format allows interaction between the user and the record content.10 The guidance accepts electronic copies as true copies only when they preserve the content and meaning of the original record, including all metadata. It also explains that for certain instruments the electronic record is dynamic, and a printout or static record does not preserve the dynamic format that is part of the complete original record.10

FDA’s examples are laboratory instruments, not data loggers, so this is an application by analogy. The analogy holds well. A logger PDF is a static rendering of readings interpreted against the alarm settings that were configured at the time. If quality later needs to evaluate the data against a different limit, such as a product-specific allowable range or a cumulative exposure budget, the PDF alone does not allow it. The readings, the configuration, and the device identifiers in the native or exported raw file do. Our view is that the raw data file, with its metadata, should be treated as the original record and retained, and the PDF should be treated as a convenient view of it.

WHO’s transport monitoring supplement supports retaining the data itself. It says that downloaded time and temperature data should in most cases be retained for at least three years in a non-volatile format that allows retrieval, and it lists printed copies, local electronic media, and secure web-based repositories as possible formats.6 EU GDP adds that backup data from computerized systems should be retained for the period stated in national legislation, and at least five years, at a separate and secure location.1 Health Canada asks that records associated with storage and transportation, including excursion investigations, be kept for one year after the product’s expiry date unless the company’s drug establishment license states otherwise.7 In practice, the longest applicable period wins.

Watch for this: WHO notes that some device types need additional proprietary hardware, software, or licensing to download data.6 If the only way to read a raw file is a vendor application on one workstation, retention for three or five years is a promise you may not be able to keep. Retrieval should be tested as part of system validation and periodically after go-live, not assumed.

Cloud Loggers and Who Holds the Original Record

Connected loggers change where the data lives. Readings are transmitted during the shipment or uploaded at the destination to a vendor-hosted platform. The receiving site may never touch a file at all. That is convenient, and it creates a question many quality agreements do not answer: who holds the original record, and how is it retained if the service ends?

For a cloud monitoring platform, the questions are the same ones you would ask of any GxP computerized system. EU GDP requires that before a computerized system is brought into use, it should be shown through validation or verification that it achieves the intended results accurately, consistently, and reproducibly; that data is entered or changed only by authorized people; that data is protected against accidental or unauthorized changes; and that stored data is checked periodically for accessibility.1 For a vendor-hosted platform, those controls sit partly with the vendor and partly with you. The quality agreement and the supplier assessment should say which party is responsible for audit trails on threshold changes, for data export in a readable format, and for retention after contract end.

Gaps, Duplicates, and Clock Problems

Raw data is only useful if it is complete. Three data quality checks belong in every excursion review before anyone looks at the science:

  • Continuity. Are there missing intervals? A gap is not evidence of compliance. It is an unknown, and it should be treated as part of the excursion until explained.
  • Coverage. Does the record start before packing was complete and end after receipt? If not, the parts of the chain outside the record are unmonitored.
  • Time alignment. Can the readings be lined up against custody events, such as pickup, airport handoff, customs hold, and delivery, using a known time zone? Without this, you can see that an excursion happened but not where, which makes the root cause and the lane trend unreliable.

Where a shipment carries more than one device, compare them. Agreement between two loggers strengthens the record. Disagreement is itself a finding that needs an explanation, often probe position or a device fault.

Alarm Handling: From Notification to Quarantine

An alarm is a signal that a threshold has been crossed. It is not a verdict on the product. The purpose of alarm handling is to protect the product from further harm, preserve the evidence, and start the clock on an investigation, all without making a disposition decision that belongs to quality later.

Set Alarms So They Mean Something

EU GDP requires alarm systems that alert when there are excursions from predefined storage conditions, with alarm levels set appropriately and alarms tested regularly.1 The MHRA Inspectorate has written about the failure on the other side. In a 2020 post on applying quality risk management to transport risks, the author described a temperature trace in which alerts had not been set appropriately, and noted that the lack of alarm triggering led to incorrect assurance that stock was within range and to an inaccurate risk assessment.11

Alarm thresholds should be derived from the product’s labeled storage range and any approved transport limits, not from device defaults. Many companies also set a pre-alarm a little inside the limit. On a connected device, a pre-alarm is useful because it can prompt intervention before the limit is reached. On a device read only at receipt, it mainly adds noise to the summary.

The Response Sequence at Receipt

WHO describes how go/no-go information from indicators should be recorded on the product arrival report and used to decide whether to accept a consignment into storage or to quarantine it until an investigation has taken place and a final disposition has been made.6 Health Canada asks receiving sites to examine shipments on arrival, confirm that conditions were met, and record the results.7 A response sequence that holds up in an inspection usually looks like this:

1

Stop the Clock on Further Exposure

Move the product into its correct storage condition straight away, under quarantine status. Do not let the investigation delay putting a refrigerated product back into a refrigerator.

2

Preserve the Evidence

Stop the logger, download or confirm upload of the raw data, photograph the packaging and indicator state, and record the logger serial number against the delivery. Keep the device until the data has been confirmed as complete.

3

Record the Receiving Facts

Capture arrival time, packaging condition, coolant state, and any carrier notes on the arrival record. These facts often explain the excursion and cannot be recovered later.

4

Notify the Right Parties

EU GDP expects transport excursions to be reported to the distributor and the recipient.1 Health Canada expects them to be communicated to the responsible party, usually the market authorization holder.7 Define in your procedures who calls whom and within what time.

5

Open the Deviation

Log the event in the quality system with the raw data attached. The deviation record becomes the container for everything that follows: the stability comparison, the disposition, and the root cause.

Alarms During Transit

With connected loggers, alarms arrive while the product is still moving, which creates a new decision point: who acts, and what are they allowed to do? A logistics coordinator can ask a carrier to move a pallet into a cold room or replace coolant. That person should not be deciding whether the product is still usable. Procedures should separate the operational response, which aims to limit exposure, from the quality decision, which happens later with the full record. They should also say what happens when an alarm arrives outside business hours. EU GDP already expects designated people and written procedures for emergency deliveries outside normal hours, and the same logic applies to in-transit alarms.1

Matching Excursion Data to Stability Data and Allowable Time Out of Storage

This is the step where the science happens, and it is the step regulators most often find weak. The question is not whether the product was outside its range. The record already shows that. The question is whether the known stability of this product, in this packaging, supports continued use after this specific time and temperature exposure, taking into account every other exposure the same batch has already had.

What “Supported by Stability Data” Means in Practice

The draft consolidated ICH Q1 guideline, endorsed as a Step 2 draft on 11 April 2025, includes a section on excursions outside the label storage claim. It says transient excursions may be acceptable if justified and supported by stability data, that assessing their risk requires comprehensive knowledge of the supply chain and of the product’s stability profile, and that stability studies, accelerated studies, stress testing, or transport simulation studies can be used to evaluate the effects. It adds that statistical evaluation or modeling can be used when the degradation pathway is understood well enough to fit an appropriate model, and that each excursion should be documented and handled within the quality management system.14 As of late October 2026 the text is still a draft. ICH’s February 2026 work plan targets Step 4 adoption in November 2026, so check its status before citing it as final.15 The principles it states are already consistent with current expectations.

Health Canada describes the same idea from the distribution side. A justification for a brief excursion during transport should follow quality risk management principles, rest on stability data that covers the excursion, and consider the worst case for how often and how severely excursions might occur along the distribution chain.7

The MHRA has been direct about how often this falls short. In the 2020 post on transport risk, the author wrote that it is rare to find sound scientific justification for accepting a load after an excursion, that stability information obtained from the marketing authorization holder is often not directly comparable to the excursion experienced, and that the most common reason for accepting a consignment with an excursion is purely commercial.11

“Directly comparable” is the phrase to build your process around. The stability data used in a disposition should match the product, the presentation, and ideally the container closure, and it should cover a temperature at least as high (or as low) as the excursion for at least as long. Data from accelerated studies at 25 °C for six months says nothing useful about a freeze event. Data showing no change after a short period at 25 °C does not cover a longer period at 30 °C.

Build a Stability Budget for Each Batch

A single excursion is rarely the whole story. A batch may have spent time outside refrigeration during packaging, a short excursion on the way to a regional distributor, and another on the final leg to a clinic. Each one, assessed alone, may look acceptable. Added together, they may not be.

The most reliable way to manage this is a stability budget: a defined allowance of time outside the labeled condition, per temperature band, that is supported by stability data and approved by quality. Each recorded exposure is subtracted from the allowance for that batch. When the remaining allowance is too small to cover the next planned step, the batch is held for review. Many companies call this allowable time out of storage or time out of refrigeration. The terms vary. The mechanism is the same.

WHO’s route profiling supplement offers a simple way to express cumulative exposure in transport studies. It describes a degree-hour method in which each reading outside a threshold contributes the recording interval in hours multiplied by the temperature difference from the threshold, summed over the trip to give total exposure in degree-hours, which can then be compared with the maximum exposure a container is qualified for.12 WHO uses this for qualifying packaging, not for product disposition, but the same arithmetic gives quality a consistent, reproducible number to compare across shipments.

Input 1

The Approved Allowance

Time permitted outside the labeled range for each temperature band, with the stability study that supports it referenced by number. Approved by quality and held under change control.

Input 2

The Batch Exposure History

Every recorded exposure for the batch, from release onward, with source data files linked. This is the part most companies cannot assemble quickly, because it spans several systems.

Input 3

The New Event

Duration and peak temperature from the raw data, with any data gaps counted as exposure until explained. Calculated the same way every time.

Output

Remaining Allowance and Decision

What is left after the new event, and whether it supports release, release with restriction, further testing, or rejection. Recorded in the deviation with the calculation shown.

The stability budget is also where stability data management and distribution meet. If your stability program data lives in spreadsheets that distribution quality cannot easily query, the budget will be rebuilt by hand for each investigation, and it will be rebuilt differently each time.

Where Mean Kinetic Temperature Helps and Where It Misleads

Mean kinetic temperature (MKT) is a single calculated temperature that represents the combined thermal effect of a varying temperature history on degradation. USP <1079.2>, Mean Kinetic Temperature in the Evaluation of Temperature Excursions During Storage and Transportation of Drug Products, is the compendial chapter on its use.16 A 2026 USP proposal to revise the controlled room temperature definition in <659> summarizes the current position: MKT remains the primary tool for evaluating short-term excursions above 25 °C, it should be calculated using all available temperature data for the observation period (the time the product is in the holder’s possession, or 30 days when the exact duration is not known), and all data and calculated values must be documented. The same briefing notes that <1079.2> sets a maximum allowable excursion duration of 24 hours and does not allow time under cold or cool conditions to offset excursions outside controlled room temperature ranges. These rules were written for controlled room temperature products.17

Two cautions matter for cold chain products specifically. First, Health Canada lists situations where MKT may not be appropriate, including products that require refrigeration or freezing, biologics, liquids or suspensions that undergo phase change, and cases where data suggest excursions affect product quality.7 Second, MKT averages, and averaging hides peaks. A peer-reviewed simulation study in BMC Public Health cites example data from an earlier study of a 14-week shipment in which temperatures ranged from about minus 2 °C to 41 °C, yet the calculated MKT was 24.4 °C.18 For a product that can be damaged by freezing or by a short period at high temperature, that single number would be the wrong basis for a decision.

The same study also shows why storage history matters for the budget. In its simulations of a model solid oral product, shelf-life loss began immediately when long-term storage matched the maximum labeled temperature, and on average each day at 40 °C consumed about three and a half days of shelf life for products labeled for 25 °C storage.18 The study modeled a small-molecule oral product, not a biologic, so the specific figures do not transfer. The principle does: the impact of an excursion depends on everything else the batch has experienced.

The MHRA’s warning on MKT: In its 2020 transport risk post, the MHRA Inspectorate noted that some companies had tried to apply mean kinetic temperature inappropriately to underestimate impact, rather than develop good control and preventive measures.11 MKT is a tool for a defined set of products and conditions. It is not a way to make an excursion disappear.

Documenting the Disposition Decision

The disposition record is the document an inspector will read. Everything before it is supporting evidence. It needs to stand on its own, so that someone who was not involved can follow the reasoning from data to decision without asking anyone a question.

The Minimum Content of a Defensible Disposition Record

ElementWhat It Should Contain
IdentificationProduct, batch, quantity, shipment or storage location, logger serial numbers, and links to the raw data files
Data integrity reviewConfirmation that the data is complete, covers the full custody period, is time-aligned, and comes from a calibrated device
Exposure descriptionPeak temperature, duration outside each band, and cumulative exposure for the batch, calculated by the approved method
Stability basisThe specific stability study or data set relied on, why it is comparable, and the remaining allowance after this event
Product-specific risk factorsFreeze sensitivity, phase change, presentation, and any known degradation pathways relevant to this exposure
Marketing authorization holder inputWhere the decision maker is not the MAH, the MAH’s assessment and who provided it
Decision and authorityRelease, release with restriction, additional testing, or rejection, signed by a person with authority to make it
Root cause and follow-upWhy the excursion happened and whether it links to a lane, carrier, or packaging trend

Who Decides, and When the Manufacturer Must Be Involved

Wholesalers, third-party logistics providers, clinical depots, and manufacturers each hold different parts of the knowledge. The party that receives the product sees the excursion. The party that holds the marketing authorization holds the stability data. Health Canada notes that the market authorization holder may need to be consulted about an excursion’s effect.7 A distributor deciding without access to product-specific stability data is in exactly the situation the MHRA described: stability information that is not directly comparable to the excursion, and acceptance that ends up driven by commercial pressure.

Quality agreements should say who decides for each product type and each point in the chain, what data must be sent with the request, and how quickly the MAH responds. Where the answer is “always the manufacturer,” the agreement should also say what the distributor does with the product while waiting.

Returns and Products That Have Left Your Control

Returns are a special case that exposes weak records quickly. EU GDP says that products requiring specific temperature storage conditions can only be returned to saleable stock if there is documented evidence that they were stored under authorized conditions the entire time. If any deviation occurred, a risk assessment must show the product’s integrity. The evidence should cover delivery to the customer, examination of the product, opening of the transport packaging, return of the product to the packaging, collection and return to the distributor, and return to the distribution site refrigerator.1 For most returned cold chain product, the honest answer is that this evidence does not exist, and the procedure should say so rather than leave room for a judgment call.

What FDA Looks for When Data Was Not Matched to Batches

A September 8, 2026 FDA warning letter to kdc/one Chatsworth, an over-the-counter drug manufacturer, shows how the agency reads a failure to connect temperature data to product. The letter cites 21 CFR 211.142(b). FDA described a batch held in a building where recorded temperatures exceeded both the labeled storage condition and the firm’s own monitoring protocol during the storage period. A review of that building’s temperature data from April 2025 through March 2026 identified a period of weeks with temperatures above a threshold; FDA redacted both the number of weeks and the temperatures, so the letter does not show how large the problem was.13

FDA found the firm’s response inadequate because it did not take immediate corrective action and did not complete a thorough retrospective review of product impact, including the formation of impurities and degradants when products are exposed to heat. The agency asked for a batch risk assessment, a retrospective review of temperature data across all storage areas covering all products and all periods for which data exists, a documented assessment of any affected lots, and procedures to include storage conditions on certificates of analysis and on the labels used for transport.13 This was a warehouse case, not a transport case, but the expectation carries over directly: temperature data must be tied to batches, and a gap found once must be checked everywhere.

Individual dispositions answer whether a batch is usable. Trending answers whether the distribution process is under control. It is the part of the excursion program most companies under-build, because each investigation closes on its own and nobody is responsible for the pattern.

Build the Lane Taxonomy First

A trend is only as good as the categories it counts. The MHRA’s 2020 post suggests grouping similar routes and transport modes into lanes, such as ambient air freight to mainland Europe, cold chain air freight to Europe, road freight using company transport, and road transport by courier, and notes that each lane has a risk profile common to its shipments but distinct from the others.11 WHO defines lanes simply as transport routes from a point of origin to a destination.12

For trending, a lane record should carry at least the origin, the destination, the mode, the carrier or logistics provider, the packaging system, and the temperature class. If any of these is free text in the deviation system, the trend will split the same lane across several spellings and hide the pattern. Fix the taxonomy before building the dashboard.

Keep Monitoring After Qualification

WHO’s route profiling supplement says that once a route has been formally profiled, periodic monitoring should continue, because it helps identify risks, process changes, and trends that the formal study did not capture and that may later affect transport performance.12 EU GDP requires risk assessment of delivery routes to determine where temperature controls are needed, and temperature mapping of temperature-controlled vehicles that takes seasonal variation into account.1 Routine excursion data is the evidence that tells you whether those assessments still hold.

Metrics Worth Trending

MetricWhat It ShowsTypical Action When It Moves
Excursion rate per lane (excursions per 100 shipments)Whether a lane performs as qualifiedReview packaging qualification and route profile for that lane
Excursion rate per carrier or provider across lanesWhether a problem follows a provider rather than a routeSupplier performance review and quality agreement discussion
Excursion location in the chain (origin, handoff, transit hub, final mile)Where in the custody chain exposure happensTargeted controls at a specific handoff or hub
Seasonal pattern by laneWhether summer or winter packaging configurations are adequateAdjust seasonal packaging dates or configurations
Data completeness rate (shipments with complete raw data)Whether the evidence chain itself is reliableTraining, device configuration, or upload process fixes
Disposition outcome mix (released, tested, rejected)Whether decisions are consistent and whether losses are risingReview of stability allowances and decision criteria

Data completeness deserves its own line. A lane with few recorded excursions and many shipments missing data is not a good lane. It is an unmonitored one.

When a Trend Should Trigger CAPA

The MHRA’s 2016 post on handling unexpected deviations under EU GMP Annex 16 gives a useful test. It describes a product labeled for storage below 25 °C that reached up to 29 °C for three days in transport from a third country, with stability data showing no issues at 30 °C for up to three months. That could be treated as an unexpected deviation if the transport process had been designed to comply with the registered conditions. The post then states that if there were no controls over shipment conditions, using stability data as a routine means to justify such an excursion would not be acceptable, and the root cause should be found and corrected. It also notes that recurring deviations no longer meet the “unexpected” criteria.19

That is the trending threshold in plain terms. The first excursion on a lane may be a disposition question. The third on the same lane in the same season is a process question, and stability data cannot answer it. Set a numeric trigger per lane, write it into the procedure, and make sure crossing it opens a CAPA rather than another set of individual dispositions.

Where Automation and Real-Time Monitoring Change the Process

Connected loggers, carrier telemetry, and monitoring platforms are now common in pharma and biotech distribution. The MHRA noted in 2020 that technology now offers easy and inexpensive ways to relay temperature at receipt or as live data, and that it is normally easier to monitor temperature throughout the load, or to combine monitoring with vehicle temperature mapping, than to rely on validation alone.11 These tools change the process in specific ways, and leave other parts unchanged.

What Changes

  • The first decision moves earlier. With live alarms, the operational response happens during the excursion, not after delivery. That can prevent an excursion from becoming a rejection.
  • Data capture stops depending on the receiving site. If readings are uploaded automatically, the risk of a discarded logger or a lost file falls sharply. The record is complete by default rather than by effort.
  • Custody events can be joined to readings. When location and handoff data come from the same platform, it becomes possible to say where an excursion happened, which is what lane and carrier trending needs.
  • The stability budget can be calculated automatically. If exposure data, batch identity, and approved allowances are in connected systems, remaining allowance can be shown before a batch is picked, not after a deviation is opened.

What Does Not Change

Real-time data does not make a disposition decision. It does not supply the stability data, and it does not change who has the authority to decide. A live alarm with no defined response is a notification that someone will read in the morning. Health Canada’s guidance makes a related point from the opposite direction: a qualified thermal container may not need ongoing monitoring if its performance is confirmed periodically, while temperature-sensitive drugs may warrant ongoing monitoring.7 The choice of how much monitoring to apply is still a risk-based quality decision, not a default set by what the technology can do.

Integrating Temperature Data With ERP, WMS, and Stability Systems

The hardest part of automation is not the sensor. It is connecting the readings to the batch. A 2024 MIT thesis prepared with a large pharmaceutical company’s gene therapy supply chain found that, although digital temperature monitoring was already in place, tracing a product’s temperature history across multiple legs of the supply chain had to be done by manual review of separate temperature records. The thesis set out requirements to integrate temperature data across six enterprise systems, including sensor data, ERP systems for shipments and warehouse management, and serialization records.20

That finding matches what we see in mid-size pharma and biotech companies. The monitoring platform knows the logger. The transport management or ERP system knows the shipment. The warehouse system knows the batch and location. The stability system, or a spreadsheet, knows the allowance. The deviation system holds the decision. Until those are joined by shared identifiers (logger serial, shipment number, batch, and lane code), automation produces faster alarms but the same slow investigations.

Validation Scope for the Monitoring Platform

A monitoring platform that holds the original record of temperature exposure, applies alarm logic, and feeds disposition decisions is a GxP computerized system. Its validation should focus on the parts that affect the excursion record:

  • Configuration control over alarm thresholds and profiles, with an audit trail for every change
  • Data completeness and handling of transmission gaps, including how store-and-forward data is flagged
  • Time stamp handling and time zone display
  • Export of raw data with metadata in a readable format, tested for retrieval over the retention period
  • Any calculations the platform performs, such as time above threshold, MKT, or degree-hours, verified against independent calculation
  • Interfaces to ERP, warehouse, and quality systems, with reconciliation that shows no records are lost or duplicated

A sensible sequence: Standardize the lane taxonomy and the disposition record first. Define the stability allowances per product and temperature band next. Then connect the monitoring platform to those structures. Companies that start with the platform usually end up with a faster way to produce the same incomplete record.

Conclusion

Temperature excursion data has a long trail, and each link has its own owner: the person who configures the logger, the receiving clerk who saves the file, the logistics coordinator who answers the alarm, the stability scientist who holds the data, and the quality reviewer who signs the disposition. Regulators look at the whole trail, and the expectations from EU GDP, USP, WHO, Health Canada, and FDA are consistent: monitor with devices you can trust, keep the original data, protect the product while you investigate, base the decision on comparable stability evidence, and fix recurring causes rather than justifying them one batch at a time. Most failures we see are not failures of science. They are records that were never designed to be joined.

Sakara Digital works with pharma and biotech organizations on the data side of quality operations, including how monitoring, stability, and deviation systems connect. If you are reviewing your excursion process or planning a move to connected monitoring and want an independent view of where your record structure needs work first, we are happy to have that conversation.

For Further Reading