On this page
What makes an FDA meeting background package useful?
Organize it around the decisions in the granted meeting scope. For each question, state the sponsor’s position, summarize relevant evidence with enough detail to interpret it, disclose limitations and point to exact source versions. Reconcile the question list, agenda and development context; attachments should support that reasoning rather than replace it.
Before you begin
PDUFA meeting packages under the final August 2026 guidance; tailor content and timelines to the granted meeting and its development stage.
What you will prepare: A concise, traceable briefing package that supports each requested decision.
Freeze the questions and evidence cutoff
Reconcile the granted meeting purpose, final questions, sponsor positions, attendees, agenda and date with the request. Establish a data cutoff and source versions. The background package must let FDA assess the questions; it should not ask reviewers to infer the development strategy from a pile of reports.
The guidance §VII.C calls for the request information plus updated attendee information, background, proposed discussion and supporting data organized by discipline and question. For end-of-phase discussions, the package should support assessment of the planned trials with relevant dose-response, efficacy, safety, design and analysis information. Do not claim phase 2 evidence is available when only a planned analysis exists.
Use an evidence-to-question structure
A practical structure is: product and development context; brief prior-FDA-interaction history; question list; discipline-specific background; sponsor position for each question; quantified evidence and limitations; focused proposed plan; references. Keep identifiers stable across the request, package and slides.
Report the population, denominator, endpoint, timepoint, effect estimate and uncertainty needed to interpret a result. State whether endpoints or analyses changed during the trial. “Statistically significant” alone is insufficient. Distinguish exploratory observations from prespecified findings and avoid using a cross-study comparison as if it were randomized evidence.
Full protocols, complete reports and detailed raw data are generally not appropriate substitutes for the summarized meeting package described by the guidance. Where a specific question needs a relevant excerpt or design detail, provide it with the necessary context and a precise source reference.
Worked check: favorable result, different population
Fictional exercise: the question proposes an endpoint for an untreated population, but the supporting table reports only previously treated participants. Add the population difference and its implications to the sponsor’s rationale; do not relabel the table. If the evidence cannot support the requested conclusion, narrow the question or identify the needed work.
Change the meeting to a CMC-focused discussion: replace irrelevant efficacy background with the process, product comparability or control-strategy evidence needed for the actual questions. The guide’s structure remains useful, but the scientific content must change.
Review each question as a small evidence argument
Use an internal map to check whether a reviewer can move from the question to the proposed decision without reconstructing the program from appendices. This is an authoring aid; FDA does not require this particular table.
| Element | Review question | Common gap |
|---|---|---|
| Question and proposed answer | What exactly does the sponsor want FDA to assess? | A broad request for program acceptability |
| Relevant evidence | Which results or technical findings support the proposal? | A favorable headline without population or denominator |
| Interpretation | Why does this evidence support the proposed next step? | Association described as causation or exploratory work as confirmatory |
| Limitation | Which mismatch or uncertainty could change the advice? | A different population, process or analysis set left unexplained |
| Source and version | Can the reviewer find the result and its context? | A table copied from an undated slide deck |
| Proposed consequence | What changes if FDA disagrees? | No connection between the question and the development plan |
CMC exercise: a meeting question concerns the proposed commercial process, but the supporting comparability table uses an earlier manufacturing scale. State which process versions the table compares and which difference remains relevant to the proposed process. Ask the technical owner for the needed rationale or evidence. Renaming the column “commercial” would misrepresent the source and leave FDA without the context needed for advice.
Use stable question numbers in tables, section headings and cross-references. Separate observed results from planned analyses. For clinical findings, reconcile population, denominator, endpoint, timepoint, estimate and uncertainty with the source; for CMC, use the corresponding product/process versions, batches, methods and acceptance context. The same reasoning structure can support different disciplines without recycling irrelevant clinical background.
If material new data arrive after the package is submitted, identify what changed and contact the project manager about handling it. Sections VIII–IX explain that new information or proposals can require additional review, a different meeting arrangement or a new request. Preliminary responses are not an invitation to send a new proposal and assume it will be reviewed on the original schedule.
Check the meeting request and package deadlines, then set up the follow-up record with the same question IDs.
Your preparation checklist
0/3 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
Can full study reports replace the meeting-package narrative?
Generally not. FDA’s guidance calls for summarized information organized around the meeting objectives and questions, with enough quantified detail to interpret the relevant findings. Protocols, full reports and detailed data are generally not appropriate substitutes. Use precise references and focused supporting material where needed, while keeping the reasoning explicit.
Can exploratory results be included in a briefing package?
They can inform a discussion when their status and limitations are clear. Identify whether endpoints or analyses changed and explain the population, methods and uncertainty. Do not present exploratory observations as prespecified confirmation, or ask reviewers to infer that distinction from a report buried in an appendix.
What should happen if important data arrive after the package deadline?
Assess how the new information changes the questions or sponsor position and discuss handling with the FDA project manager. The guidance recognizes that additional data or questions may require more review time or a different interaction. Do not silently replace the evidence or assume the original meeting schedule guarantees review.
Is a favorable p-value enough evidence for an FDA meeting question?
No. The guidance expressly notes that calling a result significant is insufficient. Explain the endpoint, population, analysis status and relevant quantified findings, including uncertainty and limitations. The package must show why those results support the proposed decision, rather than relying on a statistical label alone.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Guidance
Formal Meetings Between FDA and Sponsors or Applicants of PDUFA Products ↗Final August 2026; §§III–VII and XI. Replaces September 2023 draft. PDF and final-status landing page checked September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.6.2. A heading identifies placement, not mandatory applicability.