Validation Plans define the scope and goals of a validation project. The Validation Plan is written at the start of the validation project (sometimes concurrently with the user requirement specification) and is usually specific to a single validation project.
The collection of documents produced during a validation project is called a Validation Package. Once the validation project is complete, all documents in the validation package should be stored according to your site document control procedures.
Validation Plans are different than Validation Master Plans. Validation Plans are usually project specific; Validation Master Plans govern validation activities for an entire organization or site. Sometimes plans are also named for the applicable subject area, such as a Software Validation Plan.
A Validation Plan should include:
The plan should be written with an amount of detail that reflects system complexity.
Q: What is the definition of Validation Plan?
A: The FDA uses the NIST definition: A management document describing the approach taken for a project. The plan typically describes work to be done, resources required, methods to be used, configuration management and quality assurance procedures to be followed, schedules to be met, project organization, etc. Project in this context is a generic term. Some projects may also need integration plans, security plans, test plans, quality assurance plans, etc. (See: documentation plan, software development plan, test plan, software engineering.) In practice, the validation plan describes how the validation project is going to be performed.
Q: Can I see an example of a validation plan?
A: We have a sample validation plan available for download.
The following terms or abbreviations are sometimes used: Validation Plan, VP.