This is a ready-to-use quarterly rollup report for a person-in-plant program, built to answer a question no single trip report can: is the program, as a whole, catching what it exists to catch, or is “no news” actually “nobody is tracking whether findings ever really close.” Replace every <<FILL: ...>> placeholder with your own specifics, populate it from the underlying visit reports and the PIP Observation and CAPA Escalation Log, and route it to sponsor technical operations and quality leadership. A filled specimen follows.
Document control header
| Field | Entry |
|---|---|
| Document title | PIP Program Metrics and Trend Scorecard, <<FILL: period, e.g. Q3 2026>> |
| Document number | <<FILL: e.g. PIP-MS-2026-Q3>> |
| Reporting period | <<FILL>> |
| Prepared by | <<FILL: e.g. PIP Program Lead>> |
| Distributed to | <<FILL: Sponsor Technical Operations, Quality leadership>> |
1. Purpose
This scorecard rolls up person-in-plant program performance across every covered campaign for the period above, so program-level trends, a rising recurrence rate, a widening gap between findings logged and CAPAs opened, a coverage shortfall against the risk model, are visible on a fixed cadence rather than discovered only when a repeat failure forces the question.
2. Scope
| Dimension | Decision |
|---|---|
| Reporting period | <<FILL>> |
| Campaigns and sites covered by this rollup | <<FILL>> |
| Source records | <<FILL: PIP visit and trip reports, the escalation and CAPA log, the portfolio coverage matrix for this period>> |
3. Metrics
| Metric | This period | Prior period | Trend | Target / threshold |
|---|---|---|---|---|
| Visit-to-report turnaround (average, business days) | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: e.g. same day to 2 business days>> |
| Escalation-to-tracked-item conversion rate (% of logged findings with a corresponding CAPA or tracker entry) | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: e.g. 100%>> |
| Claimed-closure versus verified-closure rate (% of closed items that recurred within the period) | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: e.g. under 5%>> |
| Coverage rate against risk-flagged campaigns (% of risk-tier-one/two campaigns per the portfolio matrix that received their assigned coverage level) | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: e.g. 100% or a named, accepted exception>> |
| Deviation rate trend per site, campaign over campaign | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: site-specific baseline>> |
State each trend as improving, flat, or declining, not just a number; a flat metric sitting just inside threshold for four consecutive quarters is itself a finding worth naming.
4. Site-by-site detail
| Site / CDMO | Visits this period | Findings logged | CAPAs opened | Items recurred | Coverage per portfolio matrix | Notable pattern |
|---|---|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: met / gap, with rationale reference>> | <<FILL>> |
5. Two-quarter decline trigger
| Field | Entry |
|---|---|
| Has any metric in section 3 declined for two consecutive periods? | <<FILL: Yes/No>> |
| If yes, root-cause action | <<FILL: named owner, due date, and the program-level (not single-visit) corrective action>> |
A single bad quarter can be noise. Two consecutive declines on the same metric is a program-level signal and gets a program-level root-cause look, not a note carried to next quarter’s scorecard unaddressed.
6. Conclusion and actions
<<FILL: overall program health statement for the period, and any actions carried forward, each with a named owner and due date>>
7. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL>> | <<FILL>> | Initial issue. |
8. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (PIP Program Lead) | <<FILL>> | ||
| Reviewer (Sponsor Quality Leadership) | <<FILL>> |
Filled specimen
Extract from Acme Therapeutics’ Q3 2026 scorecard, covering four CDMO relationships and six campaigns; the company and CDMO names are illustrative, continuing the same specimen used in the linked portfolio coverage matrix.
| Metric | This period | Prior period | Trend | Target |
|---|---|---|---|---|
| Visit-to-report turnaround | 1.4 business days | 1.1 business days | Slightly declining | 0 to 2 business days |
| Escalation-to-tracked-item conversion rate | 100% (22 of 22 findings) | 95% (19 of 20) | Improving | 100% |
| Claimed-closure versus verified-closure rate | 91% verified (2 of 22 closed items recurred) | 82% verified (4 of 22) | Improving | Under 5% recurrence |
| Coverage rate against risk-flagged campaigns | 83% (5 of 6 risk-tier campaigns fully covered; 1 accepted-risk exception per the portfolio matrix) | 100% | Declining | 100% or a named, accepted exception |
| Deviation rate trend, Meridian Fill Services | 2 deviations this period, down from 5 | 5 deviations | Improving | Site-specific, trending down expected during onboarding |
Site-by-site detail flags one pattern: the ATX-207 campaign at the new CDMO onboarding site shows the coverage gap already documented and accepted in the Q3 portfolio matrix (virtual oversight only, no qualified PIP available), and the recurrence rate on that specific site’s findings (1 of 3 closed items recurred) is running above the program average.
Two-quarter decline trigger: coverage rate declined for the first time this period (from 100% to 83%); this is the first decline, not the second, so section 5’s root-cause action is not yet triggered, but it is flagged for direct tracking into Q4 given the recurring-shortfall pattern already noted in the linked portfolio matrix.
Conclusion: program health is improving on documentation and closure-verification metrics, the two areas targeted by last quarter’s corrective action, but the coverage-rate decline traces directly to the known PIP qualification gap for new-CDMO onboarding campaigns. Action: PIP Program Lead to bring a staffing proposal to Q4 technical operations review, addressing the recurring-shortfall pattern flagged in the linked portfolio matrix, due 2026-10-15.
Common findings this scorecard prevents
- A PIP program running for years on the assumption that no news is good oversight, with no metric ever actually measuring whether findings stay closed.
- A coverage gap accepted quietly at the single-campaign level with no program-level visibility into how often that acceptance is recurring.
- A declining metric carried silently from quarter to quarter with no named trigger for when it becomes a root-cause action rather than a passing note.
- Program health represented only by anecdote (“the sites seem to be doing better”) with no measured trend behind the claim.
How to adapt this scorecard
- Pull the metrics in section 3 directly from the underlying visit reports, the escalation and CAPA log, and the period’s portfolio coverage matrix; do not estimate from memory.
- Set thresholds in section 3 to values your program can defend, not arbitrary round numbers, and revisit them as the program matures.
- Populate section 4 for every site with PIP activity in the period, even a site with nothing notable to report; a blank site row is itself a data point.
- Track the two-quarter decline trigger in section 5 every period without exception; this is the mechanism that turns a drifting metric into an actual corrective action before it becomes a pattern.
- Distribute the finished scorecard to the same audience every quarter so trend comparison is possible without hunting for the prior version.