[ HOW-TO GUIDE ]

How to Perform Cleaning Validation

Prove your cleaning procedure reliably removes residues below a health-based limit.

What a how-to is not

A how-to is SPEQ’s practitioner method, not a procedure. It does not replace your own SOP, it is not a validated approach, and the judgement calls in it belong to your quality unit.

Cleaning validation demonstrates that a cleaning procedure consistently reduces product, cleaning-agent, and microbial residues on shared equipment to a safe, calculated level. Modern practice sets limits from health-based exposure data (HBEL/PDE) rather than the old arbitrary criteria, then proves the cleaning meets them with a validated, sampled, analytical method.

THE STEPS
  1. 1

    Establish health-based residue limits

    Derive the acceptable carryover from a health-based exposure limit (HBEL/PDE) for the product, not a legacy 10-ppm or 1/1000-dose rule alone. The HBEL is the toxicological anchor; the maximum safe carryover (MACO) follows from it, batch size, and shared surface area.

  2. 2

    Identify worst case

    Validate the worst case — hardest-to-clean product, most potent/toxic compound, hardest-to-reach equipment geometry, and the longest dirty-hold time. If the worst case passes, the bracket it represents passes.

  3. 3

    Define sampling and a validated method

    Choose swab and/or rinse sampling with a justified recovery study, and use an analytical method validated to detect the residue at the limit. A limit you cannot reliably measure is not a limit.

  4. 4

    Write and execute the protocol

    Run the cleaning procedure and sample across the required number of runs, with pre-defined acceptance criteria for chemical, cleaning-agent, and microbial residues, plus visual inspection.

  5. 5

    Establish hold times and revalidation triggers

    Validate clean-hold and dirty-hold times, and define what triggers revalidation (new product, formulation or equipment change, procedure change).

  6. 6

    Report and move to monitoring

    Summarise the outcome and, where appropriate, transition to routine monitoring/verification so the validated state is maintained — cleaning validation is part of a lifecycle, not a one-off.

USE THE TEMPLATE
Cleaning Validation Protocol
Skip the blank page — start from SPEQ’s structured, regulator-aligned template for this procedure. Open the template →
COMMON PITFALLS
  • !Setting residue limits by arbitrary rules (10 ppm, 1/1000 dose) instead of a health-based exposure limit — the expectation has shifted to HBEL/PDE.
  • !No recovery study, so swab/rinse results cannot be trusted quantitatively.
  • !Validating a convenient case, not the worst case.
  • !Ignoring the analytical method’s limit of detection relative to the acceptance limit.

How to Perform Cleaning Validation: frequently asked questions

Common questions on perform cleaning validation.

What is HBEL and why did it replace the old limits?

A Health-Based Exposure Limit (expressed as a Permitted Daily Exposure, PDE) is a toxicologically derived safe daily amount of a residue. Regulators shifted to HBEL because arbitrary criteria like 10 ppm or 1/1000 of a dose are not tied to actual patient safety; HBEL sets a scientifically justified acceptable carryover.

How many runs does cleaning validation need?

The number is risk-based and justified, not fixed. Traditionally three consecutive successful runs were used; current lifecycle thinking sets the number by risk and supports it with ongoing monitoring rather than a fixed count alone.

What is a recovery study?

A recovery study spikes a known residue amount onto a representative surface and measures how much your sampling method recovers, giving a recovery factor. Without it, a swab or rinse result cannot be converted to an accurate surface residue level.

Do I need to validate hold times?

Yes. Clean-hold time (how long equipment stays acceptably clean before use) and dirty-hold time (how long soiled equipment can sit before cleaning still works) both affect residue and bioburden, so both are established and validated.