Qualification, validation, verification: the vocabulary that decides your audit

Cold chain borrowed this vocabulary from pharmaceutical equipment qualification and kept the meanings intact. The definitions below come from documents an auditor would recognize on sight: EU GMP Annex 15 (2015), the WHO’s model guidance for time- and temperature-sensitive pharmaceutical products (Technical Report Series 961, Annex 9, 2011), and USP <1079>. This post is the terminology layer; the operational how-to — protocol elements, probe placement, acceptance criteria — lives in how to validate your own packout, and we will not repeat it here.

The ladder, in the auditor’s dialect

Note what the ladder implies: qualification is the unit of work, validation is the assembled case, verification is the maintenance of the case. A pharmacy that runs a flawless chamber study but files it as “validation” has a vocabulary problem that becomes an audit problem — the study is OQ evidence, one input to a validation, not the validation itself.

What each stage means for a shipping packout

Mapped onto the thing you actually ship:

• DQ is the design case: the container, insulation, refrigerant mass, and conditioning spec, with the reasoning that says this assembly should hold 2–8°C for the rated duration. In practice most of this work arrives from the packaging supplier’s development program — the territory of development-series testing like ISTA 7D, which ISTA itself distinguishes from formal thermal validation (see ISTA 7D and 7E, explained).
• IQ barely applies to a disposable parcel — but it fully applies to the equipment around it: your environmental chamber, refrigerators, and monitoring systems all have installation records an auditor can ask for.
• OQ is chamber testing: the packout, in a defined configuration, held against defined ambient profiles for beyond its rated duration.
• PQ is the real world: instrumented shipments in your actual configurations on your actual lanes, across seasons. USP <1079> is explicit that qualification studies “should reflect actual load configurations and environmental conditions.”

“Is your shipping process validated?” is a document request

When an accreditation surveyor or board inspector asks the question, they are not asking for a feeling of testedness. They are asking whether a specific file exists:

• A written protocol with acceptance criteria defined before the runs;
• OQ records — chamber data against named ambient profiles;
• PQ records — instrumented shipments on your lanes, in your configurations;
• The analysis against the criteria, including the runs that failed;
• A signed conclusion stating the qualified configuration and its limits;
• A verification schedule showing the conclusion is still being tested.

“Our vendor says it’s tested” fails this question — not because vendors lie, but because the sentence names no configuration, no acceptance criteria, no lane, and no owner. It is an answer about qualification, offered where validation was asked.

The vendor file and the pharmacy file

A packaging supplier’s chamber data is real evidence — about the supplier’s configuration. Their payload, their refrigerant mass, their conditioning, their ambient profile. In your validation it is an input, typically the OQ layer, and a legitimate one. ACHC’s published cold chain guidance draws exactly this line:

“Third-party vendors can be helpful in developing your own testing program. However, they may only provide limited validation data based on specific pack-outs and environmental conditions, which may vary from your needs.”

ACHC, Understanding Cold Chain Shipping

USP <1079> makes the ownership point structurally: its table of calibration, qualification, and validation activities across the supply chain marks shipping packaging performance qualification as an activity of pharmacies and compounding pharmacies — not manufacturers only. Your validation is the file that covers your products, your configurations (every vial count you actually ship), and your lanes and seasons. The moment any of those differs from what the vendor tested, the vendor file stops covering you.

Verification: the tense nobody budgets for

Validation is past tense; audits happen in the present. Verification is how the file stays alive, and the reference documents are specific about its rhythm. The WHO model guidance requires transport temperature monitoring devices to be calibrated against a certified, traceable reference standard at least once a year, with alarm functionality checked on the same cadence, and calls for requalification consideration whenever equipment is significantly modified or monitoring shows unexplained variability (WHO TRS 961, Annex 9, §§6.6–6.7). For a parcel operation, the practical verification set is: periodic instrumented shipments per lane, re-testing when the seasonal packout flips, calibration records for every logger you rely on, and a change-control trigger list that reopens qualification when the configuration moves.

A validation file that has not produced a new record in two years is a historical document. Auditors read dates.