This is a ready-to-use trending register. It does not replace an individual change control record; it aggregates the population of change controls closed in a period so a reviewer can see whether the process itself is under control, not just whether any single change was handled correctly. Replace every <<FILL: ...>> placeholder with your own specifics. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it.
Document control header
| Field | Entry |
|---|---|
| Document title | Change Control Metrics and Trending Register |
| Document number | <<FILL: LOG-ID, e.g. LOG-CSV-011>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Effective date | <<FILL: effective date>> |
| Document owner | <<FILL: role, e.g. CSV Lead / Head of Quality Assurance>> |
| Applies to | <<FILL: sites / systems in scope>> |
| Review cadence | <<FILL: e.g. quarterly, monthly for a site under heightened scrutiny>> |
Purpose
This register captures the volume and performance metrics of the change control program over a defined period so trends are visible before they become inspection findings. A change control system that processes every individual change correctly can still be an unhealthy process if emergency changes are climbing, closures are slipping, or the same system keeps generating changes tied to deviations. This log is the evidence that the trend, not just the individual record, is being watched.
How to use this register
- At the end of each review period, pull the change control data for that period from the change control system.
- Complete one row per period in the trend table (section 1).
- Compare each metric against its threshold. Where a threshold is breached, complete an escalation entry (section 2).
- QA reviews the completed period and signs.
- Feed the period’s summary into periodic review and management review per
<<FILL: periodic review SOP-ID>>and<<FILL: management review SOP-ID>>.
1. Trend table
Complete one row per review period. Carry the prior period’s figures forward so the trend is visible at a glance.
| Period | Total closed | Category 1 | Category 2 | Category 3 | Emergency changes | Emergency rate (%) | Median time-to-close, Cat 3 (days) | Reopened / reworked | Linked to a deviation or CAPA | Overdue open (count) |
|---|---|---|---|---|---|---|---|---|---|---|
<<FILL: e.g. 2026-Q3>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
2. Thresholds and escalation
Set a threshold for each metric based on your own historical baseline and risk tolerance. A single breach is a flag; a sustained breach across two or more consecutive periods is an escalation.
| Metric | Default threshold | Action on breach |
|---|---|---|
| Emergency-change rate | <<FILL: e.g. no more than 5% of total closures>> | Sample the emergency records; confirm each meets the SOP definition of an emergency; if the normal process is being bypassed for convenience, escalate to the change control process owner |
| Time-to-close, Category 3 | <<FILL: e.g. within the 4 to 12 week target>> | Identify the bottleneck (review, testing, approval); if systemic, raise a process CAPA rather than expediting individual records |
| Reopened / reworked rate | <<FILL: e.g. no more than 5% of closures>> | Sample reopened records for boilerplate or incomplete impact assessments; retrain or revise the impact assessment template |
| Changes linked to a deviation or CAPA | <<FILL: e.g. any system with 2 or more in a period>> | Review whether the same system, change type, or requestor recurs; consider whether the underlying change process, not just the system, is the root cause |
| Overdue open change controls | <<FILL: e.g. no more than 10% of open records >30 days past target>> | Review the backlog by owner and age; escalate resourcing or prioritization to the change control process owner |
3. Escalation log
Complete an entry whenever a threshold is breached per section 2.
| Ref | Period | Metric breached | Value vs threshold | Root cause (if known) | Action | Owner | Due date | Status |
|---|---|---|---|---|---|---|---|---|
<<FILL: ESC-1>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
4. Acceptance criteria
A period’s trending is complete and acceptable when all of the following hold:
- Every metric in section 1 is populated from the change control system, not estimated.
- Every threshold breach in section 2 has a corresponding escalation entry in section 3.
- Escalations from the prior period are either closed or carried forward with a current status, never silently dropped.
- The period summary was reviewed and signed by QA and fed to periodic review or management review within
<<FILL: number>>days of period close.
References
21 CFR 211.68 (automatic equipment); 21 CFR 211.100 (written procedures). EU GMP Annex 11, section 10 (controlled change). ISPE GAMP 5, A Risk-Based Approach to Compliant GxP Computerized Systems (2nd edition). ICH Q10, Pharmaceutical Quality System (management review and continual improvement). ICH Q9, Quality Risk Management (risk-based thresholds).
Confirm the current version and clause numbers of each reference before issue.
5. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
6. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author | <<FILL>> | ||
| Reviewer (Change Control Process Owner) | <<FILL>> | ||
| Approver (QA) | <<FILL>> |
Filled specimen
Illustrative two-quarter trend. Replace with your own.
| Period | Total closed | Category 1 | Category 2 | Category 3 | Emergency changes | Emergency rate (%) | Median time-to-close, Cat 3 (days) | Reopened / reworked | Linked to a deviation or CAPA | Overdue open (count) |
|---|---|---|---|---|---|---|---|---|---|---|
| 2026-Q2 | 118 | 71 | 38 | 9 | 4 | 3.4 | 41 | 5 | 2 | 3 |
| 2026-Q3 | 126 | 68 | 39 | 19 | 11 | 8.7 | 39 | 4 | 5 | 4 |
Escalation log:
| Ref | Period | Metric breached | Value vs threshold | Root cause (if known) | Action | Owner | Due date | Status |
|---|---|---|---|---|---|---|---|---|
| ESC-2026-014 | 2026-Q3 | Emergency-change rate | 8.7% vs 5% threshold | 7 of 11 emergency changes were certificate renewals on the same cluster of servers, none a genuine unplanned failure | Move certificate renewal to a scheduled normal change with advance calendar tracking; retrain the on-call rotation on the emergency definition | IT Infrastructure Lead | 30 Sept 2026 | Open |
| ESC-2026-015 | 2026-Q3 | Changes linked to a deviation or CAPA | 5 vs 2-per-system threshold, 3 on the same LIMS instance | Configuration change to the LIMS result-rounding rule was under-tested; two downstream deviations traced to rounding discrepancies | Reopen the change’s impact assessment, add a rounding-boundary regression test to the standard LIMS change test set | CSV Lead | 15 Sept 2026 | Open |
QA review: R. Gomez, 2 Oct 2026. The emergency-change rate breach and its root cause (a scheduling gap, not a true emergency pattern) were reviewed and accepted as accurately captured; the LIMS-linked deviations were escalated to the CSV lead with a process fix rather than a one-off retest, because the same rounding gap could recur on the next LIMS change. Both escalations were fed to Q3 management review.
This is the pattern a reviewer wants to see: a metric moved, the register caught it inside the period rather than at the next inspection, the root cause was investigated rather than assumed, and the fix targets the process rather than the individual change.
Common inspection findings this register prevents
- A change control system with clean individual records but no visibility into the population, so a climbing emergency-change rate or a growing backlog is never seen until an inspector counts it.
- Emergency changes trending up with no review of whether they are genuine emergencies or a workaround for a slow normal process.
- The same system or requestor generating repeated deviations traced to change control, with no pattern ever surfaced because no one looks across records.
- Periodic review or management review receiving no change control trend data, so “the process is under control” is asserted rather than shown.
How to adapt this register
- Set your document number, owner, and review cadence in the header.
- Set your own thresholds in section 2 from your historical baseline; do not import defaults from elsewhere without checking they fit your volume and risk profile.
- Point the cross-references to your real periodic review and management review procedures.
- Decide whether you track this register manually or generate it from your change control system’s reporting; either is acceptable if the source data is reliable and the register is reviewed and signed.
- Confirm every regulation in the references against the current published version before issue.