Table of contents
At a glance
How do you carry out an Annex 11 and Part 11 gap analysis with credible evidence?
Define the process, then identify the relevant Annex 11 and Part 11 source passages separately. Assess how each control works, what evidence supports that conclusion and which gaps remain. A common control may cover several requirements. Assign an owner and verifiable completion criteria to each action. A missing document does not prove a functional failure, and a supplier description does not prove that the control works locally.
- Evaluate efficacy and demonstration separately.
- Joint inspections require precise source anchors and a clearly defined scope.
- Prioritize based on potential impact and uncertainty, not on the number of open boxes.
Limit the inspection task before the first checklist is completed.
Maintain records of system version, location, operating environment, intended use, and relevant documentation. Which interface, user group, and archive pathway applies? Applicability is confirmed in advance for the specific process flow. If only Annex 11 applies, the Part 11 column is omitted; the method for control, verification, and corrective action remains unchanged. A joint evaluation assumes actual applicability of both regulatory frameworks.
Define the outcome as an assessment with a rationale, actions and any restrictions on use. Reviewing only the user interface would miss privileged changes, exports and outsourced backups. The review need only include an ancillary application if there is a reason to bring it into scope.
Annex 11: Complete breakdown as a standalone audit aid
The overview presents items 1 to 17 of Annex 11 as a framework for the audit assignment. The questions are concise summaries and neither replace the original text nor the assessment of actual applicability. Points that are not applicable are justified; the number of ticked lines does not reflect a compliance rate. Part 11 anchor points will be added separately where actual applicability is confirmed.
| Section of Annex 11 | Own entry question |
|---|---|
| 1 Risk management | Are validation and data controls justified based on risk? |
| 2 Personnel | Are roles, qualifications and access rights defined? |
| 3 Suppliers and Service Providers | Have suitability, agreements, and required information been resolved? |
| 4 Validation | Are the usage, requirements, testing, evidence, and deviations traceable? |
| 5 Data | Are required controls considered during data exchange? |
| 6 Accuracy verification | Have critical manual entries also been adequately verified? |
| 7 Data storage | Are data accessible, protected, and recoverable? |
| 8 prints | Are readable copies and release-related amendment information available? |
| 9 Audit Trails | Are risk-based change documentation, rationale, and review considerations addressed? |
| 10 Change and Configuration Management | Are relevant changes managed? |
| 11 Periodic Evaluation | Is the existing appropriate state regularly assessed? |
| 12 Safety | Are access and required personal data action records adequately controlled? |
| 13 incidents | Are incidents assessed and critical root causes addressed as the basis for CAPA? |
| 14 Electronic Signatures | Are the effects, permanent association, and timing considered during their use? |
| 15 Batch release | Is the intended authorization and signature taken into account for a recorded QP certification and release? |
| 16 Business continuity | Are appropriate alternatives in place and evaluated for required system availability? |
| 17 Archiving | Will availability, readability, integrity, and retrievability of relevant changes be maintained? |
Sources: [1]
Translate the Norman into a verifiable control target
For each point, specify what should be prevented or reliably detected in the process. Access control is thus made concrete: a former employee must not be able to modify required records using the previous access rights. Data copying means: the required contents must remain in the agreed output format, fully intact and analyzable.
Link this objective to the relevant individual responsibilities. Annex 11 §12 and Part 11 §11.10(d), (g) have points of overlap but are not word-for-word equivalent requirements. Additional responsibilities apply to electronic signatures. A common technical implementation may be beneficial; however, the assessment must clearly demonstrate which specific elements it actually covers.
Distinguish Function, Configuration, and Evidence
A supplier's description first proves an offered function. A configuration export describes a concrete status. A meaningful test or proof of operation shows behavior under named conditions. These documents can complement each other; no one automatically replaces the others.
Evaluate supplier documentation based on its actual scope of coverage. If the version, configuration, operating model, and testing objective align, existing results may be relevant. In the absence of customer-specific role-based access controls, this remains open. Additionally, indicate whether a deviation was observed or whether only the evidence for evaluation is missing. This impacts the next appropriate action step.
Work with a completed detection matrix
Example: An electronic batch process falls under both regulatory domains in the assumed human medicinal product manufacturing environment. Individual accounts, an electronic data set, a report export function, and a specifically intended electronic signature are utilized. The following observations are intended use cases for a workflow assistance feature.
| Requirement and Control | Present evidence in the example | Gap | Next action |
|---|---|---|---|
| Annex 11 §12; §11.10(d),(g): Changes permitted only through authorized accounts | Role list and successful positive test for editors | Access revocation was not verified; effect unknown | IT deactivates test account; the responsible specialist verifies login and modifications upon withdrawal. |
| Annex 11 §9; §11.10(e): relevant change traceable | Change from 8.0 to 8.4 with user and time visible | In the test, the rationale for the GMP-relevant change is missing | Correct configuration and workflow; re-evaluate the affected change process. |
| Annex 11 §8; §11.10(b): appropriate readable and electronic copies | PDF shows final value 8.4 and Record-ID | The PDF alone does not contain all the information required for the intended review. | Determine an appropriate additional data/historical format and compare content against the original. |
| Annex 11 §7.2; §11.10(c): Retention and Availability of Records | Security job reports success | No appropriate documentation available for restoration at the considered stage | Review covered supplier certificates; define remaining restoration testing. |
| Annex 11 §14; §§11.50, 11.70: Intended signature linked to record | Screen displays name, time, and significance | Release after export has not yet been assessed | Review the representation and binding at the relevant export; do not accept a mere signature graphic. |
Determine the priority from the possible sequence
In the example, a detected missing change justification must be handled differently from a yet-unsubmitted restore report. Both situations may be relevant, but the information carries different implications. Assess the data and decision impact, existing controls, and uncertainty. An unverified critical path requires a robust decision; it cannot be offset by numerous inconsequential minor issues.
A calculated compliance rate based on assessed points and open actions would still not yield a meaningful release statement. A small number of open items could pertain to a critical process. Therefore, define who assesses the remaining uncertainty and whether usage must be restricted until clarification is achieved. A rigid QA signature for each action is not derived from this.
Define the release at the planning stage of the corrective action.
A measure such as "improve audit trail" is too vague. Describe the existing deficient state, the responsible role, and the required evidence of closure. Changes to configuration or procedures follow the predefined change process; relevant impacts on other functions are assessed concurrently.
A schedule is an organizational agreement, not a mandatory or automatically excluded standard period as defined in Annex 11 or Part 11. Similarly, a full retest is not automatically required nor automatically excluded. The scope is determined by the modified component and its dependencies.
| Finding | Closure criterion | Responsibility in the example | Boundary |
|---|---|---|---|
| Reason for change missing | Test change includes starting/updated value, assignable user, time, and justified reason for change; review can evaluate it. | The user initiates the process; the qualified reviewer evaluates the evidence. | Successful test of this case does not prove all audit trail functions. |
| Export incomplete for intended review | The fixed release package includes the required record context and associated history; the reconciliation confirms content and assignment. | Records - Responsible party defines content; IT provides output; authorized decision-maker accepts the result. | Not every export needs to contain all technical data; the intended purpose is decisive. |
Treat FDA enforcement policy as its own evaluation level
The FDA Guidance from 2003 addresses Enforcement Discretion with respect to certain Part 11 requirements relating to validation, audit trails, retention, and copies. It does not constitute a waiver of the regulation. Requirements from predicate rules remain in effect; other Part 11 controls are not generally exempted.
Therefore, clearly specify which normative text, which FDA interpretation, and which EU GMP requirement underpins the decision. Where there is dual applicability, a FDA implementation statement cannot substitute for a missing Annex 11 control. Similarly, a risk-based justification should explain the specific evidence pathway, rather than merely invoking the term "risk-based" as an exception.
Keep the analysis feasible and manageable for a small team
Start with the decision-critical data pathway and supplement it with relevant parallel pathways. Assign a responsible individual to maintain the evidence list and designate qualified decision-makers for the affected processes. Role distributions may vary by organization. It is essential that no open action item becomes a permanently overlooked list point.
After completion, a comprehensible link remains between finding, modification and evidence of efficacy. Keep the original context of findings so that subsequent changes do not reintroduce the same gap.
- Scope and dual applicability are documented.
- Every result has a precise reference standard and a clear control objective.
- Existing records are clearly referenced and evaluated for coverage.
- Observed errors and lack of evidence are distinguished.
- Risk and, if applicable, usage limitations are clearly justified and decided.
- Measures shall have ownership, defined timeline, and verifiable completion criteria.
- The closure demonstrates the relevant impact and takes into account subsequent modifications.
Project experience and collaboration
Identify the decision needed for each gap
Link every gap to the actual use of the system. With the process owner, QA and IT, we might follow an electronic approval and map its controls to each applicable requirement. For every open question, record the missing evidence and its potential consequence. A focused check may clarify an ambiguous description. An uncontrolled critical function needs an effective action or a restriction on use. The assessment determines priority and closure, regardless of how many other rows in the table are green.
Frequent Questions on Annex-11/Part-11 Gap Analysis
Do we need to perform two separate gap analyses for Annex 11 and Part 11?
Is a missing test report already a proven system error?
Can a manufacturer's checklist suffice as a complete justification?
Only to the extent that their specific statements and supporting evidence actually cover the intended use. Verify version, configuration, responsibility boundaries, and evidence quality. A general affirmation of Part 11 support does not demonstrate either your role assignments or the content of your customer-specific export.
Sources: [1]
Should every open question be classified as a critical finding?
No. Distinguish the potential impact, existing controls, and the nature of the uncertainty. A detected error in a critical data pathway may carry different weight than the absence of a reference to previously established evidence. Document this rationale clearly and transparently.
Sources: [1]
How do we determine the minimum number of samples?
Can we proceed with the work despite open items?
Use of a system despite open action items is only justified if the implications for the intended use have been assessed and formally approved by the authorized party. Evaluate each relevant finding rather than merely counting them: effective transition controls and limited usage may constitute part of the solution in specific cases; uncontrolled critical data pathways are not acceptable. Annex 11, Section 4.2 requires reporting of validation deviations. Ensure that decisions, supporting evidence, limits, and remediation timelines are clearly documented and traceable.
Is a successful backup job sufficient as evidence of a restore?
A successful backup run and proven restore capability are distinct assertions. Annex 11 §7.2 also addresses restore and verification of backup data. Assess which existing records cover the specific operational period and identify any targeted additional documentation that may be required.
Sources: [1]
Must every correction be fully revalidated?
Can a finding from the FDA Guidance of 2003 close an audit trail?
When does a corrective action become considered closed?
Sources and review date
Source date: 6 October 2026. The eCFR display was consolidated up to 2 October 2026. EU references pertain to Human Medicinal Product GMP and the listed Annex 11 version from January 2011; draft versions are not considered enforceable requirements. Examples and matrices are internal reference tools.
- EU GMP Annex 11: Computerised SystemsRevision January 2011, Effective Date 30.06.2011; listed in the human medicinal product section on 06.10.2026. Relevant provisions: Principle; §§1–4; §§5–10; §§11–17
- 21 CFR Part 11 — Electronic Records; Electronic SignatureseCFR: Title 21 consolidated through 02.10.2026; Title 21 last amended on 30.09.2026. The display does not constitute a claim of a Part 11 amendment on this date. Citations: §11.1(a)–(e) and sector-specific exemptions (f)–(p); §11.2; §11.3(b)(4),(5),(6),(7),(9); §11.10(a)–(k); §11.30; §§11.50, 11.70, 11.100, 11.200, 11.300
- FDA: Part 11 — Scope and Application, Original-PDFOriginal cover page August 2003, Pharmaceutical CGMPs; Contains nonbinding recommendations. Currently listed by FDA as Final. Reference locations: I. Introduction, printed pages 1–2; III.A, page 4; III.B.1–2, pages 5–6; III.C.1–5, pages 6–8
Sources checked: .
Applicability and targeted review of evidence
We support you in professionally categorizing your gap matrix, prioritizing outstanding evidence, and ensuring corrective actions are verifiable and completed. The starting point is your specific process together with its existing controls.
- GAMP 5 consulting →
Understand how GAMP 5, EU GMP Annex 11 and 21 CFR Part 11 apply to your systems. We translate the relevant requirements into proportionate validation work and evidence your team can defend in an audit.

