Every batch can pass.The process can still shift.

Continued process verification across your batch and lab records. Ask neil to review the trend and prepare the next steps.

Bring a process to review
Illustration of a seal examining a circled change in a trace alongside run, sample and procedure records.

Assay across 24 reviewed batches

Assay · % label claim
10510095
B-101B-117 → B-124
Example records · reference 100% · specification 95–105%
All results meet specification. Anything to review?
neil

Yes. The last 8 results are all above the reference.

That triggers this plan’s review rule. Passing the specification doesn’t clear the signal.

Which records are included?

24 reviewed results from recipe v09. One result is pending and one batch uses v10; neither is plotted. Both remain in the source list.

What changed? Prepare the review for MSAT and Quality.
neil

The material lot changes at the same point as the higher results. That gives us a lead—not a cause. I’d check the measurement and compare the process context before drawing a conclusion.

What should each team do next?

Check the measurement

QC / analytical lead

Confirm source results, method version, standards and instrument performance. Review B-126 when its result becomes available.

Investigate the shared context

MSAT / process owner

MAT-B appears with the eight higher results. Compare material attributes, process conditions and relevant events. The timing alone does not establish a material effect.

Agree the next monitoring window

CPV lead / Quality

Document the signal assessment, any required investigation and the next review. Keep recipe v10 separate unless pooling is scientifically justified. Do not move the reference simply to clear the signal.

Assay trend / CPV review

Fictional example · Source records

For MSAT and Quality · B-101–B-126 · August 2026

Finding

All 24 included assay results meet the 95–105% specification. The last eight, B-117–B-124, are above the fixed 100% reference, triggering the example review rule in CPV-PLAN-014 v02.

Scope and completeness

26 expected records. B-125 uses recipe v10 and is not pooled with v09. B-126 is pending. Included results use AM-009 v03 on Site A / MIX-02 at 1,000 L.

Investigation lead

MAT-B replaces MAT-A from B-117. The change coincides with the run of higher values. These records do not distinguish a material effect from a measurement or process effect. No root cause is established.

Proposed follow-up

Check the measurementQC / analytical lead

Confirm source results, method version, standards and instrument performance. Review B-126 when its result becomes available.

Investigate the shared contextMSAT / process owner

MAT-B appears with the eight higher results. Compare material attributes, process conditions and relevant events. The timing alone does not establish a material effect.

Agree the next monitoring windowCPV lead / Quality

Document the signal assessment, any required investigation and the next review. Keep recipe v10 separate unless pooling is scientifically justified. Do not move the reference simply to clear the signal.

Review decision

Open. The responsible reviewers must assess the signal, missing evidence and next monitoring window. No batch disposition, process-control conclusion or approval is recorded.

A trend is only useful if you can explain what went into it.

Bring manufacturing context, analytical results and quality events into the same review. Keep the link to each source.

Batch context

Orders, material lots and the production version.

LabWare

Analytical results

Samples, method versions, units and result status.

Veeva Vault

Quality context

Deviations, changes and supporting documents.

Explore systems and connections

The review should lead somewhere.

Keep the finding, the response and the next review connected. A signal is the start of a decision—not a conclusion about its cause.

Investigate the signal

Carry the affected batches and source evidence into the investigation.

Investigation

Control the response

Assess proposed process or monitoring changes before putting them into use.

Change control

Review the outcome

Bring the reviewed analysis and outstanding work into the product review.

APQR

Questions from CPV teams.

For the underlying lifecycle approach, see FDA’s Process Validation guidance, Stage 3 ↗.

Batch release and CPV answer different questions. A result can meet its specification while a series changes over time. CPV reviews process performance and variation across a defined population; authorised reviewers still make product and process decisions.
No. The example specification is 95–105% label claim. Its fixed monitoring reference is 100%, with an illustrative eight-result rule. The reference is not a statistically estimated control limit. Your team selects and verifies the appropriate limits, methods and signal rules for the real process.
No. The chart, replies and review use fictional, fixed example records. The calculations operate on those records; no laboratory or manufacturing system is queried. The example does not establish process control, root cause or batch approval.
Yes. Scope the records, time basis, units, process phases and version references for each connection. Permitted source data or supplied exports can form the review population. Connections depend on the source API, configuration and access.
Keep expected records visible, even when an analysis cannot include them. The example separates one pending result and one different process version from its 24 reviewed results. Your monitoring plan defines completeness, inclusion, exclusion and comparability; missing is never silently converted to zero.
Ask neil to prepare the dataset, proposed method, calculations and interpretation for review. Your qualified team verifies assumptions, population, limits and implementation before using them for CPV decisions. This small demonstration deliberately does not report Cp or Cpk or claim a qualified control chart.
Keep the reviewed population, analysis definition, findings, linked investigations and open work with the periodic review. A later dataset or method revision should not silently replace the evidence behind an earlier conclusion.

Bring the trend your team is discussing.

Start with one parameter, the monitoring plan and its batch history. Review the population, inspect the findings and agree the next piece of work.

Book a demo