FDA published final guidance on August 13, 2026 covering formal meetings between FDA and sponsors or applicants of products subject to the Prescription Drug User Fee Act. It applies to drug and biological products regulated by CDER and CBER and finalizes the draft issued in September 2023.
This is guidance, not a new binding regulation. But for regulatory teams, it represents FDA’s current thinking about how these interactions should work.
What Changed?
The guidance covers standardized procedures for:
- requesting meetings;
- selecting meeting types;
- preparing background packages;
- scheduling;
- meeting formats;
- conducting meetings;
- documenting outcomes.
FDA says changes from the 2023 draft include additional Type D meeting scenarios, clarification around Initial Targeted Engagement for Regulatory Advice on CDER and CBER ProducTs meetings, and additional information about meeting formats FDA may grant.
Those changes matter because not every regulatory issue requires a traditional, broad Type B meeting.
Sponsors increasingly need to match the size of the question with the appropriate FDA interaction.
Why This Matters
A meeting with FDA can influence years of drug-development work. Yet many teams spend enormous effort on the science and surprisingly little time deciding whether they are requesting the right meeting, asking questions FDA can realistically answer, or giving reviewers enough information to provide useful advice. A poorly designed FDA meeting can waste a valuable regulatory interaction.
Imagine a sponsor asking six broad questions spanning clinical design, CMC, statistics and labeling in a meeting format designed for a narrower issue.
FDA may not have enough time or sufficiently focused background information to resolve them.
The operational lesson is simple: Meeting preparation should begin with the regulatory decision you need, not with the slide deck you want to present.
The final guidance provides a more mature framework for matching questions, meeting type and supporting documentation.
Who Is Most Affected?
This is particularly relevant to:
- regulatory affairs;
- clinical development;
- CMC;
- statistics;
- nonclinical teams;
- program management;
- medical writing;
- senior development leadership;
- external regulatory consultants.
Small biotechnology companies may have even more at stake because a single FDA interaction can determine whether a study proceeds as designed or needs substantial revision.
Regulatory Foundation
FDA notes that these formal interactions sit within existing regulatory frameworks including 21 CFR Part 312 for investigational new drug applications, Part 314 for NDAs and related applications, and Part 601 for biologics license applications. The guidance itself is issued under FDA’s good-guidance-practice framework in 21 CFR 10.115 and is nonbinding.
The distinction is important.
A recommended background-package structure in guidance is not the same thing as a statutory requirement.
However, ignoring FDA’s stated meeting practices can reduce the quality of the advice a sponsor receives.
What Changes in Practice?
Companies should examine their FDA meeting SOP, not just distribute the new guidance to regulatory affairs. A useful internal process would require teams to answer five questions before submitting a meeting request:
1. What decision do we need from FDA?
“Discuss Phase 3” is too broad.
A better internal framing might be:
“Determine whether FDA agrees that the proposed primary endpoint and analysis population can support the pivotal efficacy assessment.”
That forces the team to identify the regulatory decision.
2. Is this the correct meeting type?
The final guidance expands examples associated with Type D interactions.
Companies should check whether existing SOPs still assume that every meaningful development issue belongs in a Type B meeting.
3. Can FDA answer the questions as written?
Questions such as: “Does FDA agree with our program?”
are usually less useful than focused questions supported by clearly stated sponsor positions.
A good question gives FDA something concrete to react to.
4. Is the background package decision-focused?
Large packages are not automatically better packages.
The reviewer should be able to understand:
Issue → Sponsor position → Supporting evidence → Question.
5. How will advice be captured and implemented?
The meeting is not finished when the call ends.
Organizations need a controlled process for:
- reviewing minutes;
- resolving discrepancies;
- translating advice into program decisions;
- updating development plans;
- documenting why FDA advice was or was not followed.
What Should Sponsors Review Now?
First, compare the final guidance with the current regulatory-interaction SOP.
Look specifically at:
- meeting-type definitions;
- meeting-request templates;
- package preparation timelines;
- internal governance;
- question-writing standards;
- attendee selection;
- rehearsals;
- meeting-minute review;
- commitments made during meetings;
- post-meeting action tracking.
Second, examine any FDA meeting currently being planned.
Do not assume procedures based on the 2023 draft remain unchanged.
Common Gaps
A frequent problem is question inflation.
Once teams learn a meeting is being requested, every function wants to add its issue.
The result can be a package containing unrelated questions that compete for limited reviewer attention.
Another gap is poor traceability between FDA feedback and subsequent decisions.
Six months after a meeting, someone may ask:
“Why did we choose this endpoint?”
The organization should be able to trace the answer back to:
FDA interaction → internal assessment → decision → protocol/version.
Example
A sponsor developing a rare-disease therapy needs FDA input on one focused statistical issue.
Under an old internal model, the team might wait months to bundle that question with several other topics for a larger meeting. The updated framework may lead regulatory affairs to evaluate whether a more targeted meeting is appropriate.
The practical gain is not merely speed.
It is receiving regulatory advice before a downstream protocol decision becomes expensive to reverse.
Frequently Asked Questions
Is FDA’s formal meeting guidance legally binding?
No. FDA explicitly states that the guidance represents its current thinking and does not establish legally enforceable responsibilities.
Which products does the guidance cover?
It concerns formal meetings involving development and review of new drugs and biological products regulated by CDER and CBER under PDUFA.
What changed from the 2023 draft?
FDA identifies additional Type D scenarios, clarification around targeted regulatory-engagement meetings and additional meeting-format information among the changes.
Should sponsors update their SOP immediately?
There is no blanket requirement to rewrite an SOP simply because guidance changed. However, organizations should perform a documented impact assessment and determine whether existing procedures still reflect FDA’s final recommendations.
What is the biggest practical improvement companies can make?
Create stronger traceability between each meeting question, FDA’s answer, the internal decision and the resulting protocol, CMC, statistical or submission change.