Table of contents
At a glance
What would the 2025 draft Annex 11 change compared with the 2011 text?
As of 18 October 2026, EudraLex still listed the January 2011 Annex 11 revision. The 2025 text is a consultation draft. Among its proposed changes are separate sections on the pharmaceutical quality system, alarms, security and backup. It names ALCOA+ and proposes multifactor authentication for remote access to critical systems from outside controlled areas. Address existing gaps under applicable requirements and assess draft proposals separately. An announced target date does not make the draft binding.
- Version 2011 remains the currently referenced benchmark.
- An draft difference is not automatically a current compliance gap.
- Technical supplier qualification and internal process suitability remain separate.
- New chapter headings do not replace actual effective controls.
1. Current version, draft, and work plan differ
The consultation on the revised Annex 11 took place jointly with Chapter 4 and Annex 22 from 7 July to 7 October 2025. The draft is available in the official consultation collection. The current guideline overview for human medicinal products continues to reference the January 2011 revision, with its implementation date set at 30 June 2011.
In the EMA Work Plan 2026-2028, Q4 2026 is the target for a final text to the Commission. The planning does not confirm an already adopted new annex and no additional transitional period. In a gap evaluation, the version used, the verification date and the status of each allegedly new requirement should therefore be explicitly stated.
2. Correctly interpret selected changes
The draft provides a more detailed treatment of various topics and explicitly references areas such as PQS and risk management. Nevertheless, the lifecycle thinking did not begin with this revision. Risk management, traceable requirements, supplier assessment, changes, access controls, and regular reviews were already included in the 2011 version.
The following matrix presents selected anchor points. It is not a complete word-by-word comparison and does not constitute a binding checklist of all obligations. For a specific finding, actual control is decisive, not merely the fact that a document employs the new chapter structure.
| Topic | Version 2011 | Draft 2025 | Operational inspection question |
|---|---|---|---|
| Requirements | §4.4: Lifecycle Reference | §6: Detailed Requirements and Configuration Specifications | Do the requirements and evidence still fit the current system? |
| Suppliers | §3: Responsibilities and Assessment | §7: Control and available evidence of detailed documentation | What performance and evidence are actually agreed upon? |
| Access and Security | §12: Security | Section 11 and Section 15: Access control and security management | Are relevant accesses, risks, and retry mechanisms controlled? |
| Periodic evaluation | §11: Periodic Evaluation | §14: Review conducted on a risk-based frequency basis | Do findings provide a justified basis for decisions? |
3. Link current usage requirements to existing operations
An older URS may still contain valid requirements. It becomes problematic when enhancements, interfaces, or alternative operating procedures do not appear in any controlled as-bought specification. Start with the decisions supported by the system: Which input is accepted, which status is updated, and which evidence is required later?
The draft sets out requirements irrespective of SaaS operation or development model and links them to design and test evidence. Assess even a supplier URS against your own use. For each critical function, map the current requirement, configuration, relevant test and known limitation. Missing traceability and a demonstrated functional failure are distinct findings.
4. Verify supplier documentation against its actual scope
Cloud-based operations alter the distribution of responsibilities, not the need for traceable accountability. Even the 2011 version requires appropriate agreements and risk-based supplier evaluation. The draft further clarifies control, performance monitoring, and access to explainable documentation.
Therefore, do not unilaterally require the entire development archive or always conduct on-site audits. First, clarify which services are critical, which document versions are involved, and which questions remain open. An appropriate manufacturer's record can support a specific requirement. It does not automatically confirm customer-specific roles, interfaces, or process decisions that fall outside the scope of its reviewed activities.
5. Do not remove MFA and security management from its context
The draft specifies MFA for remote authentication at critical systems located outside controlled areas. This should not be interpreted as a justification for omitting MFA at every work location; currently, Annex 11 mandates MFA without exception at all work sites. Furthermore, the draft status does not imply that known, current security risks should remain unaddressed pending revision.
Assess user identities, privileged access, actual attack vectors, available support, and recovery capabilities. A security certificate may serve as potential evidence with a defined scope. It does not automatically address whether a former user within the same tenant can still trigger a quality-relevant release. This connection between technical controls and process flow makes the evaluation valuable.
6. Example: a change with four different decisions
An electronic document system has twelve defined requirements. Eight are clearly fulfilled on the basis of appropriate up-to-date documents. Two are now concerned with additional roles, one for the tested restart and one for an access constellation, which has so far only been explicitly considered in the draft. The team thus counts four open evaluation positions, not automatically four today's violations.
The two role themes and the reactivation will be evaluated against current usage and existing framework. The fourth position will be assigned a dedicated status draft proposal. If a specific safety risk exists, a corrective action may still be necessary or beneficial today; in such cases, the justification must derive directly from the risk. A percentage figure alone would obscure this distinction.
After completion of the two role assignments, ten out of twelve evaluation positions are closed. The 83.3 percent completion rate reflects only an interim status. As long as the required restart remains unexplained, this does not indicate the operability of the process. The team therefore documents the decision and finding for each position.
| Positions | Trigger | Evidence needed | Decision |
|---|---|---|---|
| 8 existing requirements | Documentation aligns with current usage | Document and validate reference and validity | Further usable |
| 2 Role requirements | Process and responsibilities updated | Authorization and Negative Verification | Today's clarification |
| 1 Retest requirement | Existing evidence is unsuitable | Representative restoration validation | Today, risk-based clarification |
| 1 Draft position | Future proposal with reference to usage | In-control check and risk assessment | Separate preparation, no fictitious deadline violation |
7. Take actions throughout the product lifecycle
A comparison table is only useful when decisions are implemented. Assign a responsible party, relevant requirements, required validation evidence, and a final approval decision to each change. The need for evaluation may also extend to unchanged associated functions if the change affects their behavior. Conversely, appropriate existing documentation may remain validly supported.
The regular evaluation should integrate these elements: changes, relevant incidents, supplier status, safety concerns, and ongoing suitability. The draft explicitly addresses risk-based review frequency. It does not prescribe a universal annual schedule that replaces the assessment of your system and its actual changes.
8. A compact preparation for QA and IT
Start with a key process and its existing documentation. This will reveal whether the issue lies in understanding of the operating procedures, in missing documentation, or in an ineffective control. A small team requires clear involvement of the process owner and access to relevant IT and supplier information.
The following internal checklist prevents the entire framework from being prematurely renamed based on an initial draft. It also consolidates existing improvements that remain useful independently of the subsequent text version.
- Current version and draft clearly identified.
- Define the GMP-relevant use and identify affected decisions.
- Assess existing controls with specific evidence.
- Current gap, future proposal, and voluntary improvement differ.
- Verify supplier invoices regarding version and actual scope.
- Determine and justify the testing depth based on the impact.
- Document decisions, responsible parties, and closure verification.
- Verify the publication and application date of a final revision.
Project experience and collaboration
Separate gaps against current requirements from preparations for the draft
With QA and IT, we compare current requirements with the draft when assessing an existing system. Evidence missing for current use needs attention now. For a newly proposed control, we assess its operational value and whether a decision can wait for binding text. This distinction matters for long-term procurement and system changes. Your team can see why an action is planned and which assumption to revisit if the text changes.
Frequently asked questions about Draft Annex 11
Do we need to update our documents to align with the Annex 11 draft?
When does the new Annex 11 come into effect?
Does every additional section in the draft create a new obligation?
Does Annex 11 require MFA everywhere today?
No. The current version of 2011 does not specify a general MFA obligation. The 2025 draft proposes multi-factor authentication for remote access to critical systems from outside controlled areas (No. 11.6). This is a draft requirement with a specific application scope. Regardless, existing access controls must be appropriate for actual use.
Can a supplier's URS replace our own requirements specification?
It can provide appropriate content, but must be aligned with the intended use and system status. Own roles, interfaces, and decision-making processes must not be missing without notice. Review and accept appropriate requirements in a controlled manner, rather than treating the supplier document as complete solely due to its title.
Do we need on-site audits for every software supplier?
No, not every supplier has to be audited on site in the same way. Already Annex 11 of 2011 makes the audit requirement dependent on a risk assessment (No. 3.2). Depending on the risk and criticality, the draft mentions audit or thorough evaluation (No. 7.2). Choose type and depth based on the concrete performance and available evidence; a certificate alone does not clarify open critical questions.
Is a new safety feature always fully to be revalidated?
The scope follows the documented impact. In addition to the new function, dependent workflows may be affected. Existing documentation may be considered where applicable. Specifically justify which assessment addresses the relevant uncertainty, rather than mandating a full retest or blanket waiver.
Does a high fill rate indicate system availability?
Must the Periodic Review take place annually?
No. Neither section 11 of the version in force since 2011 nor section 14.3 of the draft prescribes an annual assessment for every system. The draft proposes a risk-based frequency. Scope and interval should suit operations, and relevant changes or incidents may trigger an additional assessment.
How can we update our comparison when the final text is published?
Sources and review date
Source date: October 6, 2026. Current guideline versions and draft consultation documents are distinctly identified. The numerical example is a standalone reference document and does not represent a completed product test.
- Stakeholders’ Consultation on EudraLex Volume 4 – Chapter 4, Annex 11 and New Annex 22Consultation 07.07.2025–07.10.2025, 23:59 CEST
- EudraLex – Volume 4 – Good Manufacturing Practice guidelinesRetrieval issue; Human and veterinary medicines separately handled
- The 3-year work plan for the Inspectors Working Group – January 2026 to December 2028Document Cover Sheet: January 2026–December 2028; Copyright 2026
- Annex 11: Computerised SystemsRevision 1, January 2011; applicable from 30 June 2011
- Annex 11: Computerised Systems – consultation draft 202519-page consultation PDF, assignment 2025 by EC consultation page
Sources checked: .
Translate regulatory status into specific decisions
We support you in aligning applicability, existing evidence, and meaningful next steps for your specific use case.
- GAMP 5 consulting →
Understand how GAMP 5, EU GMP Annex 11 and 21 CFR Part 11 apply to your systems. We translate the relevant requirements into proportionate validation work and evidence your team can defend in an audit.

