Naga MounikaDrug Product · Validation · CMC
Menu
Working document

PIP Observation and CAPA Escalation Log

A plug-and-play running log tracking person-in-plant observations from escalation through verified closure, distinguishing closure as claimed from closure as verified, with a filled specimen.

Document typeLog
Topic areaTech Transfer & NPI
LevelIntermediate
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 person-in-plant observation from the moment it is escalated through verified closure. Replace every <<FILL: ...>> placeholder. Update it at every visit and review it before each new campaign starts, so an open item from a prior campaign is never quietly dropped. A filled specimen follows.

Instructions

Log every observation escalated by a PIP, regardless of how minor it seems at the time. An item is not removed from this log when the CDMO reports it fixed; it moves to “closure claimed” and stays open until the verification method confirms the fix held. Retain per <<FILL: document retention period>>.

Field definitions

FieldFormatRequiredWho completes itWhen
ID<<FILL: sequential, e.g. PIP-OBS-001>>YesPIPAt observation
Date/time observed<<FILL>>YesPIPAt observation
ObservationFree text, specificYesPIPAt observation
Risk category<<FILL: e.g. data integrity, aseptic technique, documentation, equipment>>YesPIPAt observation
Escalated toNamed roleYesPIPAt escalation
CAPA / tracker reference<<FILL: system and number>>Yes, once assignedCDMO or sponsor qualityAt escalation
OwnerNamed individualYesCDMO or sponsor qualityAt escalation
Due dateDateYesCDMO or sponsor qualityAt escalation
Status<<FILL: open / closure claimed / verified closed>>YesSponsor qualityOngoing
Verification method and dateFree textYes, before “verified closed”Sponsor quality or PIPAt verification

Log

IDDateObservationRisk categoryEscalated toCAPA refOwnerDue dateStatusVerification
<<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>>

Filled specimen

IDDateObservationRisk categoryEscalated toCAPA refOwnerDue dateStatusVerification
PIP-OBS-014<<FILL: date>>Environmental monitoring excursion response took 40 minutes versus the SOP’s 15-minute target during a Grade B viable count alarmFacility / EMCDMO floor quality representativeCAPA-2026-0077CDMO Shift Supervisor<<FILL: +10 business days>>Closure claimedShift retrained on excursion SOP; training records attached, but response time not yet re-tested against a live excursion
PIP-OBS-014 (follow-up)<<FILL: next campaign date>>Next EM excursion on the same suite responded in 12 minutes, within the SOP targetFacility / EMN/ACAPA-2026-0077N/AN/AVerified closedResponse time observed directly within target on the first real excursion after retraining; closure verified, not just claimed
PIP-OBS-015<<FILL: date>>Line clearance checklist signed before physical clearance completed, see DEV-4471Documentation / batch recordCDMO Manufacturing SupervisorCAPA-2026-0091CDMO Manufacturing Supervisor<<FILL: before next changeover>>Verified closedSecond-person verification step observed in use during the next changeover before the signature was entered

The specimen shows the distinction the log exists to enforce: PIP-OBS-014 was not removed from the log when training records arrived. It stayed open, correctly labeled “closure claimed,” until an actual excursion tested the fix.

Common inspection findings this log prevents

  • A finding marked closed on the strength of a training record alone, with no evidence the underlying behavior actually changed.
  • An open item from one campaign silently absent from the next campaign’s records, with no trace of what happened to it.
  • No distinction anywhere in the sponsor’s records between a CDMO’s claim of a fix and a sponsor’s own verification of it.

How to adapt this log

  1. Set your own risk category list to match your product and process types.
  2. Never delete a row on closure; change its status and add the verification entry, so the full history stays visible.
  3. Review all open and closure-claimed rows before every new campaign at the same site, not only at the point a new observation is made.
Add this site to your home screen Full screen, works offline, one tap from your home screen.