Instrument Operational Qualification (OQ) Protocol

This is a ready-to-use operational qualification protocol for a laboratory instrument. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, attach the test standards and certificates the protocol calls for, and route it through your normal document control, review, and approval. A worked filled specimen for an HPLC system follows the template so you can see how a completed version reads. Verify each cited regulation against the current source before you rely on it.

OQ proves one thing: that the installed instrument actually operates as intended across the ranges you will use, not just that it powers on. It is the third stage of the qualification lifecycle, after design qualification (DQ) and installation qualification (IQ) and before performance qualification (PQ) or the method-specific system suitability that confirms the instrument plus method plus column work together. OQ challenges each module against its own specification with traceable references: the pump for flow and gradient, the autosampler for injection precision and carryover, the detector for wavelength accuracy, linearity, noise, and drift, and the column compartment for temperature accuracy. Pass OQ and you have a documented baseline of operating performance that PQ, calibration, and change control all build on.

Document control header

1. Purpose

This protocol defines the functional tests and acceptance criteria to confirm that instrument <<FILL: instrument ID / asset number>>, already installed and IQ-approved under <<FILL: IQ reference>>, operates correctly across its intended operating ranges. The objective is a documented, inspection-ready record that each module performs to specification (pump flow and gradient proportioning, autosampler injection precision and carryover, detector wavelength accuracy, linearity, noise and drift, column compartment temperature accuracy) so the instrument is fit to enter routine use, PQ, and method validation.

2. Scope

This protocol applies to the single instrument identified in the header and section 5, including its modules and the controlling data system. It covers operational performance against specification across the configured operating ranges. It assumes IQ is complete and approved; OQ does not re-verify installation. It does not establish performance for a specific method, sample, and column, which is covered by PQ or by method-specific system suitability under <<FILL: cross-reference SOP-ID>>, and it does not set calibration intervals or routine maintenance, which are governed by <<FILL: cross-reference SOP-IDs>>. Software functional verification for the data system (audit trail, access control, calculations) is coordinated with the computerized system validation under <<FILL: CSV SOP-ID>> and is not replaced by this protocol.

3. Responsibilities

4. Definitions

• Operational qualification (OQ): documented verification that an installed instrument operates as intended across its specified operating ranges.
• Performance qualification (PQ): documented verification that the instrument consistently performs for the intended application, often using a method and column; the stage after OQ.
• Operating range: the span of a parameter (flow rate, wavelength, temperature, gradient composition) over which the instrument will be used and is therefore challenged at low, mid, and high points.
• Acceptance limit: the tolerance an instrument module must meet, taken from the manufacturer specification or a recognized standard, against which the actual measured value is judged.
• Traceable standard / reference: a certified test tool or material (for example a holmium oxide or didymium filter for wavelength, a caffeine or potassium dichromate solution for linearity, a calibrated flow meter, a thermocouple) traceable to a national or international standard.
• Instrument category (USP <1058>): the tier assigned to an instrument under the USP <1058> risk-based scheme, which scales how much qualification an instrument needs to its complexity. The most complex tier covers software-driven analytical systems, for example a chromatograph paired with a data system, and these get the full module-by-module OQ in this protocol; refer to the current chapter for the tier names and how to assign them.

5. Instrument and operating ranges under qualification

State the instrument category per USP <1058> in section 5.1, then define the exact operating ranges to be challenged in section 5.2. Test at the low, middle, and high of each range you will actually use, not just one convenient setpoint, and not beyond what you intend to use. Acceptance limits come from the manufacturer specification and recognized standards; record the source for each.

5.1 Instrument identification

5.2 Operating ranges and acceptance limits

6. Prerequisites

Confirm and record the following before any test runs. A test executed without a valid prerequisite is not acceptable.

7. Test cases

Each test case states what to verify, the method in brief, the expected result against the acceptance limit, where the actual result and evidence are recorded, and the pass/fail call. Record the actual measured value (not “OK”), attach the evidence (chromatogram, spectrum, calibration printout, certificate), initial and date each line, and reference any deviation. A test case passes only when the actual result meets the acceptance limit and the evidence is attached.

7.1 Pump flow rate accuracy

Set the pump to low, mid, and high flow and measure delivered volume gravimetrically or with a calibrated flow meter over a timed interval. Compare delivered to set.

7.2 Gradient proportioning (composition accuracy)

Run a step gradient using a traceable tracer (for example a low concentration of a UV-absorbing additive in line B against line A) and confirm the measured plateau heights match the programmed percentages within tolerance. Test the steps you will actually use.

7.3 Autosampler injection precision and linearity

Make replicate injections of a stable standard at a representative volume for precision, then a series of volumes for linearity. Report peak-area RSD for precision and the correlation for linearity.

7.4 Carryover

Inject a high-concentration standard, then inject blank diluent under the same conditions, and confirm the residual peak at the analyte retention time is within limit relative to the preceding peak.

7.5 Detector wavelength accuracy

Measure the absorbance maxima of a certified reference (for example a holmium oxide filter or solution, or didymium) and compare to the certified values across the working range.

7.6 Detector linearity (photometric)

Inject or measure a series of concentrations of a stable standard (for example caffeine, or potassium dichromate for photometric checks) across the working absorbance range and confirm the response is linear.

7.7 Baseline noise and drift

Record the baseline at a defined wavelength and flow for a defined period with no injection and measure short-term noise and drift against specification.

7.8 Column compartment temperature accuracy

Set the column compartment to low, mid, and high temperatures and verify with an independent calibrated thermometer or thermocouple. Confirm setpoint accuracy and (where specified) stability.

8. Acceptance criteria

The OQ is acceptable when all of the following are true:

• Every applicable test case in section 7 has a recorded actual measured value that meets its acceptance limit, with evidence attached, and is marked Pass.
• Each operating range was challenged at low, middle, and high as defined in section 5.2, with no setpoint outside the intended range substituted.
• All test tools and reference standards used were in date and traceable, with certificates attached.
• The firmware and software stayed at the IQ baseline throughout testing, with no undocumented change.
• Any deviation raised under section 9 is resolved and assessed as not affecting the qualified operating state.

A single failed test case prevents progression to PQ / routine use until it is resolved or justified through deviation handling. Do not average a failing replicate set to a pass.

9. Deviations

Any actual value outside its acceptance limit, any use of an out-of-date or untraceable standard, any version change from the IQ baseline, or any departure from this protocol is documented as a deviation per <<FILL: deviation SOP-ID>>, assessed for impact, and resolved before the OQ is approved and the instrument enters use. Record each deviation below and reference the full deviation record.

10. Summary and conclusion

On completion, the executor summarizes the outcome and states whether the instrument passed OQ and may progress to PQ / routine use.

11. Attachments

12. References

21 CFR 211.68 (automatic, mechanical, and electronic equipment) and 211.160(b) and 211.194 (laboratory controls and records). EU GMP Annex 15 (Qualification and Validation), 2015 revision. USP <1058> Analytical Instrument Qualification (and the Group A / B / C categories that set OQ depth). USP <621> Chromatography and USP <1226> Verification of Compendial Procedures (for chromatographic performance context). USP <857> Ultraviolet-Visible Spectroscopy (for wavelength accuracy and photometric checks). ICH Q2(R2), Validation of Analytical Procedures (linearity, precision concepts applied to instrument tests). ICH Q9, Quality Risk Management (for the risk-based ranges and test depth). Where the instrument holds GxP data: 21 CFR Part 11 and EU GMP Annex 11. ISO/IEC 17025 (for the calibration laboratory and traceability of the test standards).

Confirm the current version and clause numbers of each reference before issue.

13. Revision history

14. Approvals

Filled specimen

The following shows the protocol executed for an example HPLC system, so you can see the level of detail an inspector expects. The company, instrument, values, and numbers are illustrative; replace them with your own.

Instrument identification

Operating ranges and acceptance limits

Selected test case results

Worked calculation: injector precision (test 7.3.1)

Six replicate 5 uL injections of the caffeine standard gave peak areas 1452.1, 1448.7, 1455.3, 1450.0, 1446.9, 1453.8. Mean = 1451.13, standard deviation = 3.18, RSD = (3.18 / 1451.13) x 100 = 0.22 percent. Recorded as 0.38 percent after including the second replicate set per the protocol; well inside the 1.0 percent limit. Pass.

Worked calculation: wavelength deviation (test 7.5.1)

Certified holmium oxide maximum 241.0 nm; instrument reported the absorbance maximum at 240.6 nm. Deviation = 240.6 - 241.0 = -0.4 nm, inside the +/- 1 nm limit. Pass.

Deviation raised

Summary

In this example the executor challenged each module at low, mid, and high points of the real operating range, recorded actual measured values and worked the calculations rather than ticking “OK”, used certified traceable standards, caught a genuine failure at the 60 C column setpoint instead of averaging it away, raised it as a deviation, found the root cause, recalibrated, and re-tested before declaring OQ PASS. That sequence, challenge each range to record actual values to deviation to root cause to re-test to documented conclusion, is exactly what a reviewer is expected to demonstrate.

Common inspection findings this protocol prevents

• OQ executed with “OK” or “Pass” ticked but no recorded actual values, so there is no evidence the instrument actually met any limit.
• Modules tested at a single convenient setpoint instead of across the operating range, so accuracy at the extremes you actually use is unknown.
• Acceptance limits left blank or invented, with no link to the manufacturer specification or a recognized standard.
• Test tools and reference standards out of date or with no traceability certificate, undermining every result that depended on them.
• A failing replicate set averaged into a pass, or a failing high setpoint quietly dropped from scope.
• Firmware or software changed between IQ and OQ with no change control, so the OQ no longer reflects the operating configuration.
• OQ approved with an open deviation, so the instrument entered routine use before its operation was actually confirmed.
• No requalification trigger defined, so the instrument runs for years on a one-time OQ with no link to repairs, moves, or module swaps.

How to adapt this protocol

1. Set your document number, owner, room, linked DQ/IQ/PQ references, and effective date in the header.
2. State the USP <1058> instrument category in section 5.1 and scale the test cases to it: a Group B balance or pH meter needs accuracy and precision checks but not the full chromatography menu, while a Group C HPLC, GC, or UHPLC needs the module-by-module tests in section 7.
3. Fill section 5.2 with your real operating ranges and the acceptance limits from your manufacturer specification sheet, and challenge each range at low, middle, and high.
4. Replace the chromatography test cases in section 7 with the parameters that matter for your instrument type (for example resolution and detector response for a plate reader, rotation speed and temperature for a dissolution apparatus, oven ramp accuracy for a GC).
5. Point the cross-references in sections 2 and 9 to your real PQ / system suitability, CSV, deviation, change control, and calibration procedures, and set the requalification trigger in section 10.
6. Where the vendor performs OQ, keep the test-case structure and acceptance limits and use them to review and accept the vendor records against your own criteria, rather than substituting the vendor report for this protocol.
7. Confirm every regulation in section 12 against the current published version before issue.