Write and sign PPQ protocols and reports for each new product and change
- A sourced draft to start from
- Unmeetable criteria found before PPQ
- Client answers they can act on
A process validation protocol for PPQ in which each acceptance criterion carries its source, runs on the plant batches already made before anyone signs, and reaches the client's QA section by section.
See one PPQ protocol drafted, rehearsed and signed ↓A validation engineer builds the PPQ protocol by copying the last one written for a similar product, then editing it against a development report, a risk assessment, an impurity assessment, the client's specification, method reports and equipment records. Criteria end up reading meets specification or report result, the sampling plan belonged to another product, and the batch count is three because it has always been three.
Nobody learns that a criterion cannot be met until a PPQ batch fails it. The miss turns into a deviation inside validation, a send-back from the client's quality team or a question from the investigator, and at a CDMO it moves the client's filing. Review comments travel in marked-up copies that never land on the record.
Built forValidation leadsQA validation reviewersMSAT leadsQC lab heads
Each new PPQ protocol starts as a copy of the last, and the first test of its criteria against the process is the first PPQ batch.
Typed into the protocol by hand
Built-in controls
Criteria the process cannot meet surface on batches already made, and the client's QA and the investigator see the reason behind each limit.
One drug substance protocol, from the agents' first read of its sources to the client's answers and the report.
demoEvery name, batch number and result in the screens below is sample data.
The people who write, check and approve one PPQ protocol and its report.
Write and sign PPQ protocols and reports for each new product and change
Review protocols for the quality unit and countersign as second person
Own the ranges, the risk assessment and each process decision
Confirm methods and lab capacity before the first PPQ batch
The rest of the team's screens around one protocol.
demoSample data, from the working solution.
Eight agents draft and check; people decide and sign.
Reads the development report, risk and impurity assessments, specifications, instructions and equipment records, and notes each one's approval state.
Lays each critical parameter's normal and proven range under the day it applies, with the experiments behind each edge.
Places PPQ samples where development showed variability: cake positions, drum positions, after the scavenger.
Writes each criterion with its source and the sum behind it, and applies a learned rule once the plant QA head has signed it.
Justifies the number of PPQ batches from residual risk and capability bounds for each attribute.
Runs each criterion on the plant batches already made and labels the result as development data.
Argues as the inspecting investigator and as the client's QA, and turns on the work of the other agents too.
Builds the PPQ report from the protocol, fills it from executed batches and writes the hand-off to continued process verification.
A process validation protocol is the approved plan for process performance qualification: how each PPQ batch is run and sampled, the criteria it must meet, and how many batches are made. FDA's guidance and ICH Q7 expect the quality unit to approve it before execution.
No fixed number. ICH Q7 treats three consecutive successful batches as a guide, and EU GMP Annex 15 asks for a count justified by quality risk management. Here residual risk sits beside three published approaches and confidence bounds per attribute, for QA validation to review.
FDA's guidance lists it: manufacturing conditions, critical parameters with ranges, a sampling plan with its rationale, criteria for each significant step, statistics for variability within and between batches, deviation handling, and equipment, method and training status.
A batch with a criterion not met stays in. Leaving out any other plant batch needs a written reason and a QA signature from someone other than the requester; it clears the signatures and withdraws the client's copy.
The validation lead signs as author, QA validation countersigns, and the plant QA head approves with the client's QA under the quality agreement. Execution waits for that approval, blocked while a source is a draft or the batch instructions are unapproved.
It follows the protocol criterion by criterion, filled from executed batch records and lab results, with each deviation and its effect on the conclusion, and hands PPQ sample points to continued process verification. The author proposes the conclusion; QA validation, then the plant QA head, sign it.
Any batch-record question answered in seconds, cited to the page and step.
1-min demoValidation Document AutomationProtocols drafted in minutes, every value traced to its source.
1-min demoManufacturing Batch AnalyticsBatch analysis that took three months now takes hours, with the query behind every answer.
1-min demoSend a development report, its risk assessment and the plant batch records; we will rehearse the criteria they support.