FDA De Novo Readiness Calculator: Measure Submission Preparedness Before You Spend

This calculator gives your team a weighted readiness score for De Novo planning, based on classification rationale quality, evidence design, quality-system maturity, and operational execution. It is designed for practical pre-submission decision making.

How the Readiness Score Works

The scoring model intentionally weights classification and evidence quality above administrative readiness because those two domains usually drive the majority of review-cycle risk in De Novo programs. Teams often underestimate the cost of unclear classification framing and overestimate the value of producing many reports that are not tightly tied to reviewer decision points. In this model, classification maturity and evidence maturity each represent 30% of total score. Quality-system maturity contributes 20%, and operational execution contributes 20%. That blend reflects what most teams experience in real programs: decisions fail less because a document is missing and more because the rationale and proof structure do not align.

A low score is not a failure; it is an early warning that prevents expensive misallocation. If you discover that your evidence strategy scores low while operational readiness scores high, that means you can execute quickly but may execute the wrong work. If quality scores are weak while evidence planning is strong, you may face preventable records or traceability issues once submission package assembly begins. Using a weighted model forces transparent tradeoffs. Your team can decide where to invest first and why.

Score Bands and What to Do Next

Deep Dive: Classification Readiness

Classification readiness is about the quality of your reasoning, not just whether your team prefers a pathway. For De Novo planning, you need a coherent explanation of why existing classifications are insufficient and why your proposed controls can support safety and effectiveness for the intended use. Strong teams do not stop at a single narrative paragraph. They document alternatives considered, why each was rejected, and what evidence implications follow from the chosen approach. This structure protects your program when new information arrives.

Practical checklist: define intended use sentence-level language, identify population and use environment boundaries, map primary clinical or performance risk vectors, and maintain a assumptions register with owner/date fields. If your classification rationale changes, downstream evidence logic should update automatically. Teams that cannot trace this dependency typically burn time reworking tests late in the cycle.

Deep Dive: Evidence Readiness

Evidence readiness is where most budget variance begins. Many teams create long testing wish lists but cannot explain which tests answer which reviewer decision questions. Better teams build an evidence matrix that ties each key claim to a risk context, endpoint, acceptance criterion, and reporting artifact. They also pre-define what negative outcomes would trigger design changes versus narrative justification updates. This makes evidence work resilient to surprises.

In software-heavy programs, evidence planning should integrate cybersecurity, interoperability, and lifecycle controls early rather than as add-ons. In hardware or patient-contacting products, biocompatibility rationale, sterilization or reprocessing strategy, and packaging/shelf-life logic must be scoped using intended use and contact profile assumptions. In all cases, the same principle applies: build a small set of decisive evidence threads, then expand only where risk or claim complexity demands it.

Deep Dive: Quality and Operations Readiness

De Novo programs stress quality systems differently than routine sustaining work. Even when your organization has ISO-centered procedures, readiness depends on whether those procedures are practical for the submission timeline you are targeting. If design changes happen rapidly, your document control and traceability workflows must keep pace. A mature quality setup means people can find decisions quickly, verify approved versions, and link CAPA or complaint learnings where relevant.

Operationally, readiness means more than owning a project plan. It means your team has clear decision rights, escalation clocks, and weekly review rituals. Teams with strong operations use a small set of dashboards: assumptions aging, unresolved cross-functional questions, critical path risk, and evidence status by ownership. This sounds simple, but execution quality in these routines is what separates predictable programs from chaotic ones.

How to Use This Calculator with Provider Selection

If you are evaluating external support, run this readiness model before and after each provider workshop. Ask each team to propose a 60-day plan to improve your current score and request concrete artifacts they would deliver. Then compare proposals against this question: does the plan improve your decision quality, or only increase document output? Providers should be able to raise readiness scores by changing how your team decides, not just by writing faster.

You can also use score deltas as procurement guardrails. For example, release milestone payments when specific readiness outcomes are reached: classification rationale approved with alternatives logged, evidence matrix reviewed cross-functionally, or quality traceability checks passing. This aligns commercial terms with program value.

Common Misreads and How to Avoid Them

• check_circle
  Misread: "We scored high, so submission is guaranteed." Fix: treat score as planning confidence, not review outcome prediction.
• check_circle
  Misread: "Low score means stop everything." Fix: prioritize top two drivers and run focused closure sprints.
• check_circle
  Misread: "Operations can compensate for unclear evidence logic." Fix: strengthen rationale first; speed amplifies both good and bad plans.
• check_circle
  Misread: "External experts will solve all gaps quickly." Fix: keep internal ownership of assumptions and final decisions.

Frequently Asked Questions

Is this calculator an FDA decision tool?

No. It is an internal planning tool to improve De Novo program quality. FDA does not use this score.

Can a startup use this model with limited staff?

Yes. Reduce process overhead but keep the same logic: explicit assumptions, weighted priorities, and clear ownership.

How often should we rescore?

At minimum monthly, and after any major strategic change such as updated intended use language, test redesign, or provider transition.

References

• FDA: De Novo Classification Request
• 21 CFR Part 860 Subpart D
• Q-Submission Program Guidance
• Content of Premarket Submissions for Device Software Functions
• FDA Cybersecurity in Medical Devices Q&A