Research

Continued Process Verification In Pharma: What Literature Shows

CPV theory is well understood, but literature shows execution is uneven, here's what real-world data reveals about running Stage 3 well.

SS
By Simantini Singh Deo
Aug 28, 202611 min read
Share
Continued Process Verification In Pharma: What Literature Shows

Introduction

Ask any quality professional in pharma manufacturing about Continued Process Verification, and you'll probably get a textbook answer within seconds. Stage 3. State of control. Statistical trending. Everyone knows the theory.

But here's the more interesting question: what does the actual published literature, the warning letters, the technical reports, the case studies, say about how CPV really plays out on the shop floor? 

Not the polished version from a training slide, but the messy, real version where data doesn't behave, signals get ignored, and spreadsheets still rule the day in more facilities than anyone would like to admit.

That's what this article digs into. No jargon-heavy lecture, just a plain look at what researchers, regulators, and practitioners have actually observed.

First, A 60-Second Refresher

If you're new to the term, here's the short version. In 2011, the FDA published guidance that reorganized process validation into three stages instead of treating it as a one-time event:

  1. Stage 1 – Process Design: You build process understanding, usually through development studies and design of experiments.

  1. Stage 2 – Process Qualification: You prove, through qualification runs like Process Performance Qualification (PPQ), that the process can actually produce consistent commercial batches.

  1. Stage 3 – Continued Process Verification (CPV): You keep watching. Forever. Or at least for as long as the product is on the market.

This isn't a one-off exercise. It's an ongoing, statistically driven program to collect and trend process and product data during routine commercial manufacturing, and it's grounded in a specific regulatory requirement, 21 CFR 211.180(e), which calls for this kind of continuous monitoring to confirm a manufacturing process stays in a validated "state of control." A single successful PPQ batch doesn't count as CPV. CPV is the program that keeps running long after that milestone is behind you.

That's the theory. Now let's get into what the literature says actually happens.

What Does Literature Actually Show?

1) CPV Is Treated As A Checkbox Far More Often Than It Should Be

Despite being a formal regulatory expectation for well over a decade, plenty of companies still treat Stage 3 as an afterthought. Industry commentary has pointed out that CPV has historically been overlooked, with many companies unaware that a proper CPV program is actually a regulatory requirement rather than a nice-to-have. That's a striking finding for a stage of validation that has existed in guidance since 2011. It tells you the gap here isn't about knowledge of the rules; it's about prioritization and resourcing.

2) Data Problems, Not Conceptual Problems, Cause Most Of The Pain

You'd think the hard part of CPV would be understanding the statistics. In practice, the literature suggests the harder part is simply getting clean, usable data in the first place. One recurring theme is that manufacturing data is often positively autocorrelated, meaning consecutive results tend to resemble each other rather than being fully independent. 

Left unaddressed, this quietly breaks the assumptions behind standard control charts, because biopharmaceutical manufacturing data has a tendency to show sequential dependence, which means each quality attribute needs to be evaluated for the causes of this behavior and adjusted for with an appropriate statistical approach, such as charting residuals from a fitted time-series model rather than the raw values themselves.

On top of that, many facilities are still stuck with manual, paper-heavy record keeping. This isn't a minor inconvenience, either. Analysis of real-world CPV programs has found that companies relying on manual, non-standardized processes often end up with weaker regulatory standing, because paper-based batch records can't be synced with electronic systems, which makes data collation genuinely difficult and slows the entire CPV cycle down.

Manual, paper-heavy records aren't unique to CPV, they're a recurring quality bottleneck across pharma manufacturing.

Read: Pharmaceutical Quality Control: 2025 Playbook

3) Statistical Rigor Isn't Optional, And Regulators Are Enforcing That

This is one of the sharper findings in recent literature: choosing the wrong statistical tool for your data isn't just a technical misstep, it's an inspection finding waiting to happen. A documented example from 2024 makes this concrete. 

Regulators expect firms to justify their statistical choices with things like normality testing and capability analysis, and a firm in 2024 that applied standard control charts to non-normal dissolution data received a formal observation for lacking statistical rationale, which illustrates exactly why data-suitability checks can't be skipped. 

The takeaway here is simple but important: you can't just default to the same control chart for every quality attribute. The right tool depends on how the underlying data actually behaves.

4) There's Still No Industry-Wide Playbook For Reacting To A Signal

Detecting a signal in your CPV data (say, a control chart rule violation or a capability index that's drifting) is one thing. Knowing exactly what to do about it, consistently, across teams and sites, is another. Professional bodies have flagged this as an open gap. 

As one industry group observed, there is currently no regulatory guidance describing how the industry should respond when a CPV data signal appears, which is why efforts are underway to standardize the decision-making process around these signals. 

Until that standardization matures, a lot of "what do we do now" decisions still come down to local judgment calls, which naturally leads to inconsistency between companies, and sometimes between sites within the same company.

5) Statistical Tools Are Being Used, But Often As A Menu Rather Than A Strategy

The good news: nobody in the literature is arguing against statistics. Tools like control charts, capability indices (Cpk), and Six Sigma-style methods are widely referenced as the backbone of CPV. But there's a subtler point buried in the guidance: the choice of tool should be phase-appropriate and risk-based, not a one-size-fits-all default. 

Recommended practice is that a CPV statistical strategy should be built around the amount of data available and where the product sits in its lifecycle, ideally documented in an SOP with a tiered structure based on lot volume, so the level of statistical scrutiny scales sensibly rather than staying static forever.

6) Digital Tools & AI Are Entering The Conversation, But They're Not A Substitute For Good Data Hygiene

There's growing interest across the literature in using machine learning and advanced analytics to handle the sheer volume of CPV data more efficiently. That's a reasonable direction, given how much data a single commercial process generates over its lifetime. 

But the more groznded pieces of literature are careful to note that this is additive, not a replacement for the fundamentals: advances in statistical analysis, modelling, and machine learning are increasingly expected to be part of how the industry uses the process knowledge it builds up across the validation lifecycle. 

In other words, better tools help you see problems faster, but they don't fix a program that never had solid data collection or statistical rationale to begin with.

Digital and AI-driven quality systems are reshaping more than CPV, eQMS platforms are changing how compliance gets managed industry-wide.
→ Read:
Best Compliance Tools for Pharmaceutical Companies

The Pattern Behind All Of This

Infographic highlighting four recurring operational challenges behind Continued Process Verification programs.

If you zoom out across these findings, a pattern emerges. The conceptual side of CPV, the "why" and the "what," is well understood and rarely disputed. Nobody in the literature is questioning whether ongoing monitoring matters. The struggle is almost entirely in the "how":


  • How do you collect data consistently across manual and digital systems?

  • How do you choose a statistical method that actually fits your data's real behavior?

  • How do you make sure a detected signal leads to a timely, well-reasoned action instead of sitting in a report nobody reads?

  • How do you keep the program appropriately scaled instead of either under-monitoring or drowning teams in irrelevant alerts?


None of these are exotic problems. They're operational and cultural as much as they are statistical.

What A Well-Run CPV Program Tends To Have In Common?

Infographic outlining six traits of a well-run Continued Process Verification program in pharma.

Pulling from what tends to work well across the literature, a handful of traits show up again and again:


  • A written, risk-based statistical strategy that's tied to product lifecycle stage and lot volume, not a generic template copied across products.


  • Data suitability checks before tool selection — normality, autocorrelation, and distribution shape are examined before a control chart or capability index is applied.


  • Electronic, integrated data capture that avoids the delays and gaps that come with paper-based batch records.


  • A documented signal-response process so that when something looks off, the next step is clear rather than debated case by case.


  • Periodic review cycles where the CPV plan itself gets reassessed, not just the data flowing through it.


  • Cross-functional ownership, since CPV genuinely sits at the intersection of manufacturing, quality, and statistics, and tends to fail when it's treated as any one department's sole responsibility.


Why Does This Matters Beyond The Inspection Binder?

It's tempting to frame CPV purely as a compliance obligation, something you do because 21 CFR says so. But the literature makes a quieter, more practical case too: a mature CPV program genuinely reduces failure rates and lowers the cost of quality over time, because it catches drift before it becomes a deviation, and catches a deviation before it becomes a recall. Regulatory compliance and operational reliability aren't really two separate goals here. They're the same goal, viewed from two different desks.

In Conclusion 

The literature on Continued Process Verification doesn't describe a system that's broken. It describes a system that's conceptually mature but operationally uneven, strong on principle, inconsistent on execution. 

Companies that treat Stage 3 as seriously as they treat Stage 2 tend to show up in the case studies as the success stories. Companies that treat it as paperwork tend to show up in the warning letters.

The gap between those two outcomes isn't usually a knowledge gap. It's a discipline gap, and closing it is well within reach for any manufacturing team willing to put in the same rigor at Stage 3 that they already bring to Stage 1 and Stage 2.

FAQs

1) What Is Continued Process Verification (CPV) In Pharma?

Continued Process Verification is Stage 3 of the process validation lifecycle. It involves ongoing monitoring and statistical trending of manufacturing process and product data to confirm that the process remains in a validated state of control during routine commercial production.

2) What Are The Biggest Challenges With CPV In Real-World Pharma Manufacturing?

A major challenge is getting consistent, reliable, and usable data. Manual records, disconnected systems, inconsistent data formats, and poor data integration can make it difficult to collect and analyse CPV data efficiently.

3) Why Is Statistical Analysis Important In CPV?

Statistical analysis helps manufacturers identify process trends, variability, and potential signals before they become significant problems. However, the statistical method must suit the characteristics of the data. For example, normality and autocorrelation should be considered before applying standard control charts or capability analysis.

4) What Should A Company Do When A CPV Signal Is Detected?

A company should have a documented signal-response procedure that defines how signals are assessed, investigated, and escalated. The response should be based on the type and significance of the signal rather than treating every statistical variation as a manufacturing failure.

5) How Can Digital Tools Improve CPV Programs?

Digital systems can make data collection, integration, trending, and analysis faster and more consistent. Advanced analytics and AI can also help identify patterns in large datasets. However, digital tools cannot compensate for poor data quality, weak statistical strategies, or inadequate CPV processes.

TopicsResearch
SS
Written by
Simantini Singh Deo

Reporting on the science, business and regulation shaping the pharmaceutical industry.

Discussion

Loading discussion…

More from the Knowledge Hub

All articles →