What a Periodic Review Actually Confirms
After your system is GMP released — VSR approved, system in production use — the validation clock does not stop. Every change made since release, every deviation raised, every calibration that has drifted, every account that has not been disabled when someone left: all of it accumulates. The periodic review is the formal mechanism that looks back across the entire operation period and asks a single question: is this system still in its validated state?
The regulatory basis is EU GMP Annex 11 §11 (Periodic Evaluation), which requires computerised systems to be periodically evaluated to confirm they remain in a validated state. GAMP 5 translates this requirement into a structured review process — documented, multi-disciplinary, and concluded with a formal sign-off.
Critically, the periodic review is not a re-validation. It is a review of evidence accumulated since the last review. It does not repeat OQ test cases unless specific findings require it. What it does do is examine the change control log, the deviation ledger, the audit trail, calibration status, training records, and process performance data — and draw a documented conclusion about whether the validated state has been maintained.
EU GMP Annex 11 §11: "Computerised systems should be periodically evaluated to confirm that they remain in a valid state and are compliant with GMP." This is a mandatory requirement, not guidance. The absence of a periodic review record for a GMP system is a direct Annex 11 non-compliance finding.
When It Triggers — Four Scenarios
There are two types of periodic review: the scheduled review that happens on a fixed calendar cadence, and triggered reviews that are required by specific events. Both are governed by SOP-PR-SYS-001.
The Seven Review Sections
The PRR-SYS-001 template structures the review across seven sections. Each requires specific source documents to be reviewed and specific checks to be performed. An auditor reading the approved PRR will look for evidence that each section was genuinely reviewed — not just ticked off.
Review every entry in CCL-SYS-001 since the last review (or since VSR approval for the first review). Confirm all Type 1 changes were re-tested, CAPA closed, and VSR amended where required. Confirm no unauthorised changes — shadow changes.
Review all MDL entries from the operation period. Confirm all deviations are closed. If any Category A deviations were risk-accepted rather than corrected, confirm the risk-acceptance rationale is still valid and the residual risk is still acceptable.
Export a minimum of 50 audit trail events from the review period. Review for: all setpoint changes have reason entries, no shared accounts, no unexplained access denials suggesting attempted security bypass, NTP drift within ±30 seconds.
Perform the SQL write-once check: attempt an UPDATE command on one historical audit trail record directly in the database. The command must be blocked or produce an audit trail entry itself. This adversarial check is the one most inspectors ask for first.
Review EL-SYS-001 Sheet 9 (Calibration Register) — confirm no GMP-critical instruments are overdue. Calculate backup success rate from SCADA backup status historian tag. Verify UPS has been function-tested within the last 12 months. Confirm validated software archive is current and accessible.
Confirm training records are complete for all current personnel with system access. Confirm all personnel who have left the organisation have had their accounts disabled (not deleted — disabled to preserve audit trail attribution). Review role assignments — all roles still appropriate to current job functions.
Review PQ Phase III ongoing monitoring data. Generate trend charts for each critical process parameter and each Point of Use. Identify any out-of-trend (OOT) results that are not yet OOS but show a worsening direction. Compare seasonal data if two or more annual cycles are available — seasonal patterns are expected in some systems and should be documented rather than treated as anomalies.
Review any updates to EU GMP Annex 11, 21 CFR Part 11, GAMP 5, and applicable pharmacopoeias (USP, EP) issued since the last review. Assess whether any changes create a gap with the current validated state. This section is frequently underperformed — regulatory updates are not always announced loudly and it is the system owner's responsibility to track them.
The Three Possible Conclusions
The Periodic Review Report must state one of three conclusions. Each has different implications for what happens next.
A hash mismatch between the current deployed PLC software and the validated archive baseline is not a "minor action." It means an undocumented change has been made to the validated software — a shadow change. This is among the most serious findings in a GMP validation inspection. The system cannot be considered to be in its validated state. The change must be investigated, root cause documented, impact assessed, and the system formally re-tested and re-released before GMP production can resume.
Preparing for a Review — What to Gather
The SOP requires review preparation to begin at least 4 weeks before the scheduled date. The source documents needed are:
- CCL-SYS-001 — Change Control Log: all changes since last review, with re-test evidence and CAPA closure status
- MDL-SYS-001 — Master Deviation Ledger: all deviations from the operation period, status confirmed current
- Historian audit trail export — minimum 50 events covering the full review period, exported to a certified read-only format
- EL-SYS-001 Sheet 9 — Calibration Register: all GMP-critical instruments, calibration certificate references, next due dates
- PQ Phase III monthly sampling data — all PoU results from the review period, trend analysis prepared
- TRF-SYS-001 — Training Records: all current operators, training dates, role assignments
- Validated configuration archive — current PLC and SCADA software hashes for shadow change verification
SOP-PR-SYS-001 defines the full periodic review process — preparation timeline, execution steps for each of the seven sections, escalation criteria, and approval routing. PRR-SYS-001 is the pre-structured review report template with all seven sections, the shadow hash verification table, the SQL write-once check record, and the three-option conclusion checklist. Both documents are designed to work together — the SOP tells you what to do, the PRR gives you the format to record it.