What The New PDUFA Guidance Means For Drug Development

By Krishna Sai Penumarthi, PharmD, PgDipRA, MSRA, CCRP

What can one conversation change in the life of a drug development program?

Potentially, quite a lot.

A development team can spend months generating data, debating strategy, and preparing for a critical interaction with the FDA. Then a relatively short exchange can validate the path forward, raise a question the team had not fully considered, or create the need to rethink an important part of the program.

And the impact rarely stops with regulatory affairs. A question about an endpoint can reach clinical development and biostatistics. Manufacturing feedback can move into CMC and quality. A request for additional evidence can affect operations, resources, and timelines.

That is what makes formal FDA meetings so important. The meeting itself is only one moment. The real story is everything that has to happen before it, and everything that may change after it.

FDA's newly finalized guidance, Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products, provides an updated framework for these interactions. Issued in August 2026, it applies to formal meetings related to the development and review of new drug and biological products regulated by CDER and CBER.

One of the biggest changes is that sponsors now have more options for when and how they can approach the FDA. PDUFA VII introduced two newer meeting types, Type D and INTERACT. Type D is meant for situations where a sponsor has a few specific questions and may not need a broader meeting. INTERACT comes even earlier, giving developers of novel products an opportunity to speak with the FDA before the traditional pre-IND stage. In practical terms, sponsors do not always have to wait for a major development milestone to get FDA input when an important question comes up.

These changes are useful, but the meeting type is only part of the picture. The value of an FDA meeting still depends heavily on how well a sponsor prepares for it and what the team does with the feedback afterward.

Not Every FDA Meeting Is the Same

The FDA's framework includes different meeting types because development teams need different kinds of regulatory input at different points.

Type A meetings are intended for issues that can stall an otherwise progressing development program or for certain important safety matters. Put simply, when a significant issue is preventing the program from moving forward, a Type A meeting can provide a pathway for timely FDA discussion.

Type B meetings occur around established development milestones, including pre-IND and pre-NDA or pre-BLA meetings, while Type B end-of-phase meetings address certain important transition points. Think of these as opportunities to align with the FDA before moving through major stages of development.

Type C meetings cover matters that do not fall within the other meeting categories. In practical terms, they provide a route for FDA discussion when an important development question does not fit one of the more specifically defined meeting types.

Type D meetings, a newer meeting type introduced under PDUFA VII, are intended for a limited set of focused issues that do not require a broader discussion. INTERACT meetings, also introduced under PDUFA VII, allow for earlier FDA engagement on novel products before the traditional pre-IND stage.

The interaction itself may also take different forms, including in-person, virtual, teleconference, or written response. The review division ultimately determines the meeting format if the request is granted.

For people outside regulatory affairs, the simplest way to think about all of them may be this: Formal FDA meetings create structured opportunities to reduce uncertainty before important development decisions are made.

Choosing the right meeting matters, but it’s only the beginning.

The Most Important Part May Happen Before The Meeting

One of the strongest messages I take from the guidance is the importance of preparation.

A sponsor is not simply requesting time on FDA's calendar. The meeting request and supporting package need to explain the purpose of the interaction, provide relevant background, and identify the questions for which FDA's input is being sought.

That sounds straightforward but asking a good regulatory question can be difficult. A well-prepared meeting package must reflect conversations across clinical development, statistics, CMC, quality, operations, and other functions.

Imagine a team has concerns about the acceptability of an endpoint in a planned trial. It could broadly ask the FDA what it thinks about the strategy. A more useful approach is to identify the decision the team is facing, provide the evidence supporting its proposed approach, and ask a focused question that FDA can meaningfully address.

This is also where internal alignment becomes critical. Before asking whether the FDA agrees with an approach, the organization should understand why it is proposing that approach and what it will do if FDA does not agree.

The FDA Responds — Sometimes Before The Meeting

For applicable meeting types, the FDA provides preliminary written responses before the scheduled meeting.

If the FDA provides clear written responses ahead of time, spending limited meeting time repeating them may accomplish little. Instead, the team should use that time to discuss what remains unresolved, determine where clarification is needed, and identify which issues deserve deeper discussion.

A sponsor’s preparation does not end when the briefing package is submitted but continues even after the FDA starts answering the questions.

The FDA's Answer Rarely Belongs To Regulatory Affairs Alone

Earlier in my career, while working on the sponsor side, I saw how discussions surrounding FDA interactions could extend beyond the regulatory function. Regulatory affairs may serve as the primary interface, but the implications can reach many different teams.

That experience changed how I think about FDA meetings. I recently saw a good example of this at our site in August 2026. We were preparing to start a new study when the sponsor informed us that the FDA had requested additional changes to the protocol. The sponsor needed to submit an amendment, which meant the study could not move forward as originally planned.

For us, that changed the start-up timeline almost immediately. Activities we had been preparing for had to be put on hold while we waited for the amended protocol and further direction from the sponsor. We were not part of the FDA discussion itself, but we felt the impact of it directly.

This is how FDA feedback can move beyond the regulatory team. At the site level, it may eventually show up as protocol amendments, revised eligibility criteria, additional assessments, new training requirements, or shifts in enrollment timelines. What starts as a regulatory discussion at the sponsor level can ultimately affect how and when a study is carried out at the site..

The people who need to understand FDA feedback, therefore, are not necessarily limited to the people who participated in the meeting.

The Meeting Ends, But The Work Doesn't

Once the meeting is over, the team has to decide what to do with the FDA’s feedback. That may mean changing part of the protocol, revisiting the statistical approach, doing additional CMC work, adjusting timelines, or collecting more data before moving forward. The feedback itself is important, but what really matters is how the team responds to it.

The FDA's framework emphasizes documentation and follow-up, helping establish what was agreed upon, what remains unresolved, and what actions may follow.

Follow-up can also matter when the FDA's feedback is not completely clear. The framework provides a formal Request for Clarification process following formal meetings or written responses. This is not an opportunity to introduce new questions or proposals; rather, it allows a sponsor to clarify its understanding of feedback already provided.

Where FDA Guidance Helps, And Where It Can Only Go So Far

The FDA's final guidance provides something all development programs need: structure. It establishes a common framework around meeting types, formats, requests, packages, timelines, preliminary responses, meeting conduct, and documentation. That predictability can make important regulatory interactions easier to plan and manage.

However, there is a limit to what procedural guidance can accomplish. The FDA can welcome a meeting, but it cannot ensure that a development team comes to the meeting with right question. The FDA can describe what information should support the discussion. It cannot create alignment among clinical, regulatory, statistical, CMC, quality, and operational teams. The FDA can provide feedback. It cannot determine how effectively an organization will translate that feedback into action. And finally, the FDA can standardize the meeting process, but it cannot standardize the quality of the conversation.

The most effective FDA meetings, therefore, are opportunities to reduce uncertainty at moments when the decisions ahead can have significant consequences for a development program. Making the most of those opportunities requires asking the right questions, bringing the right evidence, involving the right people, listening carefully to the answers, and then doing something meaningful with them.

References:

1. U.S. Food and Drug Administration. (2026, August). Formal meetings between the FDA and sponsors or applicants of PDUFA products: Guidance for industry. FDA guidance
2. U.S. Food and Drug Administration. (n.d.). Formal meetings and requests for feedback for CBER-regulated products. Retrieved September 2026, from FDA CBER resource

About The Author:

Krishna Sai Penumarthi, PharmD, PGDipRA, MSRA, CCRP, is a clinical research manager whose work spans clinical trial operations, regulatory affairs, and research quality across pharmaceutical sponsors, CROs, and investigator sites. Over more than six years in the field, he has contributed to Phase 1–4 drug, biologic, and medical device studies and has held leadership responsibilities in the operational and regulatory management of industry-sponsored clinical research.

In his current role, Krishna leads a portfolio of clinical trials and works across study start-up, regulatory compliance, quality systems, inspection readiness, sponsor and CRO collaboration, and trial execution.

Krishna has completed more than 35 independent manuscript reviews for medical and scientific journals and has been selected to evaluate scientific work through programs including the Regeneron International Science and Engineering Fair and the Sigma Xi Student Research Showcase. He is an IEEE Senior Member, a Full Member of Sigma Xi, and a SOCRA Certified Clinical Research Professional.