Person-in-Plant Oversight Plan · Naga Mounika Nuguri

Document type	Plan
Topic area	Tech Transfer & NPI
Level	Intermediate
Updated	September 2026

This is a ready-to-use plan for a person-in-plant (PIP) program covering a specific CDMO relationship or campaign. Replace every <<FILL: ...>> placeholder, confirm the plan’s authority traces to the governing quality or technical agreement, and route it through document control before the campaign starts. A filled specimen follows.

Document control header

Field	Entry
Document title	Person-in-Plant Oversight Plan for `<<FILL: product / CDMO / campaign>>`
Document number	`<<FILL>>`
Version	`<<FILL>>`
Effective date	`<<FILL>>`
CDMO / site	`<<FILL>>`
Governing quality or technical agreement reference	`<<FILL: agreement number, section defining oversight scope>>`
Plan owner	`<<FILL: e.g. Sponsor Technical Operations Lead>>`

1. Purpose

This plan defines the scope, oversight model, roles, and escalation channel for sponsor person-in-plant presence during <<FILL: campaign / product / unit operation>> manufacturing at <<FILL: CDMO name>>, consistent with the authority granted under the governing agreement referenced above.

2. Scope

Dimension	Decision
Product(s) and batch(es) covered	`<<FILL>>`
Unit operations covered	`<<FILL: full campaign, or specific steps>>`
Duration	`<<FILL: campaign dates>>`
Out of scope	`<<FILL: e.g. does not include CDMO's own internal audit program>>`

3. Oversight model selection

Situation	Applicable to this campaign (Y/N)	Model selected
First campaign at a new CDMO	`<<FILL>>`	`<<FILL: on-site, full campaign>>`
Recent inspection finding or open quality concern relevant to this product	`<<FILL>>`	`<<FILL: on-site until resolved plus one clean campaign>>`
Complex or historically failure-prone unit operation	`<<FILL>>`	`<<FILL: on-site for that operation, virtual for the rest>>`
Non-recoverable batch (autologous product, short-shelf-life intermediate, high-value single lot)	`<<FILL>>`	`<<FILL: on-site for critical steps regardless of site maturity>>`
Mature relationship, clean deviation trend	`<<FILL>>`	`<<FILL: virtual with periodic on-site spot checks>>`
Post-event recovery (a 483, a recall, a repeat deviation)	`<<FILL>>`	`<<FILL: on-site, elevated cadence, until CAPA verified effective>>`

State the model selected for this specific campaign and the risk basis, referencing the rows above rather than restating the logic each time.

4. Roles and responsibilities

Role	Responsibility
Person-in-plant (sponsor)	Observes, verifies against the plan, documents contemporaneously, escalates through the channel in Section 5; never directs operators, touches product or equipment, or signs batch records
CDMO floor quality representative	Receives PIP escalations in real time, decides immediate floor action, opens the deviation
CDMO quality unit (QA/QC)	Retains GMP accountability for the batch; disposition authority; owns the CDMO’s CAPA system
Sponsor quality unit	Reviews PIP reports; owns the sponsor’s own oversight tracker; retains ultimate responsibility for product quality per ICH Q10 Section 2.7
Sponsor technical operations lead	Approves this plan and any mid-campaign change to the oversight model

5. Escalation channel

Step	Action	Owner
1	Observation made, documented contemporaneously	PIP
2	Escalated to `<<FILL: named role, e.g. CDMO floor quality representative>>` within `<<FILL: e.g. same shift>>`	PIP
3	CDMO opens a deviation or takes immediate floor action	CDMO floor quality
4	Finding logged in `<<FILL: CDMO CAPA system / sponsor oversight tracker>>` with a named owner and due date	CDMO quality unit or sponsor quality, per Section 4
5	Closure verified against the next relevant occurrence, not accepted as claimed	Sponsor quality unit

6. Reporting

The PIP issues a report per visit or per defined interval using the paired PIP Visit / Trip Report template, distributed to sponsor technical operations and quality leadership and, in a form the CDMO can act on, back to the site.

7. Acceptance criteria for the program

This oversight program is considered functioning as intended when every escalation in Section 5 reaches a named owner and due date in a real tracking system, every report reaches both sponsor leadership and the site, and no verbal commitment from CDMO staff goes untracked past the visit in which it was made.

8. References

21 CFR 211.22, Responsibilities of quality control unit. FDA guidance, “Contract Manufacturing Arrangements for Drugs: Quality Agreements” (November 2016). ICH Q10, Pharmaceutical Quality System, Section 2.7, Management of Outsourced Activities and Purchased Materials.

9. Revision history

Version	Date	Author	Summary of change
`<<FILL: 1.0>>`	`<<FILL>>`	`<<FILL>>`	Initial issue.

10. Approvals

Role	Name	Signature	Date
Author (Technical Operations)	`<<FILL>>`
Reviewer (Quality)	`<<FILL>>`
Approver (Sponsor Quality Unit)	`<<FILL>>`

Filled specimen

Acme Therapeutics, autologous CAR-T fill campaign at Meridian Fill Services, third campaign at this CDMO.

Field	Entry
Scope	Batches 7 through 9, fill and finish operations only
Situation applicable	Non-recoverable batch (autologous product); mature relationship with a clean deviation trend across the last two campaigns
Model selected	Hybrid: on-site for fill and viral inactivation steps, virtual for formulation and labeling, stepped down from full on-site presence used in the first campaign
Escalation channel	PIP escalates to the CDMO’s floor quality representative within the same shift; findings logged in the CDMO’s electronic CAPA system, with a copy in the sponsor’s own oversight tracker for visibility
Acceptance result	All three batches completed with two escalated observations, both logged with a named owner and due date, one closed and verified against the next batch’s changeover, the other still open and tracked into the next campaign’s plan

Common inspection findings this plan prevents

A PIP program with no documented basis in the governing quality or technical agreement.
An oversight model applied uniformly regardless of site maturity or product risk, with no recorded rationale for the level chosen.
Escalations that happened verbally with no channel or owner defined in advance.

How to adapt this plan

Confirm the governing agreement referenced in the header actually grants the access this plan assumes; add the language if it is missing before the campaign starts.
Select the oversight model in Section 3 from the actual risk situation, not the model used last time by default.
Name real roles, not placeholders, in Sections 4 and 5 before the campaign begins.