Regulations and compliance · Practical guide

Annex 11 system descriptions: content and level of detail

A technical diagram can be accurate without explaining how an input becomes reliable quality information. For a critical GMP system, connect application, infrastructure, data flows and protection measures. A laboratory interface example shows which details help assess changes without reproducing complete manuals or test records.

Table of contents

At a glance

What should the Annex 11 description of a critical system explain?

Annex 11 section 4.3 describes an up-to-date description of critical systems covering physical and logical arrangements, data flows, interfaces, technical prerequisites and security measures. Define the application boundary and show where data originate, change, are reviewed and are used. Refer to controlled detailed documentation. A system description explains architecture. It does not replace user requirements or evidence that controls work.

  • The specific level of description in § 4.3 relates to critical systems.
  • A data flow requires meaning in the process, documentation, and accountability.
  • Status, references, and reasons for changes are equally important as the initial drawing.

1. Criticality and purpose prior to scope definition

Annex 11 distinguishes between the inventory of relevant systems and the detailed description of critical systems. Therefore, assess first the importance of the considered system for product quality, patient safety, and data integrity. The number of users or the server size does not answer this question.

The description should subsequently support concrete decisions: which components are affected by an update? Where can a result be modified? What dependencies are impacted in the event of a failure? For this, the technical department, QA, and IT require a shared understanding. A document that merely reproduces the manufacturer's brochure neither explains your configuration nor the actual workflow.

Sources: [1] [4]

2. Practically define the system boundary

State the intended use, location, relevant authorities, and the considered software version. Distinguish between production use, test environment, and historical read access, where applicable. Shared services may lie outside the immediate application boundaries; their impact on the application must remain evident.

A directory service can provide user authentication, while the application itself determines which roles are authorized to modify data. A central repository can store reports without requiring substantive review or release. Such distinctions help assign responsibility appropriately. A drawn line represents a methodological definition and must not obscure real influence capabilities.

Sources: [1] [3]

3. Integrate physical and logical views

The physical view identifies where components are operated and how they are interconnected. The logical view explains services, authorizations, processing, and data relationships. Both can be combined into a clear, consolidated presentation with supporting tables. Annex 11 does not require the use of a specific programming language or strictly separated files.

The table serves as an internal reference tool, identifying which information supports a relevant validation question. Secrets such as passwords should not be included in widely distributed documentation. Security-critical documentation can be protected and referenced, provided that authorized personnel can access and evaluate it in the required context.

Own work aid: Description element and inspection purpose
ElementSpecific descriptionSo that the question is prepared
Application Instance LAB-P; Result verification Which functions does this instance support?
Platform Application service and database, referenced status What prerequisites support the operation?
Identity Central Registration; Roles in LAB-P Where is actual access actually restricted?
Storage Results database and linked report Where is the complete relevant record located?
Data transfer LAB-P sends material status to ERP-P What significance must remain in the objective?

Sources: [1] [2]

4. Track data from origin to use

For each data flow, describe the source, what the data represents, the relevant identifiers and how the recipient uses it. Identify automated processing, manual transfers and human decisions. Temporary storage and intermediate manual steps can also affect traceability.

PIC/S PI 041-1 identifies the examination of the data flow as a useful approach to data risks. From your description, a specific question can be derived: Can another person trace a selected record through the process using the document? If an export loses its original identifier, a technically correct network path alone will not suffice.

Sources: [1] [3]

5. Example: Laboratory status reaches the material management system

Suppose LAB-P assesses sample P-041 for material batch M-018. After the specified process decision, it sends status F to ERP-P. In this example, F means released for the intended material use. It does not mean legal certification of a medicinal product batch by the Qualified Person.

The description must explain how the sample, batch, and decision remain linked, and what occurs in the case of missing assignment. The table represents a fully completed example of what is required. It does not claim functionality of a specific product. Whether the controls depicted function within your system would need to be independently verified.

Example: Data flow with pre-defined expected value
StageData and ProcessingAlarm or error response
LAB-P P-041 belongs to M-018; Decision F Assignment and decision makers remain identifiable
Transfer M-018 + F + Decision Reference Process only fully assigned messages
ERP-P F is assigned to a defined intended use Authorization is exclusively valid for M-018.
Failure scenario Message contains unknown batch M-999 Do not release a similarly named batch as a substitute
Repetition Identical decision to be retransferred Do not invent a new independent decision.

Sources: [1] [3]

6. Security measures relating to their effect

Carry out an assessment of which entities are responsible for preventing or detecting unauthorized changes, loss, or misidentification. This may include roles, protected storage, controlled configuration, logging, and recovery procedures. The description should clearly indicate which layer bears control responsibility and who administers that control.

"Access is protected" remains overly ambiguous. For example, verify whether an application user could modify the same data through a file path that the user interface only displays in read-only mode. The presence of existing security measures does not automatically ensure that restored data aligns correctly. Describe the relevant dependencies without inferring absolute protection against data manipulation from a security function.

Sources: [1] [3]

7. Link requirements, descriptions, and tests

The URS defines the technical intent, the description outlines the specific design, and the validation provides evidence of compliance with selected criteria. These objectives can be integrated within a structured documentation model. There is no substantive benefit in independently maintaining the same interface table across multiple files.

Use clear references: A requirement for correct batch assignment refers to the described data transfer and its review documentation. The test report can then indicate which version and environment were validated. Changes remain assessable, as they do not require reconstruction from scattered screenshots to determine the system connection at the time.

Sources: [1] [2]

8. Current operational description maintained

Anchor the review of currency in changes and periodic assessment. New interfaces, modified data repositories, role models, or operational responsibilities may require adjustments. A purely editorial change in reference links may be handled differently than a new data pathway; the distinction should be clearly justified.

Start with an existing system and provide verifiable information. Explicitly mark unconfirmed assumptions and clarify them at actual operational use. A neatly designed diagram does not serve as evidence for an unknown state. The checklist supports the technical completion of the document; it does not replace the evaluation of open risks.

  • Criticality, intended use, and specified instance identified.
  • Clear physical and logical structure.
  • Data pathways including manual transfers and relevant storage locations explained.
  • Interfaces described with professional identifiers and intended use.
  • Safety measures and technical requirements assigned.
  • Status, ownership, detailed references, and open assumptions reviewed.

Sources: [1] [2]

Project experience and collaboration

Make the system description usable for operations and testing

We write the system description for the people who will use it. Where does the application run, which data paths matter and who owns the handovers? IT and process owners define a manageable system boundary. One application may need a concise overview with clear references. Several connected services need explicit mapping of components, interfaces and operating responsibilities. We test the description against a change or incident to see whether an owner can find the information needed for a decision.

Frequently asked questions about System description

Is a system description required to be equally detailed for each relevant system?

Annex 11 § 4.3 explicitly links the detailed description to critical systems. The appropriate classification and level of detail must be justified. For other systems, clear documentation may also be appropriate; however, this does not result in an identical scope for every application.

Sources: [1]

Does the manufacturer's handbook suffice?

It can explain product functionalities and prerequisites. Nevertheless, the actual instance, configuration, usage, and integration must remain identifiable. Therefore, assess which sections of the handbook are applicable and which operational enhancements are required, rather than rewriting everything from scratch.

Sources: [1]

Do we need to list every server name in the main document?

Not necessarily required there. A controlled reference to a current technical overview can be valuable. What is essential is that the described system status remains unambiguously resolvable. A link to an indeterminate collection of changing files scarcely fulfills this purpose.

Sources: [1] [2]

Are paper records included in the representation?

If they are part of the relevant data pathway, their role should be clearly identifiable. Chapter 4 also addresses hybrid documentation forms. For example, describe how a signed paper record is linked to an electronic dataset and which step utilizes the information.

Sources: [2] [3]

Do we necessarily require a graphical data flow diagram?

The form is not prescribed. A well-structured table may be sufficient for a clear and manageable workflow. When multiple interfaces are involved, a diagram often aids orientation, but it requires clarified data and directions to go beyond a simple technical network sketch.

Sources: [1] [3]

How detailed must security measures be described?

For example, describe application roles and the influence of administrative access. Sensitive technical details can be referenced protected. Complete passwords or access keys do not belong in the document.

Sources: [1] [3]

Does the description replace a validation?

No. It makes setup, boundaries, and data pathways understandable and thus supports risk-based evidence planning. Whether an assignment, authorization, or error handling actually functions must be demonstrated through appropriate evidence. A plausibly designed control is still not a validated control.

Sources: [1]

When must the system specification be updated?

If the described state or its interpretation is altered, this includes new data sources, different storage locations, or changed responsibilities. Specify in the change management process how document impacts are assessed; not every change requires a complete re-development.

Sources: [1] [2]

Who should verify the information?

The IT and system ownership areas provide different components. QA evaluates alignment with the quality process. Key factors are appropriate technical expertise and clearly defined responsibilities. A signature from a non-involved party does not render an unverified technical assertion reliable.

Sources: [1]

How should we handle undocumented legacy interfaces?

Identify the gap and examine the actual data path controlled. Use configuration, operational proofs and appropriate observation. Avoid uncontrolled interventions in productive data. Until clarification, the description should leave uncertainty visible and not pretend complete knowledge.

Sources: [1] [3]

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.

  1. EU GMP Annex 11: Computerised SystemsRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. Citations: Principle; §§1–2, 4.3–4.4, 4.7, 5, 7, 10–12, 15
  2. EU GMP Chapter 4: DocumentationRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. References: §§4.1–4.5, 4.10
  3. PIC/S PI 041-1: Good Practices for Data Management and IntegrityPI 041-1, 01.07.2021; Access date 07.10.2026. Citations: §§9.1.2, 9.1.5–9.1.6, 9.4–9.5
  4. 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 medicinal products / Annex 11 / Chapter 4
  5. 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: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

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.

Send a project enquiry Customer testimonials →