VeriqaVeriqa
Book a demo
Customer story
VeriqaVeriqa
×Customer under NDA

The drift no one
was looking at.

How an established, multi-product API manufacturer surfaced a slow yield decline that was invisible in every product — and fixed its root cause before a single batch went out of spec.

Global API manufacturerMulti-product portfolioShared-equipment operations
0
products collapsed into a single cohort signal
7
batches released out of specification
0
shared reactor re-qualified at the root
The challenge

Every product looked fine on its own.

Five APIs ran on shared equipment. Across three of them — the ones sharing a single reactor line — a slow yield decline crept in, batch over batch. But each product's readings stayed comfortably within spec when reviewed alone.

Per-product review — the way every QA team works — showed nothing. The drift only existed in aggregate, where no one was looking.

Per-product drift · each reviewed aloneall in spec
Metformin HCl
API-01
Atorvastatin Ca
API-02
Losartan K
API-03
Amlodipine Bes.
API-04
Ranitidine HCl
API-05
overlay the cohort
“We’d reviewed each product for months and everything passed. Seeing them together changed the picture in an afternoon.”
QA Director · Multi-product API manufacturer
What Veriqa saw

Overlay the batches, and three drift as one.

Veriqa reasons across products, not just within them. Combine every batch into one view and three of the five — the reactor-line cohort — trace the same downward path toward the spec limit.

Sigma drift by batch · all five products, one viewdecline detected
+0.50−0.5−1.0−1.5−2.0−2.5Sigma drift from first batchlower spec limit · −2.0σ123456789Batch sequence
Metformin HCldriftingAtorvastatin CadriftingLosartan KdriftingAmlodipine Bes.stableRanitidine HClstable
Root cause traced to a shared reactor running below its qualified speed — the one variable common to the three drifting products.
The outcome

Fixed at the source, before any batch failed.

With the root cause named, the customer re-qualified the reactor and opened a CAPA — while every batch was still in spec. No deviation. No rejected product. No recall.

Cohort drift surfaced across 3 of 5 productsdetected
Traced to shared reactor below qualified speedroot cause
Reactor re-qualified to speccorrected
CAPA opened — 0 batches out of specclosed

What would Veriqa surface
in your data?

See the signals hiding across your products — on your own records, live.

Book a demo