Type A, B, and C FDA Meetings — CMC Request Strategy and the Pre-Submission Intelligence Framework

FDA formal meetings are among the most consequential strategic decisions in drug development, and most CMC teams use them incorrectly. Not because they fail to request them — Type B End-of-Phase 2 meetings are standard in most development plans. But because the CMC section of the meeting background package is written to inform FDA rather than to force FDA to take a position. A question that asks FDA to “evaluate our proposed control strategy” produces advisory commentary. A question that states your proposed position, cites the specific CTD section it applies to, and ends with “is this approach acceptable?” produces a binding regulatory record. The difference between those two outcomes is the difference between intelligence and documentation — and most CMC teams are producing documentation.

The commercial consequence compounds silently: every CMC question that produces advisory commentary instead of a binding position is a decision point your NDA reviewer will revisit from scratch, years later, with no prior FDA record to anchor the discussion — while a properly designed question becomes a regulatory asset you can cite directly at chemistry review.

Type A, B, and C FDA Meetings — The PDUFA VII Timeline Commitments and the CMC Application at Each Development Milestone

Under PDUFA VII’s performance goals for fiscal years 2023 through 2027, FDA’s meeting-type commitments carry specific timelines that determine how each meeting type functions strategically. Type A meetings — reserved for matters necessary for a stalled program to proceed, such as clinical hold removal, dispute resolution, or a post-Complete Response Letter meeting — must be held within 30 days of FDA’s receipt of the request; CMC use of Type A is rare, arising specifically when a sponsor needs to dispute FDA’s interpretation of a CMC deficiency following a CRL or negotiate a revised post-marketing commitment timeline. Type B meetings — including Pre-IND, End-of-Phase 1, End-of-Phase 2, and Pre-NDA/BLA meetings — are the primary CMC intelligence vehicle and must be held within 60 days of the request, with FDA increasingly resolving these through a written-response-only alternative rather than a face-to-face meeting. Type C meetings, covering general CMC advice on topics not addressed by a Type A or B meeting, must be held within 75 days and are the right vehicle for specific technical questions — stability protocol acceptability, a method validation approach — that arise between major development milestones.

The meeting background package for a Type B pre-NDA meeting carries binding structural constraints under FDA’s internal CDER operating procedures: a page limit in the 40-to-50-page range, of which the CMC section typically occupies 15 to 25 pages, and a maximum of five substantive questions per meeting. That five-question budget is the single most consequential constraint most sponsors underweight — if all five questions address topics FDA guidance already answers, the meeting produces no new intelligence regardless of how well the questions are written, while a package that dedicates two of five questions to the program’s primary CMC uncertainty returns substantially more regulatory value than a package that spreads coverage thinly across routine confirmations.

Meeting Background Package CMC Architecture — The Specification Table, the 5-Question Budget, and the Binary Question Design That Forces a Position

FDA’s 2017 Formal Meetings guidance is explicit that if the agency cannot answer a question from the information provided in the background package, FDA is not obligated to provide a definitive answer — which makes the CMC section’s supporting content as consequential as the questions themselves. A defensible CMC section includes a concise program status summary covering manufacturing site, current scale, and validation status; a proposed specification table for drug substance and drug product, because FDA cannot evaluate acceptance criteria that are never disclosed; a stability summary showing the time points available and the extrapolation basis for the proposed shelf life; and the specific questions themselves, each with supporting context.

The question design itself follows four criteria that together force a binding FDA position rather than commentary: the question references a specific CTD section by number — 3.2.P.4, 3.2.S.4.2, 3.2.P.8.3 — states the sponsor’s current proposed approach with its supporting rationale summarized in three to five sentences, names the specific acceptance criterion, analytical method, or design choice at issue, and ends with a binary: “is this approach acceptable?” A question that instead asks FDA to “evaluate,” “review,” or “comment on” a program invites exactly the advisory language — “the approach appears reasonable,” “FDA has no major concerns at this time” — that cannot be cited as a regulatory record at NDA review, because it never required FDA to commit to a position in the first place.

Meeting Minutes as Regulatory Records — The 30-Day Confirmation Window and the Binding Protection That Depends on Using It Correctly

FDA issues draft meeting minutes within 30 days of the meeting, and the sponsor then has 30 days to confirm their accuracy — a hard deadline, not a courtesy window. Confirmed minutes constitute a regulatory record that FDA reviewers at the NDA or BLA stage are expected to honor: if confirmed minutes state that a proposed specification is acceptable, the reviewer at NDA chemistry review cannot require a different specification without documented scientific rationale and supervisory concurrence. Sponsors who let the 30-day window lapse without confirming, or who confirm minutes without challenging hedged qualification language, lose meaningful ground: minutes that state FDA’s position is “acceptable pending review of the complete application” read, to a sponsor, like an approval — but that qualifying phrase gives a future NDA reviewer room to apply a different standard, asserting the position was never fully settled. The 30-day confirmation window is the sponsor’s only opportunity to negotiate that kind of hedging language out of the record before it becomes permanent.

The strategic implication for programs planning under PDUFA VII’s written-response-only trend is direct: a well-constructed written response to a precise, binary CMC question carries the same regulatory weight as confirmed meeting minutes, meaning sponsors should not default to requesting an in-person meeting when a properly framed written request, supported by adequate data in the background package, can secure the same binding protection in a fraction of the time.

The XGene FDA Meeting CMC Intelligence Framework Designing Pre-Submission Interactions That Create Durable Regulatory Protection

The XGene FDA Meeting CMC Intelligence Framework is a structured regulatory strategy for designing Type A, B, and C meeting requests that generate binding CMC positions rather than advisory commentary.

Step 1 — Meeting Type Selection and Milestone Mapping: Map each development milestone against the Type A/B/C decision tree, reserving Type B meetings for the highest-value pre-NDA and End-of-Phase 2 junctures and directing narrower, between-milestone CMC questions to Type C requests where a full Type B slot would be wasted on a single issue.

Step 2 — Meeting Background Package CMC Architecture: Build the specification table, stability summary, and program status section first, so every question submitted has the supporting data FDA needs to answer it definitively rather than deferring for lack of information.

Step 3 — Binary CMC Question Design and Five-Question Prioritization: Draft every question to the four-part standard — CTD section reference, stated sponsor position, named acceptance criterion, and binary close — and rank the program’s CMC uncertainties so the five-question budget is spent on the questions FDA guidance does not already answer.

Step 4 — Minutes Confirmation and Qualification Language Review: Treat the 30-day minutes confirmation window as an active negotiation opportunity, reviewing every FDA position statement for hedging language that would allow a future NDA reviewer to reopen the question, and formally challenging that language before the confirmation deadline rather than after.

The output of the XGene FDA Meeting CMC Intelligence Framework is a confirmed regulatory record — meeting minutes or a written response — that can be cited directly at NDA chemistry review to defend a specification, method, or process decision, not a meeting transcript that reads well but commits FDA to nothing.

A CMC team that spends its five-question budget generating advisory commentary has used the same 60-to-90-day window a better-prepared program would have used to secure binding FDA commitments on the exact issues an NDA reviewer will scrutinize years later. The cost of that gap is not visible at the meeting — it surfaces at NDA chemistry review, when a specification the sponsor assumed was settled becomes an open question again, this time under a PDUFA review clock rather than a pre-submission planning timeline. Programs that treat every formal meeting as an opportunity to build a durable regulatory record, rather than to inform FDA of their plans, are the ones that reach NDA review with fewer open questions and less exposure to reviewer discretion.

For your next FDA Type B pre-NDA or End-of-Phase 2 meeting, can you identify today whether each of your CMC questions includes a stated sponsor position with supporting data, a reference to the specific CTD section it addresses, and a binary “is this approach acceptable?” conclusion?