On this page
How do you prepare an FDA formal dispute resolution request?
Identify the regulatory action and the unsuccessful attempt to resolve it with the original deciding office. Build the scientific or medical argument from information already in the relevant administrative record, state the requested resolution and follow the center’s submission instructions. Separate an appeal from new evidence, advice clarification and any later appeal of a final decision.
Before you begin
CDER/CBER sponsor scientific or medical appeals above the division level; not a universal route for inspection, device or informal advice disputes.
What you will prepare: A focused appeal package and a controlled record of subsequent clarifications and decisions.
Sections covered in this guide (3)
Establish what decision is being appealed
Identify the FDA action, its date, deciding office, affected application and the precise disagreement. Assemble the decision letter and record of efforts to resolve the issue at the original level. The guidance distinguishes a regulatory action from advice in meeting minutes or general correspondence. A disagreement with advice should not automatically become a formal appeal.
State the requested outcome and why the existing record supports it. If new data or a new analysis would change the decision, give the original deciding office the opportunity to review that information first. FDA treats new analyses of old data as new information for this purpose; changing the statistical presentation is not necessarily a permissible clarification.
1.10.1: write an argument the deciding official can navigate
Organize the package around the disputed issue, not the entire development history. Use a chronology of the action and attempted resolution; an accurate statement of FDA's position; the sponsor's scientific reasoning; exact references to material already in the administrative record; the proposed resolution; and an explanation of why that resolution addresses the concern. Include application identity, contact, and any requested meeting in accordance with the guidance.
An editorial issue table can use five columns: FDA concern; original-record location; sponsor interpretation; consequence for development; requested resolution. Preserve unfavorable evidence and its limitations. Avoid introducing fresh analyses in an appendix labeled background.
Check the current center-specific handling instructions. CDER identifies submission to the application and a copy to its formal-dispute-resolution project manager. The guidance distinguishes CBER handling. Do not send the same unresolved matter through competing FDA routes without a deliberate procedural assessment.
1.10.2: keep clarification separate from a new appeal
A follow-up should identify the appeal, the FDA communication being answered and the requested clarification. Answer in the same numbering as the request and cite the existing record. State explicitly if material is new rather than disguising it as a correction. Preserve interim responses, final decisions, meeting correspondence and any subsequent appeal as distinguishable records.
Before escalating again, establish whether the current response is final and which management level made it. Do not label an interim request for clarification a final denial. A delivery receipt is evidence of transmission, not a favorable resolution.
Worked review: a persuasive new analysis belongs elsewhere first
Fictional editorial exercise: a clinical-hold appeal includes a newly pooled safety analysis that the division has never reviewed. The team argues that it uses previously submitted patient data.
Flag the analysis as new information and resolve the route with the regulatory owner. Build the appeal from the actual record or first submit the new analysis to the original level. If the original action or reconsideration response cannot be found, the procedural history is incomplete; do not infer that escalation is ready.
Check the argument against the original decision record
Before polishing the appeal, review each supporting item for its relationship to the original decision. This working table helps identify a procedural problem that persuasive writing cannot solve.
| Supporting item | Record check | Consequence for drafting |
|---|---|---|
| Decision letter | Actual action, date, application and deciding office | Quote or summarize the disputed conclusion accurately |
| Previously submitted report | Submission date, document version and exact location | Explain how the existing evidence supports the requested outcome |
| New analysis of submitted data | Whether the original official had the analysis for review | Submit for original-level review; old data do not make a new analysis old information |
| Reconsideration history | Request, meeting if applicable and actual response | Establish that the original level had the opportunity to resolve the issue |
| Interim appeal response | Clarification requested and current deciding level | Answer the request; do not treat it as a final denial |
Record exercise: a sponsor attaches an unchanged table from its previously submitted report and also a newly calculated subgroup comparison. The first item can be traced to the existing record; the second is a new analysis even if every participant was in the original dataset. Separate the two. An appendix named “clarification” does not change what the analysis is. The guidance also cautions against adding new information or analyses to a reconsideration request itself; route new evidence to the application for review by the original office.
For each contested issue, write the agency concern first, then the sponsor’s interpretation, the exact supporting location and the proposed resolution. Explain unfavorable evidence instead of omitting it. Finish with a short procedural chronology so the deciding official can see what happened without searching several years of correspondence.
Track acceptance, the response due date, interim responses and the final decision separately. The guidance’s 30-calendar-day response framework for covered human-drug applications permits an interim response; it does not promise a final resolution within 30 days. Meetings and clarification can establish different response anchors. Use the actual acknowledgment and subsequent correspondence to maintain the record.
For a disagreement about advice rather than a regulatory action, start with the meeting follow-up guide. When the argument depends on new evidence, assess the appropriate amendment route before escalating.
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 FDA meeting advice be appealed through formal dispute resolution?
The guidance distinguishes advice in minutes or general correspondence from a regulatory action suitable for this appeal process. Identify what FDA actually did before selecting a route. A discussion or clarification with the review division may be appropriate; disagreement alone does not turn advice into an appealable action.
Is a new analysis allowed if the underlying data were already submitted?
FDA treats new analyses of previously reviewed data as new information for formal dispute resolution. The original deciding official might have reached a different conclusion after reviewing them. Submit the new analysis to the application for original-level review rather than embedding it in an appeal as background or clarification.
Can an interim response be appealed to the next management level?
The guidance says FDA does not intend to accept that escalation until the lower management level has made a final decision on the appeal. Preserve the interim response, identify what clarification or interaction is requested and track the eventual final disposition before assessing a further appeal.
Does the 30-day response framework guarantee a final appeal decision?
No. For applications covered by the guidance’s PDUFA, BsUFA or GDUFA framework, the response can be interim or final. Meetings and clarifying information have their own response anchors. Record the actual acknowledgment and correspondence instead of equating 30 elapsed days with a final decision or a successful appeal.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Technical specification
FDA eCTD v4.0 headings and hierarchy ↗Version 2.2, February 2025; Module 1 printed pages 2–3 and application-specific mapping appendix. Placement does not establish applicability.
Guidance
Formal Dispute Resolution: Sponsor Appeals Above the Division Level ↗November 2017, Revision 1 final guidance; III–VI. Reopened September 22, 2026.
FDA resource
CDER Formal Dispute Resolution ↗Current CDER process and contact route checked September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.10. A heading identifies placement, not mandatory applicability.