This is a ready-to-use report for assessing whether a company’s Validation Master Plan, or the absence of one, actually describes the program as it runs today. Use it before an anticipated inspection or diligence request, or any time a VMP has gone more than a year without review. Replace every <<FILL: ...>> placeholder and route the completed report through document control. A filled specimen follows.
Document control header
| Field | Entry |
|---|---|
| Document title | VMP Gap Assessment for <<FILL: site / program>> |
| Document number | <<FILL>> |
| Date | <<FILL>> |
| Trigger | <<FILL: e.g. anticipated inspection, investor diligence, VMP overdue for review, no VMP currently exists>> |
| Assessment owner | <<FILL: e.g. Head of Validation>> |
1. Purpose
This report documents a structured assessment of whether the current Validation Master Plan, or the absence of one, accurately describes the validation program as it actually runs today, identifies gaps with a severity classification, and records a remediation plan.
2. Scope
| Dimension | Entry |
|---|---|
| VMP assessed | <<FILL: document number and version, or "no current VMP exists">> |
| Inventory source used | <<FILL: GxP system and process inventory register, or a fresh walk of manufacturing/facilities/computerized systems if no register exists>> |
3. Methodology
The assessment runs in a fixed order. First, compare the current system and process inventory, from the GxP System and Process Inventory Register if one exists, line by line against whatever the VMP claims to govern. Second, confirm the development phase the VMP assumes against the phase the company is actually in today. Third, check the reference list against the current version of every cited regulation, guidance, and recommendation. Fourth, check the approval and review history for currency and completeness. Each step is completed in full before findings are classified, so an early step’s outcome does not bias what later steps look for.
4. Findings
| # | Finding | Class | Evidence |
|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL: documentation gap / reference currency gap / phase mismatch / program gap>> | <<FILL>> |
5. Severity classification
| Class | Definition | Typical resolution |
|---|---|---|
| Documentation gap | The VMP’s text does not match a reality that is otherwise adequately controlled | Update the VMP; no new validation work needed |
| Reference currency gap | A cited standard, guidance, or recommendation has been superseded | Update the citation; confirm no substantive content depended on the superseded version’s specifics |
| Phase mismatch | The VMP’s stated development phase no longer matches the company’s actual phase | Update the phase-appropriate rigor section; confirm protocols already executed meet the correct rigor |
| Program gap | Validation activity behind a system is missing, incomplete, or was never performed | The most serious class; schedule and execute the missing activity, a document update alone does not close it |
6. Remediation plan
| Finding # | Action | Owner | Due date | Priority |
|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: before next external request / scheduled>> |
7. Conclusion
<<FILL: state plainly whether the VMP, once remediation is complete, will accurately describe the program, and whether any program gap poses a risk that needs escalation before remediation completes>>
8. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Assessment owner | <<FILL>> | ||
| Approver (Quality Assurance) | <<FILL>> |
Filled specimen
Extract for an invented clinical-stage company whose VMP was written for a Phase 1 program and never reviewed since the company moved into a pivotal trial. Company and system names are illustrative.
| # | Finding | Class | Evidence |
|---|---|---|---|
| 1 | Two environmental monitoring instruments added to the manufacturing suite eight months ago are not listed in the VMP’s scope statement | Documentation gap | Current inventory walk vs. VMP section 2 |
| 2 | VMP states Phase 1 rigor; the program has been running a pivotal-trial comparability protocol for four months | Phase mismatch | Program status vs. VMP section 4 |
| 3 | Reference list cites “PIC/S recommendations on qualification and validation” generically, predating the PI 006-4 consolidation | Reference currency gap | VMP section 10 vs. current PIC/S publication |
| 4 | The chromatography data system supporting release testing has no periodic review on record for over 18 months against a 12-month Tier 1 interval | Program gap | Computerized system validation records |
Remediation: findings 1 through 3 closed by a VMP update completed within 10 business days, owner the VMP holder. Finding 4 escalated immediately as a program gap; the overdue periodic review was scheduled and completed within 15 business days, with an interim risk assessment confirming no adverse impact on release decisions made during the gap, reviewed and accepted by Quality Assurance.
Conclusion: once remediation completes, the VMP accurately describes the current program. Finding 4 represented a real, if contained, control gap and was escalated and resolved on an accelerated timeline rather than folded into the routine VMP update.
Common findings this report prevents
- A gap assessment that stops at “the VMP needs an update” without distinguishing a documentation fix from a genuine, unresolved program gap.
- A program gap discovered during the assessment but not escalated with its own timeline, left to be absorbed into a routine VMP rewrite.
- A conclusion asserting the program is compliant without the underlying findings and remediation status to support it.
How to adapt this report
- Run the methodology in section 3 in order; do not skip to reference-checking without first reconciling the system inventory.
- Classify every finding honestly; a program gap mislabeled as a documentation gap understates the real risk.
- Give any program-gap finding its own escalation and timeline, separate from the routine VMP document update.