On this page
How should pediatric study plans and FDA correspondence be organized?
Establish the product’s applicable pediatric obligations, then keep the iPSP, proposed pediatric study request, FDA Written Request and formal waiver or deferral decisions distinct. Map each relevant indication and age group to its evidence, study plan, proposed disposition and actual FDA record. Track amendments against the last agreed version rather than treating every submitted proposal as accepted.
Before you begin
FDA human-drug and biologic pediatric development. Application-specific legal applicability must be established before selecting a request.
What you will prepare: A pediatric decision register and a traceable study-plan or correspondence package.
Sections covered in this guide (2)
Choose the decision before choosing the heading
Start with the application pathway, indication, proposed age range, development stage, existing FDA letters and expected marketing-submission date. PREA planning and BPCA pediatric-exclusivity work can concern the same studies, but they ask different questions. A pediatric study plan does not itself constitute an FDA Written Request for exclusivity.
Use 1.9.1 for a pediatric waiver request, 1.9.2 for a deferral request, 1.9.4 for a proposed pediatric study request or amendment, and 1.9.3 for a determination request supported by the Written Request and responsive reports. Use 1.9.6 for the relevant study-plan or exclusivity correspondence that is not better described by those specific tasks. The family heading 1.9 is an organizing node; it does not require an extra introductory letter.
Build one age-by-indication decision record
Create a working table with indication, age group, evidence already available, proposed study, formulation, extrapolation rationale, proposed waiver or deferral, and unresolved question. Include every relevant age group even when your proposal is to seek a waiver. For each row, retain the source of the proposal and its real status: planned, submitted, agreed or formally granted.
Draft the iPSP around the FDA template: disease and product context; extrapolation; planned waivers and deferrals; tabular development program; age-appropriate formulation; nonclinical and clinical studies; timing and references. When a study design cannot yet be detailed, explain which data are needed and how they will inform it. Do not silently fill an endpoint or sample size from another program.
For an amendment, compare the proposed plan with the last agreed version. Give the reason for each material change and identify consequences for other age groups, formulation work and deadlines. FDA recommends separate iPSP and PPSR documents even when submitted concurrently.
1.9.6: make the requested action and baseline explicit
A useful correspondence outline is: application and plan identity; FDA letter or discussion being answered; precise question or requested action; numbered response with supporting references; revised documents; remaining actions and owners. An attachment list should say whether a plan is clean, annotated, previously agreed or newly proposed. Avoid calling a requested change “agreed” before receiving the corresponding agency record.
For oncology, product designation and the planned application date are consequential. Public Law 119-75 section 6601 has a three-year application applicability provision following its February 3, 2026 enactment. Do not automatically impose its new combination-investigation provisions on every 2026 submission. Its section 6602 enforcement transition is separate. Have the regulatory owner identify the applicable legal version and retain that decision in the program record; an adult-only indication or orphan designation alone is not a complete pediatric applicability analysis.
Worked review: the agreed plan is no longer the current proposal
Fictional editorial exercise: an agreed plan includes an adolescent tablet study and a younger-child formulation program. A formulation change now delays the younger group, while the correspondence still says the entire plan is unchanged.
Revise the affected rows, explain the evidence and proposed schedule, and show whether an amendment or a different request is needed. Keep the adolescent commitment visible. If the actual agreed plan is missing, obtain it before asserting that the change is minor. Success is a reviewer who can identify exactly what changed and what FDA is being asked to do.
Keep the pediatric documents and their decisions distinct
Use one program register, but retain separate records for the different decisions. A common study can support several documents without making those documents interchangeable.
| Document or record | Question it answers | What it does not establish |
|---|---|---|
| Initial pediatric study plan | What pediatric development is planned under the applicable PREA framework? | Agreement to every full protocol or an issued BPCA Written Request |
| Proposed pediatric study request | What pediatric information does the sponsor propose for an FDA Written Request? | That FDA has issued the request or accepted every proposed term |
| FDA Written Request and amendments | What studies and conditions define the actual BPCA request? | A favorable exclusivity determination before the package is assessed |
| Planned waiver or deferral in the iPSP | What relief or later delivery does the sponsor propose? | The formal grant made at marketing-application approval |
| FDA agreement or decision letter | What did the agency actually accept, for which version and scope? | Acceptance of later unreviewed changes |
For each age-by-indication row, record the evidence gap, proposed study or relief, formulation dependency, proposed date, source document and status. Use explicit statuses such as proposed, submitted, agreed and granted. If a letter accepts a plan subject to a condition, retain the condition beside the study; a green status alone loses information that can affect the next submission.
Plan the initial submission from the actual development pathway. Section IV of the final July 2020 guidance sets out these different situations:
| Development situation | Timing described by the guidance |
|---|---|
| End-of-phase 2 meeting held | Submit the required iPSP no later than 60 calendar days afterward, or another time agreed with FDA, and before submitting the required assessment or investigation |
| No end-of-phase 2 meeting | Submit as early as practicable, before starting phase 3 or combined phase 2/3 studies |
| No phase 3 or combined phase 2/3 study, or such studies not under IND | Submit no later than 210 calendar days before the marketing application or supplement |
The latter rows describe the guidance’s recommended planning approach; they are not interchangeable choices for whichever date is most convenient. Track the review and agreement process separately. Missing required content can lead FDA to treat an iPSP as materially incomplete, while disagreement with a supported proposal is a different issue.
Version exercise: the agreed plan uses a tablet in adolescents and a new formulation in younger children. A revised manufacturing plan changes only the younger-child formulation. Map the affected studies and dates, submit justified changes through the appropriate process and keep the unaffected adolescent plan visible. Section VII recommends a tracked copy of the agreed plan and a clean proposed amendment; the amendment is not agreed until FDA says it is acceptable. Once the marketing application is accepted for filing, the guidance instead describes negotiating plan changes during application review.
Use the waiver, deferral and PPSR guides for the individual requests. Preserve the separate applicability dates in the 2026 statute rather than applying its future oncology provisions to every current program.
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
Is an agreed iPSP also an FDA Written Request for pediatric exclusivity?
No. The iPSP concerns the pediatric development plan under PREA; the BPCA Written Request is a distinct agency document with its own terms. FDA recommends separate iPSP and PPSR documents even when submitted concurrently. Shared studies or favorable meeting advice do not merge those records.
Does FDA agreement to the iPSP mean every pediatric protocol is agreed?
No. The final guidance distinguishes the study outline in the plan from full protocols and statistical analysis plans submitted separately to the IND. Preserve the precise scope of each agency interaction. Agreement to a development outline does not establish agreement to later detailed design or analysis choices.
Is a plan materially incomplete whenever FDA disagrees with a proposed waiver?
Not necessarily. The guidance distinguishes missing required content or justification from a complete, supported proposal with which FDA disagrees. Address all relevant age groups and indications and provide the rationale for requested relief. A disagreement should be resolved on its merits without confusing it with absent information.
When can an amended iPSP be described as agreed?
Section VII says amendments should not be considered agreed until FDA issues a letter stating they are acceptable. Retain the agreed baseline, tracked changes, clean proposal and response. If FDA does not agree with the amendment, the original agreed plan remains in force; submission alone does not replace it.
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
Pediatric Study Plans ↗July 2020 final guidance; sections III–VII and initial pediatric study plan template. Reopened September 22, 2026.
Draft guidance
Pediatric Drug Development: Regulatory Considerations ↗May 2023, Revision 1; DRAFT, not for implementation. Sections III–IV are contextual recommendations, not final guidance.
Statute
Consolidated Appropriations Act, 2026 ↗Public Law 119-75, enacted February 3, 2026; sections 6601(c) and 6602 distinguish future application applicability from the enforcement transition.
FDA resource
FDA pediatric exclusivity questions and answers ↗Live FDA resource, Q1–4 checked September 22, 2026. Historical office names and references to withdrawn guidance are not used as current instructions.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.9. A heading identifies placement, not mandatory applicability.

