Procurement teams that treat a VHP pass box RFQ as a commercial document—specifying chamber size and lead time but leaving cycle program and load assumptions undefined—routinely receive quotations that cannot be validated against their actual transfer use. The gap only becomes visible during site qualification, when the supplier’s standard cycle, developed against an empty or generically loaded chamber, fails to deliver the expected log reduction under real material conditions. Correcting the cycle at that stage often requires additional development runs that were never scoped or priced, adding weeks to the qualification schedule and creating a disputed responsibility boundary between supplier and site. What follows gives QA, EHS, and procurement teams the specific RFQ elements to define, the documentation to request before quotation, and the acceptance check to apply before approving a supplier response.
Cycle evidence to request before VHP quotation
Requesting a unit price and a cycle time is not sufficient to evaluate a VHP pass box quotation. Before quotation, a supplier should be able to provide evidence from four development activities: a parameter development study showing how cycle inputs were derived, a VHP distribution study confirming uniform concentration across the loaded chamber, a biological challenge test demonstrating actual log reduction under the test load, and an exhaust degradation study establishing that H₂O₂ decays reliably to a safe residual after aeration. Each of these addresses a distinct failure mode; absence of any one of them leaves a gap that QA review will likely flag, regardless of how well the others are documented.
The consequence of requesting this evidence at RFQ stage rather than post-award is that it forces the supplier to characterize what they have actually validated before you commit to the equipment. A supplier who can provide all four studies against a comparable load configuration is substantively different from one who delivers a confident quotation backed only by a factory acceptance test against an empty chamber. That distinction is difficult to recover from after purchase order.
ISO 22441:2022, which establishes the testing framework for low-temperature vaporized hydrogen peroxide sterilization, provides useful reference context for how these development activities relate to establishing a validated process. It does not function as a line-item mandate for each study, but its framework supports the expectation that cycle parameters require systematic evidence rather than arbitrary selection.
The RFQ should also specify which cycle program is required: a LOGA 6-log reduction program, a LOGB 12-log overkill program, or a concentration-based cycle. These programs differ in sterility assurance level, and a supplier quoting against the wrong program delivers a cycle that may technically pass their own acceptance criteria while failing yours. Include a maximum cycle time—typically ≤90 minutes or ≤120 minutes depending on throughput requirements—because a cycle that satisfies biological challenge requirements but runs 150 minutes is operationally unacceptable and the RFQ is the right moment to make that constraint visible.
| Typ badania | What It Demonstrates | Risk If Absent |
|---|---|---|
| Parameter development study | Cycle parameters were systematically developed, not arbitrarily chosen | Ad‑hoc cycle may fail QA review; parameters may lack rationale |
| VHP distribution study | Uniform VHP concentration across the chamber under load | Uneven sterilization risk and validation failure |
| Biological challenge test | Actual log reduction achieved using biological indicators | Sterility assurance level remains unproven |
| Exhaust degradation study | Reliable H₂O₂ decay after aeration; residual levels safe for release | Release may be delayed or expose operators to unverified peroxide levels |
Load pattern assumptions that affect validation
The chamber dimension range for configurable VHP pass boxes can span from 600×600×600 mm to 1200×1400×1600 mm, but chamber size alone does not define the validation challenge. What drives VHP distribution behaviour inside the chamber is the density, geometry, and material composition of the actual transfer load—and a supplier quoting against an unspecified or generic load will optimize cycle parameters for conditions that may not resemble your routine use at all.
If the RFQ omits load pattern definition, the supplier defaults to whatever test configuration their development work used. That configuration may be a partial load of homogeneous containers placed with maximum airflow clearance. Your actual load may be tightly packed secondary packaging with absorbent materials that slow H₂O₂ penetration or surfaces that act as sinks. When the validation protocol runs against the real load, distribution uniformity may not be achieved and the cycle will require adjustment. At that point, the supplier’s obligation is ambiguous because the RFQ never defined load conditions as a requirement.
The RFQ should state load dimensions, approximate density class, and material types that will routinely pass through the unit. Where transfer requirements vary—some cycles carrying rigid containers, others carrying bagged soft goods—both load configurations should be described, since each may require a separate validated cycle. The cost of defining this upfront is a more accurate quotation. The cost of omitting it is a validation scope that does not cover actual use.
A related clarification that often gets deferred: whether VHP sterilization is required for all transfers or whether some transfers qualify for HEPA air-shower only, particularly if the unit supports a self-cleaning or purge-only mode. This is a procurement trade-off affecting validation scope and cost, not a compliance boundary per se, but it needs to be resolved in the RFQ to prevent the supplier from quoting a validation package that either over-scopes or under-scopes your actual requirements.
BI and CI support in supplier documentation
A supplier claiming ≥6-log reduction without providing the underlying BI/CI documentation has not demonstrated sterility assurance—they have stated a target. The distinction matters at QA review: a claim without supporting data cannot be reviewed, only noted.
The RFQ should specify Bacillus stearothermophilus (also designated Geobacillus stearothermophilus) as the biological indicator species, which aligns with standard VHP practice. Specifying the BI type in the RFQ prevents the supplier from validating against a different organism and then delivering documentation that cannot be directly compared against your internal validation protocols or accepted as equivalent without additional justification. Similarly, chemical indicators (CIs) should be specified as a required deliverable: CI data provides cycle-to-cycle process confirmation during routine operation, but the supplier’s documentation should establish what CI response correlates to validated cycle conditions under your load configuration.
The ≥6-log reduction figure is a design threshold tied to the cycle program selected, not a universal floor that applies independently of load and parameters. Verifying that a supplier’s BI/CI data actually demonstrates ≥6-log reduction under conditions comparable to your load pattern is a review check, not a self-evident given. A supplier may have robust BI data under one set of load conditions and limited or no data under others.
| Wymóg | Dlaczego to ma znaczenie | Co należy potwierdzić |
|---|---|---|
| Specify Bacillus stearothermophilus as biological indicator | Wrong BI type invalidates validation evidence | Supplier confirms B. stearothermophilus BI per standard VHP practice |
| Request complete BI/CI certificates and validation reports as deliverables | QA needs these to review cycle validation; missing documents delay approval | All certificates/reports are listed and delivered before quotation |
| Verify BI/CI data demonstrate ≥6‑log reduction under actual load conditions | Claimed log reduction without documented proof under specific load is not acceptable | Proof explicitly shows ≥6‑log reduction with your load pattern |
Missing BI/CI documentation at quotation stage is not a paperwork gap that can be resolved later without consequence. QA cannot progress a validation plan against cycle performance data that has not been reviewed, and procuring equipment before that review means qualification risk is carried forward into a project stage where correction is significantly more expensive.
For teams building their pre-RFQ documentation checklist, the Jakie dokumenty potwierdzające należy wymagać od producentów VHP przed wysłaniem zapytania ofertowego resource covers the broader documentation scope that should accompany supplier evaluation.
Aeration endpoint and release-condition records
The aeration phase is where operator safety risk is concentrated, and it is the phase most likely to be under-documented in a supplier quotation. A residual H₂O₂ concentration of ≤1 ppm before door opening is the operationally accepted release condition for most VHP pass box applications. That figure derives from occupational exposure practice rather than a single universally codified regulatory limit, but it functions as the practical threshold against which aeration endpoint is assessed and release is authorized.
Two things must be present in the supplier’s documentation to treat this threshold as validated rather than assumed. First, a logged aeration profile showing actual H₂O₂ concentration decay from peak to ≤1 ppm, recorded under the test load conditions. A calculated or modelled decay curve is not equivalent; the profile must reflect measured sensor data from development or qualification runs. Second, a confirmed safety interlock that prevents door release until the ≤1 ppm condition is met and logged. An interlock that is present in the design but not validated as a functional release gate is architecturally present but operationally unverified.
Both of these should be specified in the RFQ, not negotiated post-delivery. A supplier who has not validated the aeration endpoint under load has not completed the cycle development work—the absence of a logged profile is not a documentation lag, it signals that the release condition has not been established for that load configuration. Accepting the quotation without confirming these elements means the site will need to generate that evidence during qualification, with no guarantee the supplier’s standard aeration parameters are sufficient for the actual load.
A Skrzynka przepustek VHP that integrates the H₂O₂ generator with a calibrated residual sensor and interlocked door release provides the hardware basis for this documentation. The RFQ should confirm that the residual sensor is part of the validated cycle record, not a standalone display.
Supplier versus site VHP validation boundaries
The most common source of unresolved responsibility in VHP pass box projects is an RFQ that does not state which validation deliverables are supplier-provided and which must be generated during site qualification. EudraLex Volume 4 Annex 15 establishes the general principle that responsibilities between supplier and site must be clearly allocated in qualification activities; for a VHP pass box, that allocation should be explicit before purchase order, not reconstructed from email threads after FAT.
The practical question is whether a standard factory cycle—validated at the supplier’s facility against a defined test load—is acceptable as the basis for site qualification, or whether the specific materials, container geometries, and transfer frequencies at your site require development runs against site-representative loads. Neither option is the regulatory default. The choice depends on how closely the supplier’s test load resembles your actual load, and that comparison can only be made if both are defined.
| Validation Area | What to Clarify in the RFQ | Potential Confusion If Unclear |
|---|---|---|
| Cycle basis (factory vs site‑specific) | Whether a standard factory cycle is acceptable or development runs with actual site materials are required | Supplier may quote a cycle that fails with site load, forcing rework and delays |
| Parameter verification (concentration, time, temperature) | Which cycle parameters are supplier‑proven and which must be verified on site during qualification | Gaps or duplicate effort can arise, wasting resources and extending schedule |
Leaving this boundary undefined does not mean both parties share responsibility equally—it typically means neither party has scoped the gap, and it surfaces during IQ/OQ/PQ when the validation team discovers that the cycle data supporting the protocol covers a load configuration that is not what is actually being transferred. At that point, the supplier considers the additional work out of scope, and the site considers it a supplier obligation. The RFQ is the last practical moment to prevent that dispute.
A useful frame: define in the RFQ which parameters are supplier-proven (concentration profile, conditioning time, temperature range) and which must be site-verified (distribution uniformity under actual load, aeration endpoint under actual load density). The Protokół walidacji VHP: IQ OQ PQ dla systemów nadtlenku wodoru provides additional structure for how those site verification activities integrate into the qualification sequence.
RFQ acceptance rule for cycle and load clarity
A VHP pass box quotation response should be treated as technically incomplete—and held from QA progression—if it does not explicitly state the cycle program, load dimensions, and residual H₂O₂ release limit. These three elements are not background assumptions that can be inferred from catalog data or assumed from standard practice. They define the performance basis of the equipment in your specific application.
The acceptance check adds a fourth element: a written declaration from the supplier that the quoted cycle achieves ≥6-log reduction and ≤1 ppm residual H₂O₂ under the stated load pattern, with any deviation from that performance documented explicitly. The purpose of requiring a deviation statement is not to anticipate failure—it is to establish that the supplier has a mechanism for handling conditions where the standard cycle does not meet those thresholds, rather than simply asserting that it will.
| Kryterium akceptacji | What the Supplier Must State | Consequence of Omission |
|---|---|---|
| Exact cycle program | LOGA (6‑log), LOGB (12‑log overkill), or Concentration | Ambiguous sterility assurance; risk of under‑sterilization |
| Load dimensions | Exact load dimensions and shape matching chamber specification | Validation may not cover actual transfer use; equipment may be non‑conforming |
| Residual H₂O₂ limit | ≤1 ppm as release condition | Potential release at unsafe residual levels; operator exposure risk |
| Cycle performance statement | Declaration that the cycle achieves ≥6‑log reduction and ≤1 ppm residual under the stated load, with any deviation explicitly documented | No clear pass/fail criteria; ambiguous approval |
Omission of any single criterion is enough to make the response unacceptable for procurement approval. A quotation that specifies cycle program and load dimensions but omits the residual limit leaves the release condition undefined. A quotation that states the residual limit but does not specify load dimensions leaves open whether the claimed performance applies to your transfer configuration at all. Auditors reviewing the qualification file later will ask whether the cycle was validated against the actual load; if the RFQ and quotation do not establish that connection clearly, the answer will be difficult to support.
The Lista kontrolna audytu dokumentacji GMP VHP Passbox Validation covers what inspectors typically examine in the qualification record, which gives additional context for why the acceptance criteria established at RFQ stage need to carry forward into the validation documentation chain.
The underlying discipline this article supports is straightforward: an RFQ for a VHP pass box is a validation-boundary document, and the acceptance check applied to the supplier response is the last practical point to prevent a non-conforming installation. Cycle evidence, load pattern assumptions, BI/CI documentation, aeration endpoint records, and supplier-versus-site responsibility boundaries are not items to resolve during qualification—they are items to resolve before purchase order, because the cost and schedule impact of correcting them after equipment delivery is categorically higher than the effort of defining them upfront.
Before approving a quotation response, confirm that the supplier has answered four questions with specificity: what cycle program, against what load, achieving what performance thresholds, and with which elements validated at the factory versus which will be verified at your site. If any of those answers is absent or stated only as a general assurance, the response is incomplete and should be returned for clarification before the procurement record advances.
Często zadawane pytania
Q: What if our transfer loads vary significantly between campaigns — does the RFQ need to cover every possible load configuration?
A: Yes, each materially different load configuration should be described in the RFQ, because each may require a separate validated cycle. VHP distribution behaviour is driven by load density, geometry, and material composition — not chamber size alone. A supplier who quotes against one load type cannot claim validated performance for a second, significantly different configuration. Defining the full range of routine loads upfront produces a more accurate validation scope and prevents the qualification team from discovering mid-OQ that additional development runs are needed for loads never presented to the supplier.
Q: If a supplier cannot provide all four cycle development studies at RFQ stage, is it acceptable to request them after award as a contractual deliverable?
A: No — requiring them after award substantially increases your project risk. The purpose of requesting this evidence before quotation is to verify that the supplier has actually performed the development work against a comparable load, not to collect paperwork. A supplier who cannot produce a VHP distribution study, biological challenge data, and an exhaust degradation study at quotation stage has not completed the cycle development work for your load conditions. Accepting the award without that confirmation means you are funding development work as part of qualification, with no price certainty and no recovery path if the cycle requires redesign.
Q: At what point does a supplier-validated factory cycle stop being sufficient, and site-specific development runs become necessary?
A: A factory cycle stops being sufficient when the supplier’s test load does not reasonably represent your actual transfer materials. The comparison point is specificity: if the supplier’s BI/CI data was generated against rigid, uniformly spaced containers with full airflow clearance, and your routine load is tightly packed secondary packaging with absorbent surfaces, the distribution and penetration assumptions in that cycle do not transfer. There is no universal similarity threshold, but the RFQ is the right moment to document both configurations side by side and require the supplier to state explicitly whether their factory data covers your load — or whether site-representative development runs are required before the validation protocol can be written.
Q: How should we handle a supplier who provides the four cycle studies but against a load configuration that is partially comparable — not identical, but not wholly different — to ours?
A: Treat partial comparability as a defined gap rather than an acceptable match. Identify specifically which load parameters diverge — density, material type, geometry — and require the supplier to state whether their existing data is claimed to bound those differences or not. If the supplier asserts the data bounds your load, that assertion should be documented in writing and included in the qualification file, because an auditor reviewing IQ/OQ/PQ records will ask exactly that question. If the supplier cannot bound it, the gap becomes a site validation task that should be scoped and priced before purchase order, not discovered during protocol execution.
Q: Is the ≤1 ppm residual H₂O₂ release threshold a fixed regulatory requirement, or can it be negotiated based on our facility’s occupational exposure limits?
A: It is an operationally accepted threshold derived from occupational exposure practice, not a single codified regulatory figure — which means it can be reviewed against your facility’s specific exposure controls, but cannot simply be relaxed without documented justification. If your EHS function has established a site OEL for H₂O₂ that differs from 1 ppm, that limit should be stated explicitly in the RFQ so the supplier validates the aeration endpoint and safety interlock against your actual release condition. What the RFQ must not do is leave the residual limit undefined: an unspecified release condition means the interlock has no validated threshold to enforce, and the logged aeration profile has no acceptance criterion to satisfy.
