GHTF process validation for process systems and equipment qualification

whiteboard, man, presentation, write, display, explain, strategy, diagram, flow chart, startup, plan, corporate, business, planning, organization, data, board, management, information, technology, internet, networking, network, whiteboard, whiteboard, whiteboard, explain, explain, explain, explain, explain, diagram, diagram, diagram, flow chart, flow chart, flow chart, startup

What GHTF process validation means today

GHTF process validation is a documented way to show that a manufacturing or service process can consistently produce output that meets defined requirements. For industrial equipment and regulated process systems, the practical point is clear: when final inspection cannot fully verify product quality without unacceptable risk, the process needs validation evidence, not only end-of-line testing. The Global Harmonization Task Force guidance GHTF/SG3/N99-10:2004, posted as a final Study Group 3 document by the International Medical Device Regulators Forum, remains a widely cited reference for medical device process validation because it explains the decision logic, protocol content, IQ, OQ, PQ, statistical thinking, and revalidation triggers.

The document does not replace applicable regulations or standards. It is best used as practical guidance for building a documented, risk-based case that equipment, utilities, operators, methods, materials, software parameters, and process controls work together under real manufacturing conditions.

board, chalk, team, business, job, work, success, goals, idea, think, together, training, vision, innovation, throughts, solution, creativity, brainstorming, blackboard, marketing, team, team, job, idea, innovation, brainstorming, brainstorming, brainstorming, brainstorming, brainstorming, blackboard

When a process should be validated instead of only verified

The first question is not how many batches to run. It is whether verification alone can adequately confirm the output. GHTF frames the decision around the process specification, the desired output, and the ability to verify the output by later monitoring or measurement. If the output can be fully verified and that verification is sufficient to control risk, routine verification may be appropriate. If defects may become apparent only after use, distribution, installation, or service delivery, validation carries much more weight.

Common examples include sealing, sterilization, welding, bonding, molding, coating, filling, cleaning, automated assembly, and software-controlled process steps where product quality depends on controlled conditions over time. Some outputs can be sampled or destructively tested, but destructive testing cannot be applied to every shipped unit. In those cases, the process itself has to be qualified and controlled.

Decision point What it means for a process system Likely evidence
Output cannot be fully verified Inspection would miss latent defects or require destructive testing Validation protocol, process capability, monitoring plan
Output can be verified but risk remains Testing is possible, but not enough to eliminate unacceptable risk Risk analysis, sampling rationale, strengthened process controls
Software affects the process Recipes, setpoints, alarms, interlocks, or data handling influence quality Software validation for intended use and change control records
Supplier qualification data exists Factory testing helps, but does not prove suitability for the user’s product Site IQ, user-specific OQ and PQ, approved deviations

The validation structure for process systems

GHTF describes process validation as a planned activity that normally includes installation qualification, operational qualification, and performance qualification. These phases should not become paperwork labels. Each one answers a different engineering question and should generate evidence that quality, engineering, production, and regulatory teams can review later.

Installation qualification

Installation qualification asks whether the equipment and supporting services have been installed correctly. For a process system, this may include utilities, wiring, compressed air, water quality, environmental requirements, safety features, calibration, preventive maintenance, cleaning requirements, supplier manuals, drawings, spare parts, and software documentation. Factory acceptance testing can support IQ, but it should not replace site-specific checks. The manufacturer remains responsible for deciding whether the installed equipment is suitable for the intended regulated process.

Operational qualification

Operational qualification challenges the process across defined operating ranges. This is where teams test setpoints, alarms, action levels, software parameters, raw material limits, operator procedures, material handling, and worst-case conditions. For example, a heat-sealing process may need evidence that time, temperature, pressure, warm-up behavior, and material variation remain controlled across the approved operating window. OQ is also where designed experiments, screening studies, control charts, or failure mode analysis can help identify the parameters that pass the most variation to the output.

Performance qualification

Performance qualification demonstrates that the process consistently produces acceptable output under normal operating conditions. PQ should use actual or representative product, trained operators, approved procedures, production-like conditions, and the process parameters established during OQ. The aim is not to repeat OQ at random. It is to show repeatability and longer-term stability in the way the process will actually run. PQ data should also support the routine monitoring plan, because validation only has value if the validated state can be maintained.

What a validation protocol should contain

A strong protocol turns engineering intent into auditable evidence. GHTF lists practical elements that should be addressed before execution, including identification of the process, the product or device families covered, measurable success criteria, validation duration, shifts, operators, equipment, utilities, operator qualifications, specifications, special upstream controls, monitored process parameters, monitored product characteristics, definitions of nonconformance, statistical methods, maintenance considerations, and revalidation criteria.

For process systems, the protocol should also define the boundaries of the validated process. It should state what is inside the validation scope and what depends on linked systems such as upstream material preparation, environmental control, clean utilities, inspection systems, data acquisition, labeling, or packaging. Unclear boundaries often make validation packages difficult to defend after a process change.

  • Acceptance criteria should be objective. Pass or fail decisions should be based on defined product requirements, process limits, standards, or justified engineering criteria.
  • Sample size should have a rationale. GHTF points to statistically valid techniques rather than a fixed universal number.
  • Deviations should be evaluated. A deviation does not automatically invalidate a run, but it must be assessed, justified, and approved.
  • Test methods should reflect use conditions. A convenient lab test may not be enough if it does not represent actual product use or process stress.
  • The final report should close the loop. It should summarize protocols, results, deviations, conclusions, and approval of the validation status.

Maintaining a validated state after startup

Validation does not end when the final report is signed. GHTF emphasizes trend monitoring to confirm that the process remains within established parameters. Negative quality trends should trigger investigation, corrective action when appropriate, and consideration of revalidation. This is especially important for processes affected by gradual drift, wear, contamination, humidity, water purity, raw material variation, operator technique, vibration, or environmental changes.

Change control is central to maintaining validation. Changes to procedures, equipment, tooling, personnel, software, raw materials, suppliers, facility location, product design, process application, or external requirements should be evaluated for their effect on validation status. Revalidation may be full or partial. A new equipment installation may require repeating IQ and selected PQ activities, while established OQ ranges may remain valid if the engineering rationale is documented. A raw material supplier change may require selected OQ or PQ work because the material-process interaction may not be fully understood.

How FDA QMSR and ISO 13485 affect the context

The regulatory context changed in the United States on February 2, 2026, when FDA’s Quality Management System Regulation became effective and incorporated ISO 13485:2016 by reference with FDA-specific provisions. FDA’s published QMSR materials state that the agency stopped using the old Quality System Inspection Technique on that date and moved to an updated medical device manufacturer inspection program. FDA also stated in the 2024 final rule that ISO 13485 requirements, taken as a whole, are substantially similar to the former Quality System Regulation and support global harmonization. See also: automation and controls.

This does not make the 2004 GHTF validation guidance obsolete from an engineering perspective. Instead, it changes how companies may map their evidence. ISO 13485:2016 includes requirements for validation of production and service processes where outputs cannot be verified by subsequent monitoring or measurement. It also expects defined criteria for review and approval, equipment and personnel qualification, methods and procedures, acceptance criteria, statistical techniques where appropriate, records, revalidation criteria, and approval of process changes. Those expectations align closely with the practical validation structure described by GHTF.

The practical lesson is that teams should not rely on legacy clause numbers alone. Validation packages should clearly connect process risk, defined requirements, objective evidence, monitoring, change control, and management approval. That makes the file easier to follow whether the reviewer is working from GHTF, ISO 13485, QMSR, or an internal quality system procedure.

Practical implications for equipment and process system projects

For equipment projects, validation planning should start before purchase specifications are frozen. A process system used in regulated production should be designed with validation evidence in mind. That affects sensor selection, calibration access, recipe security, audit trails, alarm handling, data retention, cleanability, environmental controls, material contact surfaces, utilities, maintenance access, and the ability to challenge operating ranges safely.

Procurement teams often ask suppliers for validation support, but responsibility cannot be outsourced completely. Supplier documents, factory acceptance tests, material certificates, software descriptions, and recommended maintenance procedures are useful inputs. The user still needs to show that the system works for the intended product, in the intended facility, with approved operators, materials, procedures, utilities, and controls.

A practical project sequence is to define critical quality attributes and critical process parameters early, translate them into user requirements, align factory tests with future IQ and OQ evidence, reserve time for site qualification, and design routine monitoring before PQ begins. This avoids a common problem: treating validation as a documentation exercise after engineering decisions have already limited the ability to collect meaningful evidence.

Frequently asked questions

Is GHTF process validation still relevant?

Yes, as a practical guidance reference. GHTF no longer functions as the main harmonization body, and many final GHTF documents are now hosted through IMDRF document pages. The process validation guidance remains useful because it explains core validation logic that still appears in modern quality systems: define the process, understand risk, challenge operating conditions, document evidence, and maintain control.

Does every manufacturing process require validation?

No. A process should be evaluated to determine whether verification is sufficient. If the output can be adequately verified by monitoring or measurement, and the residual risk is acceptable, full validation may not be necessary. If defects cannot be fully detected before use or distribution, validation is usually needed.

Can factory acceptance testing replace IQ, OQ, and PQ?

Factory acceptance testing can support validation, especially by confirming equipment functions before shipment. It normally cannot replace site-specific qualification because utilities, environment, operators, product materials, procedures, and routine operating conditions differ from the supplier’s facility.

What is the main difference between OQ and PQ?

OQ challenges the process across defined limits and worst-case conditions to establish a controlled operating window. PQ shows that the approved process can repeatedly produce acceptable output under normal production conditions using approved procedures and representative production settings.

When should revalidation be considered?

Revalidation should be considered after changes that may affect process quality or validation status, negative quality trends, product design changes that affect the process, transfer to another facility, new process applications, or changes in external requirements. The scope should be based on documented impact assessment rather than automatic repetition of the entire original validation.