Cleaning validation is the documented proof that a cleaning procedure actually works, that it removes soil, allergens, and microorganisms from the worst-case location to an acceptable level, repeatably. It is done up front and after any change, and it is different from the daily verification that confirms each individual clean was carried out.

The distinction is the whole game. Verification asks “did we clean today?” Validation asks the harder question: “can this procedure clean at all, even on its worst day?” This guide covers the evidence that proves clean, visual, ATP, protein, allergen, and micro, how to pick worst-case soils and locations, how many runs it takes, and where validation ends and verification begins. Cleaning validation applies to any cleaning method; for the specific case of closed liquid lines, see clean-in-place and for the underlying procedures, cleaning and sanitizing procedures.

What is the difference between validation and verification?

Validation and verification are not the same word for the same thing, and treating them as interchangeable is a classic audit finding. Validation is the one-time (and on-change) scientific proof that a procedure is capable of cleaning, you run it under worst-case conditions, several times, and test hard enough to trust the result. Verification is the routine, ongoing check that the validated procedure was performed correctly on a given day, a visual inspection, an ATP swab, a sign-off. You validate a cleaning procedure once and re-validate on change; you verify it every time you run it.

Validation happens once and on change; verification happens every time Validate the method once; verify it every clean VALIDATION worst case, multiple runs verification, every clean CHANGE → re-validate new product, equipment, chemical, or procedure sends you back to re-validate
Verification is the string of daily checks; validation is the anchor at the start that makes those checks mean something. A change in product, chemical, or equipment resets the anchor.

What evidence proves a surface is clean?

“Clean” is not one measurement, it is a ladder of increasingly specific evidence, and cleaning validation uses several rungs together because each catches what the others miss:

Validation typically stacks these, visual plus a quantitative organic measure plus the specific target (allergen or micro) that the clean has to remove. Which combination you need depends on what hazard the clean is controlling.

MethodDetectsSpeedBest for
VisualGross soilInstantFirst gate, every clean
ATP swabOrganic residue (general)SecondsVerification, trending
Protein swabProtein residueMinutesGeneral food-soil check
Allergen swabSpecific allergen proteinMinutes (lab for ELISA)Allergen changeover validation
Micro swabMicrobial loadHours to daysSanitation efficacy, EMP

Why validate against worst-case soils and locations?

If the procedure cleans the hardest soil in the hardest-to-reach spot, it will clean the easy ones, so you deliberately validate against the worst case, not a convenient one. Worst-case soil means the product that is hardest to remove: the stickiest, highest-fat, most heat-set, or most allergenic thing that runs on the line. Worst-case location means the hardest place to clean: dead legs, gasket seams, valve bodies, the underside of an agitator, a weld nobody sprays directly. These are where residue survives, so these are where you swab. Validating the flat, easy-to-reach panel and calling the line clean is how allergen recalls happen, the residue was hiding in the seam you did not test.

How do you run a cleaning validation?

A cleaning validation is a protocol, run and documented as a numbered sequence:

  1. Define the worst case. Identify the hardest soil to remove and the hardest locations to clean on the equipment, and state why they are worst case.
  2. Set the acceptance criteria. Decide the pass/fail limit for each test, visually clean, an ATP threshold, a negative allergen result at the kit's detection limit, a micro limit, before you run anything.
  3. Choose the test methods that match the hazard: allergen kits for an allergen clean, micro for sanitation efficacy, ATP and protein for general residue.
  4. Run the procedure exactly as written after deliberately soiling with the worst-case product, then sample the worst-case locations.
  5. Repeat enough times to trust it commonly three consecutive successful runs, so a single lucky result cannot pass the method. Consecutive passes show the clean is reproducible, not a fluke.
  6. Document the result and lock the procedure, including the parameters that made it pass, chemical, concentration, temperature, time, and method.
  7. Re-validate on change new product, new allergen, new equipment, new chemical, or a procedure change resets the requirement.

How do you map the sampling points?

A cleaning validation is only as honest as the spots you swab, so mapping sampling points is its own step. Walk the equipment and mark the places most likely to hold residue: the hard-to-reach and hard-to-clean geometry where soil survives when everything else is clean. The usual suspects are the same across most equipment:

These points do double duty: they are the worst-case locations you validate against, and the fixed spots you return to for routine verification swabs, so results trend over time on the same geometry. A validation that swabs only the flat, reachable panels proves nothing about the seam where the allergen actually hides.

Worst-case sampling points on a piece of equipment Swab where residue survives, not where it is easy process vessel dead leg valve body agitator underside tank-bottom outlet gasket seam the same points serve as worst-case validation sites and fixed routine-verification swabs
The sampling map is the validation. Return to the same worst-case points for routine swabs so results trend on identical geometry over time.

Where does daily verification take over?

Once a procedure is validated, you do not re-run the full study every night, that is what daily verification is for. The validated procedure becomes the standard, and each execution is confirmed with lighter, faster checks: visual inspection every time, ATP or allergen swabs on a defined frequency, and periodic micro tied to your monitoring plan. Verification watches for drift and for the day the crew was rushed; validation guarantees the method can win when it is performed right. The written program that binds the two together, procedures, frequencies, records, and corrective actions, is your sanitation SSOP set, audited under every HACCP-based system.

What acceptance criteria should you set?

A validation with no pre-set pass/fail line is just data collection, the acceptance criteria are what turn swab results into a decision, and they have to be defined before you run anything. Each test method gets its own criterion tied to the hazard the clean controls. Visual is binary: no visible soil, or it fails. ATP results are compared against a threshold in relative light units that your program establishes for a clean surface, used mainly for trending and verification rather than as the sole validation proof. Allergen swabs are judged against the kit's limit of detection, for an allergen changeover, the practical target is a negative result at that limit, because there is no safe declared level for an allergen the label omits. Microbiological criteria are set as a maximum count appropriate to the surface and product. Writing these limits down first prevents the most common validation trap: running the clean, getting an ambiguous number, and deciding after the fact that it “looks fine.” The criteria, the method, and the worst-case sites together are what make a validation defensible to an auditor.

The facts worth pinning

Cleaning validation is where several regulatory threads meet:

Validation lives or dies on its records, swab results, acceptance criteria, the three consecutive runs, the re-validation triggers. When those live in a folder on one QA laptop, an auditor asking “show me the validation for this allergen changeover” starts a scramble. Keeping validation studies, daily verification swabs, and the change history that should trigger re-validation in one connected system turns that scramble into a lookup, the operational layer Harmony builds on the floor (see how CLS did it), tying cleaning evidence to allergen management and GMP compliance in one place.