Naga MounikaDrug Product · Validation · CMC
Menu
Working document

CPV Control Limit Recalculation Justification

A plug-and-play form documenting the trigger, statistical basis, and approval for recalculating Continued Process Verification control limits, so a limit never moves quietly to make an inconvenient trend disappear, with a filled specimen.

Document typeForm
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 form for documenting any recalculation of Continued Process Verification control limits. Complete one form per recalculation event and route it through change control before the new limits take effect. Replace every <<FILL: ...>> placeholder with your own specifics. A filled specimen follows.

Document control header

FieldEntry
Document titleControl Limit Recalculation for <<FILL: parameter, product, site>>
Document number<<FILL: e.g. CPV-RECALC-2026-004>>
Linked CPV plan<<FILL: document number>>
Linked change control record<<FILL: CC number>>
Requested by<<FILL>>
Date<<FILL>>

1. Purpose

This form documents the trigger, statistical basis, and approval for recalculating the control limits on a monitored Continued Process Verification parameter, so the recalculation is traceable to a predefined trigger and a documented statistical method rather than to the presence of an inconvenient signal in the data.

2. Trigger

State which predefined trigger applies. A recalculation with no trigger checked below is not eligible for approval on this form.

TriggerAppliesDetail
Scheduled annual review<<FILL: yes/no>><<FILL>>
Validated process change implemented through change control<<FILL: yes/no>><<FILL: linked change control reference>>
Accumulation of a predefined number of new stable batches since the last calculation<<FILL: yes/no>><<FILL: batch count and the number defined in the CPV plan>>
Other, state basis<<FILL: yes/no>><<FILL>>

3. Open signals at the time of this request

QuestionAnswer
Is there an open, unresolved trend signal on this parameter at the time of this request<<FILL: yes/no>>
If yes, has it been investigated and closed per the CPV trend signal log, reference number attached<<FILL: log ID, or explain why not>>

A recalculation requested while an unexplained signal remains open on the same parameter is not approved on this form; close the investigation first, through the normal escalation path, or state explicitly why the recalculation is independent of the open signal.

4. Statistical basis

FieldEntry
Data set used<<FILL: date range, batch count, n>>
Chart type<<FILL: I-MR / Xbar-R / Xbar-S / c, u, np, p>>
Minimum data sufficiency met<<FILL: confirm against the working minimum stated in the CPV plan, e.g. 20 to 25 points for I-MR>>
Prior limits<<FILL>>
Proposed new limits<<FILL>>
Batches or points excluded from the calculation, if any, and why<<FILL: an exclusion needs its own documented, QA-approved basis>>

5. Impact assessment

QuestionAnswer
Does the proposed limit change affect any filed commitment or established condition<<FILL: yes/no, and reference>>
Does the new limit remain inside the registered specification<<FILL: confirm>>
Were any batches disposed using the prior limits during the period covered by this recalculation, and does the new limit change their retrospective interpretation<<FILL>>

6. Approvals

RoleNameSignatureDate
Requestor (Statistician or designee)<<FILL>>
Reviewer (Process owner / MSAT)<<FILL>>
Approver (Quality Assurance)<<FILL>>
Regulatory affairs, if section 5 identifies a filed-commitment impact<<FILL>>

Filled specimen

Extract for an example annual review recalculation on a biologics drug substance CQA. Company and numbers are illustrative.

FieldEntry
ParameterHost cell protein, ELISA, specification not more than 100 ng/mg
TriggerScheduled annual review
Open signalsNone; last signal on this parameter closed eight months prior per CPV-SIG-009, resin lot root cause, no repeat since
Data set24 commercial batches over the prior 12 months
Chart typeI-MR
Prior limits8 to 34 ng/mg
Proposed new limits6 to 29 ng/mg, reflecting a process that has run measurably tighter since the resin lot correction from CPV-SIG-009
Impact assessmentNew limits remain well inside the 100 ng/mg specification; no filed commitment references the internal control limit values, only the specification; no batch was disposed on a control-limit basis, disposition uses the specification, so no retrospective reinterpretation applies

The specimen shows the form doing its job: the recalculation is triggered by the scheduled annual review, not by a signal sitting in the data, and section 3 confirms no open, unexplained signal existed on this parameter when the request was made.

Common inspection findings this form prevents

  • Control limits widened or recentered with no documented trigger, discovered only by comparing an old chart to a new one and finding no record explaining the change.
  • A recalculation submitted while an unresolved trend signal is still open on the same parameter, effectively making the signal disappear instead of resolving it.
  • A new limit calculated from a data set with too few points to support it, with no reference back to the working minimums stated in the CPV plan.
  • No impact assessment on file connecting a limit change to a filed commitment, discovered only when a reviewer cross-checks the filing separately.

How to adapt this form

  1. Set the trigger list in section 2 to match exactly what your own CPV plan defines as valid triggers; do not add a trigger here that the plan does not already authorize.
  2. Always complete section 3 before section 4. Confirming no open signal exists, or that one has already closed, has to happen before the new limits are calculated, not after.
  3. Route every completed form through change control, and hold the new limits from taking effect until QA approval is recorded in section 6.
  4. Attach the underlying data set and chart output as a supporting file referenced from section 4, rather than only summarizing it here.
Add this site to your home screen Full screen, works offline, one tap from your home screen.