Governance DocsGovernance Docs
Browse Toolkits

CART

No products in the cart.

Skip to content

EU GMP Annex 11: Clear Guide to the 2011 Text vs 2025 Draft

EU GMP Annex 11: EU GMP Annex 11: 2011 vs Draft

EU GMP Annex 11, Computerised Systems, is the European rulebook for computerized systems used in GMP activities, and it is being rewritten. The January 2011 text is in force. A consultation draft published on 7 July 2025 is not. That draft is much longer, and teams are asking what changes and how to prepare when no adoption date exists. This post compares the two texts section by section. For the US counterpart, see 21 CFR Part 11 requirements.

EU GMP Annex 11 status: what is in force and what is draft

  • In force: Annex 11 revision 1, January 2011. It came into operation on 30 June 2011.
  • Draft, not adopted: the Annex 11 consultation draft of July 2025. Consultation ran from 7 July to 7 October 2025. It was published alongside a draft Chapter 4 and a new draft Annex 22 on artificial intelligence.

No adoption or effective date has been announced in the draft, and this post does not estimate one. Nothing in the draft is a requirement today. Where this post says “the draft expects,” it describes proposed text that could change. Check the European Commission consultation page and EudraLex Volume 4 for the current status before you rely on anything here.

Why the revision exists

According to the draft, the revision was proposed together by the PIC/S Committee and the EU’s GMP/GDP Inspectors Working Group. The aims are to track changes in regulation and manufacturing, clarify what authorities expect, and remove ambiguity and inconsistency. Its introduction points to growing use of cloud services and new technologies. In practice that means more explicit wording where 2011 left room for interpretation.

EU GMP Annex 11 at a glance: 2011 text vs 2025 draft

Feature 2011 text (in force) July 2025 draft (not adopted)
Structure A principle, 17 numbered sections and a glossary; many sections are one paragraph 17 sections and a glossary; sections 2 to 17 hold 111 numbered sub-clauses
Scope All forms of computerised systems used in GMP regulated activities All types of computerised systems used in manufacturing medicinal products and active substances
Data integrity Mentioned in the risk section, not stated as a principle Principle 2.4 refers to ALCOA+ and links it to several sections
Wording General “should” statements More specific controls, for example account rules, lockout and review independence
New topics None Alarms, a pharmaceutical quality system section, identity and access management, expanded security and backup

Section by section: where each 2011 clause goes in the draft

The draft is renumbered, so a 2011 section number is not a guide to where its content moved. This table maps them.

2011 section Where it sits in the draft What changes
Principle 2 Principles Split into eight principles, including lifecycle, alternative practices, outsourcing and no risk increase (2.8)
1 Risk Management 4 Risk Management Adds a data criticality assessment (4.5)
2 Personnel 5 Personnel and Training Adds system-specific training
3 Suppliers 7 Supplier and Service Management Nine-item contract content, oversight by service levels and indicators, audit or assessment by risk
4 Validation 6 System Requirements; 9 Qualification and Validation Requirements types, vendor specs owned by the user, test focus list, untraceable tests rejected; no counterpart to the 2011 system inventory and system description (4.3)
5 Data; 6 Accuracy Checks 10 Handling of Data Input plausibility checks, validated interfaces, migration, encryption
7 Data Storage 16 Backup; 17 Archiving Backup separation, restore testing, checksum verification before deletion
8 Printouts No separate section; 12.9 on electronic copies Electronic copy must be searchable, not a flat locked file
9 Audit Trails 12 Audit Trails Ten clauses covering content, locking, independent and timely review
10 Change and Configuration Management 3.1(ii) in the quality system section Significant change triggers re-qualification
11 Periodic Evaluation 14 Periodic Reviews Twelve review topics and a final review at retirement
12 Security 11 Identity and Access Management; 15 Security Eleven access clauses and twenty security clauses
13 Incident Management 3.1(i) deviations and CAPA Folded into the quality system, with effectiveness checks
14 Electronic Signature 13 Electronic Signatures Three expectations become nine clauses
15 Batch release No matching clause; 12.10 on QP access to audit trail reviews Check how the final text treats certification signatures
16 Business Continuity 15.5 to 15.7 disaster recovery A tested disaster recovery plan with a recovery time objective; the draft does not mention manual fallbacks
17 Archiving 17 Archiving Read-only protection, verification, durability and retrieval
None 8 Alarms New: justified settings, acknowledgment, alarm log and review

What gets stricter in the EU GMP Annex 11 draft

The biggest shifts are in operational detail, not philosophy. Examples of what the draft expects:

  • Accounts: unique personal accounts; shared accounts count as a data integrity violation unless read-only (11.1). A token or smart card alone is not enough if someone else could use it (11.3).
  • Access controls: multifactor authentication for remote access to critical systems from outside controlled perimeters (11.6), automatic lockout (11.7), inactivity logout (11.8) and an access log (11.9). GMP users hold no administrator rights (11.10).
  • Audit trails: who, what (old and new value), when and why, recorded at the time of the event (12.2). Reviews by someone not involved in the activity (12.6), before batch release unless later detection is justified (12.8). See audit trail review.
  • Signatures: full re-authentication at signing, and reliance on the login session is not acceptable (13.3). A signed record must not be modifiable, or a later change must show it as unsigned (13.8). See 21 CFR Part 11 electronic signature requirements.
  • Suppliers and cloud: a contract or approved IT procedure with nine listed contents, among them audit conditions, inspection support, an exit strategy that keeps your control of the data, and a release process that lets you test new versions first (7.5). The regulated user stays fully responsible for outsourced work (2.6).
  • Testing: test cases that do not trace to requirements fall short of the draft’s expectations (9.5). See requirements traceability matrix.
  • Periodic review and security: a twelve-topic review (14.2) and twenty security controls (section 15), including isolating unsupported or unpatched platforms.

The draft states no numbers for password length, lockout counts or review intervals. Those stay risk-based decisions you document. It also points qualification and validation to the general principles of GMP Annex 15 (9.1) and asks that testing cover standard, configured and customized functionality.

Two changes deserve extra attention because they alter how teams work, not just what they write. First, the audit trail reviewer must be independent of the activity, which rules out reviewing your own work. Second, the draft treats administrator accounts as a separation-of-duties issue: a person who can change audit trail settings should not take part in GMP activities (12.3). Where administrators are also everyday GMP users, the draft expects that to change, though it allows alternative practices proven and documented to give equal control (2.3).

What stays the same in EU GMP Annex 11

The foundations carry over: risk-based effort, a validated application on qualified infrastructure, no drop in quality or rise in risk when a system replaces a manual step (2.8 in the draft), and the regulated user’s responsibility when work is outsourced. A note for readers of the draft Annex 22: its clause 4.3 cites “Annex 11 2.7” for the no-risk-increase principle, but in the Annex 11 draft that principle is 2.8, and 2.7 covers security. See Annex 22.

How to prepare for EU GMP Annex 11 changes without a date

  1. Meet the 2011 text first. It is the standard inspectors apply today, so a gap there is a current risk.
  2. Run a gap assessment against the draft. Treat the result as a forecast, not a deficiency list. Mark each gap as current requirement, likely tightening or unclear.
  3. Start with the long-lead items. Contract terms with suppliers, access and authentication changes, audit trail review procedures, backup restore testing and platform support status take longest to change.
  4. Change documents once. Update procedures so they satisfy both texts where they overlap, instead of writing separate sets.
  5. Do not revalidate for a draft. Use your normal change control when you touch a system, and apply draft expectations where they are also good practice. The draft allows alternative practices that are proven to give the same or higher control (2.3).
  6. Watch the source. Check EudraLex Volume 4 on a schedule you set and record when you checked.

The 21 CFR Part 11 Toolkit maps both texts. It includes an EU GMP Annex 11 (2011) Compliance Assessment Checklist, an Annex 11 Draft Revision Gap Assessment Workbook and a Part 11 and Annex 11 Crosswalk. It has 105 templates (68 Word and 37 Excel) for $99.

21 CFR Part 11 Toolkit sample page: GDL-CSV-100 - Annex 11 Draft Revision Gap Assessment Workbook
21 CFR Part 11 Toolkit sample page: GDL-CSV-101 - Part 11 and Annex 11 Crosswalk
21 CFR Part 11 Toolkit sample page: GDL-CSV-073 - Audit Trail Configuration Verification Checklist

EU GMP Annex 11 FAQ

Is the 2025 draft of EU GMP Annex 11 in force?

No. It is a consultation draft. The January 2011 text remains in force.

When will the new Annex 11 take effect?

No official date exists in the draft, and any date you read elsewhere is an estimate. Watch EudraLex Volume 4 for the adopted text.

Is Annex 11 the same as 21 CFR Part 11?

No. They overlap on audit trails, access and signatures, but Annex 11 is EU GMP guidance for computerized systems generally, while Part 11 sets conditions for FDA to accept electronic records and signatures.

Does the draft say anything new about cloud or SaaS?

Yes. It addresses systems provided as a service in its requirements, supplier and validation sections, and keeps the regulated user responsible for outsourced activities. It also expects users to review and own vendor-supplied requirements and validation documents.

When a standard changes, know first

One email a month: edition changes, new deadlines, and what they mean for documentation you already have. No sales sequence.

We don’t spam! Read our privacy policy for more info.