We had run the same EPA 8260B volatile method on the same instrument for eleven months with a %RSD on the internal standard area under 6%. Then a new case of 40 mL vials with caps arrived from a supplier we had qualified two years earlier, and within three runs the 1,4-difluorobenzene area had dropped 22% and the fluorobenzene RSD climbed to 14.8%. The instrument was fine. The column was fine. The vials were not the same vials, even though the part number was identical. That is the moment a revalidation decision gets made, usually badly, because nobody wrote down what "same" meant in the first place. This article is about the revalidation triggers when a vials with caps supplier or lot changes, and about the difference between a change that forces a full revalidation and one that only needs a documented verification.
Most labs treat "new supplier" or "new lot" as a single event. It is not. A vials with caps assembly has at least six attributes that can move independently, and only some of them touch the method. The rest touch the method's container clause and the data package, which is a compliance question, not a validation question.
The attributes that can actually shift a chromatographic result are:
The first three are chemistry and mechanics. They are the ones that force revalidation. The last three are usually verification territory, provided the supplier can show you the records. The trick is that a supplier will often change all six at once and describe it as "same specification."
I use a simple rule. If the change can move a peak area, a retention time, a leak rate, or a puncture count by more than the method's own repeatability, it is a revalidation. If it cannot, it is a verification with a documented acceptance criterion.
Here is the decision table I hand to QC leads. It is deliberately blunt.
| Change | Decision | What you actually run |
|---|---|---|
| Septum formulation or durometer change | Revalidate | Full method revalidation on the affected method, minimum 6 replicates at low and high calibration points, plus a 24-hour headspace hold study |
| PTFE facing grade or lamination change | Revalidate | Extractables screen, ghost-peak blank run, and system suitability on the affected method |
| Crimp cap alloy or wall thickness change (11 mm) | Revalidate the seal | Dye ingress at 40 °C for 24 h, plus vacuum leak test at -80 kPa |
| Glass forming process change (molded to tubing) | Revalidate dimensional fit | Bore and crimp shelf measurement on 30 units, plus autosampler pickup trial of 100 injections |
| Same supplier, same formulation, new lot | Verify | One system suitability run, 6 replicates, compare to historical mean |
| Supplier moves filling line or cleanroom class | Verify | Particle count and background blank, 3 lots |
| Packaging change only (bag, liner, box) | Verify | Visual and particle check on first lot |
| Color or marking change on cap | No action | Document in change control only |
The trap is the middle row. A new lot from the same supplier sounds harmless, and most of the time it is. But if the supplier runs multiple presses and your lot came off a different press with a different mold, the septum thickness tolerance may have shifted even though the certificate says "same." This is why the verification step has a numeric acceptance criterion, not a visual check.
For a typical headspace GC method with a 1 mL injection and a split of 10:1, I set the verification acceptance criterion at ±10% of the historical mean peak area for the internal standard, with a %RSD under 10% across 6 replicates. If the new lot fails that, it escalates to revalidation. If it passes, you have a documented, defensible verification and you can release the lot.
For a leak-sensitive method (anything with a 24-hour hold, or a method that runs at 60 °C headspace oven temperature), the verification is a dye ingress test at 40 °C for 24 hours on 30 units, with zero failures allowed. A single failure at that sample size is a red flag, because the defect rate that produces one failure in 30 is around 3%, which is far above the AQL you should accept on a critical seal.
An inspector does not want a narrative. They want to see four things in order: what changed, what you assessed, what you ran, and what you concluded. If any of those four is missing, the entry gets a finding, and the finding is usually written as "change control not effective," which is worse than the original problem.
Here is the entry skeleton I use. It fits on one page.
The single most common failure I see is a change-control entry that says "supplier notified us of a minor change, no impact on method." An inspector will ask for the supplier's change notice, read the actual attribute, and then ask why you concluded no impact. If you cannot point to a mechanism, the conclusion is not defensible. The mechanism is the whole entry.
Ask for the change notice in writing, and check that it names the attribute, not just the part number. A notice that says "product improvement" is not a notice. A notice that says "septum changed from 45 to 55 Shore A, effective lot 22K-118" is. If the supplier will not put the attribute in writing, that is itself a qualification problem, and it belongs in your supplier file, not in the change-control entry. The vial supplier relationship only works if the change notice is specific.
The symptom was the one I opened with: a 22% drop in internal standard area on a 40 mL volatile vial, new lot, same part number. The measurement that identified it was a septum extractables screen. We ran a blank vial from the old lot and the new lot at 60 °C for 30 minutes and compared the total ion chromatogram. The new lot showed a siloxane cluster at m/z 73, 147, 207, 281 that was roughly 3x the old lot. The durometer had gone up, the supplier had changed the silicone cure package to hit the new durometer, and the cure package was the source of the extra siloxane.
The fix was not to revalidate the method. The fix was to reject the lot and add a septum extractables screen to the incoming verification for that part number. The method was fine. The container was not. That distinction matters, because if we had revalidated the method we would have "passed" it against a bad lot and baked the problem into the method.
The symptom was intermittent low recoveries on a 24-hour hold method, maybe 1 in 40 vials. Static leak testing at room temperature found nothing. The measurement that identified it was dye ingress at 40 °C for 24 hours, which found 3 failures in 30 units. The cause was a change in the aluminum cap alloy on an 11 mm crimp cap, which changed the crimp compression slightly. At room temperature the seal held. At 40 °C the differential expansion opened a path at the crimp shelf.
The fix was a crimp torque and crimp height check on the capping tool, plus a revalidation of the seal at the method's actual hold temperature. The lesson is that the revalidation has to run at the method's worst-case temperature, not at ambient. A seal that passes at 25 °C tells you nothing about a method that holds at 40 °C.
Once you have a decision table, the verification itself becomes routine. I standardize on four checks, and they take about half a day.
If all four pass, the lot is released with a verification record. If any fails, it escalates to revalidation on the affected method, and the revalidation follows the original method validation protocol with the new container in place. The chromatography lab team owns the suitability and extractables checks; QC owns the dye ingress and pickup trial.
A revalidation is not the original validation run again. The original validation establishes that the method works. The revalidation establishes that the method still works with the new container, which means you can narrow the scope to the attributes the container touches.
In practice, that means:
What you do not need to redo: the full specificity study, the linearity curve, and the stability study, unless the container change is a glass or coating change that touches the sample contact surface. If the change is a septum or cap change, the sample never touches it in the liquid phase, so the liquid-phase validation stands.
For reference methods, the container clause is usually in the sample collection and preservation section, not the analytical section. The EPA SW-846 methods are a good example: the container requirement is stated in the method's sample handling text, and a container change is a change to that clause, which is a compliance question that runs alongside the analytical revalidation. Keep the two records separate. The analytical revalidation goes in the method file. The container clause assessment goes in the change-control entry.
One thing that catches people: a vial change often arrives at the same time as a new lot of septa for the instrument's own inlet, or a new HPLC filter lot, or a new column. If you revalidate the method with all three changed at once and it passes, you have learned nothing about which one mattered. Change one variable at a time. If the supplier ships the vial change and the septum change together, run the verification with the old instrument consumables first, then swap.
The same logic applies to the autosampler. A new vial lot with a slightly different neck bore can change the needle depth, which changes the pickup, which shows up as a retention time shift on the first injection of a sequence. The Aijiren consumables documentation and the Thermo Fisher sample handling references both list the dimensional tolerances that matter for autosampler compatibility, and they are worth checking against the supplier's certificate before you run anything.
A CoA tells you the lot met the specification. It does not tell you the specification changed. Those are different documents, and confusing them is how a lot change slips through without a revalidation decision. Ask for both. The CoA goes in the lot file. The change notice, if there is one, goes in the change-control entry.
If the supplier cannot produce a change notice because there was no change, ask them to state that in writing for the lot. A one-line email that says "no change to formulation, process, or supplier of components since lot X" is enough, and it costs the supplier nothing. If they will not write that line, treat the lot as changed and run the verification. The Restek technical resources have good guidance on what a container specification should contain, and it is a useful checklist to hold a supplier to.
When a verification fails, work in this order. It saves time.
If all six pass and the method still fails, the problem is not the container. Look at the instrument, the column, and the sample prep before you write a revalidation.
Write the change-control entry before you run anything, name the attribute that changed and the mechanism by which it could move a result, and set the acceptance criterion in numbers. If the change can move a peak area, a retention time, a leak rate, or a puncture count by more than the method's repeatability, revalidate the affected method at the method's worst-case temperature. If it cannot, verify with 6 replicates, a blank extractables screen, 30-unit dye ingress, and a 100-injection pickup trial, and release on a documented pass. The vials with caps you buy are only as consistent as the change notice behind them, and the revalidation decision is only as defensible as the mechanism you wrote down.
Related resources from our lab consumables network:
External references and standards: