Cleaning Validation

Proof your cleaning validation holds up — reviewed, or built.

Two ways in. Have a cleaning validation? Get an independent read on whether it holds up against your own data, at the depth you choose. Need one? Send your equipment and products and we build the validation from scratch.

The trendA recurring inspection finding

Cleaning and cross-contamination control turns up on FDA 483s year after year — and the citation is rarely a missing protocol. It’s the validation that was never tested against its own residue, recovery, and limit data.

FDA GMP inspection observations

What this is

Whether your cleaning actually works — against the rules, and against your own data.

Cleaning validation is the proof that residue from the last product won’t end up in the next one. We judge the validation you hold, or build the one you are missing — against the GMP rules and against what your own residue, recovery, and monitoring records actually show, not just whether the protocol reads correctly.

Cleaning Validation Defensibility Review

An independent regulatory opinion on the cleaning validation you already have — does it hold up. Start at the base; add the records that take the read past the paper.

What this covers

Cleaning validation — residue / MACO limits
Cross-contamination & changeover control
Acceptance-limit defensibility — HBEL / MACO
Swab / rinse recovery validation
Routine cleaning verification & monitoring

What you get back

A signed written opinion you can file in your quality system, hand to an auditor or a customer, or use to fix a gap before an inspection instead of after. Each part read against the rule and against your records, with a clear conclusion and what it would take to address it. Not a template pack or a checklist app that stores the record but never tells you it’s wrong — an independent verdict on your specific data, from someone who didn’t run the validation and so can grade it. It catches the cleaning file that reads clean on paper and fails when an investigator follows the numbers.

What a review catches

A worked cleaning validation — the kind of catch that lives in the data, not the paper.

A constructed example. The protocol read fine; the file was marked validated. Here is what the deeper read surfaced once the executed data, the limit, and the monitoring were actually opened — each catch tied to the real rule. The blander the record, the worse the catch.

Specimen drawn from the PROTOCOL™ Sport case — a potent blend on shared equipment

01The cleaning was “validated” — by looking at it.

Reads asA completed cleaning validation, marked Validated, visual inspection passed on every run.

Hiding in itVisual inspection only — no swab, no rinsate, no MACO. Carryover of a potent active to the next “clean” product was never actually measured.

Why it mattersVisual-clean can’t see a potent residue at the level that matters. The file proves the equipment looks clean, not that it is.

21 CFR 111.27(d)

02The residue test measured the wrong thing.

Reads asA residue check with a passing result against a chosen marker compound.

Hiding in itThe marker is the one that’s easiest to detect — not the hardest-to-clean, worst-case residue. The compound that actually matters isn’t in the test at all.

Why it mattersA passing number on the wrong analyte tells you nothing about the residue that matters. The validation passes while the real risk goes unmeasured.

Cross-contamination control · worst-case basis

03The limit was never tied to a safe dose.

Reads asAn acceptance limit the report comfortably meets.

Hiding in itIt’s a generic, visual-clean default — no health-based derivation (HBEL/PDE to MACO), no toxicological basis for the number.

Why it mattersIf the limit isn’t derived from how much residue is actually safe in the next product, “within limit” is a number with nothing under it.

HBEL / MACO defensibility

!Validated once, off a single run.

Reads asA validation report, signed and filed.

Hiding in itA single run, no worst-case product justification, and no dirty/clean hold times — and no routine monitoring to show it still holds.

Why it mattersOne good clean on one day is not a validated state. There’s no proof it holds across products, soils, or the time equipment sits dirty before it’s cleaned.

21 CFR 111.27

Build your review

Standardthe baseline the field expects

Included

Cleaning validation, on its face$1,800

Judges the protocol and report against the GMP rules as written — scope, equipment and product coverage, the limit and the sampling plan — whether it reads correctly and is complete and defensible on its face.

You send: Cleaning Validation Protocol/ReportThe written cleaning validation for the equipment train — the protocol that defines how cleaning is proven and the report of the result.Also called: cleaning validation protocol, cleaning validation report, CV protocol/reportFull details on the Records page

Exceeding Standardstested against your own data

Optional add-on — tap to add

The executed data actually prove it+ $1,500

A protocol written correctly is not proof the cleaning works. We read the executed residue, recovery, and visual results across the required runs and check whether they actually carry the conclusion — the gap that turns a “validated” claim into a finding when someone reads the numbers.

You also send: Cleaning Validation Executed Study DataThe actual results from running the validation — swab and rinse residue readings, recovery, and visual checks across the required runs.Also called: executed cleaning data, residue & recovery results, validation run dataFull details on the Records page

Optional add-on — tap to add

The limit is health-based and defensible+ $2,400

A pass only means something if the limit it passed against is defensible. We check the health-based derivation (HBEL/PDE), the worst-case product and MACO, and swab/rinse recovery — so “within limit” means the equipment is actually safe for the next product, not just under an arbitrary bar.

You also send: HBEL / MACO Limit-Justification RecordThe derivation behind your residue acceptance limit — the health-based exposure limit (HBEL/PDE) and the maximum allowable carryover (MACO) it produces.Also called: MACO calculation, HBEL/PDE assessment, acceptance-limit justificationFull details on the Records page

Optional add-on — tap to add

It still holds in routine production+ $1,300

Validated once is not validated forever. We read your routine cleaning-verification and monitoring records and check whether the validated state is holding over time — the drift that passes the initial runs and fails six months later.

You also send: Routine Cleaning Verification / Monitoring RecordsThe ongoing records that show the validated cleaning still holds in day-to-day production — routine verification and monitoring results over time.Also called: cleaning verification records, ongoing monitoring data, periodic cleaning checksFull details on the Records page

If your validation can’t be given a clean opinion on what you send, you get a straight report on what’s missing instead, at the same fee.

Your review$1,800base only

Cleaning Validation Development

No validated cleaning program yet? Send your equipment and products and we build the validation from scratch — one flat fee, built to the standard an auditor applies.

What this covers

Cleaning validation — residue / MACO limits
Cross-contamination & changeover control
Acceptance-limit defensibility — HBEL / MACO
Swab / rinse recovery validation
Routine cleaning verification & monitoring

What you get back

The built cleaning validation package, ready to execute and file — worst-case product selection, health-based residue limits (HBEL/PDE, MACO), a swab/rinse sampling plan with recovery, and the protocol and acceptance criteria, grounded in what you actually run, not a generic template with your name dropped in. And where your equipment or products can’t be cleaned to a defensible limit as they stand, you get the honest path to fix that at the same price — never a protocol that hides it.

What you send

The specifics we build from: your equipment and process — the trains and how product runs through them; your product matrix and changeover — what you run on shared equipment and what follows what; and what you clean with — the cleaning agents and current procedure.

What this builds

The same operation, with no validated cleaning — the calls we made, and why.

Nothing to catch on a build: you send the equipment and the product matrix, and the reasoning is the work. Here is the same constructed operation — a potent blend sharing a blender with the rest of the line — brought to us to validate from scratch, and the call we made at each step.

You send the equipment, the product matrix, and the cleaning agents — the starting context lives on the PROTOCOL™ Sport case

01The worst case was the hardest-to-clean product, not the easiest to test.

From the matrix we picked the worst-case product on solubility and potency — the residue that’s hardest to remove and most consequential if it carries — and validated against that, not the marker that happens to be easiest to detect.

Worst-case selection

02The limit came from a safe dose, not a visual pass.

We derived the residue limit from the worst-case active’s health-based exposure (HBEL/PDE to MACO), so “within limit” means safe in the next product — not just “looks clean.”

HBEL / PDE to MACO

03The swab result was made to mean something — with a recovery study.

We built the swab/rinse recovery into the protocol, so the number read off the coupon actually reflects what’s on the equipment instead of whatever the swab happened to lift.

Recovery validation

!And the honest fork, up front: some things no cleaning can cure.

On this matrix a potent compound shares a blender with everything else. Past a point that isn’t a cleaning problem, it’s a separation problem. Where the equipment can’t be cleaned to a defensible limit as it stands, we said so and gave the path — dedicated equipment, or a sequence control that actually controls — not a protocol that validates around it.

Dedicated-equipment / segregation basis

Built cleaning validation$5,000fixed price

Common questions

Straight answers.

Isn’t a template pack cheaper?

Much. And it leaves you to derive the limit, pick the worst case, and defend the recovery yourself — which is exactly the part that turns into a finding. A template stores the record; it never tells you the number is wrong. You’re buying the judgment a blank form can’t give you.

Do you run the lab work or swab my equipment?

No. The review judges your validation; the build writes it. Neither runs the residue testing or sets foot on your floor — that keeps the opinion independent of anyone selling you the testing. You execute the protocol in whatever lab you choose.

What if my equipment can’t be cleaned to a defensible limit?

You get told that plainly, at the same fee. Sometimes the answer isn’t a better cleaning protocol — it’s dedicated equipment or real segregation. We lay out the path and you decide; we don’t write a protocol that validates around a problem that cleaning can’t fix.

Is this the same as a gap assessment?

No. A broad gap assessment treats cleaning validation as one line in a long checklist. This is a focused, independent verdict on the validation itself — read against your own executed data, with a conclusion you can file.

Do you execute the protocol on our floor?

No — the build delivers the validation package ready to execute and file. Running the studies, sampling, and the lab analysis are yours to carry out, in whatever lab you use.

Is this legal advice?

No — it is an independent regulatory opinion or a built work product, not legal counsel, and it creates no attorney-client relationship. If your question is whether the cleaning validation holds up against the rule and your data, that is ours.

Where to go from here.

Regulatory work product, not legal advice. A deliverable is prepared from the records you submit and is not legal counsel, not a guarantee of any regulatory or customer outcome, and forms no attorney-client relationship. It is a document review or build — not a GMP audit, not laboratory testing or on-site execution, and not the disposition or release decision. Where the records provided can’t support a defensible result, we deliver a findings report on what’s missing instead. PROTOCOL™ Sport is a constructed teaching case; no real company or product is depicted.