Frekil Logo
RWE Strategy

FDA's Single-Pivotal-Trial Shift: What It Means for RWE Teams

NT

Nikhil Tiwari

·8 min read

The important FDA news is not the December data-access update. It is the agency's move toward a different approval architecture: one strong pivotal trial, supported by confirmatory evidence, as the default path for demonstrating effectiveness.

In February 2026, Martin Makary and Vinay Prasad published a New England Journal of Medicine article titled “One Pivotal Trial, the New Default Option for FDA Approval - Ending the Two-Trial Dogma.” The point was not that FDA no longer needs rigorous evidence. The point was that a single adequate and well-controlled investigation can support approval when the rest of the evidence package is strong enough to confirm the treatment effect. PubMed record

The new bottleneck is not whether a sponsor can run two trials by default. It is whether the entire evidence package around one pivotal trial is credible, fast, and auditable enough to carry the decision.

What changed

The legal pathway is not new. FDA's September 2023 draft guidance already explained how one adequate and well-controlled clinical investigation, together with confirmatory evidence, can satisfy the substantial evidence requirement for drugs and biologics. FDA also emphasized that the evidentiary standard itself had not changed since 1998. FDA confirmatory evidence guidance

What is new is the posture. FDA leadership is signaling that the single-pivotal-trial route should be a normal starting point, not an exception reserved for unusual programs. That is a meaningful shift for clinical development teams because it changes when the confirmatory evidence has to be planned. It cannot be treated as a late-stage appendix assembled after the pivotal readout.

The December thread is different. FDA did make several speed-oriented moves late in 2025, including National Priority Voucher awards and proactive engagement after strong Phase 3 results. But the single-pivotal-trial signal belongs to the February 2026 evidence discussion, not to the December RWE guidance. The March 2026 Tec-Dara approval shows the same operating philosophy in action: FDA said the decision was issued 55 days after filing after a randomized Phase 3 trial showed large improvements, and that the same study provided confirmatory evidence for converting an existing accelerated approval to traditional approval. FDA Tec-Dara approval

Confirmatory evidence becomes strategic

A one-trial strategy only works if the evidence around the trial is strong enough to reduce uncertainty. Confirmatory evidence can come from many sources: mechanistic data, animal data, clinical pharmacology, dose-response information, natural history studies, prior clinical experience, external controls, or real-world data. The specific mix depends on the disease, product, endpoint, magnitude of effect, and feasibility of additional randomized evidence.

That makes RWE more important, not less. If the pivotal trial is the central causal test, real-world evidence can help define the disease course, size the treatment-eligible population, justify endpoint relevance, build an external comparator where randomization is infeasible, characterize safety in broader patients, and support postmarket commitments. The question is no longer simply “can RWE replace an RCT?” It is “where does RWE make the total evidence package more persuasive?”

FDA's Rare Disease Evidence Principles make this explicit for very small rare-disease populations. For eligible drugs, FDA says substantial evidence may generally be established through one adequate and well-controlled study, which may be single-arm, plus robust confirmatory evidence. The agency also says it will consider confirmatory evidence from external controls or natural history studies. FDA Rare Disease Evidence Principles

What this does not mean

This is not permission to run a small, noisy trial and fill the gaps with convenient observational data. FDA's standard still depends on substantial evidence of effectiveness. One pivotal trial has to be adequate and well controlled. Confirmatory evidence has to be relevant, independent enough to matter, and strong enough to support the treatment effect rather than merely decorate it.

It also does not mean every program gets the same evidentiary bargain. A therapy for a large common disease with modest expected benefit may still need a conventional randomized evidence base. A targeted treatment for an ultra-rare genetic condition may require a very different package. The point of the FDA shift is flexibility inside the statutory standard, not a lower standard.

The FDA's February 2026 plausible-mechanism draft guidance points in the same direction. It focuses on individualized therapies for genetic conditions where randomized controlled trials are often not feasible, and it asks sponsors to connect clinical data, natural history, biological mechanism, target engagement, and manufacturing quality into a coherent approval case. FDA plausible mechanism announcement

The practical message is not “do less evidence.” It is “make the evidence architecture smarter, earlier, and easier to inspect.”

Why RWE teams should care now

Under a two-trial default, confirmatory evidence could be treated as supporting context. Under a one-pivotal-trial default, it becomes part of the development architecture. That changes the operating cadence for RWE, epidemiology, biostatistics, clinical development, regulatory, safety, and HEOR teams.

Before the pivotal trial starts, teams need to know which real-world datasets can support natural history, endpoint validation, site selection, eligibility criteria, comparator design, background event rates, and patient representativeness. During the trial, teams need to keep those assumptions current. After the readout, teams need to assemble a decision-ready package that shows exactly where the pivotal evidence is reinforced and where uncertainty remains.

That is hard to do with one-off spreadsheet work and bespoke consulting decks. It requires reusable cohort logic, auditable phenotype definitions, source-level data quality checks, transparent confounding plans, versioned analytic code, and outputs that can be reviewed by clinical and regulatory stakeholders without rebuilding the study from scratch.

The speed lesson

The single-pivotal-trial shift is part of a broader FDA posture around speed. But speed cuts both ways. Faster review only helps sponsors who can make their evidence legible quickly. It punishes teams that wait until the end of development to discover that their natural history data are incomplete, their external comparator is not fit for purpose, or their endpoint cannot be measured consistently in routine care.

FDA's April 2026 reminder about missing ClinicalTrials.gov results is a useful warning sign. The agency said more than 2,200 companies and researchers appeared not to have submitted required trial results information, creating gaps that distort the public evidence base. That is the inverse of the future FDA is signaling: more transparency, faster review, and evidence packages that can be inspected earlier. FDA ClinicalTrials.gov results reminder

When the review clock compresses, evidence operations become strategy. The team that can answer the next FDA question with traceable analysis has an advantage over the team that needs three months to find the data.

This is where real-world evidence infrastructure matters. The work is not just querying a claims database or producing a retrospective table. It is turning messy clinical reality into a governed evidence system: definitions, assumptions, data lineage, code, outputs, sensitivity analyses, and decision logs that all point back to the same question.

The old question was whether real-world evidence could ever be regulatory-grade. The new question is whether an evidence team can produce the right supporting evidence while the pivotal program is still being shaped, not after the decision has already arrived.

That is the strategy implication. If one pivotal trial plus confirmatory evidence becomes the expected starting point, RWE is not a side project. It is one of the ways development teams make one pivotal trial credible enough to stand on.