CovaSyn
All Articles
Guide8 min readJuly 15, 2026

PDE vs TTC in Cleaning Validation: The Genotoxic Case

PDE vs TTC cleaning validation: when a health-based PDE applies, when ICH M7 forces the 1.5 ug/day TTC, and how to check the residue is even cleanable.

OK

Oliver Kraft

CovaSyn

PDE vs TTC in Cleaning Validation: The Genotoxic Case

You have a new molecule going onto shared equipment and two questions land on the same desk. How little residue is acceptable in the next product, and can your existing clean-in-place cycle actually get down to that number. If the compound is mutagenic, the answer to the first question stops being a toxicology exercise and becomes a default: 1.5 µg/day. This piece walks the decision, the arithmetic, and the cleanability check that most limit calculations skip.

PDE and TTC are not alternatives - they are two branches of one decision

A cleaning limit is derived from a health-based exposure limit (HBEL). Two routes exist and the compound decides which one you are on.

The PDE (permitted daily exposure)

is the compound-specific route, described in ICH Q3C(R8) Appendix 3 and in the EMA guideline on setting health-based exposure limits for shared facilities (EMA/CHMP/CVMP/SWP/169430/2012, in force since June 2015). You take the most relevant point of departure - usually a NOAEL or NOEL from a repeat-dose study, sometimes a clinical LOEL - and divide by a chain of adjustment factors:

PDE = (PoD x weight adjustment) / (F1 x F2 x F3 x F4 x F5 x alpha)

F1 covers interspecies extrapolation, F2 interindividual variability (usually 10), F3 study duration, F4 severe toxicity, F5 use of a LOEL instead of a NOAEL. The output is a defensible mg/day or µg/day figure that is specific to your molecule. It requires data.

The TTC (threshold of toxicological concern)

is the default when the compound is a mutagen and you do not have compound-specific carcinogenicity data. ICH M7(R2) sets an acceptable intake of 1.5 µg/day for a mutagenic impurity at lifetime exposure, corresponding to a theoretical excess cancer risk of 1 in 100,000. It is not a measured potency. It is the value the regulation assigns when the mechanism is presumed non-threshold and you cannot do better.

The practical consequence: a PDE for a moderately toxic API often lands in the hundreds of µg/day to low mg/day. A TTC-based limit is 1.5 µg/day. That is typically two to four orders of magnitude tighter, and it is the difference between a cleaning process that passes and one that does not.

PDE / HBELTTC
When it appliesCompound-specific tox data available; non-mutagenic or threshold mechanismMutagenic (ICH M7 Class 1, 2, 3) without compound-specific carcinogenicity data
BasisNOAEL/LOEL + adjustment factorsRegulatory default, 1 in 100,000 lifetime cancer risk
Typical magnitudemg/day to hundreds of µg/day1.5 µg/day (lifetime)
Governing textICH Q3C(R8) App. 3; EMA/CHMP/CVMP/SWP/169430/2012ICH M7(R2)
What decides itToxicology packageMutagenicity call (structure + QSAR)

So the first question in a cleaning validation is not "what is the PDE". It is: is this compound mutagenic? Everything downstream hangs on that call.

Worked example: chlorambucil, from structure to a cleaning route

Chlorambucil (SMILES OC(=O)CCCc1ccc(N(CCCl)CCCl)cc1, InChIKey JCKYGMPEJWAADB-UHFFFAOYSA-N) is an alkylating cytotoxic - a realistic HPAPI to put on shared equipment.

Step 1 - the mutagenicity call (CovaTox)

covatox_ich_m7 returns ICH M7 Class 2 for chlorambucil, with a statistical model score of 0.6348. covatox_structural_alerts fires two mutagenicity alerts on the same structure:

  • nitrogen_mustard - HIGH severity, mechanism aziridinium ion formation leading to DNA cross-linking
  • alkyl_halide - SN2 alkylation of DNA

Both the expert-rule and the statistical arm of the assessment are positive, which is exactly the ICH M7 two-complementary-methodologies pattern. There is no negative-prediction conflict to resolve here.

Be precise about what happened next.

The tool returned "Class 2". The 1.5 µg/day is not a field in the output - it is the regulatory consequence of the Class 2 call under ICH M7. The software classifies; the guideline assigns the number. Anyone who tells you a QSAR tool "predicted a TTC of 1.5 µg/day" has misread their own output.

Step 2 - what that does to the carryover limit

With an acceptable intake of 1.5 µg/day, the maximum allowable carryover into the next product follows the standard form:

MACO = AI (µg/day) x minimum batch size of next product / maximum daily dose of next product

Take illustrative downstream figures - these are assumptions for the arithmetic, not tool output or measurements: next product batch size 200 kg, maximum daily dose 400 mg. Then

MACO = 1.5 µg/day x 200,000,000 mg / 400 mg/day = 750,000 µg = 0.75 g across the whole 200 kg batch.

Spread over a shared train with, say, 20 m² of product-contact surface, that is a surface limit in the low tens of µg per 25 cm² swab - before you apply your recovery factor and analytical limit of quantitation. This is the point where the analytical method, not the toxicology, usually becomes the constraint.

Step 3 - can you actually remove it? (CovaSolv)

A limit you cannot reach is not a control strategy. covasolve_predict gives chlorambucil solubility across candidate cleaning agents:

Cleaning agentPredicted solubilityNote
Water, neutral0.088 mg/mLapplicability domain OK, confidence 0.98-0.99, 95% CI reported
Ethanol127 mg/mLfreely soluble
Acetone106 mg/mLfreely soluble

A neutral water flush is roughly three orders of magnitude weaker as a solvent than ethanol here. For a residue you are allowed to leave behind only in micrograms, that matters.

Bar chart of predicted chlorambucil solubility for cleaning validation: 127 mg/mL in ethanol and 106 mg/mL in acetone against only 0.088 mg/mL in neutral water.
Ethanol and acetone dissolve chlorambucil about three orders of magnitude better than neutral water. For a residue allowed only in micrograms, a plain water rinse will not reach the limit. Predictions, not measurements: good enough to rank cleaning agents, not a substitute for a solubility measurement in your own agent at your own temperature. Source: Computed with covasolve_predict for chlorambucil (SMILES OC(=O)CCCc1ccc(N(CCCl)CCCl)cc1). CovaSolv's deployed ensemble reports R2 0.91 and RMSE 0.69 log on its held-out aqueous benchmark, about 76% of predictions within 0.5 log.

There is a cheaper option than a solvent rinse. Chlorambucil is a carboxylic acid. covasolve_ph_predict and covasolve_ph_curve return a pKa of 5.8 and a +5.20 log-unit solubility correction at pH 11 - roughly a 10^5 gain over the neutral case. An alkaline CIP cycle (dilute NaOH) ionizes the acid and does the work. The SOP writes itself: alkaline wash or organic solvent, not a plain water rinse.

Caveat, stated plainly: the pH-solubility figure is a Henderson-Hasselbalch estimate and is reported as a relative log-unit gain, not an absolute mg/mL. H-H extrapolation to pH 11 overshoots the true intrinsic ceiling badly. Use it to rank cleaning agents and to justify an alkaline cycle. Do not put the extrapolated absolute number in a protocol.

What this does not tell you

  • It does not produce a filed limit. The Class 2 call is a triage output. A regulatory submission needs the ICH M7 two-methodology assessment documented, with expert review of any conflicting or out-of-domain prediction.
  • QSAR accuracy has a ceiling. CovaTox's Ames endpoint scores balanced accuracy 0.736 on a scaffold holdout of n = 1089 (0.848 on a random split). Scaffold holdout is the honest generalization number and it is the one to quote. Some endpoints in the same panel are worse and some test sets are small - covatox_assess_critical_safety explicitly flags several endpoints as out-of-domain for this molecule. Read the flags.
  • Solubility predictions are predictions. CovaSolv's deployed ensemble reports R² 0.91 / RMSE 0.69 log on its held-out aqueous benchmark, about 76% of predictions within 0.5 log. That is good enough to rank water against ethanol against an alkaline cycle. It is not a substitute for a solubility measurement in your actual cleaning agent at your actual temperature.
  • Nothing here replaces the swab study. Recovery factors, surface material effects, dried-residue kinetics, hold times, worst-case location selection - all of that is wet-lab work. In-silico gets you a defensible starting hypothesis and stops you running a cleaning study that was never going to work.
  • The TTC has qualifiers. 1.5 µg/day is the lifetime figure. Less-than-lifetime (LTL) exposure allows higher intakes; cohort-of-concern compounds (aflatoxin-like, N-nitroso, azoxy) are excluded from the generic TTC entirely and need compound-specific limits.

Frequently asked questions

When do you use a PDE and when do you use the TTC in cleaning validation?

Use a compound-specific PDE when adequate toxicology data exists and the mechanism is threshold-based; it follows ICH Q3C(R8) Appendix 3 and the EMA health-based exposure limit guideline. Use the TTC of 1.5 µg/day when the compound is mutagenic under ICH M7 and you have no compound-specific carcinogenicity data. The mutagenicity call decides the branch, so make that call first.

Is 1.5 µg/day a measured potency value?

No. It is a regulatory default. ICH M7 assigns an acceptable intake of 1.5 µg/day to a mutagenic impurity at lifetime exposure, corresponding to a theoretical excess cancer risk of 1 in 100,000. Software that classifies a compound as ICH M7 Class 2 has not predicted the 1.5 µg/day figure - the guideline attaches that number to the classification.

What does an ICH M7 Class 2 result mean for a cleaning limit?

Class 2 means the compound has a positive mutagenicity signal with no adequate carcinogenicity data, so it is treated as a mutagenic carcinogen by default. The acceptable intake falls to the TTC of 1.5 µg/day rather than a compound-specific PDE. That typically tightens the maximum allowable carryover by two to four orders of magnitude and often makes the analytical limit of quantitation the binding constraint.

How do you know whether a residue is even cleanable?

Compare its solubility across the cleaning agents you actually run. For chlorambucil, covasolve_predict gives 0.088 mg/mL in neutral water against 127 mg/mL in ethanol and 106 mg/mL in acetone, so a water flush is the wrong tool. Because it is an acid with pKa 5.8, covasolve_ph_predict shows a 5.2 log-unit gain at pH 11, pointing at an alkaline CIP cycle.

Can in-silico predictions replace a swab recovery study?

No. They set the hypothesis and the sequence. Structure-based triage tells you which limit branch applies and which cleaning agent is worth testing, before you commit equipment time. Recovery factors, coupon studies on real contact materials, dried-residue behaviour and worst-case location selection remain wet-lab work, and the validated protocol is what a regulator reviews.

What accuracy should I expect from a mutagenicity QSAR?

Quote the scaffold-holdout number, not the random-split one. CovaTox reports balanced accuracy 0.736 for Ames on a scaffold holdout of 1089 test compounds, versus 0.848 on a random split; the gap is what happens when the test molecules have unseen cores. Always check the applicability-domain flag - an out-of-domain prediction is a prompt for expert review, not a result.

Related reading

Both tools used here are on the CovaSyn free tier if you want to run your own structure through the same two steps before the next cleaning protocol goes out. - Antisolvent Crystallization Design: Pick the Route First

Tools for this topic

Use these in your AI agent right away.

  • CovatoxICH M7, Tox21, CYP450, structural alerts, ADMET triage.
  • CovasolveSolubility, pH, crystallization, antisolvent.
PDE vs TTC in Cleaning Validation: The Genotoxic Case | CovaSyn