Continued process verification (Stage 3)
Continued process verification, often called Stage 3 in the FDA lifecycle model, uses routine production data to check whether a process remains in a state of control. For dietary supplements, the approach should be proportionate to product and process risk and must not be confused with a blanket regulatory validation claim.

On this page · 16 sections
- 1What continued process verification does
- 2Create a focused CPV plan
- 3Protect data context and comparability
- 4Read variation without overreacting
- 5Act and learn
- 6Inside V5: maintaining production context
- 7Explain it for your operation
- 8Choose variables from process understanding
- 9Use suitable statistical methods
- 10Separate specification from process control
- 11Review CPV as a lifecycle activity
- 12A practical CPV example
- 13A proportionate implementation plan
- 14Internal review questions
- 15Records and evidence to retain
- 16Questions to ask when evaluating software
How does Continued process verification (Stage 3) apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What continued process verification does
CPV reviews selected process inputs, operating parameters, in-process measures, quality attributes and outcomes over time. It asks whether expected performance is being maintained and whether emerging variation requires investigation or change.
FDA's three-stage process-validation lifecycle guidance is directed to drugs and biological products. Supplement firms can use the lifecycle concepts as a quality approach, but should not imply that Part 111 imposes the same named framework in every case.
02Create a focused CPV plan
Define product and process scope, rationale for each variable, data source, frequency, statistical method, alert or action approach, responsibilities and review route. Include material, supplier, equipment and environmental factors where they can influence the outcome.
Select measures linked to process understanding rather than everything that is easy to export. Too many weak signals obscure the few variables that matter.
03Protect data context and comparability
Capture batch, recipe version, equipment, material lots, operator context, sample method, units and any deviation affecting interpretation. Confirm that methods and definitions stay comparable before combining periods.
Missing or excluded data should be visible. Investigate data-quality problems rather than silently smoothing them away.
04Read variation without overreacting
Use run charts or suitable statistical methods to distinguish common variation from meaningful signals. Specification limits describe product acceptance; process-control limits, when justified, answer a different question about process behaviour.
A trend signal prompts review, not automatic batch rejection or release. Evaluate impact through the approved quality process and by authorised people.
05Act and learn
Define how alerts are reviewed, when a deviation or CAPA is opened, when monitoring increases and when a process or specification change enters change control. Document both action and a justified decision not to act.
Periodically reassess the plan as knowledge, formulation, suppliers, equipment and scale change.
06Inside V5: maintaining production context
V5 can keep electronic production records, material lots, equipment, quality records and audit history connected. Reports and analytics can help authorised teams review performance in context.
V5 does not establish statistical limits, declare a state of control, or release product autonomously. The site defines the plan and people interpret signals.
07Explain it for your operation
Start with one process and three to five measures supported by a clear causal rationale. Reconcile historical data against original records, plot it with batch and change context, and test the response route using a known past signal.
Expand only when the first review reliably produces understandable decisions and retained evidence.
08Choose variables from process understanding
Connect each monitored input, parameter or output to a plausible effect on quality. Include material and equipment context where they explain variation. Remove metrics that never influence a decision.
Document ownership, units, sampling and calculation so the same measure means the same thing across batches and sites.
09Use suitable statistical methods
Run charts may be sufficient for some measures; control charts need rational subgrouping, stable definitions and enough data. Capability indices are meaningful only when their assumptions and specification relationship are understood.
Do not recalculate limits simply to absorb an unexplained signal. Investigate special causes and record justified changes to the monitoring method.
10Separate specification from process control
A result can remain within specification while a process trend signals loss of control. Conversely, a control-chart signal does not automatically mean product fails specification.
Define separate escalation and product-impact review. Preserve the authorised disposition decision and its evidence.
11Review CPV as a lifecycle activity
Set routine operational review and periodic cross-functional review. Include deviations, maintenance, supplier and change-control information that helps explain shifts.
Update the plan after meaningful learning and assess whether prior conclusions remain valid. Keep old plan versions and explain changes.
12A practical CPV example
For a blending and filling process, a team may monitor material potency context, blend time, selected uniformity evidence, fill-weight behaviour and relevant finished results. Each variable has a rationale, source, unit and review method. Batch, equipment and supplier changes remain visible.
A sustained shift that remains within specification enters the defined review route. Investigators consider method, material, equipment and process changes; authorised personnel assess product impact. The chart supports the decision but does not make it.
13A proportionate implementation plan
- Confirm the applicable requirement, product scope and decision owner.
- Map the current method and the records already available.
- Define terms, responsibilities, evidence and exception handling in the approved procedure.
- Pilot the method on one representative process and challenge a difficult exception.
- Train affected roles, approve the change and monitor whether the method works as intended.
- Review after significant change and retain a transparent history of decisions.
Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.
14Internal review questions
- Can a reviewer identify the source, owner, method and current approved version?
- Do summaries reconcile to original records and include unfavourable or missing evidence?
- Are exceptions visible, assessed and linked to the affected material, product or process?
- Are actions assigned, overdue items escalated and effectiveness reviewed?
- Have changes in product, supplier, equipment, method or regulation triggered reassessment?
- Does the record distinguish system support from the decision an authorised person made?
15Records and evidence to retain
- Approved scope, definitions and responsibilities for continued process verification stage 3 supplement.
- Source records and identifiers that let a reviewer reconstruct the work.
- Methods, assumptions, calculations, exclusions and any data-quality limitations.
- Exceptions, investigations, decisions, approvals and resulting actions.
- Version history showing when the approach changed and why.
Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.
16Questions to ask when evaluating software
- Can users trace every summary value back to its source record and version?
- How are roles, permissions, signatures and corrections recorded?
- Can the workflow reflect our approved procedure without inventing a universal rule?
- What happens during an outage, and how are later entries distinguished?
- Can we test the highest-risk exception with realistic data before committing?
- Which decisions remain explicitly assigned to an authorised person?
Frequently asked questions
Q.What is continued process verification stage 3 supplement?+
Continued process verification, often called Stage 3 in the FDA lifecycle model, uses routine production data to check whether a process remains in a state of control. For dietary supplements, the approach should be proportionate to product and process risk and must not be confused with a blanket regulatory validation claim.
Q.Is continued process verification stage 3 supplement required in every operation?+
The applicable product rules, market, risk and approved quality system determine what is required. The method should be justified for the operation rather than copied without context.
Q.Can software make the final quality decision?+
No. Software can organise records, calculations and workflow, but authorised people remain responsible for scientific, quality and disposition decisions.
Q.How should a site start?+
Choose one bounded process, define the decision and evidence, test the method with real records, correct gaps, then expand under change control.
Q.What evidence should be retained?+
Keep the approved method, source records, assumptions, exceptions, review, decision, approval and any resulting action with enough context to reconstruct the work.
Q.How often should it be reviewed?+
Use the applicable requirement and a risk-based cycle, with earlier review after significant change, failure, complaint, deviation or new knowledge.
Primary sources
Want to see how Continued process verification (Stage 3) could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
