EU GMP Annex 11: What it requires for computerized systems in pharma
Adam Hartmann-Kruckow
Annex 11 sets the rules for computerized systems in GxP environments: audit trails, validation status, access controls, and data integrity. The July 2025 draft expanded the standard from 5 to 19 pages, restructured into 17 sections. If your temperature monitoring system runs on software, Annex 11 applies to it.
Here is what EU GMP Annex 11 requires in 2026, what changed in the July 2025 draft, and how to align a temperature monitoring setup with the updated expectations.
Not to be confused with ICAO Annex 11 (air traffic services) or EU MDR Annex XI.
What is EU GMP Annex 11?
EU GMP Annex 11 is the European regulation that governs computerized systems used in GxP environments. It sits in EudraLex Volume 4, the EU Guidelines on Good Manufacturing Practice, alongside the other annexes that cover sterile manufacturing, qualification and validation, and documentation.
The scope is broad. Any software that touches a GMP, GDP, or GLP process falls within it: ERP, LIMS, MES, batch release systems, temperature monitoring platforms, mapping software, calibration databases. If the system holds, processes, or transmits data that supports a regulatory decision, Annex 11 applies.
Accountability stays with the Marketing Authorisation Holder. A vendor can claim its software is "Annex 11 compliant," but the regulatory obligation belongs to the company running the GxP process – not the SaaS provider behind it. That distinction matters when an inspector asks for evidence.
Geographically, Annex 11 covers the EU and EEA. It is also referenced by the UK MHRA post-Brexit, by Swissmedic, and by WHO prequalification – meaning a system aligned with Annex 11 typically meets expectations across most major regulated markets outside the US.
Also read: How to meet GMP temperature requirements
What does Annex 11 require?
EU GMP Annex 11 governs how computerized systems are validated, operated, and controlled in regulated pharmaceutical environments. The requirements cover the full lifecycle: from initial validation through ongoing operation, change control, and eventual retirement.
The core obligations are well established. Your system must be validated. Audit trails must capture who did what and when. Access must be controlled by role. Data integrity must follow ALCOA+ principles - Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, Available. These are not new ideas. What changes with each revision is the depth of expectation around each area.
For temperature monitoring specifically, Annex 11 requirements mean your monitoring platform carries the same documentation burden as any other GxP system. The software is in scope. The audit trail is in scope. The validation records are in scope.
Download an audit checklist for GMP
What do auditors look for in your temperature monitoring, mapping, and calibration processes?
Get an easy overview of the key areas regulators typically examine during GMP inspections.
What is changing in the Annex 11 2025 draft update?
The July 2025 Annex 11 draft is the most significant Annex 11 update in over a decade. The document grew from 5 to 19 pages, restructured into 17 sections – a signal of how regulator expectations have shifted since the 2011 version. The comment period closed on October 7, 2025, and the final version is expected in mid-2026.
The same release also introduced Annex 22 on AI-based systems and a revised Chapter 4 on documentation. Together, the three documents redraw the rules for digital compliance under EU GMP.
The Annex 11 changes that matter most for quality teams fall into four areas. Each one tightens an expectation that was previously handled by interpretation.
- Audit trail scope: Audit trails must now capture data creation events, not only changes and deletions. If a temperature reading is logged, that log event itself must be traceable.
- Periodic validation review: Validation status must be reviewed on a documented schedule. A one-time IQ/OQ/PQ is no longer sufficient without evidence of ongoing review.
- Cybersecurity and access management: Dedicated sections now address access controls, user authentication, and system security – previously covered only by implication.
- Penetration testing: Critical systems may require regular penetration testing. This is a materially new expectation for most pharma IT and quality teams.
Audit trail review frequency under the draft: monthly for high-risk systems, quarterly for routine systems, and always before batch release when temperature data supports the release decision.
How to get your monitoring setup Annex 11-ready
Getting your monitoring setup aligned with Annex 11 requirements does not require a full-scale project. It requires working through the right steps in the right order. Here is a practical sequence for quality teams assessing or updating their monitoring setup.
- Assess your current system against the draft scope. Map your monitoring software against the updated audit trail, access control, and validation review requirements. Identify where your documentation has gaps relative to the 2025 draft language.
- Confirm audit trail coverage for data creation events. Check whether your system logs the creation of temperature records, not only modifications or deletions. This is the most common gap under the updated standard.
- Document a periodic validation review schedule. Set a defined frequency – monthly for high-risk applications, quarterly for routine – and assign ownership. The review itself matters less than the documented evidence it occurred.
- Link calibration certificates to sensor records. Your audit trail is only as credible as the calibration evidence behind it. Certificates must be traceable to the individual sensor and the data it produced.
These steps apply regardless of which monitoring system you use. The logic is consistent with the ISPE Good Practice Guide and with how EU GDP guidelines approach risk-based qualification.
Where traditional workflows struggle to meet Annex 11
The gap between what Annex 11 requires and what traditional manual processes deliver is where audit findings come from. The table below shows what the daily workflow looks like with a fragmented, manual setup – and what it looks like when it is automated.
| Manual / fragmented approach | Automated, Annex 11-ready approach |
|---|---|
| Audit trails exported manually from separate systems, collated in spreadsheets | Automated audit trail exports, complete and timestamped, available on demand |
| Validation records stored in shared drives, version control unreliable | Validation status tied to the system, periodic review scheduled and documented |
| Access managed through generic logins or shared credentials | Role-based access controls with individual user accountability |
| Temperature excursion responses documented after the fact, inconsistently | Standardized excursion workflow with timestamped response trail |
| Calibration certificates filed separately, not linked to sensor data | Calibration certificates linked directly to sensors and audit records |
The manual approach does not fail because people are careless. It fails because the structure makes consistency nearly impossible at scale. Each manual step is a gap waiting to surface under inspection.
Eupry's system offers a highly user-friendly day-to-day interface. Eupry delivers a turnkey service enabling us to be more efficient in our work with compliance so we can deliver quality products to our customers.
Eric Clausen, Distribution Manager at Freja
How Eupry supports Annex 11 compliance
Eupry is built as a closed system, which matters for Annex 11 because closed system architecture simplifies accountability and limits the surface area for access control failures. Every user action is logged. Every record is immutable. Every calibration certificate is linked to the sensor that produced the data.
The platform provides ALCOA+-compliant records, automated audit trail exports, role-based access controls, and real-time excursion alerts with documented response workflows. For organizations subject to FDA oversight as well, a dedicated FDA 21 CFR Part 11 compliance module is available – covering digital signatures, complete traceability, and immutable audit logs for cross-jurisdictional requirements.
The 2025 Annex 11 update raises expectations around periodic validation review and cybersecurity. Eupry's validation documentation supports structured periodic review, and the platform is built to GAMP5 standards. You get a system designed for the regulatory environment you are operating in, not one you have to retrofit after the fact.
Frequently asked questions about Annex 11
Not sure where your monitoring setup stands against the 2025 draft?
Reach out and book a talk with one of our specialists to map your current system against the updated audit trail, validation, and access control requirements, and show you the gaps.
