Governance DocsGovernance Docs
Browse Toolkits

CART

No products in the cart.

Skip to content

Validation Master Plan: 8 Essential Decisions to Include

validation master plan: Validation Master Plan: 8 Decisions

A validation master plan is the document that decides, once, how your site validates its computerized systems, so each project does not reinvent the answer. Neither 21 CFR Part 11 nor the 2011 EU Annex 11 uses that exact phrase for software. Part 11 requires validation in 11.10(a). Annex 11 requires validation documentation that covers the relevant lifecycle steps and a justification for your standards, protocols and acceptance criteria. A plan is how you show those choices were made deliberately and applied the same way every time.

The July 2025 consultation draft of Chapter 4 lists a validation master plan among the master documents, as a description of the key elements of the site’s qualification and validation program. That draft is not adopted. Many sites already keep one, and it gives an inspector one place to find the logic.

What a validation master plan is, and what it is not

People mix up three documents. Keep them apart.

Document Level Answers
Validation master plan Site or program, one document What do we validate, how much, who decides, and who does what?
System validation plan One per system or project For this system, which activities, deliverables, test approach and acceptance criteria?
Validation summary report One per system, at the end Did we do it, what went wrong, and is the system fit to release?

The master plan sets the rules. The system plan applies them. The report proves they were followed. If you are starting from nothing, write the master plan after you have a draft inventory and risk criteria, since both shape what the plan says.

What the rules expect from the plan

  • Validation of the application and qualification of the infrastructure. Annex 11 (2011) states both in its principle, together with a rule that replacing a manual operation must not lower product quality or raise process risk.
  • Risk-based extent. Annex 11 clause 1 says decisions on the extent of validation rest on a justified, documented risk assessment. FDA’s 2003 guidance says the same about Part 11 validation and gives a simple example: a word processor used only to write SOPs does not call for much.
  • An inventory. Annex 11 clause 4.3 expects an up-to-date list of relevant systems and their GMP functionality, plus a system description for critical systems covering physical and logical arrangement, data flows, interfaces, prerequisites and security.
  • Lifecycle coverage. The draft Annex 11 (July 2025, not adopted) expects systems to be validated before use and kept validated through their life, and ties the strategy and effort to intended use and risk to product quality, patient safety and data integrity.

Part 11 also makes your systems and their documentation available to FDA inspectors under 11.1(e), so the plan has to be something you can hand over.

What to put in a validation master plan: eight decisions

1. Scope and applicability

Name the sites, the regulations you answer to (Part 11, Annex 11, the predicate rules that apply) and the systems in and out of scope. State the out-of-scope reasoning so it survives an audit. Plain office software that holds no regulated record is the usual example.

2. Where the inventory lives

Point to the controlled system inventory rather than copying it into the plan, or the plan goes stale the day a system is added. State who maintains it and how critical systems get their system description.

3. How you classify risk

Define the criteria and the tiers. Useful inputs are the system’s effect on product quality, patient safety and data integrity, whether it holds regulated records or signatures, its complexity and novelty, and whether it is configured or customized. The output is a tier that drives everything below.

4. Validation paths by tier

Describe what each tier receives. The worked example in the next section shows three paths.

5. Deliverables for each path

List the documents each path must produce: requirements, risk assessment, specifications, configuration record, qualification protocols, traceability, deviation handling and the summary report. See IQ OQ PQ for what the testing stages prove and requirements traceability matrix for linking tests to requirements.

Fix acceptance criteria rules here too: who may set them, that they are written before execution, and that a failed step becomes a recorded deviation with an owner, not a quiet retest. Annex 11 clause 4.2 expects validation documentation to include change control records and reports on deviations seen during validation.

6. Roles and approvals

Annex 11 expects close cooperation between the process owner, the system owner, Qualified Persons and IT, each with defined responsibilities. Say who writes, who reviews and who approves each deliverable, and where quality assurance signs. The draft expects work to follow approved plans, protocols and test scripts.

7. Supplier reliance

State when you may use vendor documentation and what you do first. Annex 11 clause 3.3 asks you to review supplied documentation against your user requirements. The draft adds that the regulated user stays accountable, and must check that vendor evidence covers the version actually implemented before authorizing its use.

8. Change, review and retirement

Annex 11 clauses 10 and 11 require controlled change and periodic evaluation. The draft expects significant changes to trigger re-qualification and a final review when a system is retired. Define what counts as significant, how often each tier is reviewed, and what the retirement report covers. Also set your rule on conditional release: the draft allows it only with a documented assessment that open items will not affect product quality, patient safety or data integrity, stated in the validation report.

Worked example: three validation paths by risk

The tiers below are illustrative. Set your own criteria, then justify them.

Path Typical system What it receives
A: critical, configured Laboratory information system or electronic batch record system on premises Full lifecycle: approved requirements, risk assessment, specifications, configuration record, IQ, OQ and PQ, traceability, summary report, release
B: critical, vendor-hosted Cloud quality management system Supplier assessment and reviewed vendor evidence, requirements, configuration record, OQ on configured and critical functions, PQ on real workflows, a defined way to test vendor releases before use
C: low impact Spreadsheet that charts trends and feeds no decision Documented risk assessment, intended use statement, a simple check against known values, a controlled copy

If you make medical devices, FDA’s February 2026 Computer Software Assurance guidance gives a two-outcome risk logic for production and quality system software: high process risk or not. It covers device manufacturers. A drug manufacturer may borrow the logic only with a documented justification. See ISO 13485 software validation for the device side.

Why the tiers matter for effort

The point of tiering is to put test effort where failure would hurt. Within a critical system, not every function carries the same weight. The draft Annex 11 asks for increased focus on key functional requirements, on functions that make sure work follows GMP, and on functions that protect data integrity. Your plan can say that for Path A and B the risk assessment ranks functions, and that high-ranked functions get scripted tests with defined expected results while low-ranked ones may be covered by supplier evidence or simpler checks, with the reasoning recorded.

A tier can also be revisited. A spreadsheet that starts as a trend chart and later feeds a release decision has moved up a path, and the plan should say who notices and how.

Common mistakes in a validation master plan

  • One tier for everything, so every system gets full treatment or none does.
  • An inventory copied into the plan and never refreshed.
  • No link to change control, so validated systems drift.
  • Vendor packages accepted without checking they cover the version in use.
  • No stated rule on deviations and conditional release, so each project invents one.
  • A plan nobody has reviewed since it was approved.

Review the plan on a set schedule and after any change in regulation, organization or technology. The EudraLex Volume 4 page lists the current Annex 11 and Chapter 4 texts, so check it before you cite a clause.

The 21 CFR Part 11 Toolkit includes a Validation Master Plan, a System Validation Plan, a Validation Deliverables Matrix by System Type and a Computerized System Inventory, so the plan and the records it points to are drafted together. It has 105 templates (68 Word and 37 Excel) for $99.

21 CFR Part 11 Toolkit sample page: GDL-CSV-040 - Validation Master Plan
21 CFR Part 11 Toolkit sample page: GDL-CSV-056 - Validation Deliverables Matrix by System Type
21 CFR Part 11 Toolkit sample page: GDL-CSV-026 - User Requirements Specification

Validation master plan FAQ

Is a validation master plan required by 21 CFR Part 11?

Not by name. Part 11 requires validation of systems in 11.10(a), though FDA’s 2003 guidance says it will exercise enforcement discretion on that Part 11 requirement. Predicate rules and your own risk assessment still point to validating, and a plan is the usual way to show how.

One validation master plan per site or per system?

One per site or program, then a system validation plan for each system. The master plan sets the rules; the system plans apply them.

How often should the plan be reviewed?

Set the frequency in the plan itself and justify it. Draft Chapter 4 says master documents should be evaluated and reviewed regularly. Review sooner after regulatory or organizational change.

Does computer software assurance replace the validation master plan?

No. The February 2026 guidance covers device production and quality system software and shapes how much assurance each feature needs. You still need a place that sets scope, roles and records.

When a standard changes, know first

One email a month: edition changes, new deadlines, and what they mean for documentation you already have. No sales sequence.

We don’t spam! Read our privacy policy for more info.