FDA Breakthrough Device Eligibility Calculator

This calculator helps teams convert a broad eligibility discussion into a structured score. It is not legal advice and it does not replace formal FDA interaction. Its purpose is to improve internal decision quality by forcing explicit assumptions around unmet need, alternatives, expected clinical impact, and evidence readiness. Teams frequently miss timeline targets because they discuss these dimensions informally. A simple scoring frame reduces that risk.

How To Use This Calculator Correctly

Most teams over-index on one persuasive element, usually clinical burden or a compelling technology narrative. FDA review logic, however, is multidimensional. You need enough strength across several dimensions to support a credible designation argument. A high score in one domain cannot fully compensate for weak evidence planning or weak differentiation from existing alternatives. The calculator enforces this balance by averaging six domains and reporting a readiness band.

Start by filling scores independently across regulatory, clinical, and product leaders. Then compare results. Large score variance is a useful warning signal. In practice, high variance means your team does not share the same assumptions about comparator care, target population, endpoint plausibility, or operational risk. Before engaging external providers, resolve those differences and document why the final score changed.

Interpretation Framework For Each Domain

1) Serious Condition Burden

This domain measures whether the addressed condition is objectively serious for the proposed population. Strong scoring requires specific burden framing: morbidity, mortality, irreversible progression, major quality-of-life impact, or repeated care dependence. Vague language such as "important" or "high-impact" is not enough. High-quality submissions usually tie burden to concrete consequences for patients and healthcare systems.

To score this domain with rigor, build a concise evidence table with prevalence/incidence where relevant, disease progression characteristics, and measurable outcome consequences. The objective is not to produce a publication-grade review; it is to prevent weak narrative drift during drafting. If your burden argument changes frequently based on audience, score this domain lower until it stabilizes.

2) Unmet Need Strength

Unmet need means current options are insufficient for your target context, not merely inconvenient. Teams often score this too high by focusing on feature-level differences rather than outcome-level gaps. To justify a strong score, define what current standards fail to deliver and why those limitations matter for the selected clinical scenario. Strong arguments are specific about who is underserved and where current management is predictably inadequate.

A practical method is to map unmet need by subgroup. If your rationale only holds for a narrow subgroup, keep the claim narrow and score honestly. Overbroad claims create downstream friction during evidence planning and increase revision cycles.

3) Alternatives Gap

This score reflects how clearly your device is differentiated from available alternatives. The gap can be efficacy, safety, speed to intervention, accessibility, continuity of care, workflow burden, or other clinically meaningful dimensions. The key is that the gap must be decision-relevant, not cosmetic. Claims like "more modern" or "AI-enabled" do not, by themselves, establish meaningful differentiation.

Build an alternatives matrix with columns for target population fit, known constraints, and evidence confidence. When teams use a matrix, they discover where assumptions are unsupported and can re-scope early. If your matrix has many "unknown" cells, lower the score and plan data generation.

4) Expected Benefit Magnitude

This domain asks how large the expected benefit is relative to current practice. Strong scoring requires measurable, patient-relevant outcomes, not only surrogate process improvements. Process gains can matter, but they should be connected to outcomes that stakeholders care about. If the expected benefit depends on ideal implementation conditions, discount your score to reflect real-world execution risk.

Benefit claims are stronger when you pre-define plausibility thresholds. For example, define what outcome change would be considered clinically meaningful, what uncertainty bounds are acceptable, and what data source will test the claim. Teams that set thresholds early avoid retrofitting narratives later.

5) Evidence Maturity

Evidence maturity evaluates whether your current data package can support designation dialogue. Early data can still be useful, but maturity is about coherence: are endpoints aligned with claims, are data sources reliable, and are limitations openly documented. Teams often inflate this score when they count volume over quality. Ten weak signals are usually less persuasive than one strong, well-contextualized signal.

Score this dimension conservatively if your data dictionary, cohort definitions, or endpoint adjudication are still changing. Evidence instability can be managed, but it should be priced into timeline and budget decisions from the beginning.

6) Risk Mitigation Credibility

Review confidence improves when potential risks are identified with clear mitigations and monitoring plans. A high score requires practical controls, ownership assignment, and measurable trigger thresholds for escalation. Generic statements such as "risk will be monitored" should not score above mid-range. This domain is especially important when your solution includes software updates, model drift concerns, or cybersecurity dependencies.

Include post-market preparedness assumptions even at early stages. Breakthrough planning is not only about winning designation; it is about sustaining a credible path through subsequent interactions and submission phases.

Why Teams Use "Eligibility Scores" In Provider Selection

When you evaluate support partners, this scorecard prevents proposal inflation. Ask each provider to review the same inputs and explain where they disagree with your scoring. High-quality providers can articulate score changes with evidence and concrete reasoning. Low-quality providers often default to high optimism without transparent tradeoffs. Structured disagreement is useful; unexplained optimism is expensive.

You should also test whether providers can translate score gaps into workplans. If evidence maturity is low, do they propose specific data milestones? If alternatives gap is unclear, do they recommend targeted landscape analysis? If risk mitigation is weak, do they define cross-functional governance? The best partner is the one that turns score deficits into explicit action paths.

Common Failure Modes This Tool Helps Prevent

How This Fits Into An End-To-End Regulatory Plan

Eligibility scoring should connect directly to timeline and budget planning. That is why this page links to related tools for interaction timeline and program budget estimation. In mature teams, the three outputs are reviewed together in one decision session: eligibility confidence, interaction sequencing, and cost exposure. This integrated view avoids the common error of approving a strategy without resourcing the work needed to execute it.

Treat the output as a living artifact. Re-score after major events: preclinical package completion, external clinical input, new comparator information, or meaningful changes to intended use. Consistent updates create traceability and improve communication with internal leadership.

Related Pages

Operational Playbook: From Score To Action

A score is only valuable when it changes behavior. After you run the calculator, create a one-page action sheet with three columns: current score, root cause of weakness, and next milestone to improve that domain. For example, if alternatives gap is weak, your next milestone might be a structured alternatives analysis with explicit subgroup logic. If risk mitigation is weak, your milestone could be a cross-functional risk workshop with named owners and trigger thresholds.

The playbook should include dates, accountable owners, and review cadence. Teams that keep this lightweight artifact current are far more likely to preserve strategic coherence under pressure. Without an action sheet, score outputs can quickly become static presentation material with no execution value. With an action sheet, the score becomes a management instrument that links planning to operational progress.

You can also use score deltas as governance signals. If one domain drops significantly after new information, escalate immediately and decide whether to narrow claims, generate additional data, or adjust timeline and budget expectations. Silent score erosion is one of the most common early warning signs of downstream rework. Visible score governance keeps leadership informed before problems compound.

Internal Review Questions Before External Submission Work

• Can each major claim be traced to concrete evidence with known limitations documented?
• Is your unmet-need claim stable across clinical, commercial, and regulatory audiences?
• Have you distinguished compelling technology attributes from clinically meaningful benefit?
• Can your team explain why current alternatives are insufficient for your precise target context?
• Do you have named owners for risk controls, monitoring thresholds, and escalation decisions?
• If external feedback challenges assumptions, do you have a predefined adaptation workflow?

These questions are intentionally practical. They convert broad strategic confidence into observable execution readiness. If answers are partial, score conservatively and prioritize closure work. Conservative scoring early is cheaper than aggressive scoring followed by major correction.

Quality Markers In High-Performing Teams

High-performing teams exhibit consistent patterns regardless of device category. They separate hypothesis from evidence, keep explicit assumption logs, and manage claim scope with discipline. They avoid rewriting strategy in each meeting by maintaining one source of truth for decision rationale. They also run short weekly reviews that focus on unresolved assumptions instead of broad status reporting.

Another quality marker is \"decision memory.\" When teams document why choices were made, future contributors can understand constraints quickly. This reduces repeated debates and preserves momentum during personnel or vendor changes. Decision memory is especially important in long-running programs where context loss can create expensive backtracking.

Finally, strong teams calibrate confidence honestly. They do not treat uncertainty as weakness; they treat it as a management input. This mindset produces better planning and more defensible communication with leadership and external stakeholders.

Frequently Asked Questions

Is a high calculator score a guarantee of designation success?

No. The calculator is a directional planning aid, not a predictor of regulatory outcome. It helps teams improve argument quality and execution readiness. External review outcomes depend on broader contextual factors and final submission quality.

How often should we re-score?

Re-score after major evidence updates, claim scope changes, meaningful feedback events, or ownership transitions. Many teams re-score monthly during active planning and immediately after significant decision points.

Can we use this for provider performance management?

Yes. Track score movement over time and map movement to delivered outputs. If provider work does not improve identified weak domains, you have objective grounds for scope correction.

References

[1] FDA, Breakthrough Devices Program overview: FDA Breakthrough Program.
[2] FDA, Q-Submission Program: Q-Sub Guidance Resources.
[3] 21st Century Cures Act (Public Law 114-255): Statutory Framework.