V5 Ultimate
Guide

EU GMP Annex 11 Readiness: A Clause-by-Clause Guide

EU GMP Annex 11 governs every computerised system used in regulated pharmaceutical manufacturing across the EU and EEA. It is short — only 17 clauses — but inspectors apply it with the same rigour as the parent GMP chapters. This guide breaks down each clause in plain language, maps it to the artefacts a quality team must be able to produce on demand, and shows how a modern eQMS like V5 Ultimate compresses the effort from months to weeks. It is written for QA leads, validation engineers, and IT owners preparing for an EMA, MHRA, or national-authority inspection.

Start free trial Free trial, no credit card, onboard in days, not months.

Scope and risk management (clauses 1 and 2)

Annex 11 applies to any computerised system that forms part of a GMP-regulated activity, from a single spreadsheet performing a release calculation up to an MES controlling a sterile fill line. Clause 1 demands a documented, risk-based approach: not every system needs the same depth of validation, but every system needs a justified decision. In practice this means maintaining a system inventory with a GxP-impact rating, a GAMP 5 software category, and a risk class. Inspectors will ask for that inventory in the first thirty minutes of a tour.

Personnel, suppliers, and service providers (clauses 3 and 3.1 to 3.4)

Personnel using or maintaining computerised systems must be qualified and trained, and the supplier of any commercial product must be assessed before purchase. The depth of that assessment scales with GxP impact: a Category 1 infrastructure component needs little more than a vendor questionnaire, while a Category 4 configured product such as an eQMS warrants an on-site or remote supplier audit. Keep the audit report, the supplier's quality manual, and any third-party certifications (ISO 9001, ISO 27001, SOC 2) in a controlled location with review dates. For SaaS systems, also retain the signed Quality Agreement and the most recent shared-responsibility matrix.

Validation lifecycle (clause 4)

Clause 4 is the longest clause in Annex 11 and the one most frequently cited in inspection findings. It mandates a documented validation lifecycle proportionate to risk, traceability between user requirements and test evidence, and formal change control thereafter. The minimum deliverables are a Validation Plan, a User Requirements Specification, a Functional and Configuration Specification, a Requirements Traceability Matrix, IQ/OQ/PQ protocols and reports, and a Validation Summary Report. Each requirement must trace to at least one test case; each test case must trace back to a requirement.

Data integrity: accuracy, completeness, and ALCOA+ (clauses 5 to 9)

Clauses 5 through 9 cover data — the heart of every modern inspection. Data must be accurate (clause 5), entered and processed by authorised people only (clause 7.1), protected from unauthorised modification (clause 7.2), and accompanied by a secure, computer-generated, time-stamped audit trail (clause 9). The MHRA and FDA have aligned on the ALCOA+ principles — Attributable, Legible, Contemporaneous, Original, Accurate, plus Complete, Consistent, Enduring, and Available. Self-audit your critical systems against ALCOA+ at least annually and after every major change. Pay particular attention to any data leaving the validated boundary — exports to Excel for trending are a perennial finding.

Electronic signatures, access, and security (clauses 12 and 14)

Annex 11 requires unique user identities, role-based access, and electronic signatures that are permanently linked to their records and that include the signer's name, date, time, and meaning of signature. Although Annex 11 itself does not mandate two-factor authentication, EU inspectors increasingly expect it for any signature that releases product or approves a critical document. Configure your eQMS so that signature meanings (Author, Reviewer, Approver, Released by) are enforced by workflow rather than chosen freely by users, and that signature records cannot be edited or deleted by any role, including system administrators.

Incident management, business continuity, and archiving (clauses 13, 16, and 17)

All incidents affecting a computerised system must be reported and assessed for GMP impact, with root cause analysis for anything that affected data integrity or product quality. A documented and tested business continuity plan must exist for any system whose unavailability would interrupt manufacturing or release. Records must be archived in a way that preserves readability and integrity for the full retention period — at least the product shelf life plus one year for batch records, often longer for clinical and pharmacovigilance data. Test your archive restoration at least once per year; an untested backup is no backup at all.

Periodic review and continuous compliance

Annex 11 clause 11 requires periodic review of computerised systems to confirm they remain in a validated state. The interval is risk-based, typically one to three years. A periodic review should cover: changes since the last review, deviations and incidents, user-access reviews, supplier status, training records, backup and restoration tests, and any new regulatory expectations.

Where this lives in V5 Ultimate

The clauses above aren't theoretical — every one maps to a shipped module and an industry profile. Jump to the parts of the product that turn this guide into evidence on a Monday morning.

Frequently asked

Does Annex 11 still apply after Brexit?
Yes. The MHRA adopted EU GMP including Annex 11 verbatim into UK law on 1 January 2021 and continues to expect the same compliance from UK manufacturers and importers. Any divergence will be communicated through MHRA guidance, but as of 2026 the text is unchanged.
How does Annex 11 differ from FDA 21 CFR Part 11?
Part 11 focuses narrowly on electronic records and electronic signatures, while Annex 11 covers the full lifecycle of computerised systems — validation, suppliers, security, business continuity, archiving. Most GxP systems must satisfy both: Part 11 for the e-records and e-signatures, Annex 11 for everything else. The two are complementary, not duplicative.
Do I need to revalidate after every software update?
No. Apply a risk-based change-control assessment: minor patches in a Category 1 infrastructure component may need only a regression smoke test, while a configuration change in a Category 4 product that touches a GxP workflow may require partial re-execution of the OQ and PQ. Document the rationale in the change record either way.
What is the single most common Annex 11 inspection finding?
Inadequate audit-trail review. Many sites generate audit trails but never review them, or review only on exception. Inspectors expect a documented, risk-based schedule of audit-trail review with evidence that the reviewer looked, what they looked at, and what they did with what they found.

See it on your shop floor.

Free trial, no credit card, onboard in days, not months.