Practical guides · Practical guide

GAMP 5 gap analysis: turning expectations into demonstrable improvements

A statement that your team follows GAMP 5 reveals little about how requirements, tests and changes connect in practice. Examine real activities and evidence against a defined edition of the guide, your procedures and applicable requirements. The outcome is a set of relevant gaps and actions. It does not confer general GAMP certification.

Table of contents

At a glance

How do you carry out a useful GAMP 5 gap analysis?

Select a specific process and identify the GAMP 5 edition used for the assessment. Distinguish industry methodology, applicable regulatory requirements and your own procedures. Examine actual transactions and evidence as well as templates. A useful finding states its basis, possible impact and suitable action. Prioritise gaps by their importance to the intended use. A percentage score does not establish that order.

  • GAMP 5 is an ISPE guideline and not a standalone legal requirement.
  • The evaluation basis and the considered system or process boundary must be explicitly defined.
  • An existing template does not automatically indicate a functioning application.
  • Actions should be based on actual root causes and impacts.

Which decision should the analysis enable?

Clarify what decision the analysis is intended to support. Is this about an existing CSV process, a specific implementation, or alignment across multiple sites? A company-wide review requires different inputs than a limited evaluation of test and review procedures.

Keep considered and excluded areas documented. Select appropriate processes that enable evaluation of actual application. The analysis must not broaden its limited scope into a general statement about all systems. Even a common procedure can be implemented differently at various locations.

Sources: [1] [2]

Three evaluation bases are separately documented.

Distinguish three bases for assessment. First, identify applicable regulatory requirements. Second, identify the GAMP principles and recommendations being considered. Third, identify approved company procedures and agreed objectives. State which basis supports each finding.

Not every deviation from a preferred method constitutes a legal violation. Conversely, an internal procedure may remain in place behind an existing requirement. This distinction clarifies the conclusion and prevents overreaching statements. Specific statements regarding the licensed guideline require access to the actually used edition. The focus of this article is the methodological review of one's own practice. For regulatory individual assessment, reference is made to the existing article on Annex-11/Part-11 gap analysis.

Sources: [1] [2] [3]

Further reading:

Verify the actual lifecycle based on activities.

Select cases related to boundary definition and implementation up to modification and operation. Allow personnel to explain the decisions they made and the evidence supporting those decisions. A clearly worded Standard Operating Procedure does not alone confirm whether a team can apply it or obtain the necessary information.

Add your actual SOP and a reviewed procedure to the inspection fields. The list links questions about the system lifecycle to Annex 11 reference points. Your methodological questions align with the publicly described ISPE focus areas; they do not reproduce verbatim requirements from the licensed GAMP text.

A useful audit pathway typically follows a requirement from risk and testing through to usage. Upon a subsequent change, it shall be assessed whether the original rationale has been appropriately maintained. Missing linkages must be specifically identified. The general statement "improve traceability" often leaves the root cause and significance ambiguous.

Verify the actual lifecycle based on activities.
Area to assessRegulatory ReferenceOwn methodological questionSearch within own procedure
Suppliers Annex 11 No. 3, 4.5 Is appropriate supplier knowledge being effectively utilized? Selection, Agreement, and Evaluation of Evidence
Risks Annex 11 No. 1 Does the justification reflect the actual testing depth? Risk assessment and acceptance
Requirements and Evidence Annex 11 No. 4.4, 4.7 Are changes to iterative work traceable? Specification, Testing, and Tracability
Tools Annex 11 No. 4.7 Are automated testing tools and testing environments adequately assessed? Purpose, Suitability Assessment and Controls
Change and Configuration Annex 11 No. 10 Is the effect being assessed instead of just a form? Change and configuration management
Operation Annex 11 No. 11, 13 Are genuine reviews and incidents incorporated into decisions? Periodic evaluation and incident handling
Archive and End of Use Annex 11 No. 7, 17 Are required data remain accessible despite system decommissioning? Data availability, archiving, and handover

Sources: [2] [4] [5]

Further reading:

How a traceable result is structured

A finding is understandable when the basis, observation, and potential impact are aligned. The table presents a reporting structure that you can adapt to your requirements. It does not establish official classification categories for findings.

Keep assumptions separate. If evidence is missing from the sample, initially remain open regarding whether the activity was performed and where it is documented. The result must demonstrate awareness of this knowledge boundary.

How a traceable result is structured
FieldContentWhy it is required
Basis Specific requirement, guiding principle or own regulation Prevents a mixed evaluation
Observation Actual considered procedure and documentation Makes the finding verifiable
Gap Difference between expectation and documented state Separates the problem from the general impression
Impact Possible consequences and remaining uncertainties Supports an appropriate prioritisation
Action Rational investigation and resolution of the root cause or gap Evaluates and implements
Closure Expected documentation and responsible decision Enables traceable and verifiable traceability

Sources: [4] [5] [2]

Risk-driven work involving mere category assignment differs

A software category can support the approach, but does not alone address the risks associated with a specific function. Verify that intended use, failure consequences, and existing controls are reasonably considered. Even a formally correctly named system type may still be inadequately assessed.

Similarly, extensive documentation does not automatically constitute a robust validation. Assess whether the records provide a credible indication of compliance with requirements and actual outcomes. The objective is a reasonable, clear approach. Neither an excessive number of pages nor a simplistic, arbitrary minimization of tests should serve as the sole criterion.

Sources: [1] [4] [2]

Example: Completed tests with unclear data linkage

Assuming a team documents numerous passed tests, the analysis still remains unclear regarding which configuration and which reference data underpin the results. The observation identifies this specific gap and evaluates the resulting limitations on conclusions drawn.

A possible approach is targeted supplementation of existing evidence, to the extent that the relationship can be demonstrably established. Where a reliable foundation is lacking, current supplementary testing may be required. Historical performance must not be fabricated.

Sources: [2] [5]

Prioritise actions based on root cause and actual significance

Distinguish an ambiguously defined procedure, lack of knowledge, and inadequately executed work. The same new template does not equally address these root causes. An appropriate corrective action may involve a procedure change, accompanied application, or specific additional validation evidence.

Name the responsible parties and justify the timelines. For relevant open risks, additional interim controls may be required. Plan also how the completion of the process can be clearly demonstrated and whether a performance evaluation is needed. A general percentage "GAMP maturity" does not replace these decisions.

Sources: [6] [4] [7]

Further reading:

What you can expect from an external analysis

An appropriate instruction shall describe evaluation criteria, sampling approach, discussions, report, and joint data review. Clarify whether regulatory classification, pure methodological assessment, or both is included. Additionally, it must be clearly defined who designs the actions and who actually implements them.

Could you provide an example of a test result and explain the rationale behind it? Can your team use this to make a decision and plan the necessary work? Standalone best-practice statements alone still offer limited insight into what has actually been assessed in your operation. The report should link specific evidence, open questions, and next steps together.

  • Objective and purpose of the analysis are explicitly defined.
  • State separately as the basis the law, guideline, and own rules.
  • Examine actual activities with original documentation.
  • Distinguishing cause, impact and open uncertainty.
  • Actions to ensure traceable results and accountability.

Sources: [8] [2]

Project experience and collaboration

Turn a gap into a finding the team can act on

We follow selected activities through requirements, testing and change records with your team. What do the existing records actually establish, and which technical question remains unanswered? A gap in a procedure calls for a different response from missing evidence for a single activity. For each finding, we discuss its basis, its possible effect and an appropriate response. A general maturity score would not give the team that information.

Frequent Questions on the GAMP 5 Gap Analysis

Is GAMP 5 legally mandated?

GAMP 5 is a professional ISPE guidance document and not a standalone regulatory requirement. Applicable regulatory requirements and internal procedures must be determined separately. The guidance may support an appropriate methodological approach.

Sources: [1]

Does a gap analysis confirm complete compliance?

A limited analysis contains only the conclusions justified by its scope and supporting evidence. It does not constitute automatic certification of all systems or processes. Verified areas, sampling results, and open questions must be clearly visible.

Does the analysis require access to the complete GAMP guideline?

A legitimate access to the selected edition is required for specific content comparisons. A public publication description does not substitute for a complete content review. General principles and regulatory requirements must be treated separately.

Sources: [1]

Is every deviation from a GAMP approach considered a GMP violation?

No. First, the specific basis for evaluation must be clarified. An alternative methodological approach may be appropriate if it demonstrably meets the actually applicable requirements. An analysis should justify this question rather than equating concepts.

Sources: [2] [1]

Can we only have our templates reviewed?

This may offer limited value, but it does not automatically demonstrate actual implementation. For a conclusion regarding the operational approach, appropriate real-world processes should be included. The conclusion must be relevant to the subject under investigation.

What should be the expected outcome?

Useful are specific findings based on root cause, observation, significance, and appropriate corrective actions. Assign responsibility, identify open questions, and specify expected closing documentation. A general maturity level alone provides limited guidance for handling.

Sources and review date

Primary source date: 17 October 2026. GAMP 5 is presented here according to its public ISPE classification as a guidance document; a comprehensive evaluation of licensed individual content is not claimed. The matrix and test list example serve as internal analytical tools. A specific gap analysis must define the actual version in use and the organization's own regulatory environment. EU GMP statements relate to human medicinal products (EudraLex Volume 4).

  1. ISPE: GAMP 5, Second Edition – Public Description of the GuidelinePublic publication description; no claimed full-text access to the paid guide.
  2. European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionHuman medicinal products – GMP; in particular, §§1–4, 7, 10–13, 16–17; specific application for each section.
  3. European Commission: EudraLex Volume 4 – current publication inventoryDate: 17.10.2026; Separate human medicinal products from veterinary medicinal products governed by the amended veterinary medicinal product regulations effective from 16.07.2026.
  4. ICH Q9(R1): Quality Risk Management, official text from the European CommissionRisk-driven decisions, appropriate formalities, and handling of subjectivity; own matrices are implementation proposals.
  5. European Commission: EU GMP Chapter 4, Documentation, January 2011 revisionControlled documentation and records; official EudraLex entry with original chapter.
  6. European Commission: EU GMP Chapter 1, Pharmaceutical Quality SystemQuality management, accountability, root cause analysis, CAPA and change control; no project budget allocation.
  7. European Commission: EU GMP Chapter 2, Personnel, effective from 16.02.2014Personal, role-specific training and assessment of practical effectiveness; official EudraLex entry with original chapter.
  8. European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP-related activities, suitability, responsibilities, agreements, and monitoring.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Bring a poorly explainable process and your evaluation basis together

Select a specific project or change where your team aims to improve documentation and traceability. In conjunction with the procedures employed, this enables the development of a clearly defined and focused analysis task.

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

Send a project enquiry Customer testimonials →