Commissioning and Qualification Planner
How a system is turned over, qualified and released for its intended use — and how much of that work can be leveraged from what the vendor already did. Qualification stages are named for what they demonstrate, never numbered as phases.
Every stage here states what it does not prove, because that is the sentence readers skip: installation qualification does not show the system functions, operational qualification does not show it works with product, and none of the four shows the system will stay qualified. Passing a gate is an internal decision by a named approver against pre-approved criteria — it authorises the next stage of work, never the marketing, distribution or clinical use of anything made with the system. The systems, components and acceptance criteria are a synthetic teaching model and do not substitute for a project-specific validation plan. To size one system’s scope from impact, severity and complexity, use the C&Q scope calculator.
The system can affect product quality, patient safety or data integrity. Documented qualification at every stage, with quality approval of protocols and reports.
Four named stages, effort by impact level, and vendor-documentation leverage.
Water for injection generation and loop
A generation skid and a hot distribution loop feeding production and laboratory points.
Water quality at the point of use, loop sanitisation effectiveness, and the ability to detect a return to poor quality before it reaches product.
Depth is a planning judgement driven by impact on product, patient and data — not a fixed schedule. Direct-impact systems earn documented testing at every stage.
Qualification stages
Four stages, each demonstrating something the previous one could not. Selecting a stage opens what it tests, what it accepts and what it leaves unproven.
Operational qualification
That the system operates as intended across its full operating range, including at its limits.
Functional testing, alarm and interlock testing, operating range challenge, failure and recovery testing, access control testing.
The system performs to specification at the range limits, alarms act at the set points, and recovery behaviour is as designed.
Operational qualification report, test records, alarm test evidence — validation platform
Engineering and Quality
That the system performs with real product, or that operators can run it.
Vendor functional testing is leverageable where it covers your configuration and your set points.
Leveraging vendor documentation
Vendor testing can be used as qualification evidence where it was performed against your requirement, under your assessment of the vendor. Where it was not, repeating it is cheaper than defending it.
| Vendor deliverable | Leverageable | Condition |
|---|---|---|
| Factory acceptance test records | Leverageable | Performed against your specification, with your witness for critical tests. |
| Site acceptance test records | Leverageable | Executed on your site, on the installed configuration, with deviations recorded. |
| Vendor calibration certificates | Leverageable | Traceable to a recognised standard and within date at installation. |
| Vendor functional test protocols | With conditions | Usable where they cover your configuration and set points; supplement where they do not. |
| Vendor validation package for software | With conditions | Covers the product as shipped, not your configuration, interfaces or data. |
| Vendor performance claims | Repeat it | Made under the vendor's conditions with the vendor's materials. Not your process. |
What qualification does not prove
The gap between a qualified system and a system in a qualified state is where most inspection findings live.
Qualification demonstrates fitness for intended use at a point in time. Compliance is a continuing state.
Every change, every drift and every deferred maintenance action erodes the qualified state.
Performance qualification uses trained people; it does not qualify everyone who will later use the system.
Qualification tests the system. Data integrity depends on access control, audit trail review and retention.
Product acceptability is a release decision made on batch evidence, not on the qualification file.
A qualification stage closes when the named approver accepts the evidence against pre-approved criteria. That is an internal decision. It authorises the next stage of work, not the marketing, distribution or clinical use of anything made with the system.
Illustrative planning aid for interface design. Stage content, acceptance criteria and leverage judgements are generic examples and do not substitute for a project-specific validation plan.