Regulations and compliance · Practical guide

Annex 15 vs Annex 11: linking qualification and CSV

The equipment is qualified and the supplier has delivered its software tests, but data migration remains unresolved. Annex 15 and Annex 11 address related yet different evidence needs at the boundary between engineering and IT. Plan their evidence together and state precisely what each test establishes.

Table of contents

At a glance

How do Annex 15 and Annex 11 work together in qualification and CSV?

Annex 15 addresses qualification and validation of facilities, equipment, utilities and processes and also refers to Annex 11 for computerised systems. Assess equipment function, application logic and data integrity separately, while sharing test records when appropriate. One test can support several requirements where its scope, criteria, result and links to those requirements are clear.

  • Qualified hardware does not validate every software function.
  • A shared test requires separate verifiable statements.
  • Only accept supplier documentation under appropriate conditions.
  • Units and interfaces should be part of the shared perspective.

1. The regulations complement each other

As of October 6, 2026, EudraLex Annex 15 is linked in the revision and Annex 11 as implemented since October 1, 2015 as amended in January 2011. This article looks at the use of human medicine GMP. Annex 15 explicitly states that computer-aided systems for the production of medicinal products should be additionally validated in accordance with Annex 11.

Define the object of each assessment. A balance must suit the intended measuring range. The application must associate a result with the right transaction. The manufacturing process needs its own evidence of suitability. None of these conclusions follows automatically from the others.

Sources: [1] [2] [3] [4]

2. Make objects and common transitions visible

Create a simplified representation of the physical process down to the quality-related decision. Include the measuring device, control, transmission, application, and used dataset. The interface between two boxes is often just as important as the function within a single box.

The following internal matrix serves as a planning aid. It does not require four separate project folders or a specific organizational model. Its purpose is to identify different questions before all stakeholders consider the same general test report as a complete justification.

Own control matrix for an integrated measurement procedure
SubjectEvidence questionExample recordOpen Boundary
Measurement device Is the measurement range and accuracy appropriate? Identity, calibration, functionality verification Does not establish that records were assigned correctly in the target system.
Control/Transmission Is the value and unit being passed correctly? Defined starting value and interface validation Don't say anything about the manufacturing process alone
Application Correct procedure, access, and further processing? Configuration, positive and negative functionality testing Does not replace device suitability
Overall workflow Does the intended use function continuously? Commonly understandable traceability justification Suitability applies only to tested conditions

Sources: [2] [3] [4]

3. A common expected outcome prevents both duplicate and missing tests

Annex 15 begins the qualification planning at the requirements level. Annex 11 links user requirements to risk and lifecycle considerations. A common requirements foundation can therefore be established, provided it fully and unambiguously addresses the relevant questions. "Measurement values are correctly transferred" would be insufficiently specific.

Precise attributes include value, unit, process identifier, rounding rule, and behavior during interrupted connections. Assign an appropriate reference to each statement. An existing test is not only linked but also evaluated for conditions and statement validity. This approach avoids unnecessary duplication and prevents the false impression of coverage based solely on similar test names.

Sources: [2] [3]

4. Purposefully utilize FAT, SAT, and manufacturer packages

Annex 15 allows, under appropriate and justified conditions, not to repeat individual functions already checked by the supplier at the site if transport and installation do not affect them. This is not a flat-rate takeover of any FAT protocol. Location configuration, connected systems and actual use may require additional evidence.

Verify version, measurement equipment, test environment, acceptance criteria, and documented results. A supplier audit may confirm device display, but it cannot validate customer-specific conversion within the LIMS. The scope of an enhancement arises from this gap. A supplier certificate and a signed cover sheet do not replace substantive evaluation.

Sources: [2] [3]

5. Example: correctly measured, incorrectly transferred

Example: A reference value of 20.000 g is compared to a displayed value of 19.998 g. For this individual exercise, a pre-defined allowable deviation of ±0.005 g was established. The difference is −0.002 g and falls within the established criterion. This is neither a general calibration limit nor a complete calibration verification.

The interface shall subsequently store the displayed value in kilograms. The correct value is 0.019998 kg. If the application instead stores 19.998 kg, the numerical value is 1,000 times too high. The equipment validation can still pass. Only through joint review is the error in the data pathway detected.

For actual review, you would link the original notification, the submitted dataset, and the target value using identical process identifier. A subsequently corrected target value alone neither explains the original error nor the scope of the correction.

Three claims about one measurement and their expected results
Test stepDefined expected resultFinding in this exampleInference
Display against reference 20.000 g ±0.005 g 19.998 g; Difference −0.002 g Single criterion met
Conversion to target 19.998 g / 1,000 = 0.019998 kg 19.998 kg Interface criterion not met
Assignment and Error Handling Process clearly defined; erroneous dataset not unobserved and further utilized. To separately assess the real-time test result A passing equipment test does not establish this

Sources: [2] [3] [4]

6. Do not shorten findings and stage release

When a predefined criterion is not met, the result must be evaluated and handled in a traceable manner. In the example, the cause, affected data sets, and process consequences should be investigated. Following a corrected recalculation, appropriate follow-up tests and a justified assessment of interdependent functions are required. A single green follow-up test does not automatically validate all previously generated data.

Annex 15 §2.10 addresses a formal release to the next qualification or validation stage. Its conditional continuation in the absence of substantiated significant impact does not constitute general authorization to use an inadequately assessed system for production. Distinguish between stage decisions, operational release, and, if applicable, product-specific decisions.

Sources: [2] [3]

7. Evaluate changes jointly, without doubling all efforts

A firmware update can affect measurement value formatting or transmission behavior. Conversely, a change in the target system may incorrectly interpret an unchanged device workflow. Therefore, when changes are made, evaluate the associated requirements and not merely the file or component that has been technically modified.

Previous relevant documentation may be considered in the evaluation. The extent of required repetition shall be based on the impact and remaining uncertainties. Engineering, IT, and process owners should also align on who is responsible for consolidating operational disruptions, maintenance activities, and relevant change insights. An organizational boundary must not result in unmonitored data transfers.

Sources: [2] [3] [4]

8. Checklist for joint validation planning

The most critical preparatory step is establishing a shared process understanding. The technical side identifies decisions and consequences of errors, engineering defines equipment requirements, IT specifies configuration and data pathways. QA supports the appropriate framework and documented assessment. Roles must be defined, but their names alone do not establish a universal approval framework.

Use this internal checklist prior to procurement, expansion, or reutilization of a test package. It complements specific project planning and does not replace a comprehensive evaluation of the relevant process.

  • Define the boundaries for device, equipment, application, and process as objects of validation evidence.
  • Track values, units, identifiers, and error cases through interfaces.
  • Specify requirements and criteria prior to the inspection.
  • Verify supplier certifications regarding version and conditions.
  • Assign common tests unequivocally to multiple statements.
  • Address unmet criteria and assess their impact.
  • Separate the release of productive use from the product decision.
  • Review changes and operational insights jointly and reassess collectively.

Sources: [2] [3]

Project experience and collaboration

Coordinate qualification with computer system validation

When equipment and software are introduced together, the equipment project team, process owners and QA consider both levels of evidence. Which test demonstrates a suitable technical prerequisite? Which shows the system working for its intended use? Overlapping tests may be reused where the result and documentation support both purposes. Site-specific conditions or additional data functions may need separate evidence. We organise documents around clarity and ownership. Conditional progression to the next qualification stage is distinct from the later decision on production use.

Frequently asked questions about Annex 15 and Annex 11

Does equipment qualification replace the CSV?

Not automatically. Annex 15 refers, for computerized systems, additionally to Annex 11. A qualified system may still possess an unverified interface or erroneous application logic. The evidence must actually support the relevant statement.

Sources: [2] [3]

Do we need separate records for the device and software?

No. Annex 11 and Annex 15 do not specify a universal requirement for splitting records into separate files. In the context of qualification, Annex 15, Section 2.5, permits appropriate combinations of documentation. Shared documents are justified when the objects, requirements, results, and authorizations remain clearly distinguishable.

Sources: [2] [3]

Can a test cover multiple requirements?

Yes, if its conditions, steps, and results provide a clear and traceable basis for the relevant statements. Simple multi-level linking is insufficient. In the measurement example, display, unit transformation, and process assignment must each be observable and verified.

Sources: [2] [3]

Do we need to perform each FAT at each location?

Annex 15 allows reasoned acceptance of suitable tests if transport and installation do not affect the relevant function. Location-dependent configuration and interfaces are to be assessed separately. The previous test report must be sufficiently meaningful for this decision.

Sources: [2]

Is a calibration a complete software test?

No. It pertains to defined metrological properties under specific conditions. The application may still incorrectly assign, convert, or store a correct value. Device and data pathway validations address different questions and must align with the intended workflow.

Sources: [4] [3]

Are the ±0.005 g in the example of this article a GMP specification?

No. In the example of this article, this is a criterion applicable only to this computational exercise. Real criteria require a reference to the measurement purpose, required accuracy, and appropriate technical foundation. The example illustrates a detection limit, not a calibration procedure.

Sources: [4] [2]

Can we proceed with production upon the existence of an open deviation?

The next qualification stage may be initiated conditionally under the conditions of Annex 15, Section 2.10, provided a documented assessment indicates no significant impact on subsequent activities. Non-compliant acceptance criteria shall be investigated and evaluated in the report (Section 2.8). This does not constitute general authorization for production operations. A separate decision by authorized personnel regarding the findings, implications, and necessary restrictions is required for the intended use.

Sources: [2] [3]

Must all testing be performed again after a interface correction?

The scope follows the documented impact assessment. In addition to the corrected calculation step, related functions and already generated data may be affected. Perform sufficient retesting to clarify the relevant uncertainties; an automated full retest is not a general derivation.

Sources: [2] [3]

What must we request jointly from Engineering and IT?

A clear description of the transition: source, value, unit, identifier, time reference, target, and behavior in error conditions. This includes appropriate configuration states and supporting documentation. Without this common view, both teams may consider their respective portions as completed, despite the overall chain being defective.

Sources: [3] [2]

Does Annex 15 apply equally to every active ingredient production facility?

The principle allows optional supplementary use for active substances without adding requirements to Part II. Assess applicability before applying individual provisions. This article concerns the defined GMP use for human medicinal products. Other contexts need their own scope assessment.

Sources: [2] [1]

Sources and review date

Source date: 6 October 2026. The referenced current guideline versions are pertinent. Tables and test cases are standalone work aids and do not constitute completed product testing.

  1. EudraLex – Volume 4 – Good Manufacturing Practice guidelinesRetrieval issue; Human and veterinary medicines separately handled
  2. EU GMP Annex 15: Qualification and Validation30.03.2015; Application 01.10.2015
  3. Annex 11: Computerised SystemsRevision 1, January 2011; applicable from 30 June 2011
  4. EU GMP Chapter 3: Premises and EquipmentApplication 01.03.2015

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify responsibilities and documentation for your operations

We support you in translating relevant requirements into practical decisions, appropriate evidence, and controlled operations.

  • 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 →