Clinical Development Plan Template: What to Include Before Your First FDA Meeting

What a Clinical Development Plan Actually Does
Core Sections to Include
Common Gaps That Slow Down FDA Meetings
Structuring the CDP for a Pre-Sub Meeting
Before You Write the CDP: Align Your Regulatory Strategy First
FAQs
Conclusion

A clinical development plan is the document that separates sponsors who walk into a Pre-Sub meeting ready to have a productive conversation from those who walk in with questions FDA already expects them to have answered. Whether your first FDA meeting is a Pre-Sub (Q-Sub), a Pre-IDE, or an early Type B interaction, the plan you bring shapes how the agency reads your program's maturity.

This article gives you a practical template: what sections to include, what each one needs to accomplish, and where sponsors most often leave gaps that slow things down.

What a Clinical Development Plan Actually Does

A clinical development plan (CDP) is not a protocol. It is the strategic document that explains your overall clinical evidence strategy across the full arc of your program — from first-in-human through pivotal, and ultimately to your target regulatory submission.

FDA reviewers use it to assess whether you understand the evidentiary requirements for your intended pathway, whether your proposed study designs will actually generate data that supports that pathway, and whether your risk management thinking is credible.

For a medical device startup, the CDP is often the first document that demonstrates regulatory competence to both FDA and your investors. Getting it right before that first meeting matters.

Core Sections to Include

1. Device or Product Description

Start with a clear, concise description of what the device does, how it works, and what it is made of. Include your intended use statement and indications for use as currently drafted — these will evolve, but FDA needs to understand what you are talking about before evaluating anything else.

If you are pursuing a 510(k), identify the predicate device here. If you are on a De Novo or PMA pathway, state that explicitly and explain why.

2. Regulatory Pathway and Target Submission Type

Specify your intended submission type: IDE, 510(k), De Novo, PMA, or HDE. Explain the rationale. If you have not yet determined the pathway, that is a legitimate question to bring to the Pre-Sub — but present your current working hypothesis with supporting reasoning, not a blank.

Include a brief summary of any prior FDA feedback and how your current plan responds to it.

3. Preclinical Evidence Summary

Summarize the bench testing, biocompatibility data, and animal study results you have completed or have underway. FDA will want to see that you have addressed basic safety questions before moving to human subjects.

Identify any preclinical gaps you know exist and your plan to close them. Acknowledging gaps proactively is stronger than leaving FDA to find them.

4. Clinical Evidence Strategy

This is the heart of the CDP. It should describe:

The number and type of clinical studies planned — feasibility, FIH, pivotal
Primary endpoints for each study and why those endpoints are clinically meaningful
The patient population and inclusion/exclusion criteria rationale
Sample size justification, even if preliminary
The statistical analysis approach
How data from each study feeds into the next and ultimately supports your target submission

For a first-in-human study, the primary focus is safety and initial feasibility. Your CDP should explain how the FIH study design addresses the specific risks identified in your preclinical program and how the resulting data will be structured to support the next study or a direct regulatory submission.

5. Risk-Benefit Framework

Describe the clinical risks associated with the device and how your study design mitigates them. Reference your risk management file and any relevant ISO 14971 analysis. FDA expects to see that your clinical endpoints and stopping rules connect to your risk assessment — not that they were developed in isolation.

For novel devices or high-risk indications, this section carries significant weight. A shallow risk-benefit analysis signals that the sponsor has not fully thought through the human subjects implications.

6. Regulatory Strategy Timeline

Lay out a realistic timeline from your current stage through your target submission. Include:

Pre-Sub or Pre-IDE meeting date, or planned date
IDE submission target, if applicable
FIH study start and completion targets
Pivotal study milestones, if applicable
Target submission date

Be honest about uncertainty. A timeline with appropriate ranges and identified dependencies is more credible than an optimistic straight line.

7. Geographic and Site Strategy

Specify where you plan to conduct the clinical work and why. This section matters more than many sponsors realize. FDA reviewers are familiar with the use of foreign clinical data under 21 CFR 812.28, and they will want to understand how your site selection and data collection practices ensure the data will be acceptable for your U.S. submission.

If any part of your clinical program will be conducted outside the United States, address the regulatory framework governing data acceptability directly. Studies conducted under ICH-GCP and ISO 14155, and structured per FDA 21 CFR 812.28, can support IDE and IND submissions. Sponsors who have run early feasibility and first-in-human studies in Latin America have successfully used that data in U.S. submissions when study design and data management standards were aligned from the start.

bioaccess® structures its FIH-12 program specifically to produce a submission-ready clinical evidence package aligned with the sponsor's intended FDA pathway, with ethics and regulatory approvals in Panama, El Salvador, Chile, and the Dominican Republic observed in 30 to 90 days.

8. Data Management and Monitoring Plan Summary

You do not need a full data management plan in the CDP, but you should describe your approach to data collection, electronic data capture, monitoring frequency, and how you will ensure data integrity. FDA is increasingly attentive to data quality, particularly for studies conducted at sites outside the United States.

Mention your quality standards: ICH-GCP compliance, audit trail requirements, and how adverse events will be captured and reported.

9. Post-Market Clinical Follow-Up (PMCF) Plan, If Applicable

For PMA and De Novo pathways, FDA often expects a PMCF plan even at the early development stage. If your device will require post-approval studies, include a preliminary description of that commitment. It signals that you are thinking about the full evidence lifecycle — not just the approval milestone.

Common Gaps That Slow Down FDA Meetings

Endpoint mismatch. The most frequent problem is proposing FIH endpoints that do not connect to the primary endpoint in the pivotal study. If your pivotal trial will measure a specific clinical outcome, your FIH study should at minimum collect data that informs your ability to measure that outcome in a larger population.

Undefined patient population. Vague inclusion criteria at the CDP stage signal that the sponsor has not yet characterized the target population carefully enough to design a study. FDA will ask.

No statistical rationale. Even for a small FIH study, you need to explain why the proposed sample size is sufficient to characterize safety and generate the preliminary efficacy signal you need. "N=10 because that is what we can afford" is not a rationale.

Regulatory pathway ambiguity. If you are genuinely uncertain whether your device is a 510(k) or a De Novo, say so explicitly and frame it as a Pre-Sub agenda item. Presenting a plan that assumes a 510(k) pathway when the device is likely De Novo or PMA wastes everyone's time.

Missing foreign data acceptability discussion. If any part of your clinical program will be conducted outside the United States, address 21 CFR 812.28 directly. Sponsors who skip this section frequently receive FDA feedback requesting clarification before the meeting can move forward productively.

Structuring the CDP for a Pre-Sub Meeting

FDA's Pre-Sub program is designed to give sponsors early feedback on proposed study designs and regulatory strategies. To get the most from the meeting, structure your CDP so that each section maps to a specific question you are bringing to FDA.

Format your Pre-Sub request with numbered questions, each referencing the relevant CDP section. For example:

"Section 4 describes our proposed FIH study endpoints. Question 1: Does FDA agree that [specific endpoint] is an acceptable primary safety endpoint for this study?"
"Section 7 describes our plan to conduct the FIH study in Panama under 21 CFR 812.28. Question 2: Does FDA have concerns about the acceptability of data collected under this framework for the subsequent IDE submission?"

This structure makes the meeting productive. Reviewers can prepare specific responses rather than reacting to a general document.

Before You Write the CDP: Align Your Regulatory Strategy First

The CDP is only as strong as the regulatory strategy behind it. Before drafting, you need clarity on three things: your intended submission type, your primary endpoint, and your patient population. If any of those are unresolved, the CDP will reflect that uncertainty — and the FDA meeting will spend time on foundational questions rather than specific feedback.

If those questions are still open, working through a structured regulatory strategy exercise before drafting is worth the time. For sponsors considering a LatAm FIH execution strategy, the FIH Launch Planner at bioaccessla.com generates a preliminary country route, timeline range, and evidence package estimate based on six questions — a useful starting point for grounding the geographic and timeline sections of the CDP.

FAQs

What is a clinical development plan and who needs one?
A clinical development plan is a strategic document describing the full evidence generation strategy for a medical device or drug from early development through regulatory submission. Any sponsor preparing for a first FDA meeting — whether a Pre-Sub, Pre-IDE, or Type B interaction — should have one before that meeting.

How is a clinical development plan different from a clinical trial protocol?
A protocol is the operational document for a single study: it specifies the design, procedures, and endpoints in detail. A CDP is the overarching strategy document that explains how multiple studies — including the protocol-governed ones — fit together to build the evidence package required for regulatory approval.

Does FDA require a clinical development plan before a Pre-Sub meeting?
FDA does not require a formal CDP as a named document, but the Pre-Sub meeting request must include a description of your device, your proposed study design, and specific questions for FDA. A well-structured CDP is the most efficient way to satisfy that requirement and get substantive feedback.

Can data from a first-in-human study conducted in Latin America be used in a U.S. FDA submission?
Yes. Foreign clinical data is acceptable to FDA under 21 CFR 812.28 when the study is conducted in accordance with ICH-GCP and the data is collected in a manner consistent with FDA requirements. Study design, endpoint selection, and data management standards must be aligned with the sponsor's intended U.S. pathway from the start.

What endpoints should a first-in-human study include?
For a medical device FIH study, the primary focus is safety: adverse events, device-related complications, and serious adverse device effects. Secondary endpoints typically include early feasibility signals relevant to the pivotal study's primary endpoint. The specific endpoints depend on the device type, indication, and intended regulatory pathway.

How long should a clinical development plan be?
There is no required length. A CDP for an early-stage device program might run 10 to 20 pages. The goal is completeness and clarity, not volume — every section should answer a specific question a regulatory reviewer or investor would ask.

When should I update the clinical development plan?
Update the CDP after any significant regulatory interaction, after completing a study that generates new data, and whenever your regulatory pathway or target submission type changes. It should reflect your current strategy, not the one you had at the start of the program.

Conclusion

A clinical development plan is not a formality. It is the document that demonstrates you have thought through the full arc of your evidence strategy before asking FDA to weigh in on any part of it. Build it section by section, connect each element to your target submission, and structure it so your Pre-Sub questions map directly to the sections where you need the agency's input. That preparation is what turns a first FDA meeting from a general orientation into a productive regulatory strategy session.

If your clinical development plan includes a LatAm FIH execution component, visit bioaccessla.com to learn how the FIH-12 program structures that work for FDA-bridgeable outcomes.