Understands how commissioning and qualification build and maintain the physical state of control, and how risk focuses verification effort.

WHAT IT LOOKS LIKE · 5

• Determines verification scope from the risk the system carries to product and patient, rather than testing every system to the same depth.
• Writes acceptance criteria that can fail, with a stated basis, instead of criteria that restate the observed value.
• Uses vendor documentation where it is good enough and says why, rather than repeating the supplier test under a new cover page.
• Keeps the qualified state current by assessing changes against it, so qualification is a condition rather than an event.
• Records a deviation during qualification as a finding to resolve, not as a document to correct.

HOW IT IS DEMONSTRATED AT WORK

Look for a scope rationale that a reviewer can disagree with — one that names the system attributes affecting product quality and derives the testing from them. Then look at the executed protocols for at least one test that failed and was resolved. A qualification package with no failures either tested nothing that could fail or has been tidied, and both are visible to an inspector who reads the acceptance criteria closely.

WHERE IT IS COMMONLY WEAK

It degrades into document production. The recurring pattern is the criterion written after the result, phrased so that whatever the system did is what it was required to do — and the requalification that never happens because no one assessed a change against the qualified state. Risk-based scoping is also commonly misread as a licence to test less; the argument has to be recorded, or it is indistinguishable from having tested less for other reasons.

WHAT TEACHES IT · 2

• CAREER PATHWAYEngineering & CQV — career pathway
• LEARNING MODULEFacilities, manufacturing, labs & supply chains

WHAT EXERCISES IT · 0

Nothing exercises this yet. 10 scenarios are published and none is linked to this entry — we would rather say so than point you at the closest one.