A thermal cycler can pass a routine calibration check and still not be formally validated for use in a regulated workflow. Calibration confirms the instrument reaches and holds the temperatures it reports; validation is the broader, documented exercise — typically structured as Installation Qualification, Operational Qualification, and Performance Qualification (IQ/OQ/PQ) — that establishes and records evidence the instrument is correctly installed, operates across its intended range, and performs reliably under the lab’s actual assay conditions. For a lab manager or procurement officer, that distinction matters directly at purchase time: what a vendor includes (or charges extra for) in an installation and validation package is a real line item, and what your accreditation body expects to see in a validation file is a real audit risk if it’s missing. This guide covers what thermal cycler validation actually consists of, when it’s required, how it differs from calibration and verification, and what to evaluate when buying an instrument or contracting validation services.
Validation, Calibration, and Verification Are Not the Same Thing
These three terms get used loosely, but in an accredited or GxP-regulated lab they describe distinct, sequential activities. CASRAI’s companion guide on thermal cycler calibration covers the ongoing metrological check of temperature accuracy against a traceable reference standard. Validation sits at a different point in the instrument’s lifecycle and answers a broader question:
- Installation Qualification (IQ) — documented confirmation that the thermal cycler was received, installed, and configured as specified: correct model/firmware, utilities (power, ventilation, bench space) in place, and all components present against the vendor’s packing list and installation checklist.
- Operational Qualification (OQ) — documented testing that the instrument functions correctly across its specified operating range under controlled conditions: does it reach and hold each programmed temperature set point, execute ramp rates, and run through a representative protocol without fault, independent of any specific assay.
- Performance Qualification (PQ) — documented testing that the instrument performs reliably under the lab’s actual, routine operating conditions — typically running the real assay(s) the instrument will be used for, with real or representative samples/reagents, and confirming results meet pre-defined acceptance criteria.
Calibration is normally the final check performed as part of OQ (confirming temperature accuracy against a NIST-traceable reference) and then repeated on its own recurring schedule afterward. Validation as a whole is a one-time (or re-triggered) qualification event that establishes the instrument is fit for its intended use; calibration is the recurring metrological check that confirms it continues to meet the accuracy element of that qualification over time.
Why Formal Validation Is Required
Whether validation is a hard requirement — and how rigorously it must be documented — depends on the regulatory or accreditation framework the lab operates under:
- GLP studies under 21 CFR Part 58 — nonclinical laboratory studies submitted to FDA require equipment used to generate study data to be adequately tested, calibrated, and maintained, with documentation supporting that the equipment functioned as intended.
- ISO/IEC 17025 (testing and calibration laboratories) and ISO 15189 (medical laboratories) both require labs to verify that equipment is capable of achieving the required performance before being placed or returned into service — the standards’ language maps directly onto an IQ/OQ/PQ-style qualification even where they don’t use that exact terminology.
- CLIA (42 CFR Part 493) and CAP accreditation checklists require clinical laboratories to establish instrument function-check and maintenance procedures and, for a newly installed or relocated instrument used in molecular testing, to verify performance before it’s used to report patient results.
- GxP environments more broadly (pharma/biotech labs operating under GMP) typically require a documented IQ/OQ/PQ package as standard practice for any equipment supporting regulated data, thermal cyclers included.
A research-only lab outside these regimes has no external mandate to run a formal validation protocol, but a documented IQ/OQ (at minimum) at installation is still good practice: it creates a baseline record of instrument performance that a later calibration or troubleshooting event can be compared against, and many institutional core facilities and grant-funded quality plans require it internally regardless of external accreditation status.
When Thermal Cycler Validation Is Triggered
Beyond initial installation, re-validation (in whole or in part) is typically triggered by:
- Physical relocation of the instrument to a new site or bench.
- A major repair or service event touching the heating block, lid, or control electronics.
- A firmware or control-software update that changes cycling behavior.
- Introduction of a new assay or protocol with materially different temperature/ramp requirements than what PQ originally covered.
- A calibration or proficiency-testing failure that raises questions about whether the instrument still performs as originally qualified.
- Expiration of a periodic re-validation interval set in the lab’s own SOP, where one applies — some accredited labs set a fixed re-validation cycle (e.g., annually or biennially) independent of the more frequent calibration schedule.
What a Validation Package Should Document
Regardless of which framework applies, a defensible thermal cycler validation file typically includes:
- A written validation protocol, approved before execution, defining the IQ/OQ/PQ test steps, acceptance criteria, and who is qualified to execute and review it.
- IQ records — installation checklist, model/serial number, firmware version, site-condition confirmation, and the vendor’s installation report if one was provided.
- OQ records — test results for temperature accuracy, block uniformity, ramp rate, heated-lid performance, and hold-time accuracy against pre-defined tolerances, generally using a NIST-traceable reference — much of the same test set covered in CASRAI’s calibration guide.
- PQ records — results from running the lab’s actual assay(s) with defined acceptance criteria (successful amplification, expected Ct/Cq values for qPCR, no cross-contamination, etc.).
- A summary validation report with a documented pass/fail conclusion and sign-off, referencing any deviations and how they were resolved.
This is the same documentation set an accreditation surveyor or FDA inspector will ask to see, and it’s the record that supports a defensible instrument-qualification history if a specific result is ever questioned.
What to Evaluate When Buying: Vendor Validation Support
Validation support is a genuine procurement variable, not just a technical afterthought, and it’s worth asking about before signing a purchase order rather than after:
- What’s included versus billed separately. Some manufacturers bundle a documented IQ/OQ package (installation checklist plus operational test protocol and results) with the purchase; others charge it as a separate line item or leave it to the buyer to execute internally. Confirm which applies before comparing quotes across vendors.
- Whether PQ support is offered at all. Because PQ depends on the lab’s specific assay, most vendors don’t perform it — confirm whether the vendor provides a PQ protocol template the lab can adapt, or leaves PQ design entirely to the buyer.
- Documentation format compatibility. Ask whether the vendor’s IQ/OQ report format matches what your accreditation body (CAP, ISO 15189, ISO/IEC 17025, or an internal GLP quality unit) expects to see, rather than discovering a mismatch at inspection.
- Traceability of reference standards used during OQ. The same requirement that applies to ongoing calibration applies here — any reference probe used to confirm OQ temperature accuracy should be traceable to NIST or an equivalent national metrology institute, with that traceability documented in the report.
- Re-validation and service-event support. Confirm whether the vendor (or your existing calibration/maintenance provider) offers a re-qualification visit after a repair, relocation, or major service event, and how that’s priced relative to routine calibration.
As with calibration, some labs source installation validation support bundled through an equipment or reagent distributor’s service contract rather than the instrument manufacturer directly, or through a dedicated accredited metrology/validation provider. LAC Health, for example, is one distributor operating in the clinical and life-science lab space that coordinates installation and service support alongside equipment supply. Which channel is the better fit depends on order volume, existing institutional purchasing agreements, and how much weight the lab places on a single consolidated vendor relationship versus a dedicated validation specialist — neither is inherently the correct choice for every lab.
Validation and Software: Where CSV Fits In
Thermal cyclers with onboard software controlling cycling protocols, data capture, or connectivity to a LIMS/ELN raise a related but separate question: whether the software itself needs computer system validation. CASRAI’s guide to computer system validation (CSV), GAMP 5, and IQ/OQ/PQ covers that software-specific validation path in depth — for most standalone thermal cyclers running fixed onboard firmware, hardware-level IQ/OQ/PQ as described here is the applicable path, but instruments networked into a LIMS or running configurable analysis software may need both.
Frequently Asked Questions
Is thermal cycler validation the same as calibration?
No. Calibration is the recurring check of temperature accuracy against a traceable reference standard. Validation (IQ/OQ/PQ) is the broader, typically one-time-per-lifecycle-event qualification that the instrument is correctly installed, functions across its operating range, and performs reliably under the lab’s actual assay conditions. Calibration is normally performed as part of OQ and then repeated on its own schedule afterward.
Does CLIA require thermal cycler validation?
CLIA (42 CFR Part 493) requires clinical laboratories to verify instrument performance before a newly installed or relocated instrument is used to report patient results, and to maintain documented equipment maintenance and function-check procedures. CAP-accredited labs document this under the applicable accreditation checklists.
Who performs performance qualification (PQ) for a thermal cycler?
PQ is generally executed by the lab itself, since it depends on the lab’s specific assay and acceptance criteria rather than generic instrument performance. Vendors typically support IQ and OQ directly but leave PQ protocol design to the buyer, sometimes providing a template to adapt.
How often does a thermal cycler need to be re-validated?
There’s no single universal interval. Re-validation is generally event-triggered — relocation, major repair, firmware update, or a new assay with materially different requirements — rather than run on a fixed calendar schedule the way calibration typically is, though some accredited labs also set a periodic re-validation interval in their own SOP.
Can validation and calibration happen in the same visit?
Yes, and for a newly installed instrument this is common — OQ testing (which includes temperature accuracy) and the initial calibration event are often performed together, with the calibration then continuing on its own recurring schedule independent of the one-time validation package.
