Techkrates logo Techkrates
Contact
DE EN

← Back to Insights

IQ vs OQ Evidence: Clean Separation for Equipment Qualification

Installation Qualification (IQ) proves the installed baseline. Operational Qualification (OQ) proves the operating window. Mixing those two makes evidence look heavy but weak when a reviewer asks what was actually proven.

A clean split keeps qualification defensible: IQ locks the as-built state; OQ challenges performance against limits with controlled methods.

TL;DR

  • IQ confirms installation, utilities, configuration, and calibration; OQ confirms performance within defined limits.
  • Separate acceptance criteria, test methods, and evidence packages for IQ and OQ.
  • Trace critical requirements to risks (ISO 14971) and to IQ/OQ tests with objective pass/fail data.
  • Control deviations and open items with clear retest triggers before release.

Why this matters

Regulatory expectations are explicit: EU MDR and FDA 21 CFR 820 require documented qualification evidence for production and quality-critical equipment. ISO 13485 document control makes missing revisions or uncontrolled records an audit risk.

Business impact is direct: if IQ and OQ evidence are blurred, QA reviews slow down, line release slips, and suppliers get conflicting rework requests.

A clear split also makes change control easier. When a configuration change occurs, teams can see immediately whether the impact is on the installed baseline (IQ) or the operating window (OQ) and trigger the right retest.

What “good” looks like

Good IQ/OQ evidence tells a simple story that stands up to audit questions.

  • IQ checklist ties to as-built drawings, utilities, safety circuits, and configuration snapshots.
  • OQ protocols challenge performance at nominal and boundary limits using calibrated tools.
  • Critical requirements are classified as installation vs performance and linked to risk controls.
  • OQ starts only after the IQ baseline is locked and deviations are resolved or controlled.
  • Data integrity is explicit: timestamps, traceable samples, and controlled data storage.

A short IQ/OQ summary table on the protocol cover page (requirement, test type, evidence location) makes QA review faster and makes deviations visible before execution.

Evidence / Artifacts checklist

Keep the artifacts distinct so reviewers can see what was proven and when.

  • Approved IQ protocol and OQ protocol with acceptance criteria and roles.
  • As-built drawings, wiring/pneumatic schematics, and installation checklists.
  • Configuration and version records (PLC/HMI/firmware) plus parameter snapshots.
  • Calibration certificates for measurement systems used in OQ testing.
  • OQ test report with raw data, boundary condition results, and deviations.
  • Requirements traceability matrix linking URS → risks → IQ/OQ tests.
  • Deviation log or punch list with impact assessment, owner, and closure evidence.
  • Environmental verification records (power, compressed air, cleanroom class).
  • Measurement system verification (MSA/GR&R) where OQ data drives release decisions.
  • IQ/OQ summary page that states what was proven, what remains open, and why.

Common audit / QA questions

  • Which requirements are verified in IQ vs OQ, and why?
  • Where is the objective evidence for boundary conditions?
  • Which measurements are traceable to calibration records?
  • What open items exist, and what is the retest trigger?
  • Is the as-built configuration locked before OQ execution?
  • How is the IQ baseline protected from changes during OQ testing?

Typical failure modes

  • IQ contains performance claims without controlled test methods.
  • OQ starts before the as-built configuration is verified and stable.
  • Test results lack raw data or traceability to calibrated measurements.
  • Deviations are logged but not tied to closure evidence or retest triggers.
  • Configuration changes between IQ and OQ are not documented or assessed.

When to call for help

If IQ is blocked by missing drawings, unclear configuration, or inconsistent work instructions, it is usually faster to pause and fix the baseline than to push forward. For a rapid evidence gap check, contact me.

Relevant services

Related insight