De Novo Clinical Evidence Calculator: estimate evidence burden before protocol decisions lock your timeline

Clinical evidence planning is where De Novo programs either become disciplined or expensive. This calculator helps you estimate evidence burden using device risk, endpoint complexity, claim breadth, and existing evidence strength. It is designed for decision quality: you can compare scenarios quickly and align stakeholders before committing to full protocol execution.

Why evidence scope planning should happen before tactical writing

Many teams spend weeks polishing narrative sections before confirming that the evidence architecture supports the intended claims. This reverses the logical order of decision-making. In De Novo programs, claims and evidence should be co-designed early. When this does not happen, teams face late-stage tradeoffs between claim reduction and added evidence generation, both of which can materially affect cost and timeline.

Evidence scope planning is not only a clinical function. It requires coordination among regulatory strategy, risk management, quality systems, biostatistics, engineering, and sometimes usability and human factors specialists. The calculator on this page gives a simple index so these groups can align quickly and escalate disagreements while options are still open.

How the scoring model works

The model combines six practical inputs. Risk profile and novelty capture uncertainty around safety/effectiveness interpretation. Claim breadth captures how much market-facing ambition is embedded in the first submission. Existing evidence strength captures how much credible support is already available. Endpoint complexity captures execution and interpretation difficulty. Baseline sample target gives you a practical anchor so scenario outputs map to operational planning.

The score does not dictate one study design. Instead, it signals the likely level of evidence burden and the degree of planning discipline needed. Lower scores suggest you may proceed with focused evidence plans and tighter scope control. Higher scores suggest deeper protocol development, pre-defined sensitivity analyses, and stronger governance around claim language.

Evidence burden tiers and what they imply

Tier 1 (focused burden)

Typical when novelty and risk are lower and existing evidence is stronger. Teams in this tier still need strong traceability but can often operate with narrower endpoint sets and fewer contingencies.

Tier 2 (managed burden)

Common for moderate novelty with mixed endpoint complexity. Requires robust protocol governance, explicit missing-data handling, and careful endpoint rationale to avoid interpretability issues during review.

Tier 3 (high burden)

Typical when novelty is high, claims are broad, and current evidence base is limited. Expect heavier scenario analysis, stronger statistical planning, and more conservative timeline and budget assumptions.

How to improve evidence efficiency without weakening submission quality

• Narrow first-cycle claims: ambitious claims can be sequenced across lifecycle milestones rather than forced into one cycle.
• Choose objective endpoints where possible: improves interpretability and reduces debate over signal quality.
• Pre-define analysis logic: reduces ad hoc decisions that create inconsistency and delay.
• Align risk controls and evidence collection: ensure test outputs and clinical outputs tell a consistent safety story.
• Protect data quality operations: clean data management often has higher ROI than late statistical rescue efforts.

Integrating this output into program governance

Use the calculator output in monthly cross-functional reviews. Track score movement over time as claims evolve and evidence accumulates. If score increases due to scope expansion, update both budget and timeline models immediately. Evidence decisions should never be isolated from program finance and launch planning.

A practical operating pattern is to maintain one decision sheet with three linked views: evidence burden score, budget scenario, and timeline range. When one view changes, all three are reviewed. This prevents local optimization where one team improves its own metric while creating risk elsewhere.

Choosing external support based on evidence tier

Tier 1 programs may only need targeted statistical or medical writing support. Tier 2 programs often need stronger integration support across protocol, regulatory narrative, and quality documentation. Tier 3 programs usually benefit from experienced strategy-led support with demonstrated ability to coordinate multi-disciplinary evidence systems.

Use this page with the provider benchmark workflow: Compare +50 FDA De Novo providers. Ask finalists how they would reduce your evidence burden score without introducing uncontrolled risk.

Frequent failure modes in evidence planning

One failure mode is endpoint inflation: adding endpoints to satisfy internal stakeholders without clear regulatory value. Another is ambiguous claim language that forces evidence overproduction because interpretation boundaries are unclear. A third is delayed protocol governance where major design choices are revisited late. All three failure modes increase complexity and reduce decision speed.

Avoid these issues by defining decision rights early and requiring explicit rationale for every major scope change. Document why each endpoint exists, how it maps to claims, and what decision question it resolves.

FAQ

Can this tool replace formal statistical planning?

No. It is a strategic scoping tool used before full statistical and protocol planning. Formal design work still requires qualified clinical and statistical leadership.

Should we always increase sample size when uncertainty is high?

Not automatically. Sometimes narrower claims, clearer endpoints, and better operational control are more efficient than simple sample expansion.

How often should score assumptions be reviewed?

At each major claim or protocol checkpoint, and any time significant new evidence emerges or core assumptions change.

What if internal teams disagree on risk/novelty scoring?

Capture both views and run scenarios. Disagreement is useful because it reveals where governance and evidence rationale need clarification.

Practical next actions after running the calculator

1. Run a narrow-claim scenario and a broad-claim scenario with identical other assumptions.
2. Compare burden score impact and estimate incremental timeline and budget impact.
3. Decide which claims are first-cycle essential versus deferrable.
4. Lock protocol governance checkpoints and evidence traceability standards.
5. Benchmark support options for your burden tier.

This process improves decision transparency and lowers late-stage surprise risk. Even when teams choose ambitious paths, they do so with explicit tradeoffs rather than implicit optimism.

Evidence architecture design pattern that scales

As programs grow, teams need an evidence architecture that can absorb new data without collapsing into version-control chaos. The most effective pattern is a layered model: claims layer, endpoint layer, data-source layer, and interpretation layer. Each layer has explicit owners and review gates. Claims owners cannot change wording without endpoint-owner signoff; endpoint owners cannot revise definitions without data-management and statistical signoff; interpretation owners cannot finalize conclusions without traceability checks. This layered discipline reduces contradiction risk and improves response readiness when clarifications arrive.

Teams often skip layered governance because it appears heavy. In reality, the overhead is modest compared with late-cycle rework. A lightweight implementation can be done with a single structured matrix that links each claim to endpoints, data artifacts, analysis outputs, and approved narrative snippets. This matrix becomes the reference point for all drafting, review, and response work.

When external providers are involved, require them to operate within your architecture instead of introducing proprietary tracking formats. This keeps intellectual control inside your organization and simplifies transition if vendors change.

Quality controls that improve evidence confidence

Three quality controls deliver outsized value. First, run endpoint definition reviews with both clinical and regulatory participants; this catches interpretability issues early. Second, run periodic data integrity checks that focus on missingness patterns, protocol deviations, and endpoint derivation logic. Third, run narrative traceability checks where a reviewer verifies that every high-impact statement maps to a specific evidence artifact.

These controls are most effective when scheduled as recurring activities rather than one-time audits. Recurring controls create early warning signals and reduce the chance that latent issues appear only at submission-finalization time. They also produce a reusable quality record that strengthens organizational learning for future submissions.

Balancing speed and rigor in evidence planning

Speed and rigor are not opposites if scope is managed intentionally. Teams lose speed when they pursue broad claims with weak evidence discipline. Teams lose rigor when they compress review cycles without clear ownership and objective acceptance criteria. The right balance is achieved by narrowing first-cycle ambition to high-confidence value claims, then planning expansion as evidence matures.

Use this calculator to make that balance explicit. If burden score is high, either increase resources and governance strength or reduce first-cycle complexity. Attempting to keep high complexity with low governance maturity usually leads to schedule drift and credibility loss. Explicit tradeoff decisions preserve trust across functions and with leadership.

For organizations under intense market pressure, define non-negotiable quality thresholds before acceleration decisions. This prevents teams from quietly trading evidence quality for calendar optics. A stable threshold framework supports faster execution because teams know where flexibility exists and where it does not.

Citations

• FDA: De Novo Classification Request
• 21 CFR Part 860
• FDA: Q-Submission Program Guidance
• FDA: Benefit-Risk Framework Guidance