FDA Meeting Package Requirements: What Submission Teams Need to Know
- 3 minutes ago
- 5 min read
A practical look at the August 2026 final guidance on formal meetings for PDUFA products.
FDA’s August 2026 final guidance clarifies how sponsors should request and prepare for formal meetings. It also sets practical expectations for where meeting packages are submitted, how they should be organized, and when FDA expects to receive them. For submission teams, there are implications for planning and timelines. For some meeting types, the package is due with the initial meeting request. Developing, finalizing, and publishing the package may require early coordination across regulatory, clinical, CMC, statistics, and other cross-functional teams. In these scenarios, that work cannot wait until the meeting is granted.
What changed in FDA’s final formal meetings guidance?
On August 12, 2026, FDA issued the final guidance, Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products. The guidance, announced in the Federal Register on August 13, finalizes the September 2023 draft and applies to formal meetings involving PDUFA products regulated by CDER and CBER. It does not apply to abbreviated new drug applications, biosimilars, or medical device submissions.
The guidance covers six meeting types: Type A, Type B, Type B end of phase (EOP), Type C, Type D, and INTERACT. Much of the document concerns meeting strategy and conduct. From a regulatory publishing standpoint, three areas deserve close attention: submission route, package navigation, and submission planning.
Where should an FDA meeting request and meeting package be submitted?
FDA says the written meeting request should be submitted through the Electronic Submissions Gateway for CDER or CBER applications or, when appropriate for CDER, through the CDER NextGen Portal. If an application or tracking number already exists, submit the request under that number.
The final meeting package follows the same basic route. FDA says it should be submitted to the relevant application through the gateway or, for applicable CDER submissions, the CDER NextGen Portal. The guidance also identifies additional options for certain CBER submissions and noncommercial IND holders.
The WAYS team has seen INTERACT meeting packages submitted successfully through the ESG. However, email and portal-based submission pathways are also commonly used.
Application routing should be an early publishing decision, not an administrative detail to resolve at the end. The team needs to confirm the destination, submission pathway, and relationship to the existing application before building the sequence.
What format does FDA expect for a meeting package?
FDA expects a meeting package that is organized for review, not simply a collection of technically correct content. The package should:
follow the proposed meeting agenda;
use sequential page numbering;
include a table of contents with appropriate electronic links;
include appropriate indices, appendices, and cross-references; and
help reviewers move between sections before and during the meeting.
In publishing terms, that means building and quality-checking the package as a navigable document. Links need to work. Page references need to be accurate. Questions, supporting summaries, appendices, and agenda items should be easy to move between. A package can be scientifically sound and still slow a reviewer down if its structure is difficult to follow.
FDA also recommends keeping the questions focused. The final package should generally contain no more than 10 questions, including subquestions. The numbering and scope should remain consistent between the meeting request and the meeting package.
When is an FDA meeting package due?
The deadline depends on the meeting type. These timelines are based on the PDUFA Reauthorization Performance Goals and Procedures for Fiscal Years 2023 Through 2027 and are reflected in the final guidance. The most important distinction is whether the package is due with the request or after FDA schedules the meeting.
Meeting type | FDA receipt of meeting package |
Type A | With the meeting request |
Type B | No later than 30 calendar days before the meeting or WRO response |
Type B (EOP) | No later than 50 calendar days before the meeting or WRO response |
Type C | No later than 47 calendar days before the meeting or WRO response |
Type C: qualifying early surrogate endpoint consultation | With the meeting request |
Type D | With the meeting request |
INTERACT | With the meeting request |
Source: FDA final guidance, Table 4. WRO means written response only. The guidance includes limited timing exceptions when certain Type B (EOP) or Type C meetings are scheduled earlier than the standard window.
Why do these deadlines matter?
For Type A, Type D, INTERACT, and the specified early surrogate endpoint Type C meetings, there is no post-request window for finishing the package. The submission-ready package needs to exist when the request is filed.
That requirement is especially important for early-stage sponsors. An INTERACT meeting may occur before a company has a full regulatory operations function in place, yet its package still needs the same disciplined planning, navigation, and quality control. If publishing starts only after the scientific content is considered final, the schedule can become very tight, very quickly.
The safer approach is to work backward from the package deadline and build in time for content stabilization, document assembly, link creation, publishing quality control, corrections, approval, and transmission. From a project management perspective, it helps to treat the meeting request and meeting package as separate deliverables, each with its own development, review, approval, and publishing timelines, even when they share the same FDA submission date.
How should teams plan an FDA meeting package?
A practical plan starts with five questions:
Which meeting type is being requested?
Is the package due with the request or before the scheduled meeting?
Which application and submission pathway will be used?
When will the agenda, questions, and supporting data be stable enough to publish?
Who owns final link testing, page and cross-reference checks, and submission QC?
For meeting types that require the package at the time of request, these decisions should be made before the request date is placed on the calendar. For Type B, Type B (EOP), and standard Type C meetings, teams have more time after scheduling, but the FDA deadline should still drive the internal production plan.
What is the key takeaway for sponsors?
FDA meeting package preparation is both a regulatory strategy task and a submission management and publishing task. The content must support the questions the sponsor wants FDA to answer, but it also must reach the correct application, on time, in a form reviewers can navigate easily.
WAYS Pharmaceutical Services supports sponsors with the formatting, linking, compilation, quality control, and submission planning behind FDA meeting packages.
Preparing for an FDA meeting? Bring WAYS in early to keep your submission organized, compliant, and on schedule. Let’s talk.
Frequently asked questions
Does an FDA meeting package have to be submitted with the meeting request?
Sometimes. Type A, Type D, INTERACT, and qualifying early surrogate endpoint Type C packages are due with the request. Other Type B, Type B (EOP), and standard Type C packages are due before the scheduled meeting or written response date.
Does FDA require electronic links in a meeting package?
Yes. FDA says the table of contents should include appropriate electronic linkage, and the package should support navigation across its sections.
How many questions should an FDA meeting package include?
FDA generally recommends no more than 10 questions in total, including sub-questions. Each sub-question should be numbered separately.
Can an FDA meeting package be submitted through the CDER NextGen Portal?
Yes, when the portal is the appropriate route for a CDER submission. FDA also identifies the Electronic Submissions Gateway for CDER and CBER applications.
What happens if an FDA meeting package is late or inadequate?
FDA may reschedule or cancel a meeting when a late or inadequate package does not allow enough time for review. For certain meeting requests submitted with the package, inadequate information can also contribute to denial.
Comments