This is a ready-to-use project plan for the multi-year readiness effort behind a marketing application’s CMC data package. It turns a readiness timeline from a slide into a governed plan: five phases from 24-36 months out to the inspection window, each with an owner, entry and exit criteria, and a place to track actual dates against planned ones. Use it alongside the pre-BLA CMC data integrity audit protocol, which this plan schedules, and the BLA/NDA readiness data package article for the reasoning behind each phase. Replace every <<FILL: ...>> placeholder. A filled specimen follows.
Document control header
| Field | Entry |
|---|---|
| Document title | CMC Readiness Timeline for <<FILL: PRODUCT / PROGRAM>> |
| Document number | <<FILL: PLAN-ID>> |
| Version | <<FILL>> |
| Product / program | <<FILL>> |
| Application type | <<FILL: BLA / NDA / supplement>> |
| Target filing date | <<FILL>> |
| Plan owner | <<FILL: role, e.g. CMC Program Lead>> |
1. Purpose
This plan governs the schedule and gate criteria for the work that has to be done, and the evidence that has to exist, before <<FILL: PRODUCT>> can be filed and can survive its pre-license or pre-approval inspection. It exists because the organizations that struggle at inspection are rarely the ones missing a specific document; they are the ones that treated data package readiness as a late-stage writing exercise instead of a scheduled, owned deliverable with its own milestones years out.
2. Scope
This plan covers the CMC data integrity readiness workstream: site and system readiness, contributing-site audits, the pre-BLA data integrity audit, the pre-submission meeting, and inspection rehearsal. It does not replace the overall regulatory submission project plan, the clinical or nonclinical readiness plans, or the eCTD publishing plan; those are referenced where they intersect. See the eCTD submission content and lifecycle plan for the publishing-side plan this one feeds.
3. Governance
| Role | Responsibility |
|---|---|
| Executive sponsor | Owns the filing date decision and resolves cross-functional resourcing conflicts. |
| CMC program lead (plan owner) | Owns this plan, tracks phase gates, escalates slippage. |
| QA / data integrity lead | Owns the pre-BLA audit phase and the defect closure gate. |
| Site quality (each contributing site) | Owns site-level audit and remediation milestones. |
| CMC regulatory lead | Owns the pre-submission meeting phase and specification/shelf-life finalization. |
| Program management office | Maintains the tracked schedule (section 5) and reports status at the cadence in section 6. |
Review this plan and its status at a standing cadence of <<FILL: monthly / at each phase gate>>, and at every phase-gate transition without exception.
4. Phases, entry and exit criteria
Phase 1, 24-36 months before filing: Foundation
Entry: Development program has produced a credible target filing window. Activities: Identify every data-contributing site and laboratory, internal, clinical manufacturing, and contract; build the multi-year audit schedule; confirm every system that will generate submission-cited data is validated or has a validation plan with a date; confirm audit trails are enabled across those systems. Exit criteria: Complete site list confirmed against the development plan; audit schedule approved; system validation gap list is zero or fully dated. Owner: CMC regulatory, QA.
Phase 2, 12-18 months before filing: Site and method readiness
Entry: Phase 1 exit criteria met. Activities: Complete pre-submission audits of all contributing sites (see the multi-site and CDMO data contribution readiness checklist); close GMP and data integrity gaps found; freeze the validated analytical methods that will generate submission data. Exit criteria: Every contributing site checklist is Pass; no open High-severity site finding; method inventory frozen and version-controlled. Owner: QA, site quality.
Phase 3, 6-12 months before filing: Data integrity audit
Entry: Phase 2 exit criteria met. Activities: Run the pre-BLA CMC data integrity audit against the actual results cited in the current Module 3 (or equivalent) draft; complete the traceability matrix; close the defect log. Exit criteria: Traceability matrix coverage complete for the defined population; zero open High-severity findings in the defect log; audit summary report approved by senior quality. Owner: DI SME, analytical and process SMEs.
Phase 4, 3-6 months before filing: Regulatory alignment
Entry: Phase 3 exit criteria met. Activities: Hold the pre-BLA or pre-NDA meeting; finalize specifications, shelf life, and CPP justifications against verified data; incorporate any FDA feedback into the submission. Exit criteria: Meeting minutes received and action items closed or scheduled before filing; specifications and shelf life locked against audited data. Owner: CMC regulatory.
Phase 5, 0-3 months before filing and through inspection: Rehearsal
Entry: Phase 4 exit criteria met. Activities: Confirm raw data retrieval works in real time for a sample of cited results; brief and rehearse subject-matter experts for interview; confirm front-room and back-room inspection logistics. Exit criteria: Live retrieval drill completed successfully for a sampled set of results; SME mock interviews completed; front-room/back-room roles named. See FDA inspection readiness and managing a live inspection for what this phase is rehearsing against. Owner: QA, site management.
5. Tracked schedule
| Phase | Planned start | Planned exit | Actual exit | Status | Slippage (days) | Escalation if slipped |
|---|---|---|---|---|---|---|
| 1, Foundation | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 2, Site and method readiness | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 3, Data integrity audit | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 4, Regulatory alignment | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 5, Rehearsal | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
6. Risk and contingency
- A phase that misses its exit criteria does not silently roll into the next phase; it is escalated to the executive sponsor with a revised date or a named risk accepted in writing.
- Phase 3 (the data integrity audit) is the phase most likely to surface work that cannot be rushed, revalidating a method, re-running a stability time point is not achievable in weeks. Build schedule buffer into Phase 2, not Phase 3, so a Phase 3 finding still has room to close.
- If a contributing site becomes unavailable (closure, loss of accreditation, acquisition) at any phase, treat it as a Phase 1 event: reassess the site list and audit schedule immediately rather than absorbing it into the current phase’s plan.
- Track status against this plan at the cadence set in section 3; a phase gate is not “on track” by default, it is confirmed on track against its actual exit criteria.
7. References
ICH M4Q(R1), The Common Technical Document for Registration of Pharmaceuticals for Human Use: Quality. FDA guidance, Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products (for the pre-BLA/pre-NDA meeting in Phase 4). FDA Compliance Program 7346.832M and 7346.832, for the inspection this plan prepares for.
Confirm the current version of each reference before issue.
8. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
9. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Plan owner (CMC Program Lead) | <<FILL>> | ||
| QA | <<FILL>> | ||
| Executive sponsor | <<FILL>> |
Filled specimen
An illustrative excerpt of the tracked schedule for an example biologic BLA, roughly 14 months into the plan.
| Phase | Planned start | Planned exit | Actual exit | Status | Slippage (days) | Escalation if slipped |
|---|---|---|---|---|---|---|
| 1, Foundation | 2025-01-15 | 2025-06-30 | 2025-06-18 | Closed | -12 (early) | N/A |
| 2, Site and method readiness | 2025-07-01 | 2025-12-15 | 2025-12-29 | Closed | 14 | Absorbed by Phase 3 buffer; noted to program board |
| 3, Data integrity audit | 2025-12-16 | 2026-05-31 | In progress | Open | 0 so far | Two High-severity findings under active closure, tracked in the defect log |
| 4, Regulatory alignment | 2026-06-01 | 2026-08-31 | Not started | Planned | - | - |
| 5, Rehearsal | 2026-09-01 | 2026-11-30 | Not started | Planned | - | - |
The 14-day slip in Phase 2 (one contract laboratory’s remediation ran long) was absorbed because Phase 1 finished 12 days early and the program board had built a buffer into Phase 3’s start rather than assuming every phase runs exactly to plan. That is the entire value of tracking actual against planned by phase instead of only tracking the single filing date: a two-week site slip six months before filing is a rounding error if you see it coming, and a crisis if you only notice it at the filing date.
Common inspection findings this plan prevents
- A readiness effort that existed only as a slide, with no owner, no tracked dates, and no visibility into whether Phase 3’s data integrity audit is actually on schedule to finish before filing.
- A site-level slip in Phase 2 that goes unnoticed until it threatens the Phase 3 audit population.
- A data integrity finding surfaced late in Phase 3 with no schedule buffer left to close it before the pre-submission meeting or the filing date.
- Inspection rehearsal (Phase 5) skipped or compressed because every earlier phase ran late and consumed its buffer.
How to adapt this plan
- Set your product, application type, and target filing date in the header.
- Adjust phase durations to your program’s actual complexity; a first-in-class cell and gene therapy BLA with multiple contract sites needs more buffer in Phases 2 and 3 than a well-precedented small-molecule NDA at a single site.
- Keep the tracked schedule (section 5) current at every governance review; a plan that is not updated against actual dates is not actually governing anything.
- Link Phase 3’s exit criteria directly to the acceptance criteria in your pre-BLA CMC data integrity audit protocol, so the two documents cannot drift apart.
- Confirm every regulation and guidance reference in section 7 against the current published version before issue.