EU Annex 11
EU GMP Annex 11 is the European Commission's GMP guideline for computerised systems used in regulated medicinal-product activities. The version in force dates from 2011 and came into operation on 30 June 2011; a revised draft went to public consultation in 2025 and is not yet final.

On this page · 10 sections
- 1What Annex 11 covers
- 2How the annex is organised
- 3The clauses most people need
- 4Project phase: what validation means under clause 4
- 5Operational phase: keeping the system in control
- 6Annex 11 compared with 21 CFR Part 11
- 7Worked example
- 8The 2025 revision draft
- 9Common failure modes and checks
- 10Where V5 fits
How does EU Annex 11 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What Annex 11 covers
Annex 11 applies to all forms of computerised systems used as part of GMP-regulated activities. It defines a computerised system simply as a set of software and hardware components which together fulfil certain functionalities. That covers a warehouse system recording quarantine status, a weighing terminal, a laboratory data system, a document management tool and an electronic batch record alike.
Its principle has three parts. The application should be validated. The IT infrastructure it runs on should be qualified. And where a computerised system replaces a manual operation, there should be no resulting decrease in product quality, process control or quality assurance, and no increase in the overall risk of the process. That last sentence is the test an inspector applies to every move from paper to software: is the new way at least as controlled as the old one?
Annex 11 is part of EudraLex Volume 4, the EU Guide to Good Manufacturing Practice for medicinal products for human and veterinary use. The document gives its legal basis as Article 47 of Directive 2001/83/EC and Article 51 of Directive 2001/82/EC, and describes itself as guidance for interpreting the GMP principles laid down for human and veterinary medicines. Manufacturers and importers in the EU must follow GMP, and inspectors use the annex as the expected standard for computerised systems.
02How the annex is organised
The annex is short — around four pages — and is laid out along the life of a system. Reading it in that order makes it easier to see who owns what.
| Part | Clauses | What it is about |
|---|---|---|
| Principle | — | Validate the application, qualify the infrastructure, no loss of control versus the manual process. |
| General | 1–3 | Risk management, personnel, suppliers and service providers. |
| Project phase | 4 | Validation: lifecycle documentation, inventory, user requirements, testing, data migration. |
| Operational phase | 5–17 | Data checks, accuracy checks, storage and backup, printouts, audit trails, change control, periodic evaluation, security, incidents, e-signatures, batch release, business continuity and archiving. |
| Glossary | — | Definitions such as application, bespoke system, COTS, IT infrastructure, life cycle, process owner and system owner. |
03The clauses most people need
| Clause | What it expects (paraphrased) |
|---|---|
| 1 Risk management | Apply risk management through the lifecycle, considering patient safety, data integrity and product quality. The extent of validation and data integrity controls should rest on a justified, documented risk assessment. |
| 2 Personnel | Close cooperation between process owner, system owner, Qualified Persons and IT; everyone with appropriate qualifications, access and defined responsibilities. |
| 3 Suppliers | Formal agreements with third parties that state their responsibilities; competence and reliability assessed, with any audit based on risk; COTS documentation reviewed against user requirements. |
| 4 Validation | Lifecycle documentation, a system inventory, user requirements traceable through the lifecycle, appropriate test methods, and checks that migrated data keep their value and meaning. |
| 9 Audit trails | Based on risk, consider a system-generated record of all GMP-relevant changes and deletions, with the reason documented; audit trails available in intelligible form and regularly reviewed. |
| 11 Periodic evaluation | Evaluate systems periodically to confirm they remain valid and GMP-compliant. |
| 14 Electronic signature | Same impact as handwritten signatures within the company, permanently linked to the record, with time and date. |
| 15 Batch release | Where the system records certification, only Qualified Persons may certify release; the system identifies and records them, using an electronic signature. |
04Project phase: what validation means under clause 4
Clause 4 is the longest in the annex. It does not prescribe a method such as GAMP 5, but it does set out what the evidence must cover. Validation documentation and reports should cover the relevant lifecycle steps, and the manufacturer should be able to justify its standards, protocols, acceptance criteria, procedures and records from its risk assessment. Validation documentation should include change control records, if applicable, and reports on deviations seen during validation.
Inventory and system description
Clause 4.3 asks for an up-to-date listing of all relevant systems and their GMP functionality. For critical systems there should also be a current system description covering physical and logical arrangements, data flows and interfaces, hardware and software prerequisites, and security measures. In practice many sites fail here first: the inventory exists but misses spreadsheets, instrument software or a cloud tool a department adopted on its own.
User requirements
Clause 4.4 says user requirements specifications should describe the required functions, be based on documented risk assessment and GMP impact, and be traceable throughout the lifecycle. Traceable means you can follow one requirement — say, 'a dispensed weight outside tolerance must block the step' — to the test that proved it and to any later change that touched it.
Supplier development and testing
Clause 4.5 asks the regulated user to take all reasonable steps to ensure the system was developed under an appropriate quality management system, and to assess the supplier. Clause 4.6 adds a formal quality and performance reporting process for bespoke or customised systems. Clause 4.7 asks for evidence of appropriate test methods and scenarios, with particular attention to parameter limits, data limits and error handling; automated testing tools need documented assessments of adequacy.
Data migration
Clause 4.8 is one sentence but it matters on every replacement project: if data are transferred to another format or system, validation should include checks that data are not altered in value or meaning. Moving five years of batch records to a new system without a reconciled migration check is a classic inspection finding.
05Operational phase: keeping the system in control
Once live, the annex expects the system to stay as trustworthy as it was on validation day. The operational clauses read like a checklist, and each maps to a routine a site must actually run.
| Clause | Routine it implies |
|---|---|
| 5 Data | Built-in checks on electronic data exchange between systems, for correct and secure entry and processing. |
| 6 Accuracy checks | A second check on critical manually entered data — by a second operator or validated electronic means — scaled by risk. |
| 7 Data storage | Physical and electronic protection; stored data checked for accessibility, readability and accuracy; regular backups whose integrity and restorability are checked in validation and monitored periodically. |
| 8 Printouts | Clear printed copies; for batch-release records, printouts that show whether data changed since original entry. |
| 10 Change and configuration | Changes, including configuration changes, made only in a controlled way under a defined procedure. |
| 12 Security | Physical and logical access restricted to authorised people, scaled to criticality; creation, change and cancellation of access recorded; operator identity, date and time recorded for entries, changes, confirmations and deletions. |
| 13 Incident management | All incidents — not only failures and data errors — reported and assessed; root cause of critical incidents identified and fed into CAPA. |
| 16 Business continuity | Documented, tested fallback (manual or alternative system) for critical processes, with time to switch over based on risk. |
| 17 Archiving | Archived data checked for accessibility, readability and integrity; retrieval tested when systems change. |
06Annex 11 compared with 21 CFR Part 11
Sites selling into both the EU and the US usually meet both, but the documents are not interchangeable. Part 11 is a binding US regulation focused on electronic records and signatures. Annex 11 is EU GMP guidance covering the whole computerised system lifecycle, including suppliers, risk management, incidents and business continuity.
| Topic | Annex 11 (2011) | 21 CFR Part 11 |
|---|---|---|
| Status | EU GMP guideline in EudraLex Vol. 4 | US federal regulation |
| Audit trail | Consider, based on risk, for GMP-relevant changes and deletions; reason documented; regular review | Secure, computer-generated, time-stamped audit trails for operator entries and actions that create, modify or delete records (11.10(e)) |
| Signatures | Same impact as handwritten within the company; linked; time and date (cl. 14) | Printed name, date/time and meaning; linking; uniqueness; certification to FDA; component rules (11.50–11.300) |
| Suppliers | Formal agreements and risk-based assessment (cl. 3) | Not addressed directly |
| Business continuity | Required for critical processes (cl. 16) | Not addressed directly |
| Batch release | Qualified Person certification by e-signature (cl. 15) | Not addressed; release rules sit in the predicate rules such as 21 CFR 211 |
07Worked example
A tablet manufacturer in Ireland moves weighing records from paper to software. Under clause 1 it records a risk assessment that rates target weights and recorded results as high impact. Under clause 3 it signs an agreement with the software supplier stating who maintains the hosting and who handles incidents, and reviews the supplier's documentation against its own requirements. Under clause 4 it writes user requirements and tests the weighing functions against them, including what happens when a balance reading is out of tolerance.
Under clause 9 it decides that changes to target weights and recorded results need an audit trail with a reason for change, and adds a monthly audit-trail review to its procedure. Under clause 7 it restores a backup to a test environment and checks the records match. Under clause 14 the reviewer's electronic signature is linked to the record and shows date and time. The Qualified Person still certifies the batch, as clause 15 and EU law require. A year later, clause 11's periodic evaluation looks at incidents, upgrades and access changes and confirms the system remains in a validated state.
08The 2025 revision draft
The European Commission ran a stakeholder consultation from 7 July to 7 October 2025 on a revised Chapter 4 (Documentation), a revised Annex 11 and a new Annex 22 on artificial intelligence. Until the Commission adopts and publishes a final text with a date of coming into operation, the 2011 Annex 11 is the version in force.
09Common failure modes and checks
- Quoting the 2025 consultation draft as if it were in force.
- An inventory that misses spreadsheets, instrument software or department-owned cloud tools (clause 4.3).
- Assuming a supplier's certificate replaces the formal agreement and risk-based assessment clause 3 expects.
- Data migrated without checks that values and meaning are unchanged (clause 4.8).
- Backups that have never been restored (clause 7.2).
- Audit trails that exist but are never reviewed (clause 9).
- Access rights granted and removed without a record (clause 12.3).
- No tested fallback for a critical system (clause 16).
- Treating Part 11 compliance as Annex 11 compliance; the documents differ.
10Where V5 fits
V5 provides audit history, electronic signatures, role-based access and controlled documents that a customer can assess against Annex 11. Enterprise may include IQ/OQ documentation and validation support. Supplier agreements, the risk assessment, validation for intended use, periodic evaluation, business continuity arrangements and Qualified Person decisions remain the customer's responsibility.
Frequently asked questions
Q.Is Annex 11 law?+
It is an EU GMP guideline in EudraLex Volume 4; manufacturers must comply with GMP, and inspectors apply the annex.
Q.Which version of Annex 11 applies?+
The 2011 revision, which came into operation on 30 June 2011, until a revised text is adopted.
Q.Has Annex 11 been revised?+
A revised draft was consulted on from 7 July to 7 October 2025. Until the Commission adopts it, the 2011 version applies.
Q.Does Annex 11 require an audit trail for every system?+
Clause 9 asks companies to consider audit trails based on risk for GMP-relevant changes and deletions, document the reason for change, and review them regularly.
Q.Does Annex 11 require supplier audits?+
Clause 3.2 says the need for an audit should be based on a risk assessment; formal agreements with third parties are expected regardless.
Q.Can an electronic signature be used for batch release?+
Clause 15 says that where a system records certification and release, only Qualified Persons may certify, and this should be done with an electronic signature.
Q.Does meeting Part 11 mean meeting Annex 11?+
No. They overlap on records and signatures, but Annex 11 also covers suppliers, risk management, incidents, business continuity and archiving.
Primary sources
Further reading
- 21 CFR Part 11The U.S. counterpart, with different wording.
- Audit TrailAnnex 11 clause 9.
- Electronic SignatureAnnex 11 clauses 14 and 15.
- Computer System ValidationHow clause 4 is usually met.
- GAMP 5Industry practice often used to meet it.
- Data IntegrityWhat clauses 5–9 protect.
- Supplier QualificationClause 3 in practice.
- Change ControlClause 10 in practice.
- Annex 11 GuidePlanning guide.
Explore this topic
EU Annex 11 sits inside this topic cluster in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
Want to see how EU Annex 11 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
