Equipment Validation (IQ, OQ, PQ): What Maintenance Teams Must Document

Calendar
Duration:
8 min
calendar today
Published on
October 20, 2026
Featured Image

Equipment validation is written proof that a machine is installed correctly, runs within set limits, and works the same way every time. Maintenance teams help by logging install checks (IQ), operating tests (OQ), and performance runs (PQ). They then keep those records current for the life of the asset.

Auditors judge validation on evidence, not intent. A pump can run perfectly and still fail an audit if nobody can show its calibration certificate, test results, or approved change record. This guide lists what to document for equipment validation at each stage, who signs it, and how to keep the file audit-ready.

Key Takeaways

  • Document by stage: Equipment validation rests on three records: IQ for the installation, OQ for the limits, and PQ for steady results.
  • Trace every record to one asset ID: Certificates, procedures, and test data must point back to the same equipment record.
  • Maintenance protects the validated state: Calibration, PM tasks, and repair logs show the machine still matches what was qualified.
  • Treat every change as an event: A repair or upgrade needs a change record and a requalification decision.

What Is Equipment Validation and Why Documentation Matters

Equipment validation as documented proof across installation, operation and performance | Cryotos

Equipment validation is the work of proving, with written records, that a machine is fit for its use. It is a core rule in drug, medical device, and food plants.

Regulators write this into their rules:

Terms vary by site. Many teams say equipment validation for the whole effort. Regulators say qualification for equipment and validation for processes. A machine counts as validated only when the paperwork proves it. Missing records can delay a product release or trigger an audit finding.

Installation Qualification (IQ): What to Document

Installation qualification (IQ) is the check that equipment arrived complete and was installed to the approved design. It sets the baseline for every later record.

Maintenance often leads the physical checks. Capture these records:

  • Design link: The approved requirements and design the machine must match.
  • Receipt and ID checks: Purchase order, model, serial numbers, and a parts list checked against the order.
  • As-built drawings: Pipe, wiring, and layout drawings that show what was built, not what was planned.
  • Utility and safety checks: Power, air, water, and interlock hookups tested and signed.
  • Instrument calibration: Certificates for each key gauge and sensor, traceable to a standard.
  • Manuals and spares: Current manuals, oil and grease needs, and the spare parts list.
  • Deviation log: Each install problem, its fix, and who approved it.

Give the machine a unique asset ID now, and tag every record with it. Asset tracking in Cryotos links each ID to a QR label and the full record history. IQ is done when every installed item matches a signed record.

Keep these files on the asset record, not on a shared drive. Cryotos does this through document management, with manuals and certificates stored on each asset.

Operational Qualification (OQ): What to Document

Operational qualification (OQ) is the testing that shows equipment runs correctly across its full operating range. Tests push the machine to the limits it will meet in production.

Write an approved protocol first. Then file the results:

  • Approved OQ protocol: Test steps, pass limits, and sign-off lines, written before testing starts.
  • Test results: Raw data, screenshots, or printouts for each step, marked pass or fail.
  • Challenge tests: Alarm, interlock, power loss, and restart checks, plus the highest and lowest set points.
  • Software and settings: Version numbers, set points, and user access levels locked during testing.
  • Test instrument records: IDs and calibration dates for every device used in testing.
  • Draft procedures: Operating, cleaning, and PM procedures tried out during OQ.
  • Training records: Names of the staff who ran the tests.

Build the protocol steps into maintenance checklists. Technicians then record each reading in the same order, with digital signatures. An OQ is complete only when every failed test has a closed deviation.

Performance Qualification (PQ): What to Document

Performance qualification (PQ) is the proof that equipment gives steady results under real production conditions. It uses real materials, trained operators, and approved procedures.

Many sites use three good runs in a row, but your validation plan sets the number. Document these items:

  • Approved PQ protocol: Run count, load size, and pass limits set in advance.
  • Run records: Settings, outputs, and quality results for every run.
  • Trend data: Temperature, pressure, speed, or cycle times that show stable behavior.
  • Sample and inspection results: Lab or inspection data for what the runs produced.
  • Final report: A summary that says whether the equipment met every limit, with approvals.
  • Maintenance readiness: PM tasks, spare parts, and calibration dates in place before release.

A signed PQ report releases the equipment for routine use.

IQ vs OQ vs PQ: What Each Stage Proves

IQ, OQ and PQ qualification stages compared in sequence | Cryotos

IQ, OQ, and PQ answer three different questions. Each needs its own signed records. The table shows how they compare.

StageQuestion it answersKey recordsTypical sign-off
IQIs it installed as designed?Specs, as-built drawings, calibration certificates, deviation logMaintenance, engineering, QA
OQDoes it run across its full range?Approved protocol, test data, challenge tests, draft proceduresEngineering, operations, QA
PQDoes it work steadily in production?Run records, trend data, final reportOperations, QA

The stages run in order. A failed stage sends the team back to fix and retest. The signed IQ, OQ, and PQ together form the qualification file.

How Maintenance Teams Keep Equipment Validation Current

Qualification Evidence Ladder: Specify, Install, Operate, Perform, Sustain | Cryotos

Maintenance teams keep equipment validation current by proving, after go-live, that the machine still matches what was qualified.

The Qualification Evidence Ladder:

  • Specify: Link the approved requirements and design to the asset record.
  • Install: File the IQ package, with calibration and as-built records.
  • Operate: File the OQ results and approved operating procedures.
  • Perform: File the PQ runs and the final report.
  • Sustain: Add PM, calibration, repair, and change records for the life of the asset.

A Computerized Maintenance Management System holds the Sustain rung in one place. It tracks recurring tasks, calibration due dates, signed checklists, and linked repair history.

Document Every Repair and Change on the Asset Record

Repairs, part swaps, and software updates can all affect the validated state. Log each job through work order management. Send anything beyond a like-for-like swap through change control for a requalification decision.

Triggers That Call for Requalification Review

Flag these events for a quality review before the machine returns to production:

  • Relocation or reinstall: Utilities, levels, and alignment may no longer match the IQ.
  • Key part or software changes: New parts or control code can shift operating limits.
  • Repeated out-of-tolerance results: Drift in key instruments puts earlier test data in doubt.
  • Process or product changes: New materials or settings may fall outside the qualified range.
  • Long shutdowns: Extended idle time may exceed what the validation plan allows.

Maintenance teams using Cryotos have reported up to 30% reduction in unplanned downtime and 25% faster repair turnaround. Fewer emergency repairs also mean fewer deviations to explain.

Common Equipment Validation Documentation Mistakes

Gaps usually come from weak links between records, not from skipped tests.

  • Unsigned or undated entries: A missing signature can sink an otherwise good test.
  • Expired test instruments: Results from an out-of-date gauge are hard to defend.
  • Untracked repairs: A part swap with no record breaks the link to the qualified state.
  • Scattered files: Records split across email, binders, and drives slow down every audit.
  • Late records: Entries written days after the work are easy to challenge.
  • Forgotten requalification: A major change with no review leaves the file out of date.

Fixing these habits closes the most common gaps.

Frequently Asked Questions

What is equipment validation in simple terms?

It is written proof that a machine is installed right, works as designed, and performs steadily. Regulated industries require it so product quality and safety can be shown with records.

How do IQ, OQ, and PQ differ from each other?

IQ checks the installation. OQ tests operation across its limits. PQ proves performance in real production. Each stage has its own protocol, results, and signatures.

Who is responsible for IQ, OQ, and PQ documentation?

Engineering or validation staff usually write the protocols, and quality assurance approves them. Maintenance teams supply install checks, calibration records, and repair history. They sign the work they perform.

When does equipment need to be requalified?

Requalify after major repairs, a move, control or software changes, or repeated failures. A documented change review sets the scope. It may call for only a partial retest.

Can a CMMS store equipment validation records?

Yes. A CMMS can hold calibration certificates, signed checklists, PM history, and repair records on each asset. Confirm with quality assurance how your site treats electronic records and signatures.

Validated equipment stays defensible when every record links to the asset it describes. Schedule a free demo to see how Cryotos keeps calibration, PM, checklist, and repair records in one audit-ready system.

Want to Try Cryotos CMMS Today?

Get Free Demo

Let AI Take Control of Your Maintenance

Cryotos AI predicts failures, automates work orders, and simplifies maintenance—before problems slow you down.

Try AI-Powered CMMS
🡢