FDA's Final PDUFA Meeting Guidance: What Changed From the Draft

On August 12, 2026, FDA finalized the draft guidance it issued nearly three years ago, Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products. The Federal Register notice followed on August 13. So did the PDUFA VIII commitment letter, which has plenty to say about meetings in its own right.

Two documents, one day apart, pointing the same direction. Here's what changed, what's coming, and what we'd do about both.

What didn't change in FDA's final PDUFA meeting guidance

If you've built a development timeline around FDA's meeting clock, that clock still works.

The six meeting categories are intact: Type A, Type B, Type B (EOP), Type C, Type D, and INTERACT. Every response target, scheduling target, and package deadline carried over from the draft unchanged.

All intervals run in calendar days from FDA's receipt of the meeting request. Specified surrogate-endpoint Type C meetings follow the at-request package rule rather than the 47-day rule.

Scope held as well. The guidance still applies to CDER- and CBER-regulated drug and biologic products, and still excludes ANDAs, biosimilar and interchangeable biosimilar applications, and device submissions.

Nothing here forces you to redo your planning math. You can check your own dates against these intervals with our FDA Meeting Timeline Calculator. What changed is what FDA expects to receive from you, and how likely you are to get the meeting format you asked for.

Type D meetings: tighter scope, and FDA can reclassify your request

The 2023 draft described Type D as a meeting for a narrow set of issues. The final guidance says what narrow means and gives FDA a mechanism when a request isn't.

A Type D meeting should generally cover no more than two focused topics, involve three to five total questions, and require input from no more than three disciplines or divisions. Anything broader, anything needing cross-center input, anything with a question list that keeps growing: that's a Type B or a Type C, and FDA now says so plainly.

The enforcement piece matters more than the definition. If FDA decides a Type D request is scoped wrong, the agency can convert it to the appropriate meeting type. You can accept the conversion or withdraw, but you don't have to submit a new request from scratch. That's a reasonable process. It's also a slower one than the Type D timeline you were counting on, which is why scoping judgment belongs at the front of the process. It's a routine part of what our regulatory affairs team works through with sponsors before a request goes in.

The final guidance also gives six concrete examples of appropriate Type D use, replacing the three thinner ones in the draft:

• A specific question about a complex or innovative trial design element, such as an innovative pediatric approach
• A specific question about presenting data after a pre-NDA or pre-BLA meeting
• A follow-up question that raises a new issue after meeting minutes, a written response, or an advice letter
• A specific Phase 3 design element previously discussed with FDA
• Specific nonclinical protocol questions after a pre-IND meeting or written response
• Clarification of a limited number of comments from a meeting held more than 20 calendar days earlier

That last one is worth noticing. It draws a line between the Request for Clarification process, which has its own 20-day window, and the point at which a clarification becomes a new meeting.

INTERACT meetings: a narrower eligibility window

The draft positioned INTERACT loosely, as a mechanism for novel products facing unique early-development challenges. The final guidance is more restrictive on both ends.

INTERACT is now expressly a pre-pre-IND mechanism, for programs facing unusual IND-enabling barriers that could delay first-in-human testing. On the front end, you should already have selected a particular investigational product or product-derivation strategy. Come too early, without a candidate, and you're not eligible. On the back end, INTERACT is generally not the right category once a pre-IND meeting has happened or an IND has been filed.

FDA also expanded the topic examples: novel nonclinical models and toxicology designs, CMC strategies supporting first-in-human studies, proof-of-concept and biodistribution studies, novel target-population considerations for a future first-in-human study, and development approaches built on limited non-U.S. data.

That list describes a specific kind of sponsor. If you're developing a radiopharmaceutical or another novel modality where the nonclinical package doesn't have an obvious precedent, INTERACT is often the right first conversation with FDA, and the narrowed window means timing it correctly matters more than it used to.

The four FDA meeting formats, and when FDA can issue written responses

The final guidance names four meeting formats:

• Hybrid in-person (HIP) face-to-face. Core FDA and requester participants attend in person where feasible, with peripheral participants joining virtually. If your core people aren't going to be in the room, request a virtual face-to-face instead.
• Virtual face-to-face video conference (VCN). All participants join by video.
• Teleconference (TCN). Participants join by audio.
• Written response only (WRO). FDA sends written responses in lieu of a live meeting.

The bigger change is about who decides. For pre-IND Type B, Type C, Type D, and INTERACT requests, FDA may grant a written response even when you asked for a live meeting. You can follow up in writing to explain why discussion is necessary, and FDA will decide whether to change the format. For Type A, non-pre-IND Type B, and Type B (EOP) meetings, a WRO happens only if you asked for one.

This authority isn't brand new. What's new is that it's written down, in a final guidance, in language that reads like an operating principle rather than an exception.

What FDA now expects in a meeting request

The final guidance is more prescriptive about what belongs in a meeting request: the proposed format, the date you plan to submit the package, a purpose and background statement that's concise but actually informative, agenda timing, your attendees, the FDA attendees or disciplines you're asking for, your objectives, and precise questions grouped by discipline.

Four specifics are worth internalizing:

• Cap your questions at 10 total, subquestions included.
• Number subquestions separately instead of using lettered subparts, and keep the numbering and scope aligned between the request and the package.
• Justify any FDA attendee who isn't essential to answering your questions, and say whether a later date would be acceptable. FDA notes directly that these requests can interfere with scheduling inside the PDUFA window.
• Check your submission route. The guidance points to the electronic gateway for CDER and CBER applications and, for CDER, the CDER NextGen Portal, while retaining document-room options for noncommercial IND holders.

Our FDA Meeting Request Checklist maps every component to the request, the package, or both, and it's been updated for the final guidance.

What PDUFA VIII proposes for FDA meetings

Everything above is final and in effect. What follows is not. The PDUFA VIII commitment letter describes commitments that would be worked out in a subsequent meeting guidance, expected before September 30, 2028. Treat it as direction of travel rather than a rulebook.

Two items stand out.

Multi-divisional meetings. A sponsor developing a product under multiple INDs across multiple therapeutic areas or review divisions could request a multi-divisional meeting within an existing formal meeting category, rather than through a new standalone type. The sponsor would submit the request simultaneously to every relevant division and propose a lead division. FDA would target a response no later than seven calendar days beyond the standard response timeline, and scheduling no later than 14 calendar days beyond the standard scheduling timeline. For anyone running a platform or a broad-indication program, this is the most interesting thing in the letter.

A justification requirement for live meetings. PDUFA VIII would require sponsors to explain, in the request itself, why interactive discussion is necessary rather than written responses. A stated preference for a teleconference or a face-to-face wouldn't be enough. The rationale would need to connect the format to the nature of the questions, not to logistics, and give FDA enough issue-specific context to judge whether discussion adds value beyond written preliminary responses.

The letter is fairly specific about what a persuasive rationale looks like. Real-time exchange is easiest to justify when FDA's answer on one point materially changes your next decision point, when you need to work through development options and tradeoffs rather than get discrete answers, when you need alignment across disciplines or divisions, or when written feedback would leave ambiguity that stalls a protocol or an application strategy.

How sponsors should prepare for FDA meetings now

The final guidance and the commitment letter are pulling in the same direction, and it isn't subtle. FDA is trying to spend its meeting capacity on interactions that need to be live, and it's asking sponsors to do more of the work in writing. Here's how we'd respond.

None of this is about writing more. It's about writing so that a reviewer with no chance to ask you a follow-up question can still give you a usable answer. For sponsors without a full-time regulatory function, that's a meaningful lift, and it's one reason we offer fractional regulatory leadership alongside project work.

FDA meeting support from Bracken

Bracken's regulatory affairs team helps sponsors choose the right meeting type, scope questions that survive FDA's gatekeeping, and build packages that hold up under written review. We work across medical imaging, radiopharmaceuticals, and clinical trial strategy, and we support everything from a single meeting request to fractional regulatory leadership.

Two free tools, both updated for the August 2026 final guidance: