Validation Master Plan (VMP): Contents, Annex 15 Expectations and PIC/S PI 006
Read the Annex 15 content list alongside PIC/S recommendations, then connect the plan to qualification evidence, change control and review.

On this page · 11 sections
- 1What a Validation Master Plan is
- 2Regulatory context: medicinal products, guidance and applicability
- 3Annex 15 section 1: the VMP content list, quoted
- 4PIC/S PI 006-3: inventory, matrix, responsibilities and scheduling
- 5VMP versus project plan, protocol, report and validation pack
- 6The validation inventory and its evidence relationships
- 7Risk assessment and acceptance-criteria planning
- 8From planned qualification to changes and exception recovery
- 9Schedules, continuing validation and VMP review
- 10VMP failure modes and practical controls
- 11A practical VMP implementation and review checklist
How does VMP apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a Validation Master Plan is
A Validation Master Plan (VMP) is a document describing a company’s validation work programme, the work to be performed, its timescales and the responsibilities for the plan. This definition follows the PIC/S PI 006-3 glossary, section 8: it describes planned work and identifies responsibility for that plan.
At site level, Annex 15, paragraph 1.4 says the key elements of the qualification and validation programme should be clearly defined and documented in a VMP or equivalent document. The focus is therefore the programme, rather than a document title alone.
The practical reading distinction is between planning the programme and documenting its execution. A VMP explains what work is intended, when it is planned and who is responsible. An inventory status or schedule entry is not, by itself, the underlying evidence that the work was performed.
For example, an equipment entry marked “qualification complete” can direct a reader to records from the IQ/OQ/PQ workflow, but the label does not replace those records. Read the VMP as the programme’s organising document; use the linked execution records to examine what was actually done and concluded.
02Regulatory context: medicinal products, guidance and applicability
Annex 15, legal basis identifies the document as guidance for interpreting GMP principles and guidelines for medicinal products. Its wording should not be presented as the verbatim text of a directive or regulation.
PIC/S PI 006-3, introduction describes recommendations concerning equipment qualification and process validation in pharmaceutical manufacture. Its section 9, PI 006-1 revision-history entry records adoption as guidance for inspectors. That designation should not be treated as proof of adoption into national law.
| Context | Product focus | Source type | Applicability check |
|---|---|---|---|
| EU GMP: Annex 15 | Medicinal products | GMP interpretive guidance | Check current product and jurisdiction scope |
| PIC/S PI 006-3 | Pharmaceutical qualification and validation | Recommendations; inspector guidance | Check local regulatory use |
| Other jurisdictions or products | Assess individually | Identify applicable instruments | Do not presume Annex 15 applies |
For current applicability, consult EudraLex Volume 4 and current rules for the jurisdiction and product. Keep food, supplements, devices, chemicals and jurisdiction-specific veterinary questions outside any blanket Annex 15 conclusion. Use the broader cGMP overview for terminology, not as a substitute for that assessment.
- Applicable binding law: identify the governing legal instruments separately.
- Attributed GMP guidance: retain each source’s scope and wording.
- Illustrative operating practices: this article’s examples and record structures are not additional regulatory provisions.
- Software support: keep any capability discussion separate from legal obligations and authorised human decisions.
03Annex 15 section 1: the VMP content list, quoted
Annex 15 frames the VMP content as information to include or reference, rather than information that must all be reproduced within one document. The guidance in paragraph 1.5 introduces the seven topics with this wording:
“The VMP or equivalent document should define the qualification/validation system and include or reference information on at least the following:”
- i. Qualification and Validation policy;
- ii. The organisational structure including roles and responsibilities for qualification and validation activities;
- iii. Summary of the facilities, equipment, systems, processes on site and the qualification and validation status;
- iv. Change control and deviation management for qualification and validation;
- v. Guidance on developing acceptance criteria;
- vi. References to existing documents;
- vii. The qualification and validation strategy, including requalification, where applicable.
Turning the content topics into an accessible plan
The following is an implementation approach, not prescribed Annex 15 formatting. Suggested headings, field names and document locations illustrate how a reader could find the controlling information without turning the VMP into a duplicate procedure library.
| Topic | Practical interpretation and possible location |
|---|---|
| i. Policy | Identify the controlling qualification and validation policy. A short “Policy basis” section could name the policy and give its document reference, allowing readers to distinguish the site's governing approach from an individual project's arrangements. |
| ii. Organisation | Use a responsibility table to name accountable roles and identify their activities. Where individuals are named, connect them to defined roles so that responsibility remains understandable when personnel change. |
| iii. Site summary and status | Provide a readable summary or reference a maintained register. Illustrative fields include “Item”, “Scope”, “Status” and “Supporting evidence reference”. These are proposed navigation aids, not an Annex 15 software inventory specification. |
| iv. Changes and deviations | Keep both topics visible. A “Controlling procedures” section could point to the relevant change-control and deviation-management procedures, with a short explanation of their application to qualification and validation work. |
| v. Criteria development | Describe the approach used to develop and justify acceptance criteria, or reference the procedure that does so. Explain where the rationale belongs rather than filling the VMP with every test's acceptance limits. |
| vi. Existing documents | Create a reference index using document identifiers and titles. Organise it so readers can locate the policies, procedures and validation documents relevant to the plan, rather than encountering an unexplained list of document numbers. |
| vii. Strategy | Explain the intended qualification and validation approach and address requalification where applicable. A strategy section can link the programme to its planned qualification stages without reproducing the detailed instructions for each stage. |
Keep criteria-development guidance distinct from test criteria
Item v concerns guidance on developing acceptance criteria. Separately, Annex 15, paragraph 2.4 says validation protocols should define the critical systems, attributes and parameters and their associated acceptance criteria. In an implementation layout, the VMP can therefore explain the criteria-development approach, while a protocol states the criteria for its particular study.
For an IQ/OQ/PQ workflow, a useful navigation pattern is to connect the strategy to the relevant protocols and their supporting rationale. The practical test is whether a reader can move from a planning statement to the document that explains or substantiates it.
04PIC/S PI 006-3: inventory, matrix, responsibilities and scheduling
PIC/S PI 006-3 addresses programme documentation separately from the Annex 15 content list. Its recommendations below are guidance, not a combined mandatory template. PIC/S PI 006-3, paragraph 2.5.7 states: “The key elements of a qualification and validation programme of a company should be clearly defined and documented in a Validation Master Plan.”
The core of the VMP: inventory, schedule and matrix
PIC/S PI 006-3, paragraph 4.2.1 says the VMP “should present an overview of the entire validation operation, its organisational structure, its content and planning. The core of the VMP being the list / inventory of the items to be validated and the planning schedule.” Paragraph 4.5.1 adds that the VMP “should be a summary document and should therefore be brief, concise and clear. It should not repeat information documented elsewhere but refer to existing documents such as Policy Documents, SOP's and Validation Protocols/Reports. The VMP should be agreed by management.”
Under the organisational-structure heading, paragraph 4.5.2.2 lists “Personnel responsibility for”:
- the VMP,
- protocols of individual validation projects,
- validation work,
- report and document preparation and control,
- approval / authorisation of validation protocols and reports in all stages of validation processes,
- tracking system for reference and review,
- training needs in support of validation.
Paragraph 4.5.2.5 then asks that “All validation activities comprised in the VMP should be summarised and compiled in a matrix format.” The matrix should contain all items subject to validation with the extent required “[i.e. IQ, OQ and/or PQ]”, including validation of analytical techniques used to determine the validation status of other processes or systems; “the validation approach, i.e. Prospective, Retrospective or Concurrent”; “the Re-validation activities”; and “actual status and future planning.” Paragraph 4.5.2.6 asks for a general statement on key acceptance criteria for the items in that matrix. PI 006-3 is dated 25 September 2007; the later Annex 15 General section states that “Retrospective validation is no longer considered an acceptable approach”, so within Annex 15’s scope the approach column would record prospective or concurrent validation, with concurrent use justified as Annex 15 describes.
These PIC/S lists are guidance on how a VMP is organised; they sit alongside, not inside, the Annex 15 section 1.5 content list quoted above. The inventory structure in the next section is an editorial implementation suggestion for keeping that matrix traceable.
Responsibilities and management commitment
Under paragraph 2.7.3, the pharmaceutical company is responsible for defining the respective “responsibilities of its personnel and of external contractors in the qualification and validation programme. This should form part of the Validation Master Plan.” The planning question is therefore not merely which departments participate, but what each participant is responsible for.
Paragraph 2.7.4 addresses the most senior level of company management: it is imperative that this level “understands the personnel, time and financial resources required to execute a qualification and validation programme and commits the necessary resources to the work.” This recommendation concerns commitment to execution, rather than simply naming a management sponsor.
Procedures, resource estimates and scheduling
Paragraph 4.5.2.8 gives a distinct procedural-reference recommendation: “List of relevant SOP’s should be presented.”
For resources, paragraph 4.5.2.9 states: “An estimate of staffing (including training needs), equipment and other specific requirements to complete the validation effort should be described in the VMP.” Its project-scheduling statement is separate: “A time plan of the project with detailed planning of subprojects.” A resource estimate and a time plan answer different questions: what the work needs, and when its component activities are planned.
An optional way to present the planning
As an operational interpretation, a compact planning table could connect each workstream with its responsible company role, contractor contribution, relevant SOP references, estimated staffing and training, equipment needs, and planned timing. This is a proposed presentation, not a prescribed PIC/S format.
For an IQ/OQ/PQ workstream, pairing responsibilities with resource estimates makes the schedule easier to assess: readers can see who is expected to perform the work and what availability the dates assume. A date alone does not show whether those assumptions are credible. Keeping these connections visible makes the plan more useful for allocating work without turning the VMP into the detailed execution record.
05VMP versus project plan, protocol, report and validation pack
The comparison below separates source-defined document functions from practical ways of organising them.
| Document or grouping | Main question answered | Typical relationship to the VMP |
|---|---|---|
| VMP | What is the site’s qualification and validation programme? | The programme-level document described above; see Annex 15, paragraph 1.4. |
| Project validation plan | How is a particular project’s validation planned? | Separate validation plans may improve clarity for large and complex projects under Annex 15, paragraph 1.6. |
| Validation protocol | Which critical systems, attributes, parameters and associated acceptance criteria apply? | Provides the detailed definition described in Annex 15, paragraph 2.4, rather than programme-level planning. |
| Validation report | What activities, data and conclusions resulted? | Documents execution rather than plans: PIC/S PI 006-3, section 8, Validation Report defines it by these three elements. |
| Per-system validation pack | Where are the related controlled records for this system? | An illustrative grouping linked to the programme, not a separately defined regulatory document in this comparison. |
Annex 15, paragraph 2.3 says document interrelationships in complex validation projects should be clearly defined. In practice, make the route from the VMP to the applicable project plan, protocols and reports explicit through document references. A pack can provide that navigation without replacing the individual records.
For an illustrative equipment project, use requirements traceability to connect requirements with evidence, and an IQ/OQ/PQ workflow to organise qualification records. These are practical connections, not additional VMP content requirements.
06The validation inventory and its evidence relationships
The site-status summary in Annex 15, paragraph 1.5(iii) can be made traceable through an inventory linked to supporting evidence. The following is an illustrative information model, not a database design prescribed by the guidance.
| Record | Purpose in this model |
|---|---|
| Validation object | Identifies the equipment, facility, system or process whose status is being tracked. |
| Planned activity | Identifies a defined piece of qualification or validation work against an object. |
| Controlled evidence document | Identifies a protocol or report and its specific revision, rather than merely its title. |
One object can have several activities, each linked to different documents and revisions. Keep those relationships explicit rather than compressing them into a single status label.
- VMP revision → validation objects covered by that revision.
- Validation object → planned activities → protocol and report revisions.
- Change or deviation → affected objects.
- Review decision → resulting planning decision, with the responsible person recorded.
Worked case: reconciling equipment records
Assume an illustrative inventory contains 12 equipment records: 7 supported by completed authorised reports, 3 linked to work in execution and 2 lacking a status-evidence reference. The reconciliation is 7 + 3 + 2 = 12 equipment records. The two unsupported entries create a reconciliation task: locate the supporting evidence or establish what work remains. They establish neither successful qualification nor actual equipment failure.
As proposed controls, use stable object identifiers, exact document revision references and accountable status updates recording who changed the status, when and on what basis. An inventory percentage is not a regulatory release decision; keep the register distinct from authorised batch release decisions.
VMP Revision
Programme scope and controlled ownership.
- vmp_id
- revision
- scope
- owner_id
- approved_by
Validation Object
Site item and supporting status reference.
- object_id
- object_type
- site_id
- validation_status
- status_evidence_id
Planned Activity
Scheduled work linked to an object.
- activity_id
- object_id
- vmp_id
- planned_finish
- responsible_person_id
Controlled Document
Versioned protocol, report or supporting record.
- document_id
- revision
- activity_id
- document_type
- authorised_by
Change or Deviation
Affected object and impact-assessment reference.
- event_id
- event_type
- affected_object_id
- impact_assessment_id
- decision
Review decision
Review trigger, outcome and accountable decision.
- review_id
- vmp_id
- review_trigger
- decision
- decision_by
07Risk assessment and acceptance-criteria planning
Annex 15, paragraph 1.7 recommends a quality risk management approach for qualification and validation activities. It also says that how risk assessments support those activities should be clearly documented. For risk-based validation, make the reasoning traceable rather than treating a category label as sufficient justification for the proposed work.
Consider a hypothetical vessel whose temperature has been identified as critical to product quality. The assessment explains why temperature matters; the planned activity follows from it, and the protocol carries the specific criteria (the criteria distinction is covered in the Annex 15 section above).
An illustrative planning record, not a mandated form, could contain:
| Field | Illustrative entry |
|---|---|
| Assessed object | Temperature-controlled vessel |
| Question being assessed | Can temperature variation affect product quality? |
| Assessment reference | Identifier and version of the documented assessment |
| Rationale | Temperature is assumed critical in this example |
| Proposed activity | Test temperature control against justified protocol criteria |
| Decision owner | Named person responsible for the planning decision |
Link this record to the relevant quality risk register entry where one is used. The useful connection is assessment → rationale → proposed activity; these fields do not prescribe a scoring scale, risk class or numeric threshold.
08From planned qualification to changes and exception recovery
PIC/S PI 006-3, paragraph 5.4.4 recommends: “An effective change control procedure should be operational and encompass the whole project from the pre-planning stage through to the final acceptance of the Process Validation exercise.” This places change control across the project, rather than only after qualification is complete.
Under Annex 15, paragraph 1.7, increased knowledge and understanding from changes during the project phase or commercial production should lead to repeated risk assessments, “as required”. For risk-based validation, that qualification matters: reassessment is not an automatic instruction to repeat qualification.
Annex 15, paragraph 2.2 states that all documents generated during qualification and validation should be approved and authorised by appropriate personnel as defined in the pharmaceutical quality system.
Worked case: controller change and reference mismatch
Assume a controller change affects one packaging line and its associated qualification documents. The following is one practical arrangement of planning, assessment, execution, authorisation and review—not a regulator-prescribed sequence:
- Record the affected controller, packaging line and document references against the change record and relevant validation-inventory entry.
- Assess the impact on the existing qualification basis. Decide and document the necessary work from that assessment, without assuming a fixed test quantity or predetermined outcome.
- Execute the agreed work and link the resulting qualification documents to the affected objects and change record.
- Obtain document approval and authorisation from the appropriate personnel identified by the pharmaceutical quality system.
- Review the resulting references and recorded status together so the inventory reflects the authorised documentary basis.
Now assume a report reference arrives with a revision mismatch. Retain the original reference, flag the mismatch and reconcile the document identifier and revision before the responsible person decides the status update. This exception-recovery arrangement links document control, inventory and change records; it is an illustrative integration design, not a software capability or an automatic approval mechanism.
- Define scopeIdentify programme boundaries and accountable document ownership.
- Map objectsConnect facilities, equipment, systems and processes to status.
- Plan activitiesAssign responsibilities, resources, dependencies and planned dates.
- Assess risksConnect documented reasoning to proposed qualification work.
- Execute protocolsRecord results, deviations and controlled evidence references.
- Authorise DocumentsAppropriate personnel approve and authorise the records.
- Review changesRecord decisions and update affected planning references.
09Schedules, continuing validation and VMP review
PIC/S guidance closes its planning-and-scheduling discussion in PIC/S PI 006-3, paragraph 4.5.2.9 with: “This time plan could be included in the above mentioned matrix (4.5.2.5). A VMP requires regular updating.” Updating the VMP is distinct from establishing the project schedule discussed above: it concerns keeping the plan current, not merely assigning dates.
The continuing programme is a separate point. Paragraph 2.5.12 states: “Qualification and validation can not be considered once-off exercises, for example, the start-up of a new manufacturing operation. An ongoing programme should follow its first implementation.”
For practical organisation, distinguish three questions—not three universally mandated procedures:
- Project dates: when is work planned, and what capacity is available?
- VMP review: does the plan still describe the intended programme?
- Technical decision: what further qualification or validation work, if any, is appropriate?
Completing one does not establish that the others are complete. An optional review record could use review_date, review_trigger, decision and next_planned_review. A site-selected cadence and a change-driven review decision are planning choices, not the quoted guidance’s list of required review elements or a universal trigger for revalidation.
Worked case 3: reviewer capacity
Assume six review activities require two reviewer-hours each, and one reviewer has four reviewer-hours per week available. Total effort is 6 × 2 = 12 reviewer-hours; 12 ÷ 4 = 3 weeks of reviewer capacity. This supports forward scheduling from available capacity. These are illustrative workload assumptions, not a review interval, committed completion date or regulatory timeline. Record the capacity estimate separately from the technical decision and the next planned VMP review.
10VMP failure modes and practical controls
These are foreseeable operational problems, not reported inspection statistics. Use the table to diagnose unclear planning relationships; it is not an additional source-defined compliance checklist.
| Failure mode | What the reviewer can observe | Practical control |
|---|---|---|
| Unresolved document relationships | VMP and project documents point to conflicting versions. | Identify the controlling reference and reconcile links. |
| Unclear decision ownership | Tasks have names, but decisions have no assigned owner. | Resolve who makes and records each decision. |
| Unsupported status entries | A status label has no traceable supporting record. | Reconcile the entry with its evidence. |
| Dates without resource assumptions | Milestones omit staffing, equipment access or dependencies. | Explain scheduling assumptions beside the dates. |
| Acceptance criteria introduced only after testing | Criteria first appear in the results report. | Establish criteria before testing. |
| Changes not reflected in planning references | Planning references still describe the previous configuration. | Link the change decision and update affected references. |
The timing distinction follows the PIC/S glossary entry for Pre-Determined Acceptance Criteria: criteria are assigned before undertaking testing. Annex 15, paragraph 1.8 says qualification and validation work should incorporate appropriate checks to ensure the integrity of all data obtained.
For evidence mismatches, use the worked cases above rather than repeating their recovery sequences. Focus the review on data integrity and, where relevant, the audit trail supporting the disputed entry.
11A practical VMP implementation and review checklist
This practical checklist organises the topics covered above; it is not a regulator-issued list or an additional set of mandatory review elements.
- Confirm the applicable product, site and jurisdictional context.
- Locate each applicable Annex 15 content topic, including referenced documents.
- Identify the relevant PIC/S planning recommendations.
- Reconcile inventory identifiers, status entries and evidence references.
- Confirm relationships between plans, protocols, reports and supporting records.
- Identify accountable decision owners.
- Check staffing, availability and other resource assumptions.
- Record unresolved decisions, owners and next actions.
Test usability by selecting a programme entry and navigating to its current evidence and accountable decision. Familiar headings alone do not demonstrate that these connections work.
Frequently asked questions
Q.Can several controlled documents together serve as the VMP or equivalent document?+
A linked document structure is consistent with Annex 15, but simply collecting documents is not enough. Sections 1.4–1.5 describe a VMP or equivalent document that defines the qualification/validation system and includes or references the listed information. Section 2.3 adds that document interrelationships in complex projects should be clearly defined. The organising document therefore needs to make those relationships understandable. For related document-management topics, see paperless validation and hybrid record systems.
Q.How should a site organise its VMP when several large validation projects run in parallel?+
Keep the site programme identifiable while using separate project plans where they improve clarity. Annex 15 sections 1.4 and 1.6 address the site programme and separate plans for large, complex projects. PIC/S PI 006-3 section 4.5.2.9 recommends a project time plan with detailed subproject planning, plus estimates of staffing, training, equipment and other specific requirements. Annex 15 Annex 15, paragraph 1.7 separately addresses risk-based validation, including documenting how risk assessments support activities—a relevant connection to the quality risk register.
Q.Can installation qualification and operational qualification share one document?+
Yes. Annex 15 section 2.5 explicitly allows qualification documents to be combined where appropriate, giving IQ and OQ as its example. This concerns document structure. PIC/S PI 006-3 section 5.5.5 separately recommends written authorisations for both IQ and OQ before release to process validation, with calibration, cleaning, preventative maintenance and operator training requirements finalised and documented. A combined document should therefore not obscure the two authorisations within the IQ/OQ/PQ workflow.
Q.How should responsibilities be divided when an external contractor prepares qualification documents?+
The pharmaceutical company should define the respective responsibilities of its personnel and external contractors in the VMP. PIC/S PI 006-3 section 2.7.3 also says the company’s Quality Assurance function should normally have a critical oversight role. Document preparation is distinct from approval: Annex 15 section 2.2 places approval and authorisation with appropriate personnel defined in the pharmaceutical quality system. This division belongs within the QA process; related documentation principles are covered under data integrity.
Q.How much detail about acceptance criteria belongs in the VMP rather than the protocol?+
Keep the VMP at the level of a general statement and guidance on developing criteria: Annex 15, paragraph 1.5(v) and PIC/S PI 006-3, paragraph 4.5.2.6. Specific, predetermined criteria belong in the protocol under Annex 15, paragraph 2.4.
Q.How should a shared utility be represented when it supports several validation projects?+
Represent the utility through the site-system summary and make the relationships between its qualification documents and the projects clear. Annex 15 section 1.5(iii) calls for a summary of site facilities, equipment, systems and processes, including qualification and validation status. Sections 1.5(vi) and 2.3 address document references and interrelationships. These provide a basis for referencing the utility’s qualification information across projects, without treating every project as a separate utility. See also commissioning and decommissioning.
Q.What should happen to the VMP time plan when reviewer capacity becomes unavailable?+
Update the time plan to reflect the changed staffing position rather than retain dates that assume unavailable reviewers. This is a planning application of PIC/S PI 006-3 section 4.5.2.9, which recommends staffing estimates and detailed subproject planning and states: “A VMP requires regular updating.” The section does not prescribe a reviewer-specific rescheduling interval. Backward scheduling is a related planning topic; it should not be mistaken for a PIC/S-mandated scheduling method or a substitute for the staffing estimate.
Q.Does completing the final scheduled project activity mean the validation programme is finished?+
Not on the strength of the schedule alone. PIC/S PI 006-3 section 4.5.2.9 calls for regular VMP updating, while Annex 15 section 1.5(vii) includes requalification, where applicable, in the qualification and validation strategy. Section 1.7 also calls for risk assessments to be repeated as required when changes increase knowledge and understanding during projects or commercial production. Distinguish completion of scheduled work from these continuing planning considerations, including the connection to change control.
Primary sources
Explore this topic
VMP sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
URS-through-PQ lifecycle, GAMP 5 categorisation and CSA's modern alternative.
Want to see how VMP could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
