Conference Intelligence — PDA-FDA Joint Regulatory Conference, Cell and Gene Therapy CMC Framework

Three weeks after the PDA/FDA Joint Regulatory Conference closed at the Westin DC Downtown in Washington, DC (September 14–16, 2026), the most operationally consequential CMC signal for the remainder of 2026 is the same one that dominated the September floor discussions: FDA’s formalized flexible CMC framework for cell and gene therapies — “Flexible Requirements for Cell and Gene Therapies to Advance Innovation,” issued January 11, 2026 — is not a relaxation of standards, it is a restructuring of when and how CMC rigor is demonstrated, and every CGT CMC team that reads the guidance as permissive rather than strategic is building a specification architecture that CBER will challenge at BLA review. The conference also surfaced two additional signals — the FDA/EMA joint AI/ML guiding principles entering the CDER draft guidance pipeline, and data governance being operationalized by FDA inspection teams as a CGMP infrastructure requirement — that demand team-level assessment before year-end.

CMC teams that leave a conference like the September 2026 PDA/FDA Joint Regulatory Conference without a structured response process are not just slow — they are accumulating risk. Each of these three signals maps to a specific named section of your development program: a CTD module, an SOP, a specification document, or a validation protocol. The teams that will enter Q1 2027 in the strongest regulatory position are not the ones with the best products — they are the ones that converted conference intelligence into assigned program actions within 30 days. The teams that did not will discover the gaps at BLA review or on a Form 483.

FDA’s Flexible CGT CMC Framework: What the Conference Confirmed and What CMC Teams Must Do Now

FDA’s “Flexible Requirements for Cell and Gene Therapies to Advance Innovation,” issued January 11, 2026, is among the most significant structural changes to CGT CMC expectations in years. The guidance formalizes flexibility across three distinct pillars: clinical development, commercial specifications, and process validation. In the clinical development pillar, manufacturers are not required to meet full CGMP requirements before Phase 2 or Phase 3 trials, and no process validation is required for investigational products — but a phase-appropriate process control strategy is expected. This is not an absence of regulatory expectation; it is a defined, documented expectation calibrated to development stage.

The commercial specifications pillar introduces FDA’s willingness to consider flexibility for small patient populations, with specifications revisable based on postapproval manufacturing experience. The process validation pillar permits concurrent release of qualification lots and removes any mandatory three-lot requirement, shifting the regulatory burden to process understanding and product-specific justification. The critical strategic implication — confirmed repeatedly in September conference discussions — is that this flexibility restructures the timing and justification of CMC rigor, not the existence of it. A CGT CMC team that uses these flexibilities without a documented development rationale tied to each pillar will face CBER review challenges that no amount of post-submission remediation can efficiently resolve.

The conference consensus was unambiguous on one point: sponsors must discuss their CMC development approach with the relevant CBER review division before implementing any flexibility strategy. Teams that treat the January 11, 2026 guidance as regulatory permission to defer specification development or to slim down process validation packages without prior division alignment are not working within the flexibility framework — they are building a BLA package with unjustified gaps. For CGT programs currently in IND-stage development or approaching BLA filing, the immediate action is a gap assessment of which CMC decisions to date have assumed flexibility without documented CBER alignment.

AI/ML in Pharmaceutical Manufacturing: Reading the CDER Guidance Signal Before the Draft Arrives

CDER’s planned draft guidance on AI/ML quality considerations in pharmaceutical manufacturing — listed on CDER’s 2026 Guidance Agenda (published February 2026) — has not yet been issued, but the interim compliance framework is already operational. The FDA/EMA joint January 14, 2026 publication, “Guiding Principles of Good AI Practice in Drug Development,” established ten principles applicable to manufacturing AI systems: human-centric design, a risk-based approach, adherence to standards, clear context of use, multidisciplinary expertise, data governance and documentation, model design and development practices, risk-based performance assessment, life-cycle management, and clear essential information. These principles are not aspirational — they are the architecture against which CDER’s incoming draft guidance will be structured, and they are the framework FDA reviewers and inspectors are already applying to manufacturing AI systems they encounter.

The operational consequence is direct: any AI model currently used in process analytical technology (PAT), real-time release testing (RTRT), or batch disposition decisions needs to be inventoried and assessed against these ten principles before the CDER draft guidance arrives and imposes formal validation requirements. Teams using AI-assisted process control without documented lifecycle controls and human oversight records carry the highest pre-guidance vulnerability — not because they have violated a finalized rule, but because when the CDER draft arrives and sets validation thresholds, the remediation effort will be compressed into a timeline that conflicts with every other Q4 and Q1 regulatory priority. The September conference surfaced this signal as an immediate preparation priority, not a 2027 action item.

The ICH Q12 framework, “Technical and Regulatory Considerations for Pharmaceutical Product Lifecycle Management” (2019), provides relevant structural precedent here: established conditions and post-approval change management protocols developed under Q12 share the same documentation logic required for AI lifecycle controls under the FDA/EMA joint principles. Teams already operating mature Q12 change management systems have a head start; teams that are not should use the current pre-draft window to build AI system lifecycle documentation against Q12’s established conditions logic before the CDER guidance creates a compliance deadline.

Data Governance as CGMP Infrastructure: The Post-Conference Operational Priority

Data governance is no longer a quality systems enhancement initiative — it is a CGMP infrastructure requirement being operationalized by FDA inspection teams under 21 CFR Part 211. The regulatory distinction that CMC and quality teams must internalize is precise: data integrity refers to the completeness, accuracy, consistency, and attributability of individual data records; data governance refers to the organizational policies, system controls, and lifecycle management framework that ensures sustained data quality across the entire manufacturing enterprise. FDA Warning Letters for drug manufacturers rose roughly 50–59% year-over-year in FY2025, and documentation practices — missing signatures, incomplete forms, uncontrolled data — appear repeatedly across those letters, driving repeat observations at both US and foreign manufacturing sites.

The scale of inspection exposure is significant context: FDA issues several thousand Form 483 observations annually from drug quality inspections, and over 62% of FDA drug quality inspections in FY2024 targeted foreign manufacturing sites. Data governance gaps are not the exclusive problem of non-US facilities, but the concentration of inspection volume at foreign sites means CMC teams with manufacturing partners or CDMOs outside the US carry compounded exposure.

The post-conference action is not another gap assessment — it is assigning a named owner to your organization’s data governance policy framework, mapped explicitly to 21 CFR Part 211, with a target completion date that lands before your next scheduled FDA inspection or pre-approval inspection window.

The XGene Framework: Conference Intelligence Translation Protocol

XGene’s Conference Intelligence Translation Protocol is a structured 30-day post-conference methodology for converting FDA/EMA regulatory signals surfaced at major industry conferences into assigned CMC program actions.

Step 1 — Signal Triage: Within 72 hours of conference close, categorize each signal as immediate program action versus 90-day monitoring. The September 2026 conference produced three signals: the CGT flexible CMC framework is an immediate action item for any program in active development; AI/ML quality considerations is a 90-day monitoring item for programs without manufacturing AI, and an immediate action item for programs with active PAT, RTRT, or AI-assisted disposition; data governance is an immediate action item for any site with a scheduled or anticipated FDA inspection in the next 12 months.

Step 2 — Gap Mapping: For each signal categorized as immediate, identify the specific named CTD section, SOP, specification document, or validation protocol the signal affects.

Step 3 — Regulatory Response Memo: Produce a single memo — within 30 days of conference close — listing each signal, its triage classification, gap mapping output, responsible owner, and target completion date.

CMC teams that do not build a structured response to regulatory intelligence surfaced at major conferences fail at BLA submission, when specification gaps in the CGT flexible framework are questioned by CBER reviewers who expected prior division alignment. They fail at FDA inspection, when data governance deficiencies under 21 CFR Part 211 generate Form 483 observations that could have been closed in Q4 2026 with a targeted SOP revision. They fail when the CDER AI/ML guidance finalizes and their PAT or RTRT systems require retroactive validation documentation.

For your CMC team, can you identify today which of the three signals from the September 2026 PDA/FDA Joint Regulatory Conference maps to a specific named document, SOP, specification, or validation protocol in your current program, and whether that action item has been assigned to a responsible owner with a target completion date?