Naga MounikaDrug Product · Validation · CMC
Menu
Working document

CPV Trend Signal Investigation and Escalation Log

A plug-and-play running log tracking every Continued Process Verification signal from the rule that fired through assessment, investigation, and closure, so a chart with a visible pattern and zero investigations never passes as a clean record, with a filled specimen.

Document typeLog
Topic areaProcess Validation
LevelAdvanced
UpdatedSeptember 2026
How to use this document

Copy the template below into your quality system. Replace every <<FILL: ...>> placeholder with your company, system, and process specifics, then route it through your own document control, review, and approval. The filled specimen shows one worked example; adapt the numbers and scope to your operation and verify each cited regulation or standard against the current source before you rely on it.

This is a generic, originally worded starting point. It contains no confidential, proprietary, or employer material, it is drafted with AI assistance and reviewed, it is not legal or compliance advice, and adopting it does not by itself create or prove compliance. See the Disclaimer and Terms.

This is a ready-to-use running log for tracking every signal a Continued Process Verification chart produces, from the specific rule that fired through to a documented, closed outcome. Replace every <<FILL: ...>> placeholder with your own specifics. Update it at every review cycle, and review the open and recently closed rows before every periodic review or annual product review, so a visible pattern with no recorded investigation is never the state a reviewer or an inspector finds. A filled specimen follows.

Instructions

Log every signal a monitored chart produces against the rules defined in the CPV plan, whether the outcome is a documented single-point assessment or a full investigation. A row is not removed from this log when an assessment or investigation reaches a conclusion; it moves to “closed” with the conclusion recorded, so the full history of what the chart showed and what was done about it stays visible across the product’s commercial life. Retain per <<FILL: document retention period>>.

Field definitions

FieldFormatRequiredWho completes itWhen
ID<<FILL: sequential, e.g. CPV-SIG-014>>YesCPV program ownerAt signal detection
ParameterName of the monitored CQA, CPP, or leading indicatorYesCPV program ownerAt signal detection
Rule fired<<FILL: e.g. single point beyond 3-sigma, 9 points one side of centerline, 6-point trend>>YesStatistician or trained designeeAt signal detection
Review cycle / date<<FILL>>YesCPV program ownerAt review
Tier<<FILL: single-point assessment / formal investigation>>YesProcess ownerAt triage
Assignable cause investigatedFree textYes, for a formal investigationProcess owner / MSATDuring investigation
Outcome<<FILL: explained, no action / CAPA opened / limit recalculation proposed>>YesProcess ownerAt closure
CAPA or change control reference, if opened<<FILL: system and number>>Yes, if applicableProcess ownerAt closure
QA review and dispositionFree textYesQuality AssuranceAt closure
Status<<FILL: open / under investigation / closed>>YesCPV program ownerOngoing

Log

IDParameterRule firedReview cycleTierInvestigationOutcomeCAPA/CC refQA dispositionStatus
<<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>>

Filled specimen

Two rows from an example oligonucleotide drug substance program’s log. Company and numbers are illustrative.

IDParameterRule firedReview cycleTierInvestigationOutcomeCAPA/CC refQA dispositionStatus
CPV-SIG-014Full-length purity, ion-exchange chromatographySingle point at 98.9%, above the 98.6% control limit, within the 90.0 to 100.0% specification<<FILL: date>>Single-point assessmentReviewed against the batch record; coincided with a documented column regeneration performed one cycle earlyExplained, no action; column regeneration timing noted for trend watchN/AAssessment accepted; regeneration timing added as a watch item for the next three batchesClosed
CPV-SIG-015Full-length purity, ion-exchange chromatographySix consecutive points trending upward, most recent at 98.7%<<FILL: date>>Formal investigationTraced to a new resin lot installed two cycles prior, showing a slightly higher binding capacity than the qualified lotCAPA opened; resin lot qualification range narrowed, incoming resin lot testing addedCAPA-2026-0143Root cause accepted; control limits not recalculated, since the resin qualification range is being tightened instead of the process movingClosed

The specimen shows the distinction the log exists to enforce: CPV-SIG-014 closed as a documented single-point assessment with a specific, checkable explanation, while CPV-SIG-015 escalated to a formal investigation and a CAPA rather than being explained away with the same light-touch review. Neither row treats the control limit as something to move; the second row fixes the resin qualification instead.

Common inspection findings this log prevents

  • A chart with a visible pattern spanning many batches and no row in any log showing it was ever investigated.
  • A signal explained verbally at a team meeting with no documented basis, indistinguishable later from a signal nobody looked at.
  • A single-point assessment and a formal investigation not distinguished anywhere in the record, so a reviewer cannot tell which response tier was actually applied.
  • A CAPA number referenced in a CPV report with no corresponding row here connecting the chart signal that triggered it.

How to adapt this log

  1. Set the tier definitions and rule list to match the escalation rules stated in your own CPV plan; do not invent a different rule set for the log than the plan actually uses.
  2. Log every signal that fires, including ones later explained as noise. A log that only records investigations makes the single-point assessments invisible, which is itself a gap an inspector can find.
  3. Review all open rows before every periodic review and before the annual product review, not only when a new signal appears.
  4. Never edit a closed row’s original entry when new information emerges; add a follow-up row referencing the original ID instead, the same way a corrected batch record entry works.
Add this site to your home screen Full screen, works offline, one tap from your home screen.