Practical guides · Practical guide

Validation master plan vs system validation plan

Every new system has a detailed plan, but priorities, shared rules and responsibilities remain unclear. A validation master plan and a system-specific plan can connect portfolio decisions with the evidence required by an individual project.

Table of contents

At a glance

How does a validation master plan differ from a system validation plan?

A validation master plan or equivalent documentation describes the overall strategy, responsibilities and organisation of qualification and validation. The system validation plan defines scope, risks, evidence, criteria and execution for a specific project. Align those levels. A file name does not establish complete planning, and repeating thirty pages of general policy rarely helps an individual project.

Two planning levels with different decisions

Annex 15 describes the organization of qualification and validation activities within a validation master plan or an equivalent appropriate documentation. Annex 15 Section 1.5 specifies the minimum contents of the master plan or an equivalent documentation. For large and complex projects, separate validation plans may improve clarity (Section 1.6). For computerized systems, the specific framework from Annex 11 is additionally applicable. The specific document architecture depends on the quality system, scope, and complexity. This does not imply a general waiver of overarching planning, nor does it require the creation of a comprehensive master plan for every IT project.

The overarching level addresses: How do we manage the portfolio and under what principles do we operate? The system level answers: What do we specify for this application and this site? Before creating a new file, review existing quality documentation. A well-integrated approach can function with references. However, information must be retrievable, current, and formally approved. A scattered set of unbinding notes does not constitute equivalent planning.

Sources: [1] [2]

What belongs at the overarching level

Describe the organisation, roles, basic strategy, and control of relevant activities. Integrate the relationship with the system inventory, risk assessment, change control, and regular review. Common rules for supplier verification, document management, and deviations can be centrally defined. The master plan should provide guidance without redundantly repeating technical details of individual projects.

For multiple systems, dependencies and priorities are made visible. A shift to an ERP system can impact laboratory integration, warehouse processes, and archiving. Planning must demonstrate which decisions are interrelated. Consider capacities and responsibilities. A list of all systems without sequence or next steps is more akin to inventory than a guiding plan. The specific form represents a methodological decision and must remain actionable within the organization.

Sources: [1] [3]

What the System Validation Plan must specifically define

The system specification outlines the intended use, system boundaries, relevant risks, validation strategy, and acceptance criteria. It defines which supplier documentation will be utilized, which in-house assessments will be performed, and how results will be evaluated. Responsibilities, prerequisites, and transition to operational use should be specified. A project schedule alone does not address these technical considerations, although it can be systematically integrated with the validation plan.

Refer to overarching guidelines rather than copying them verbatim. Describe project-specific decisions and justify any deviations. For a configured SaaS application, alternative forms of evidence may be appropriate compared to in-house software. The selected strategy must align with the actual complexity and risk profile. Additionally, document the conditions that must be met prior to testing, prior to use, and for subsequent operation.

Sources: [2] [1]

Example: ERP, Excel, and Archive in the portfolio

In this example, a company plans to implement an ERP system, revise critical Excel-based calculations, and decommission an outdated archive. The overall strategy establishes shared roles, priorities, and governance rules. The ERP system plan details specific business processes and integration points. The Excel documentation addresses calculation and versioning risks. The archive initiative evaluates future historical data retrieval capabilities. No single system plan should attempt to comprehensively address these distinct considerations.

A key dependency is: the old archive may only be decommissioned once the required access in the target concept has been demonstrated. The ERP project requires early access to specific master data and decisions. The following matrix serves as an internal reference tool. It illustrates how a common strategy and specific implementation can be aligned. The listed initiatives and sequences apply solely to this example; they do not represent any general legal prioritization.

Internal Work Aid: Decisions at Portfolio and Project Levels
DecisionOverall LevelSystem- or initiative level
Responsibility Role model Named Responsible Parties
Priority Portfolio and Dependencies Concrete next step
Evidence Principles and Acceptance Procedures Selected Tests and Criteria
Deviation Evaluation and Escalation Procedure Specific finding with implications
Operation Common Minimum Processes System-specific execution
Closure Governance and Review Rationalized usage decision

Sources: [2]

Align enterprise objectives with compliance decisions

A plan should clarify the intended operational purpose of the proposed activity: making the system available, preserving knowledge within the team, enabling faster access to evidence, or facilitating a structured system transition. These objectives support a logical sequence and design approach. However, they do not replace essential quality and data controls. A schedule or cost objective must not justify an unacceptable risk.

A regulatory finding is also addressed within this context. Initially, immediate actions and binding deadlines are evaluated and implemented. Thereafter, root causes, similar vulnerabilities, and strategically appropriate improvements are assessed. An isolated, supplementary SOP may document the symptom without effectively improving the process. The plan therefore integrates finding management with sustainable responsibilities and actionable guidelines. The specific regulatory response and associated deadlines are separately evaluated on a case-by-case basis.

Sources: [3] [2]

Sleek document architecture instead of repetition

Assign each piece of information to a central location. The central rule for test deviations does not need to be fully repeated in every system plan. The system plan shall include a relevant reference and project-specific amendments. This results in fewer inconsistent versions. However, verify that the reader can actually access the reference and that the referenced rule aligns with the intended approach.

Lean means decision-capable. A brief table can more clearly link scope, responsible parties, evidence, and criteria than many pages of general definitions. The absence of decisions must not be dismissed merely by referencing pragmatism. During review, ask: What concrete actions can the team take after reading this, and what essential question remains unanswered? Page count is neither a quality justification nor an appropriate general upper limit.

Sources: [2] [4]

Maintain traceability of changes, residual points, and releases

A plan evolves alongside the project. Changes to scope, risks, or validation evidence are reviewed and controlled. Maintain the relevant historical version to ensure clarity at a later stage regarding the strategy applied for the conducted tests. A revised plan prepared after execution must not imply that all decisions were made prior to testing. Deviations and justified adjustments remain transparent.

Establish the evaluation of open items and responsible decision-making. An administrative residual issue and a critical functional defect must be treated differently. Annex 15 outlines a justified transition to the next qualification level under specific conditions; this does not imply blanket approval for productive use despite unacceptably high risks. The specific decision on usage takes into account requirements, results, and effective operating conditions.

Sources: [2] [1]

Retain operational control capability during operation

The master plan or overarching concept is maintained and refined through portfolio changes and relevant experience. The system plan transitions into controlled operational information and final evaluation. Responsibilities for changes, deviations, access, review, and system decommissioning remain unchanged. Without this handover, planning often concludes with the project team, while operations is left to re-evaluate and make actual decisions.

Assess the impact through practical considerations: Are critical systems prioritized, are evidence readily retrievable, and are decisions made in a timely manner? Are recurring gaps actually being reduced? A large volume of completed documents may be helpful, but provides little insight into process quality. Effective planning links strategic direction with concrete implementation, enabling the team to generate necessary evidence purposefully and to leverage it sustainably over time.

Sources: [2] [3]

Project experience and collaboration

Align the individual project with the rules in the master plan

We compare the company-wide validation strategy with a plan for one system. Which rules apply across the organisation, and which decisions are specific to the project? This separates shared responsibilities from project scope. A small portfolio can document both levels concisely. Multiple sites or system types need explicit ownership of common rules and justified exceptions. Suitable existing guidance can be referenced without copying policy text into every system plan.

Frequently asked questions about Validation master plans for computerised systems

Is a validation master plan always a separate file?

Annex 15 provides for a VMP or equivalent appropriate documentation. The specific structure depends on the quality system and scope. Existing documents can be integrated if the strategy, responsibilities, and organizational structure are clearly defined. A different file name alone neither constitutes sufficient nor inadequate planning.

Sources: [1]

Can the system validation plan replace the master plan?

A standalone plan initially addresses the questions of a specific system. Overarching organizational structures, priorities, and common rules may remain incomplete. Review both levels. For a small scope, an integrated documentation approach may be appropriate, provided that the necessary decisions are clearly and fully discernible.

How long should a system validation plan be?

As long as necessary for scope, strategy, responsibilities, and verifiable decisions. Refer to relevant central rules and describe project-specific points. A fixed page count is not a quality benchmark. Excessively general text is equally inappropriate, as is a brief list lacking acceptance criteria.

Should corporate objectives be included in validation planning?

Yes, as a contextual framework for meaningful design, prioritisation, and operational benefit. They do not replace required quality controls. For example, integrate system implementation, knowledge transfer, and archive access with the necessary validation evidence. Time and cost objectives must not justify unacceptable risks.

How is a regulatory finding incorporated into the plan?

Address initial required corrective actions and specific deadlines. Link root cause and sustainable improvements to the overall portfolio. Assess similar systems and strategic dependencies. An isolated document gap should not be considered a permanent solution if the underlying process remains inadequate.

Sources: [3]

How does one know that planning functions effectively in day-to-day operations?

To the responsible parties, justified priorities, timely available evidence, and clear decisions. Additionally, assess the handover to operations and the handling of changes. The mere number of signed documents alone does not demonstrate control or sustainable improvement.

Sources and review date

As of October 14, 2026. The regulatory classification is based on the listed original sources. Planning matrix and portfolio example are internal reference tools; adapt them to your systems and projects.

  1. European Commission: EU GMP Annex 15, Qualification and Validation (2015)Qualification and validation, supplemented by the specific framework for computerized systems.
  2. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  3. EMA / ICH: Q10 Pharmaceutical Quality System, Step 5 (2008)Section 3.2.2: Root Cause Analysis, CAPA, and Effectiveness Evaluation. The planning matrix and portfolio example from the contribution are standalone work aids.
  4. European Commission: EU GMP Chapter 4, Documentation (2011)Document referencing and records. No general specification regarding the number of pages for an SOP.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

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