Life sciences
Continued process verification stops at data
Stage 3 verifies your process forever. The procedures, interpretations and answers built on top of it were approved once and never re-verified, and an AI assistant cannot tell the difference. What continued verification of knowledge would look like.
Cognatum Team · Oct 13, 2026 · 6 min read
A European GMP inspector said it plainly on an ECA course: your validation is only as good as your last batch.
Cognatum governs the entry
source · version · approver · permissions
That one line is the case for continued process verification. A process that passed qualification two years ago is not one you can vouch for today. So the industry stopped treating validation as an event. It treats it as a duty that never closes.
The knowledge around the process never got the same treatment.
What continued process verification commits you to
Continued process verification is stage three of the FDA's 2011 process validation framework. Stage one is process design. Stage two is process qualification. Stage three has one job: ongoing proof, during routine production, that the process stays in a state of control. EU GMP Annex 15 sets the same duty and calls it ongoing process verification.
In practice it means a plan, a data set and a cadence. ISPE says the agency now recommends stage 3 for all commercial processes, because it gives the best evidence that a process is running under a state of control. Control charts and Cpk analysis are the usual tools.
What an inspector expects to see
The inspector's expectations go further than charts. He expects an approved plan that names the process under review, the scope of verification and its frequency, set against process knowledge and performance. He expects anomalies to be caught during the commercial phase, not at the next revalidation. In the non-sterile space, ongoing verification replaces routine revalidation outright.
Adoption is not universal. A 2025 PDA Journal poster on implementing a CPV program notes that CPV has historically been overlooked, with many companies unaware that a program is a regulatory expectation at all.
The guidance already says knowledge has a lifecycle
ICH Q10 names knowledge management as one of two enablers of the pharmaceutical quality system, alongside quality risk management. Its definition is a systematic approach to four things: acquiring, analysing, storing and sharing information about products, processes and components.
Then it says when. Product and process knowledge should be managed from development through the commercial life of the product, up to and including product discontinuation. EU GMP chapter 1.4(ii) comes at it from the other side and asks that product and process knowledge be managed throughout all lifecycle stages.
An obligation with no mechanism
So the obligation to keep knowledge current is written down. What is not written down is a mechanism. The ICH Q9(R1) questions and answers are explicit that there is no regulatory requirement for a formal knowledge management system, only an expectation that knowledge is appropriately utilised.
Verified continuously, approved once
Hold the two side by side. A critical process parameter is trended, charted and reviewed on a defined frequency, forever. The procedure that tells an operator how to handle an excursion in that parameter was approved once, by someone who may have left, against a regulation that may have been amended since.
One of those two things has a verification cadence. The other has a revision history and a hope.
What happens when an assistant answers from it
That asymmetry was survivable while knowledge moved through people. A supervisor who knew the 2022 interpretation was stale would say so. An assistant will not. It retrieves the text it can reach, assembles a fluent answer and returns it with no approver, no effective date and no source version attached.
Retrieval is not verification. The first preregistered study of retrieval-based legal research tools tested products from LexisNexis and Thomson Reuters. Each one hallucinated between 17% and 33% of the time. Law has cleaner source material than most manufacturing document stores. Grounding an answer in a document says nothing about whether that document is still the right one.
The triggers are already on your list
The inspector's own list of anomalies that should prompt a closer look is instructive: changes in personnel, including management; maintenance, repairs and equipment changes; deviations in the manufacturing process; trends in analytical results; customer complaints; regulatory changes.
Every item on that list can invalidate an answer as surely as it can shift a process. A regulatory change makes a written interpretation wrong. A departure takes the context behind a procedure out of the building. Your CPV program routes those signals to the process. Nothing routes them to the knowledge base.
AI systems are getting a monitoring duty of their own
Article 72 of the EU AI Act makes providers of high-risk AI systems set up a post-market monitoring system. It has to collect, document and analyse performance data actively and systematically, across the whole life of the system. The plan behind it becomes part of the technical documentation. The Commission is due to publish a template by 2 September 2027.
Read closely, it is continued process verification for software. It also has the same boundary. It monitors the system, not the library the system answers from. Two assistants with identical monitored performance can give opposite answers because one reached a superseded SOP first.
What continued verification of knowledge would look like
It looks like the controls you already run on the process, pointed at the content instead.
Cognatum is a governed knowledge base built around that idea, as the Cognatum Knowledge Loop. Entries are compared against their sources continuously. When a source changes materially, every entry that depends on it is flagged, and a revision is routed for re-check. Until a person approves that revision, readers keep getting the last approved version, with its approval date in view. Cognatum notifies you when a source moves. It does not quietly rewrite the answer behind you.
Conflicts, retirement and the signed record
Where two approved entries disagree, both are held apart and routed to a named person rather than averaged or settled by recency. Where an entry no longer applies, it stops being served on every channel at once and its approval history is retained, so an answer given while it was live stays traceable. A named person signs off at the Approve gate, and that record of approver, date and source version travels with every answer.
None of that confers compliance with Annex 15, ICH Q10 or the EU AI Act. It produces the evidence trail your own reviewers and inspectors ask to see.
A test worth running this week
Pick a question your CPV program depends on: a sampling frequency, an action limit, an excursion response. Ask your sanctioned assistant. Then ask for the approved entry behind the answer, the person who approved it and the date.
If the first answer arrives in seconds and the second takes a week of emails, your process is under continued verification and your knowledge is not. Your company's knowledge isn't missing. It's unusable. Cognatum changes that.
See how the loop works at cognatum.ai/the-loop.
Sources
- Continued Process Verification in Stages 1 to 3 (ispe.org)
- Ongoing/Continued Process Verification, the perspective of a European GMP inspector (gmp-compliance.org)
- Implementation of a Continued Process Verification Program (journal.pda.org)
- EU GMP Annex 15, Qualification and Validation (health.ec.europa.eu)
- ICH Q10 Pharmaceutical Quality System (database.ich.org)
- Is Knowledge Management a Part of the Pharmaceutical Quality System? (gmp-compliance.org)
- EU AI Act Article 72, post-market monitoring by providers (ai-act-service-desk.ec.europa.eu)
- Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Tools (arxiv.org)
- The Cognatum Knowledge Loop (cognatum.ai)
Common questions
Questions this raises.
Is continued process verification a regulatory requirement?
It is stage 3 of the FDA's 2011 process validation framework, and EU GMP Annex 15 sets the same duty under the name ongoing process verification. ISPE notes the agency now recommends stage 3 for all commercial processes, because it gives the clearest evidence a process is running under a state of control. A 2025 PDA Journal poster reports that it has historically been overlooked, with many companies unaware a program was expected at all.
What is the difference between continued and ongoing process verification?
Wording rather than substance. The US FDA guidance says continued process verification; EU GMP Annex 15 says ongoing process verification. A European GMP inspector summarised it as different wording between the EU and the US with the same lifecycle approach. In the non-sterile space, ongoing verification replaces routine revalidation.
Does ICH Q10 require a formal knowledge management system?
No. ICH Q10 names knowledge management as an enabler of the pharmaceutical quality system alongside quality risk management, and expects product and process knowledge to be managed from development through commercial life up to product discontinuation. The ICH Q9(R1) questions and answers state plainly that there is no regulatory requirement for a formal knowledge management system, only an expectation that knowledge is appropriately used.
Does a CPV program cover the procedures and answers people work from?
Usually not. CPV scopes to process parameters and quality attributes, and its outputs are trends and control charts. The anomalies an inspector watches for, including personnel changes, equipment changes, deviations, analytical trends, complaints and regulatory changes, all age the written knowledge as well. Most programs have no route from those signals to the knowledge base.
Can software make our AI answers compliant?
No, and no vendor can. Software can tie each entry to an approved source, hold a human approval gate, notify you when a source changes, surface conflicts between entries rather than picking a winner, and keep a point-in-time record of what an answer was based on. The compliance obligation stays with you. What the tooling supplies is the evidence your reviewers and inspectors ask for.