Table of contents
At a glance
What information belongs in an up-to-date Annex 11 system inventory?
Annex 11 section 4.3 calls for an up-to-date inventory of relevant systems and their GMP functionality. Start with the actual process and record identifiable applications, responsibilities and relevant dependencies. Link supporting evidence rather than duplicating it in the inventory. Determine useful additional fields and update triggers from your systems. The section does not prescribe a fixed table format.
- GMP function and actual usage make an entry understandable.
- Dependencies must be identifiable without requiring explanation of any server for internal use.
- An inventory remains only valid when changes trigger a responsible change control process.
1. What the inventory requirement actually encompasses
The framework discussed here is the EU-GMP guideline for computer-aided systems in the production of medicinal products for human use. On 7 October 2026 EudraLex continues to run Annex 11 January 2011. The inventory requirement concerns relevant systems including GMP functionality. The subsequent sentence on a detailed system description is explicitly related to critical systems.
Therefore, for practical implementation: Ensure the entry point is clear and facilitate progression into deeper levels. An inventory does not need to include all technical attributes nor must it justify every validation decision on its own. However, it should indicate where such decisions are made and which unresolved entries still require further review.
2. Processes to be reviewed rather than evaluating licenses alone
Walk through the actual workflow with the department: where are the data generated, who processes them further, and what outcome leads to a decision? During this review, inquire about files, local computers, device programs, and manual transfers. Procurement and IT inventory provide useful starting points, but do not necessarily capture every internally developed analysis.
A spreadsheet may calculate a release-ready result, even though it does not appear as acquired software. Conversely, a large enterprise application within the considered domain may support only scheduling functions. Classification requires a specific use case. Unclear usage is flagged as open and assigned to a responsible individual for clarification; it does not automatically disappear from the register.
3. Which information renders an entry valid and actionable
As a recommended auxiliary tool, a stable key per isolated system is advised. Include a clear designation, location, or usage area, GMP function, responsible role, operational status, and references to evaluation and documentation. When multiple independently operated instances exist, it must remain clearly identifiable which configuration the entry pertains to.
Not every additional detail value is permanently included in the inventory. For changing technical components, a well-kept reference to the IT documentation can be better than a second, fast-adjusting copy. It is crucial that the reference actually leads to the correct inventory and is maintained even when renaming or organizational change.
| Information | Example | Question addressed by this answer |
|---|---|---|
| System identification | SYS-017 / laboratory analysis | Which specific system are we referring to? |
| GMP Function | Calculates the reported active ingredient content | Which quality decision depends on this? |
| Usage and Responsibility | Labor Location North / Laboratory Director | Who verifies the actual use? |
| Dependencies | Waagenexport, file storage, identity service | What changes could contribute? |
| Reference to evidence | Evaluation B-017; Description D-017 | Where are the rationale and detailed status located? |
4. Assign infrastructure and interfaces appropriately
The principle of Annex 11 distinguishes between validated applications and qualified IT infrastructure. For the register, this does not mean that you should manage two separate, disconnected worlds. A laboratory application may depend on the rights management directory service and a data storage service for the availability of its data. This integration remains relevant, even if both services support multiple applications.
Avoid both the blanket exclusion of shared services and the overly repetitive listing of all components in every line. A referenced dependency list is sufficient when direction and purpose are clearly understandable. For interfaces, first describe source, target, and the subject matter; detailed mapping rules should be included in the appropriate system or interface documentation.
5. Example: three applications, different analytical questions
An operation uses a laboratory application, a calculation template, and a document management system. The calculation template manually imports a value from the laboratory report. All three systems share the same identity management; the template is stored on a central repository. The identifiers in the table are example values.
The practical benefit does not lie in achieving the highest possible system count. The inclusion of the submission highlights an otherwise easily overlooked transition: the accuracy of manual data entry and the approved version of the submission must be evaluated within the appropriate procedure. A joint registration alone neither verifies this control nor confirms the technical suitability of the calculation.
| entry | Function and Interconnection | Documented need for clarification |
|---|---|---|
| SYS-017 Laboratory Application | Generates result report; central registration | Assessment and description of existing items, status to be verified |
| SYS-018 Calculation Template | Manually records results; central storage | Clarify responsibilities, version control, and data entry validation |
| SYS-019 Document Management System | Provides approved work instruction | Verify the correct revision is used |
| INF-003 Identity Service | Common technical interdependence | Ensuring reference to proof of rights and operating documents |
6. Ensure status is maintained such that gaps remain visible
A single "validated: yes" field may mask significant differences. Separate the evaluation of whether a system is actively used in production, the current assessment status, and whether critical tasks remain unresolved. The specific status logic represents a design decision; EU GMP Annex 11 does not prescribe a universal traffic light or a fixed number of states.
Therefore, an unfully assessed legacy system is operated with its actual usage and the open task remains active. Acceptance does not constitute release. For decommissioned systems, visibility is retained regarding where required data and access rights continue to exist. Do not remove the reference that enables future investigations to access historical data environments.
7. Connect care to real changes
Who reports changes and who provides professional verification of the entry? Typical triggers include the introduction of a new interface, an additional site, changed usage, a different operating mode, or decommissioning. A version update does not necessarily require modifications to all text fields; however, its impact on the described system must be assessed.
Link this task to existing procurement, change, and review processes. This ensures no isolated calendar test remains blind between two dates. During periodic reviews, the list of actual users, contracts, and operational information can be cross-checked. The scope and frequency of these reconciliations should align with the dynamics of change.
8. Start with a verifiable sample segment
For a growing inventory, a common walkthrough through a critical process is often more efficient than immediately dispatching a lengthy blank table. QA provides the quality decision, the functional department carries out the actual work, and IT manages the technical integrations. Open items are assigned a responsible party and a clear progress status.
The following checklist supports this initial approach. It does not guarantee completeness. The output should represent a usable register excerpt, enabling a third party to identify the relevant applications and understand the next required evidence. Only after this can it be determined whether additional fields provide genuine value or merely generate unnecessary administrative burden.
- GMP process and applicable applications jointly referenced.
- Local files, auxiliary programs, and outsourced services explicitly reviewed.
- GMP responsibilities and accountability for each entry clearly described.
- Essential dependencies and document references for accessibility checked.
- Visible open assignments with processing responsibility.
- Approved, shutdown, and review triggers agreed.
Project experience and collaboration
Reconcile the system inventory with actual use
We compare your existing inventory with the applications and data flows actually in use. This can reveal missing systems and unclear boundaries between applications, local files and shared services. At a small organisation, a maintained spreadsheet may be easier to use than a new tool. Several sites need clear identifiers and assigned responsibility for upkeep. We keep pending assessments visible so legacy systems with limited evidence stay in scope.
Frequently asked questions about System inventory
Is the system inventory the same as an IT asset list?
No. An asset list typically describes devices, licenses, or technical components. The GMP inventory must demonstrate the relevant function within the process. Existing data may be reused and linked, but professional usage and system boundaries should be clarified and enhanced accordingly.
Must each Excel file have its own entry?
Not solely based on file format. Assess functionality, usage, and organizational boundaries. A guided template with numerous generated records may be captured differently than several independently maintained calculation applications. The rationale must enable recognition of the actually controlled inventory.
Do pure commercial applications fall within the scope?
Assess their actual impact and dependencies. An "commercial" label does not automatically exclude GMP relevance if, for example, relevant master data is transmitted. A clearly non-relevant application does not need to be artificially justified as part of a GMP system.
Sources: [1]
Who should own the inventory?
The specific role is defined by your operation. It is prudent to assign a named care responsibility, supported by technical validation from process or system owners. IT alone may not be fully aware of all local usage patterns; QA alone may not have full knowledge of all technical dependencies. Collaboration must function effectively.
Sources: [1]
Does every system require an immediate detailed description?
The corresponding paragraph in Annex 11 § 4.3 refers to critical systems. The current inventory of relevant systems must be distinguished from this. Additional descriptions may be technically appropriate but should not be presented as a uniform requirement for every entry.
Sources: [1]
How do we capture jointly used cloud services?
Can an unassessed legacy system remain in inventory?
Yes. A GMP-related legacy system must be included in the inventory, even if its assessment is still pending: Annex 11, Section 4.3 requires a current list of all relevant systems. Maintain a record of the actual status, open questions, and responsible handling. Inclusion in the inventory is neither a usage authorization nor a substitute for missing evidence.
Does Annex 11 require an annual inventory?
Section 4.3 requires a current inventory but does not specify an annual unit frequency. Establish appropriate review triggers and additional checks in alignment with the frequency of changes. A routine annual review alone is insufficient as a method if significant changes are inadvertently overlooked between reviews.
Sources: [1]
Can the inventory be maintained in a table?
The format alone does not determine suitability. Access, change control, accountability, and actionable references must align with the intended use. Additionally, assess whether the implemented solution itself processes sensitive information or automates decisions; in such cases, its own control requirements must be evaluated.
What do we start with when dealing with a large number of open entries?
Select a relevant process, jointly walk through its data pathway, and address specific ambiguities on a risk-based basis. Use the derived definitions consistently throughout the remaining documentation. The processing order shall make visible open systems without obfuscating their current state.
Sources and review date
Source date: 07.10.2026. The relevant area here is human medicinal product GMP. EudraLex incorporates Annex 11 and Chapter 4 as of January 2011; the consulted draft from 2025 is not considered a current regulatory requirement. The completed examples and tables are internal work aids and do not constitute official template documents.
- EU GMP Annex 11: Computerised SystemsRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. References: Principle; §§1–2, 4.3, 10–11, 17
- EU GMP Chapter 4: DocumentationRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. Citations: §§4.1, 4.5, 4.10
- PIC/S PI 041-1: Good Practices for Data Management and IntegrityPIC/S PI 041-1, 1 July 2021, accessed 7 October 2026. Relevant sections are 9.1.1–9.1.6, 9.1.10 and 9.3.
- European Commission: EudraLex Volume 4Status as of 07.10.2026: Human medicinal product section implements Annex 11 January 2011 and Chapter 4 January 2011; Access date 07.10.2026. Relevant provisions: Human medicines / Part I / Annex 11
- European Commission: Consultation 2025 on Chapter 4, Annex 11 and Annex 22Status as of 07.10.2026: closed; 07.07.–07.10.2025. Occurrences: details; revision of Annex 11; links explicitly marked as draft guidelines. Serves solely for status demarcation and is not considered an authoritative source of requirements.
Sources checked: .
Address the specific control and verification requirements
Daniel Herrmann Consulting supports you in adapting this procedure to your system portfolio, evaluating gaps, and preparing appropriate validation evidence. The scope and level of involvement are determined by your actual process.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

