AI GxP validation for regulated life sciences
Compliance

Periodic Review: The Annex 11 Obligation Almost Everyone Is Behind On

Periodic review is required, routinely overdue, and the fastest way for an inspector to find out that a validated estate stopped being validated. What it is, what it is not, and how to catch up.

Cybroscape Technologies5 min read

Key takeaway

Periodic review is required, routinely overdue, and the fastest way for an inspector to find out that a validated estate stopped being validated. What it is, what it is not, and how to catch up.

EU GMP Annex 11 clause 11 requires that computerised systems are periodically evaluated to confirm they remain in a valid state and compliant. It is a short clause. It is also, in our experience, the single most commonly overdue obligation in the whole annex.

The reason is structural rather than negligent: periodic review is a lifecycle duty with no project attached to it, no go-live date driving it, and no sponsor whose bonus depends on it.

What a periodic review is

A structured assessment of whether a system is still what its documentation says it is. It looks at the change history since the last review, incidents and deviations, operational performance, user access, calibration status where relevant, and whether current regulatory expectations have moved.

It produces a conclusion — the system remains validated, or it does not and here is what must happen — with findings that become tracked actions.

What it is not

It is not a revalidation. This confusion is the main reason reviews get deferred: someone scopes it as a full re-execution of IQ/OQ/PQ, costs it accordingly, and the whole thing becomes a project that cannot be funded this quarter.

It is also not a tick-box. A review that concludes "no issues" on a system with eleven uncontrolled changes and an overdue supplier assessment is worse than no review, because it documents that you looked and did not see.

How often

The annex does not fix an interval. You set it based on the system's criticality, its change history and its incident record, and you justify the choice. Annually is common for critical systems; a stable, low-risk system may reasonably be reviewed less often.

What matters is that the interval is defined, justified, and actually met. An undefined interval is a finding by itself, and a defined interval that is routinely missed is worse than a longer one that is kept.

Catching up when you are behind

If several systems are overdue, resist the instinct to do them all properly and in parallel. That is how the backlog becomes permanent.

  • Triage by criticality and by change volume. A system with forty changes since its last review is a different proposition from one with none.
  • Do the highest-risk system properly and completely. It establishes the template and tells you how long one actually takes.
  • For low-change, low-risk systems, a short review that honestly concludes little has changed is legitimate and fast.
  • Schedule the next round before closing the current one. The backlog rebuilt itself last time because nobody did this.

Our EU Annex 11 & Annex 22 readiness work usually starts with this triage, and Cybroscape GxP Copilot reports change history, incidents and calibration status against each system so the review is an assessment rather than an archaeology exercise.

Why inspectors go here early

Because it is a fast, reliable signal. A validation package tells an inspector how you behaved during a project, when attention was high and budget existed. A periodic review record tells them how you behave the rest of the time.

An estate with current reviews and documented findings reads as controlled. An estate with an immaculate original package and no review since go-live reads as one where validation was an event rather than a state — and that shapes everything they look at next.

Where to go next

Explore Cybroscape GxP Copilot for AI-native validation, Cybroscape TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.

Validated state
Periodic reviewA set cadence confirms the system still does what it was validated to do
Change controlEvery change is assessed for its impact before it is made
Supplier reassessmentVendor releases and evidence are checked when they change
Deviations and incidentsProblems are investigated and fed back into the record
Validation does not end at go-live. Each of these can move a system out of its validated state, and each brings it back with evidence.
See it on your own systemBring a URS or a system. We run GxP Copilot against it live on the call.

Sources

Primary documents referred to on this page, from their official publishers.

periodic review annex 11gxp periodic reviewperiodic evaluation computerised systemsannex 11 clause 11validated system review
FAQ

Frequently Asked Questions

Prefer to talk first? Chat with us on WhatsApp or book a call with an expert.

What is a periodic review under Annex 11?

A structured assessment confirming a computerised system remains in a valid state and compliant. It examines change history since the last review, incidents and deviations, operational performance, user access, calibration status where relevant, and whether regulatory expectations have moved — and concludes with findings that become tracked actions.

Is a periodic review the same as revalidation?

No, and this confusion is the main reason reviews get deferred. Someone scopes it as a full re-execution of IQ/OQ/PQ, costs it accordingly, and it becomes a project that cannot be funded. A periodic review is an assessment of whether the system is still what its documentation says it is, not a repeat of the original testing.

How often must periodic reviews be performed?

Annex 11 does not fix an interval. You set it based on criticality, change history and incident record, and justify the choice — annually is common for critical systems. An undefined interval is a finding by itself, and a short interval that is routinely missed is worse than a longer one that is actually kept.

Why do inspectors look at periodic reviews early?

Because it is a fast and reliable signal. A validation package shows how an organisation behaved during a project, when attention and budget were high. A periodic review record shows how it behaves the rest of the time. An immaculate package with no review since go-live reads as validation being an event rather than a state.

Keep reading

All articles
ComplianceGxP Archiving and Data Retention: The Complete Compliance GuideEverything regulated teams need to know about GxP archiving: retention periods by record type, regulatory requirements, format obsolescence, migration, and the difference between archiving and backup. · 8 min readComplianceGxP Compliance Checklist 2026: 60 Items Across FDA, EMA, and MHRA That Auditors Actually CheckA practitioner-grade GxP compliance checklist covering 21 CFR Part 11, EU Annex 11/22, data integrity, change control, training, and supplier qualification, with pass/fail criteria auditors use. · 7 min readComplianceGxP Compliance in the Pharmaceutical Industry: A 2026 Practitioner's GuideEverything a quality or validation professional needs to know about GxP compliance in pharma: the regulatory framework, the practical requirements, and where most companies fall short. · 7 min readComplianceGxP Risk Assessment: Deciding What Actually Needs ValidatingHow to run a defensible GxP risk assessment: determining GxP impact, scoring severity and detectability under ICH Q9, and using the result to set validation effort instead of validating everything equally. · 7 min readComplianceGxP Roles and Responsibilities: Who Signs What, and WhyThe roles a GxP system depends on (process owner, system owner, QA, IT, validation lead): what each is accountable for, why separation of duties matters, and the handover gaps that cause findings. · 7 min readComplianceGxP vs GMP vs GLP vs GCP: What Each One Actually CoversA side-by-side breakdown of the GxP disciplines: what each regulates, where they overlap, which one applies to your work, and the boundary mistakes that create audit findings. · 8 min readComplianceInspection Readiness for Pharma: FDA & EMA Audit Checklist + Live Inspection Room GuideA practitioner's guide to FDA, EMA and MHRA inspection readiness: how to build an always-ready posture, the 7-item retrieval checklist, live inspection request room tracking (Cybroscape eQMS), and the findings that recur most often. · 8 min readComplianceWhat Is GxP? A Plain-English Guide to GMP, GLP and GCPGxP explained without the jargon: what the letters mean, which rules apply to which work, who enforces them, and what "being GxP compliant" actually requires of a system or a team. · 8 min read

Bring a system. We'll show you the package.

Book a demo, or ask a validation lead a quick question on WhatsApp.

  • We reply within one business day
  • We run your URS live on the call
  • You get a clear plan for your system
Chat on WhatsApp

Book a demo

Four fields. The right specialist replies within one business day.

Your details stay private. We never share them.