This is a ready-to-use assessment for deciding whether an inherited validation package, from a product acquisition, an in-license, or a divestiture received into the business, is adequate to support continued commercial or clinical use under the acquiring company’s own Validation Master Plan, or whether it needs supplementing or redoing. Run this before a deal closes, not after. Replace every <<FILL: ...>> placeholder with your own specifics. A filled specimen follows.
Document control header
| Field | Entry |
|---|---|
| Document title | Validation Package Adequacy Assessment for <<FILL: acquired/in-licensed product>> |
| Document number | <<FILL>> |
| Assessment date | <<FILL>> |
| Transaction | <<FILL: acquisition / in-license / divestiture received>> |
| Originating company or site | <<FILL>> |
| Assessment owner | <<FILL: e.g. Head of Validation or Quality>> |
| Linked VMP | <<FILL: this company's own VMP document number>> |
1. Purpose
This assessment states, system by system and process by process, whether the validation evidence inherited with <<FILL: product>> meets this company’s own GxP-impact risk tier requirements, under this company’s own methodology, and records a disposition, accept as-is, accept with supplementation, or revalidate, for each item, so the acquiring company is never relying on an inherited validation conclusion it has not independently checked.
2. Scope
Applies to every GxP-relevant system, process, utility, and computerized system connected to the manufacture, testing, or release of <<FILL: product>>, as inherited from <<FILL: originating company or site>>, whether or not those systems or that site transfer with the deal.
3. Methodology
This assessment does not accept “the process has been running for years” as validation by itself. For every item, three questions are answered in order. First, run this company’s own GxP-impact test and risk tier assignment on the item, independently of whatever tier, or lack of one, the originating company used; a prior tier is informative, not controlling. Second, determine whether anything material has changed since the inherited evidence was generated, a site move, an equipment change, a new raw material source, a different quality system, since a change of that kind breaks the continuity any validation conclusion, retrospective or otherwise, depends on. Third, where no material change has occurred, confirm the inherited evidence would meet ICH Q7’s own conditions for a retrospective validation claim, a well-established process, critical quality attributes and critical process parameters already identified, in-process controls already established, no significant unexplained failures, a characterized impurity profile, and data from enough representative batches to support the claim, recognizing that FDA’s current process validation guidance does not use the term “retrospective validation” at all and treats prospective or concurrent validation as the current expectation even for an existing process. An item that fails any of the three questions is supplemented or revalidated, not accepted as-is.
4. Adequacy assessment table
| # | Inherited item | This company’s own risk tier | Material change since evidence generated | Disposition | Rationale |
|---|---|---|---|---|---|
| 1 | <<FILL: e.g. drug substance PPQ at originating CDMO>> | <<FILL>> | <<FILL: Yes/No>> | <<FILL: accept as-is / supplement / revalidate>> | <<FILL>> |
| 2 | <<FILL: e.g. cleaning validation>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 3 | <<FILL: e.g. computerized system used to generate release data>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 4 | <<FILL: e.g. analytical release method>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Add one row per system or process the product touches; an acquisition spanning more than one originating site typically needs a separate set of rows per site.
5. Supplementation and revalidation plan
| Finding # | Item | Action required | Owner | Due date |
|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL: e.g. method transfer bridging study, new computerized system validation, full revalidation>> | <<FILL>> | <<FILL>> |
An item disposed “accept as-is” is cross-referenced into this company’s own GxP system and process inventory register at the risk tier assigned in section 4, not re-recorded under the originating company’s prior tier.
6. Residual risk statement
<<FILL: state plainly whether, once the supplementation and revalidation plan completes, the inherited validation package will meet this company's own VMP requirements in full, and whether any accepted residual risk remains between deal close and plan completion, with the rationale for accepting it and any interim control in place>>
7. Roles
| Role | Responsibility |
|---|---|
| Business development / corporate development | Flags the pending transaction to the assessment owner early enough for this assessment to run before close, not after |
| Assessment owner (Validation or Quality) | Runs the methodology in section 3, completes the assessment table, owns the overall disposition |
| Receiving site or CDMO quality unit | Confirms whether the receiving site’s own facility, equipment, and quality system actually match what a given inherited item’s disposition assumes |
| Quality Assurance | Approves the completed assessment and any accepted residual risk |
| Executive sponsor | Is informed of any finding that could affect transaction timing or post-close supply continuity |
8. References
ICH Q7, Good Manufacturing Practice Guidance for Active Pharmaceutical Ingredients, Section 12.4, Approaches to Process Validation (retrospective validation conditions, 12.44 to 12.45), and Section 12.5, Process Validation Program (12.50, batch count expectation for a retrospective claim). FDA guidance, “Process Validation: General Principles and Practices” (January 2011). See the paired article, Validation Master Planning for a Clinical-Stage Biotech, for the reasoning behind treating an inherited validation package independently of the originating company’s own risk framework.
Confirm the current version of each reference before issue.
9. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL>> | <<FILL>> | Initial issue. |
10. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (Validation or Quality) | <<FILL>> | ||
| Reviewer (Receiving site or CDMO quality unit) | <<FILL>> | ||
| Approver (Quality Assurance) | <<FILL>> |
Filled specimen
Extract for an illustrative acquisition: a clinical-stage biotech acquires an approved AAV gene therapy asset from a smaller originating company, with drug substance manufactured at the originating company’s CDMO and fill-finish moving to a newly contracted second CDMO post-close. Company and CDMO names are illustrative.
| # | Inherited item | This company’s own risk tier | Material change | Disposition | Rationale |
|---|---|---|---|---|---|
| 1 | Drug substance process performance qualification, originating CDMO, same site and equipment post-close | Tier 1 | No | Accept as-is, cross-referenced into this company’s own inventory register | Clears this company’s own GxP-impact test; no site, equipment, or process change since PPQ |
| 2 | Fill-finish cleaning validation, originating company’s prior fill-finish CDMO | Tier 1 | Yes, fill-finish is moving to a newly contracted second CDMO | Revalidate at the new site | Cleaning validation is site- and equipment-specific; the inherited conclusion does not transfer to equipment it was never run on |
| 3 | Originating company’s LIMS, release testing data capture | Tier 1 | Yes, system will not transfer with the deal | New computerized system validation required for the receiving instance | Inherited validation speaks to a system that will no longer exist in production |
| 4 | Potency release assay, validated at the originating company’s contract analytical lab | Tier 1 | No change to the method itself; execution moving to this company’s own contracted lab | Accept the original validation data as supporting evidence, supplement with a method transfer bridging study at the new testing site | Method’s scientific validity carries over; the new site’s ability to execute it reproducibly needs its own evidence |
Supplementation plan: finding 2, fill-finish cleaning revalidation at the new CDMO, owner Validation Lead, scheduled to complete before the first post-close commercial batch; finding 3, new LIMS CSV, owner Computerized Systems Owner, scheduled to complete before the receiving instance is used for release testing; finding 4, method transfer bridging study, owner QC, scheduled to complete before the new lab issues a release result.
Residual risk statement: drug substance manufacturing and the potency assay’s underlying science are accepted on inherited evidence, cross-referenced at this company’s own Tier 1 classification. Fill-finish cleaning validation and LIMS computerized system validation are not yet complete at deal close; interim control is that no post-close commercial batch releases until each open finding closes, a condition stated to the executive sponsor and tracked against the supplementation plan rather than assumed covered by the inherited package.
Common findings this assessment prevents
- An inherited validation package accepted because it exists, with no check against this company’s own GxP-impact risk tiers.
- “Retrospective validation” invoked as a general label for any pre-existing process, when ICH Q7’s own exception is bounded to a well-established process with no significant change, and current FDA process validation guidance does not name the approach at all.
- A site, equipment, or quality-system change between the originating company and the acquiring company’s own operations overlooked because the underlying process or product name did not change.
- A post-close commercial release proceeding on an inherited computerized system’s validation when the receiving instance is, in fact, a different installation that was never itself validated.
How to adapt this assessment
- Run section 3’s methodology before the transaction closes; a finding discovered after close is a supply continuity problem, not a due diligence checkbox.
- Score every item against this company’s own risk tiers independently; do not carry forward the originating company’s tier as a given.
- Treat any site, equipment, or quality-system change as breaking continuity for that item, regardless of how long the underlying process has run elsewhere.
- Build a separate set of assessment rows for each originating site or CDMO if the acquired product’s manufacturing network spans more than one.