Table of contents
At a glance
What should a practical validation plan include?
A validation plan links intended use and the specific system version to required deliverables, relevant existing evidence, execution prerequisites and decision paths. Define responsibilities, dependencies, and how changes and deviations will be handled. The system’s risk determines the scope and depth. The suggested structure is a working aid. It does not impose a separate document, fixed number of phases or universal timeline for every system.
- Plan verifiable work results instead of solely document titles.
- State the system version and prerequisites for each relevant test.
- Use appropriate existing evidence with its documented scope.
- Keep changes and outstanding decisions visible before execution depends on them.
1. Address a common planning issue
The key question is: What additional evidence must we provide for this intended use, and how will we achieve it? A validation plan proactively addresses this question. It enables early identification of inappropriate test schedules, missing incoming documents, and unclear responsibilities. In contrast, a test protocol details the specific evaluation performed; a report assesses what was actually carried out and observed.
The regulatory example framework here is Human Medicines GMP. Annex 11 deals with risk-based validation and life cycle evidence for computer-aided systems. Among other things, Annex 15 describes the site-related validation program or equivalent documentation. Its concrete qualification levels are in the plant, facility, supply and process context; for computer systems he refers to Annex 11.
Therefore, distinguish between site-level VMP, system-specific planning, and individual test documentation. Annex 15 identifies separate plans for large and complex projects as a potential aid to clarity. This does not imply a requirement for identical document titles across all software. Your controlled documentation must support the necessary decisions; the following work aids illustrate a possible implementation.
2. Intended use, limits, and considered state to be documented
Start with the intended use: Who uses which function for what process? Describe then the current state of application, configuration, relevant interfaces, and data. For an expansion, the plan may reference an existing system description and clearly define the changes. It does not need to retell the entire system history.
An exclusion is only helpful when its significance is clearly defined. For example, "ERP not to the extent" is insufficient if the ERP system provides data used in manufacturing. In such a case, it must be explicitly stated which data and controls are required at that boundary. An actually unchanged, unaffected area may remain outside the scope of new testing.
Assign open assumptions to a responsible party and a required clarification deadline. The plan may initially reflect a developmental stage. Before a review on a specific assumption is conducted, it must be clearly evident whether the assumption remains open or has already been documented. A planned configuration state is not yet confirmed test precondition.
3. Plan required results instead of document volumes
Define the output required from each activity. For access control evidence, demonstrate that assigned roles can perform permitted actions and that unauthorised actions are prevented under specified conditions. Whether to record this in a dedicated protocol or a section of a broader test is a separate organisational decision.
The following structure clearly illustrates what is already known and what still requires development. Refer to referenced documents instead of repeatedly copying their contents. A concise plan can be robust provided the references are unambiguous. An extensive plan may still contain gaps if it merely describes results as "in accordance with standard" without specifying the applicable standard.
| Content plan | Specific statement | What it is intended for use |
|---|---|---|
| Use and Status | Considered process, release and relevant configuration | The reader understands the intended use of the planning. |
| Bounds and Dependencies | Related interfaces and justified exclusions | Prerequisites located outside the project scope will not be overlooked. |
| Required results | Substantiated professional statements and their alignment to requirements/risk considerations | Document quantity is not equated with substantiation. |
| Existing evidence | Appropriate records with revision and acceptance decision | Available evidence is purposefully utilized. |
| Prerequisites for execution | Test setup, data, responsibilities, tools, and required decisions | Testing begins on a verifiable foundation. |
| Responsibility and Handover | Result owner and responsible decision-maker with authority | Open points and handovers receive a specific addressee. |
| Acceptance and Results | Reference to criteria, handling of deviations, and required evaluation | The evaluation will be prepared prior to execution. |
| Update and Completion | Change triggers, status management, and planned consolidation of results | Planning remains aligned with the actual project status. |
4. Plan the existing evidence with its scope
Distinguish new assessments, existing suitability evidence, and documents still under evaluation. An existing supplier or partner report may already cover a specific requirement including your configuration. In such cases, the plan should utilize this result instead of routinely prescribing an identical additional test. A justifiable rationale for the suitability decision is required.
The plan does not need to repeat the complete takeover sheet. It can refer to it and take over its results as well as remaining conditions. If, for example, the local printer configuration remains open, exactly this gap is to be planned. "Supplier package is not yet available, however, does not describe which statement is actually supported.
Plan early for inquiries and required access points. A report delivered only after the scheduled test start date cannot establish a verified foundation prior to that time. Similarly, a promised supplier certificate remains a pending dependency until verified. The planning must not prematurely indicate the availability of the intended test result. This prevents an unreviewed schedule from inadvertently implying a completed compliance status.
5. Identify prerequisites for meaningful testing
Define the requirements that must be in place prior to each respective test. This may include validated requirements, a designated test setup, appropriate roles, prepped datasets, and evaluated support tools. Not every test requires the same inputs. A document review may be performed earlier than a physical print test, which requires a specific printer, a template, and suitable materials.
Describe relevant differences between test and subsequent operational environments. It is essential to determine whether they affect the intended conclusion. For example, a print test using a different printer driver must be justified by additional reasoning to represent the intended print combination. A mere difference in computer name, on the other hand, does not necessarily imply significance. Evaluation remains functionally based.
Define the starting conditions and what to do if a test fails or is interrupted. Must print jobs be removed, test data reset or user roles restored? Include the necessary instructions in the relevant test document. The plan should allow time to prepare them. Approving a schedule alone does not prepare the tests.
6. Specify criteria and procedures for handling results
Reference the applicable acceptance criteria and explain how results are assessed. “All tests passed” says little if the test scope or handling of cases that could not run is unclear. Distinguish a planned test, its execution and the conclusion drawn.
Control the pathway for deviations without predefining any future corrective action in the plan. Who records the finding, who assesses its significance, and what evidence is required following a correction? Refer to the existing established process for this. The plan shall ensure that results are not artificially completed by omitting a failed step.
A release for a next step is to be distinguished from the later decision on the productive use. Annex 15 deals with conditional transitions to the next qualification stage under certain conditions. This passage does not justify a general permission to use any computer system productively with open critical questions. The final decision remains a separate subject.
7. Example: specifically plan a labeling release
The following scenario does not make any claims regarding a specific product. A company implements Release L-2 within its existing labeling system. This release includes two revised templates from suite V-7, a modified role assignment, and the intended printer D-1. The print engine remains unchanged in this example. Order data is manually entered; integration with an ERP system is not part of this release.
The technical requirements are already defined: Only an approved and authorized template may be used for each specific order. Article code, batch number, and expiration date must appear on the label according to established rules. No print order shall be generated in the assumed workflow without the required batch information. These rules constitute the prerequisites of the example and do not represent general guidelines applicable to every labeling system.
A validated supplier report demonstrates certain unchanged functionalities of the press engine in the scenario. It, however, does not include the newly introduced local templates and the intended driver version. The plan adopts the justified appropriate outcome and intends to supplement it with additional local validations. Another report could cover more aspects; the boundary is defined here by the assumed delivery scope.
8. Executable result assignments from the example make
The second workflow assistance displays a section of the example plan. The table does not claim any successful tests, but rather assigns planned results to their respective prerequisites. The department clarifies the expected label contents, the IT or system owner confirms the technical status, and the structured evaluation of evidence is carried out by duly authorized personnel.
Assuming the intended driver is replaced shortly before the pressure test: the test result assignment remains in place, but its prerequisite is no longer met. First, the change is assessed and the relevant status is updated. Then, it must be determined which records still apply and which additional testing is required on the new status. Existing, unchanged evidence that is appropriate remains valid and is not automatically invalidated.
| Intended result | Required prerequisite | Proposed evidence | Open decision point |
|---|---|---|---|
| Use and L-2 levels are clearly defined. | Validated Description of V-7, D-1, and Drum Changeover | Review of the referenced requirements and configuration statuses | Unclear document assignment prior to the test based on it triggers. |
| Appropriate engine documentation is utilized. | Evaluation report for unchanged relevant engine functions | Reference to specific acceptance decision | Assess any relevant limitations or deviations prior to use. |
| Local labels contain the correct order data. | V-7, approved driver, D-1 and defined target examples | Comparison of intended contents with actual pressure and associated records | Clarify the implications of a driver or material change prior to execution. |
| Permissions and missing mandatory indications are appropriately addressed. | Defined roles and prepared test data covering valid and invalid inputs | Review intended and unauthorized actions, as well as pressure prevention, deliberately. | The expected behavior must be unambiguously defined prior to execution. |
| The results can be evaluated coherently for L-2. | Execution documents and associated findings are available. | Planned consolidation against the defined scope | Identify conclusions the evidence does not support and decide what to do. |
9. The plan is continuously monitored and updated
A plan is not a retrospective success story. Document the when and why of any changes to scope, prerequisites, or intended evidence. The current version should reflect the current state of work; the change history enables traceability of decisions made at specific times. This is particularly important when inspections have already begun.
Do not automatically equate a schedule change with a substantive change. If only the availability of a reviewer changes, an organizational adjustment may suffice. However, if roles, data flow, or acceptance criteria change, the implications for risk and evidence must be assessed. Documentation should clearly distinguish these different implications.
Plan from the outset how results will be consolidated. The final report should clearly link the planned scope, actual execution, deviations, and remaining conclusions. It does not need to reproduce the plan verbatim. Upon completion, relevant prerequisites and outstanding actions shall be transferred to routine operations or the responsible usage decision-maker; the plan does not replace these decisions.
10. Enter the correct inputs to begin
To initiate the process, you need a clear system usage procedure, an assessment of the scope of proposed changes, an initial risk evaluation, and an overview of available supporting documentation. Open items may remain visible, provided it is clearly established when they will be required for subsequent activities. The process owner, IT or system owner, and QA should jointly review the plan for technical and organizational gaps.
Effort arises primarily due to unclear process rules, changing configurations, unavailable test environments, and difficult-to-attribute third-party dependencies. Start with a key outcome assignment and fully clarify its prerequisites. This early reveals whether the project requires a brief supplemental planning or more extensive coordination. Fixed page limits or generic weekly estimates provide little practical guidance.
- Intended use, system status, and considered changes clearly specified.
- Required results associated with requirements and risks.
- Existing records and their actually assessed scope are referenced.
- Timing-appropriate assignment of implementation prerequisites and outstanding dependencies.
- Confirm that the team knows the acceptance criteria, how to report findings and who has decision-making authority.
- Reasons for changes and updates are defined.
- Integration of results and handover to subsequent decisions planned.
Project experience and collaboration
Base the validation plan on deliverables and prerequisites
With QA, IT and process owners, we define intended use and the version to be demonstrated. We assign deliverables, existing evidence and outstanding tests to owners. An unavailable test environment or unresolved data migration becomes an explicit prerequisite. A limited modification may need a concise additional plan. For a new system, we also agree handovers and decision responsibilities across teams. The plan should describe work that can be carried out and verified afterwards.
Frequently asked questions about Validation planning
Is a validation plan the same as a validation master plan?
No. A VMP or the corresponding documentation describes the site-specific qualification and validation program. The planning shown here, in contrast, links a specific system usage or a change to the required outcomes. Both can reference each other. What matters is that the intended purpose is clearly fulfilled; a further document title alone does not constitute additional evidence.
Sources: [3]
Does every minor software update require a separate comprehensive plan?
The planning should align with the scope and significance of the change. A small, clearly defined intervention can be planned using existing controlled documentation supplemented by targeted additions. Assess relevant requirements, risks, prerequisites, and supporting evidence. Annex 15 does not impose a universal requirement for a separately detailed, lengthy plan for every update in the context of large and complex projects.
How specifically must the system status be described in the plan?
So that the intended statements and their underlying assumptions can be linked. Relevant versions, configurations, interfaces, and where applicable, equipment must be identifiable. Reference to appropriate existing documentation is permitted. A product name alone is insufficient if different templates or roles alter the behavior. Conversely, every irrelevant technical detail does not need to be repeated in the plan.
Must all subsequent test steps be predefined in the plan?
No. The plan outlines the required outcomes, approach, and prerequisites. Detailed inputs, steps, and supporting documentation may be provided in the relevant test documentation. It must remain clear which question is being addressed and when the documentation must be available. A reference to tests that have not yet been conducted is initially a planned task, not a completed demonstration.
How do we consider a manufacturer's validation package?
Accept the outcome of a traceable suitability assessment with its full scope. The plan identifies which internal statement is supported by it and which condition or additional requirement remains open. Manufacturer or partner documentation may adequately cover customer-specific functionalities. Therefore, a blanket repetition is equally unjustified, and an automatic full transfer based solely on package name is inappropriate.
May we proceed, despite certain prerequisites still being unmet?
Independent pre-activities may be feasible. The key question is whether the missing prerequisite is required for the next specific step. A review does not necessarily need to await an outstanding printer; however, a conclusive test of the intended print combination is required. Explicitly document this dependency. A general project initiation does not substitute for an assessment of specific implementability.
Who is involved in the planning, and who makes the decision?
Process owners explain the technical use, IT or system owners provide the relevant technical requirements, and QA defines the established documentation pathway. The decision is made by duly authorized personnel. In a small and medium-sized enterprise (SME), roles may overlap, provided that responsibilities and authorities remain clearly defined. A fixed number of signatures or a universal organizational structure is not specified in the sources.
What happens if the configuration changes during the inspection?
Evaluate which planned or already issued statements are affected. Update the current status and required prerequisites before proceeding with subsequent assessments. Suitable unaltered documentation may remain usable. The plan should clearly reference the decision logic; it must not inadvertently blend old and new statuses into a seemingly uniform outcome.
Is an approved plan already a release for productive use?
No. It describes how the required evidence should be generated and evaluated. Actual results, their assessment, and further relevant operational conditions only contribute to a subsequent decision on usage. Furthermore, the release mentioned in Annex 15 to the next qualification level is not automatically equivalent to general product release. Separate the various decisions and their respective scopes.
What documents should we bring for the first planning meeting?
Useful are intended use (URS), change descriptions, relevant system overview, risk status, and existing supplier documentation. Supplement known bottlenecks such as missing test data, equipment, or point of contact. The effort primarily depends on these open dependencies and the complexity of the intended result. A fully developed result line better demonstrates the need for clarification than an estimation based on document page count.
Sources and review date
Sources opened on 6 October 2026. The regulatory example framework is Human Medicinal Product-GMP. Annex 15 is applied in its qualification and validation context, without transferring all software-related audits. Tables, checklist, and labeling release are standalone work aids.
- European Commission: EudraLex Volume 4, current human medicinal product GMP overview
- EU GMP Annex 11: Computerised Systems, January 2011 revision
- EU GMP Annex 15: Qualification and Validation, Revision 2015
- EU GMP Chapter 4: Documentation, January 2011 revision
- ICH Q9(R1): Quality Risk Management, European Step-5 Edition 2023
Sources checked: .
Turn open tasks into actionable validation planning
Daniel Herrmann Consulting supports you in defining required results, planning existing evidence, and ensuring prerequisites for meaningful testing are clarified in a timely manner.
- 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.

