Software Master Validation Plan All You Need to Know!

The validation plan is a strategic document that should state what is to be done, the scope of the approach, the schedule of validation activities and tasks to be performed.

The plan should also state who is responsible for performing every validation activity. Once reviewed the validation plan should then be signed off by the associated project team members.

The Validation Project Plan (VPP)

Validation plans are documents that express the philosophy of the company and how they intend to establish a working model for the project at hand. Validation plans state who is responsible for performing development and validation activities, who identifies which systems need to be validated and who identifies the nature and extent of the inspection and testing expecting for each system and who outlines the framework to be followed to accomplish the validation.

In general the project validation plan describes the organization, activities, and tasks involved in the development of a computerized system including:

  • Organizational structure of the computerized project
  • The departments or individuals responsible
  • Resource availability
  • Risk management
  • Time restrictions
  • The SLC and methodology that needs to be followed
  • Deliverable items
  • Overall acceptance criteria
  • Development schedule and timeline
  • System release sign-off process
  • Sample formats for key documentation

Verification of Documents

During the execution of a project, verification will check the reliability of the work as established by the project plan so that when the due dates for completion or handover arrive a high degree of certainty exists that the system is fully validated.

When multiple departments are involved in a project, the system owner will take responsibility for the validation documentation. Other department will provide documentation and personnel to support the development, validation and maintenance effort.

Predicated Regulations

Validation plans are not required by any of the predicated regulations but are considered a key project management practice. Validation plans are an essential documents for the overall management of projects, and are crucial for the success of the project.


Typically, managers their peers, end-users, and those responsible for delivering the system, approve validation plans. Quality assurance may also sign the document. The validation project plan and the requirements specification deliverable, together define the technical and regulatory requirements applicable for a project.

When to Start the MVP

Project validation plans should typically start during the early stages of the project, its usually the first document that will get attention. Initial project concepts and planning estimates should be elements in the creation of a project validation plan.

The initial project verification activities will assess the project teams capability to produce a validated system and provide input for defining the level of testing effort expected. Project verification will identify any critical deviations to the expected project timing and quality levels, as well as other issues affecting the timely approval of the validation report.

Approved Version

An approved version of the validation plan should be available when a computer technology supplier or contract developer is being selected, and should be updated whenever project events or verification results require a change.

Documents that support the update of the validation plans are:

  • System requirements
  • Criticality and complexity analysis
  • Project verification results
  • Other system descriptions

Validation Plan Format

The format of a validation project plan is flexible and may incorporate Gnatt charts. The contents of the validation plan may include, but are not limited to the following list:

Document Control Section

  • System/Installation name
  • Author(s)
  • Creation, save and print date
  • Version number
  • Document identification
  • Reviewer and review date
  • External document references
  • Table of contents
  • Intended audience
  • Scope
  • Objective
  • System description
  • Validation acceptance criteria
  • Verification activities and deliverables

Qualification Activities and Deliverables

  • Qualification planning
  • Project verification
  • Installation qualification
  • Operational qualification
  • Performance qualification
  • Process validation (if applicable)

Roles and Responsibilities

  • Application owner
  • Project management
  • QA
  • Validation team
  • Computer technology supplier or contract developer

Project Schedule

  • Project activities
  • Project documentation and delivery

Plans and Protocols, How Many?

When developing the validation plan, a decision has to be made about the manner in which the documents will be organized.

Small System

For small systems, it is possible to integrate the validation plan and all protocols into one document, and have one report to summarize all results.

Large System

For large system with many components, a validation project plan can be created that divides the validation effort into smaller, more manageable units with separate plans.

Multiple versions of the plan and protocols could be needed, with intern or partial reports.
The review and approval of the plan by QA is optional, but will provide an endorsement that the plan conforms to the current written procedures on computer systems validation, and that the document incorporates applicable regulatory requirments.

Validation Schedule

Validation plans and associated schedules are live documents that should be reviewed periodically. It’s a good idea to designate the system owner to ensure that the plan is always current.

As part of the conceptualization period, senior managers are presented with , and estimate the total effort to be expended (including maintenance for the project). Maintenance of existing software can account for over 70% of all effort expended by a software organization and this cost will be passed on to the customer.

As part of the schedule, it should be considered that the majority of the development of computer systems fails due to poor gathering of requirements. An investment up front can yield notable savings later.
The following list is a good example of items that need to be tracked as part of the project schedule.

  • Project kick off
  • Validation plan preparation, review and approval
  • Training of the validation team
  • Applicable SLC periods and events
  • Quality checkpoints for review
  • Project documentation due dates
  • Supplier or contractor developer audits
  • Development and approval of procedural controls
  • Specific plans and protocols for IQ/OQ/PQ
  • Development of traceability analysis and verify the traceability of design and testing elements against user requirements
  • Monitor the execution of specific protocols
  • Assemble, review and approve the results
  • Assemble, review and approve the final


  • Dr. Narayan G K A S S

    This is a new interactive format that is very ueser friendly.

  • suresh Garg

    Please send format

  • Duchnicz

    please, send me an example on electronic VMP. Do you have any other softwares for other validation documents ?

  • Navdeep Singh

    this is really an elaborated and useful information

  • Mohan Dass

    give me an example of a good validation report

  • Ranjit Barshikar

    This is excellent. It will help to all concerned in a big way if implemented.

  • mattossa

    An article of high value; thanks for your contribution.

  • Gilbert249

    Kindly share the format with me. Thanks a lot!!

  • Mohamed Orouk

    please, send me an example on electronic VMP. Do you have any other softwares for other validation documents ?

  • Please send me the copy of VMP. It will be very helpful. Thanks.

Similar articles:

The Similarity Between Device Master Records & Chocolate Chip Cookies [Video]

The device design once complete, must be adequately transferred to manufacturing. This is typically accomplished through product specifications, standard operating procedures, work instructions and training.

Collection of Documents

Often a product specification is thought of as a document. The reality is the product specifications should be thought of as an association of written documents.

The product specifications typically include:

  • Assembly drawings
  • Component procurement specifications
  • Manufacturing instructions
  • Inspection
  • Test instructions
  • Digital data files
  • Manufacturing fixtures (jigs and molds)
  • Training materials
  • Artwork associated with labels
  • Acceptance criteria
  • Etc

Device Master Record (DMR)

The ultimate document to ensure adequate design transfer is the Device Master Record, or DMR.

The DMR is somewhat theoretical in that it is really a compilation of all the documents which are needed to realize the product.

For that reason, the DMR, is often established as an index which simply lists all of the documents needed to realize the product.

Contents of the DMR

The DMR typically includes the following documents:

  • Product specifications
  • Work instructions for device realization
  • Device history records/Forms to generate device history records
  • Component drawings/Specifications
  • Label artwork/Specifications
  • Test/Inspection methods
  • Software/Firmware
  • Validation Master Plan (VMP)

Since these documents may be revising and changing and may be at various distribution points, the DMR typically is an index of all the documents.

Chocolate Chip Cookie Analogy

One very common analogy is to envision the DMR as a chocolate-chip cookie recipe. If the DMR is complete, by providing the DMR to someone they can make the exact same chocolate-chip cookies.

While this is somewhat simplified, it’s an excellent analogy, but in order to make the perfect chocolate-chip cookie we would want specifications for the grade of flour, chocolate chips, sugar and other components.

We’d also like to know which equipment was validated, how they are tested/inspected, what are the instructions for each processing step, etc.

If we have all the relevant information we can reproduce the cookies exactly.

The DMR is the key to any successful design transfer whether it is an internal transfer to manufacturing or a transfer to a Contract Manufacturing Organization (CMO).


Similar articles:

The Four Phases of Conducting a Laboratory Investigation [Video]

The process which will be described here is based on the process discussed in the MHRA’s guidance on Out of Specifications Investigation.

When an out of specification, atypical or suspect result is obtained, it is particularly important that all solutions and reagents associated with the test are retained, as this will greatly assist the investigation.

The MHRA advocate laboratory investigations should proceed in four phases as follows:

Phase I(a)

Phase I (a) consists of a preliminary review, by the analyst, to determine whether there has been a clear and obvious error or event that caused the OOS, atypical or suspect result.

Phase I(b)

Phase I (b) occurs after phase 1(a) has failed to identify a clear and obvious cause. This is a more detailed investigation by the analyst and supervisor to identify a laboratory assignable cause.

Phase II

Phase II occurs after the phase I investigation has failed to identify a laboratory assignable cause for the OOS, atypical or suspect result and are driven by written and approved instructions in order to test particular hypothesis.

Phase III

In Phase III all the information obtained during Phases I and II of the laboratory investigation, and any manufacturing investigation, is reviewed and assessed, and a decision is made on the disposition of the batch

Learn More About Laboratory Investigations

If you would like to learn more about laboratory investigations click here for an overview of this course.



Similar articles: