40–60%
reduction in documentation effort
15–25%
faster validation cycle time
50%
less audit preparation time
Authoring aid, not an author. The quality team remains accountable for every claim the dossier makes.
CQA/CPP Matrix — Process Validation
SAGA-DEMO-0419 · Rev 03 · Approved 2026-04-11
Process validation reads as a matrix, not a chain. A Critical Quality Attribute of the final product — potency, impurity, particle size, moisture — couples to one or more Critical Process Parameters on the line: mixing speed, reaction temperature, drying time, inlet-air humidity. The validation question is which couplings are load-bearing, where the acceptable envelope lies, and how you know the envelope still holds three batches or three years from now.
SAGA carries the CQA/CPP matrix as a first-class artefact. Each CQA row references the CPPs that drive it; each CPP row records the design-of-experiments run that established its tolerance; each batch record rolls up against the same matrix so continued process verification is a query against your own evidence, not a rebuild.
The shift from traditional three-batch qualification to continued process verification is the central modernisation. SAGA holds both reads in one frame — the initial PPQ evidence that established the envelope, and the ongoing statistical signal that confirms the process still lives inside it.
The two reads are not alternatives — they are the two halves of a lifecycle. A qualification that never revisits its envelope drifts into a narrative; a continued-verification programme without a qualification baseline has nothing to compare against.
One-time qualification
Three Process Performance Qualification batches establish the envelope: each CQA measured inside specification, each CPP held inside its design-of-experiments range, deviations captured against the protocol. The dossier closes once the three-batch evidence aligns with the URS.
This is the audit-visible surface: a signed PPQ report, a CQA/CPP matrix with its couplings justified, a DoE record that backs every tolerance. The qualification is a point in time; it documents the envelope the process was shown to hold.
Continued verification
Every subsequent batch feeds the same matrix. Process parameters and quality attributes are logged against their envelope; trend analyses run quarterly or per-batch; out-of-trend signals open a controlled deviation before they reach out-of-specification.
Continued process verification is not an addendum — it is the answer to the inspector's hardest question: the process is still inside the envelope you qualified against. SAGA keeps the matrix live, so the answer is in the same frame as the original qualification, not a separate quality-system search.
Whether you are validating a new process at first PPQ, retrofitting an existing process whose CQA/CPP matrix has never been written down, or joining a qualification already in flight, the matrix shape stays consistent and the batch record keeps counting.
New validation projects start in SAGA from kickoff — the dossier shape is set the first day, and every artefact lands in the framework as it's authored.
In-production equipment and existing systems can be retrofitted into the framework so ongoing validation work joins SAGA without pausing operations.
Mid-engagement validation projects load existing material into SAGA and continue in parallel — switching over fully when the dossier shape is ready.
Bring the process you are least sure of — a CQA whose CPP coupling is implied but never documented, a continued-verification trend that has been drifting quietly, a DoE record that never quite closed on its tolerance. A focused session, your artefacts in front of us, clear outputs.
https://verheim.dev/validation/process/