This is a ready-to-use ICH Q12 Product Lifecycle Management (PLCM) document. It is the single structured summary submitted with the marketing application and maintained across the product’s life: the established conditions and their reporting categories, any post-approval change management protocols (PACMPs), and outstanding post-approval CMC commitments. Replace every <<FILL: ...>> placeholder with your own specifics and keep it under version control, tied to the change record that drove each revision. A worked specimen follows. Verify each cited regulation against the current source before you rely on it.
Document control header
| Field | Entry |
|---|---|
| Product | <<FILL: PRODUCT NAME, dosage form, strength(s)>> |
| Marketing application number(s) | <<FILL: NDA / ANDA / BLA / MAA number(s) by region>> |
| Document number | <<FILL: PLCM-ID>> |
| Version | <<FILL: version>> |
| Effective date | <<FILL: date>> |
| Owner | <<FILL: Regulatory Affairs CMC lead>> |
| Dossier location | <<FILL: CTD Module 3.2.R or applicable regional section>> |
| Regions where this PLCM applies as filed | <<FILL: e.g. US only; confirm EU established-conditions applicability separately>> |
1. Purpose and status
This document summarizes the established conditions (ECs) for <<FILL: PRODUCT>>, their proposed regulatory reporting categories, any agreed post-approval change management protocols, and open post-approval commitments. It is a living document: every implemented change that touches an EC, and every new or executed PACMP, triggers a revision. It is not accurate merely because it was accurate at approval.
2. Development approach summary
State the approach underlying the EC granularity below, since an assessor reads the EC table against this context.
| Item | Entry |
|---|---|
| Development approach | <<FILL: minimal / enhanced, and for which unit operations>> |
| Registered design space(s), if any | <<FILL: parameter(s) and registered boundary, or "None">> |
| Supporting Q11 criticality assessment reference | <<FILL: document number>> |
3. Established conditions and reporting categories
Transcribe this table directly from the approved established conditions identification and classification matrix; the two documents must agree line for line.
| Established condition | Description / form | Dossier location | Proposed reporting category | Linked PACMP? |
|---|---|---|---|---|
<<FILL>> | <<FILL: parameter-based value/range, performance-based output, or design-space boundary>> | <<FILL: Module 3 section>> | <<FILL>> | <<FILL: Yes, reference / No>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
4. Post-approval change management protocols in effect
| PACMP reference | Change covered | Approval date | Status | Reporting category on execution |
|---|---|---|---|---|
<<FILL: PACMP-ID>> | <<FILL>> | <<FILL>> | <<FILL: approved, not yet executed / executed, date>> | <<FILL>> |
5. Outstanding post-approval CMC commitments
Actions agreed with a health authority to complete after approval, tracked here until closed.
| Commitment | Agreed with (region/authority) | Due date | Status | Closure evidence |
|---|---|---|---|---|
<<FILL: e.g. submit validation data on 3 additional commercial-scale batches>> | <<FILL>> | <<FILL>> | <<FILL: open / closed>> | <<FILL: submission reference>> |
6. Regional applicability notes
State, per target region, whether the established-conditions mechanism and this PLCM apply as a binding regulatory tool or as internal reference only.
| Region | ICH Q12 EC / PLCM mechanism applicable as filed? | Notes |
|---|---|---|
| United States | <<FILL: Yes, per 21 CFR 314.70 / 601.12 implementation>> | <<FILL>> |
| European Union | <<FILL: Partial; established conditions and PLCM are not fully compatible with the current EU variations legal framework per the EMA implementation statement; PACMP remains usable>> | Re-confirm against current EMA guidance before relying on this row. |
<<FILL: other region>> | <<FILL>> | <<FILL>> |
7. Maintenance procedure
- Any change-control record that touches an EC, executes a PACMP, or closes a post-approval commitment triggers a PLCM revision within
<<FILL: number>>business days of implementation or closure. - The revision cites the change-control or submission reference that drove it.
- Regulatory Affairs (CMC) confirms the updated PLCM still reconciles with the current Module 3 detail before issuing the new version.
- Quality Assurance confirms the change-control screening form (see the established-condition screening form) references the current PLCM version, not a superseded one.
8. Acceptance criteria
- Every EC in section 3 traces to an approved worksheet row and to a specific Module 3 location.
- Every PACMP in section 4 is either approved-and-pending or executed with a recorded outcome; none are silently stale.
- Every commitment in section 5 has a due date and a status; none are open past their due date without an escalation on file.
- Section 6 has been reviewed for every region where the product is marketed, not assumed identical across regions.
- The document version and its effective date match the current change-control record that authorized the latest revision.
9. References
ICH Q12, Technical and Regulatory Considerations for Pharmaceutical Product Lifecycle Management (Step 4, 2019), Annex I and Annex II. US FDA, 21 CFR 314.70 and 21 CFR 601.12. EU Variations Regulation (EC) No 1234/2008 and the European Commission Variations Classification Guideline. EMA implementation statement on ICH Q12 regarding applicability of established conditions and the PLCM document within the EU legal framework.
Confirm the current version and clause numbers of each reference before issue.
10. Revision history
| Version | Date | Author | Change-control reference | Summary of change |
|---|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL>> | <<FILL: N/A, initial filing>> | Initial PLCM submitted with the marketing application. |
11. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Regulatory affairs (CMC) | <<FILL>> | ||
| Quality assurance | <<FILL>> | ||
| Process development / MSAT | <<FILL>> |
Filled specimen
The following shows an illustrative extract for a tablet product with one active PACMP and one open commitment. Values are illustrative.
Section 3 extract:
| Established condition | Description / form | Dossier location | Proposed category | Linked PACMP? |
|---|---|---|---|---|
| Finished-product assay method | Validated HPLC method, USP-equivalent | 3.2.P.5.2 | Low / notification, via protocol | Yes, PACMP-2026-003 |
| Granulation end-point moisture | Parameter-based, 2.0% w/w | 3.2.P.3.3 | Moderate | No |
Section 4 extract:
| PACMP reference | Change covered | Approval date | Status | Category on execution |
|---|---|---|---|---|
| PACMP-2026-003 | Replacement of the compendial assay method with a validated UPLC alternative | 14 January 2026 | Executed 22 June 2026 | Low / notification, as pre-agreed |
Section 5 extract:
| Commitment | Agreed with | Due date | Status | Closure evidence |
|---|---|---|---|---|
| Submit annual stability data through 36 months for the first three commercial batches | FDA (approval letter condition) | 30 September 2026 | Open | Pending; annual report submission in preparation |
The PACMP row shows the mechanism working as designed: the method change was pre-agreed in January, executed in June once the equivalence data passed, and reported through the reduced category the protocol had already secured, without a fresh prior-approval wait.
Common inspection findings this document prevents
- A PLCM that was accurate at approval and has not been updated as changes accumulated.
- An executed PACMP with no closure entry, so the record does not show the reduced category was actually earned.
- A post-approval commitment past its due date with no status or escalation visible.
- Regional applicability assumed identical everywhere, contradicting the actual EU established-conditions position.
- A PLCM that does not reconcile with the current Module 3 detail, so an assessor cannot confirm what is actually established.
How to adapt this plan
- Populate section 3 by transcribing the approved established-conditions worksheet; do not re-derive the EC list from memory.
- List every PACMP the product has, whether pending or already executed, and keep the status current.
- Track every post-approval commitment from the approval letter or equivalent regional instrument until closed.
- Fill in section 6 honestly per region; do not assume US established-conditions treatment applies in the EU or elsewhere without confirmation.
- Wire your change-control procedure to trigger a PLCM revision automatically, per section 7, rather than relying on someone remembering to update it.